From owner-freebsd-stable@FreeBSD.ORG Sun Sep 21 00:48: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE23BAB5 for ; Sun, 21 Sep 2014 00:48:06 +0000 (UTC) Received: from frv197.fwdcdn.com (frv197.fwdcdn.com [212.42.77.197]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE89FF0D for ; Sun, 21 Sep 2014 00:48:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-Id:To:Subject:From:Date; bh=cRoHwayg80oSBAmlEEjXND/ydQLdHA6Pajh8HMWjeCg=; b=TQ3MvoMnoZU5Xnf3m8LByTZj3HTg+A+SDA5zvjLRL9KCzPeR6YMcaRh9po++8MHvDOaKZMCFFXrH03B5MnViXwciCieVEA3+GJftK18IMPvUGlTzoXxmTqBwmew0C0wtn9g6KbaWieZuscvkpSssPnPGXna2gFsW8TpzNVXcpuM=; Received: from [10.10.10.35] (helo=frv35.fwdcdn.com) by frv197.fwdcdn.com with smtp ID 1XVVJd-00050R-Mp for freebsd-stable@freebsd.org; Sun, 21 Sep 2014 03:47:49 +0300 Date: Sun, 21 Sep 2014 03:47:48 +0300 From: Vladislav Prodan Subject: Re: FreeBSD 10 network performance problems To: "freebsd-stable@freebsd.org" X-Mailer: mail.ukr.net 5.0 Message-Id: <1411259605.674669006.339g4pd4@frv35.fwdcdn.com> In-Reply-To: References: MIME-Version: 1.0 Received: from universite@ukr.net by frv35.fwdcdn.com; Sun, 21 Sep 2014 03:47:49 +0300 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary Content-Disposition: inline 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, 21 Sep 2014 00:48:07 -0000 --- Original message --- From: "Rumen Telbizov" Date: 20 September 2014, 19:12:17 > Hello everyone, > > I am in the process of upgrading our main PF firewalls from 9.2-RC4 to > 10.1-BETA1 (r271684) and as part of the process I have been testing the > forwarding capability of FreeBSD 10 (pf firewall disabled) to have a > base-line and find any bottlenecks on a 10GbE network. > Please show the output of these commands: pciconf -lv | grep -A 4 ix\[0-9\] netstat -m ngctl list | wc -l sysctl -a | egrep 'net.(inet.(tcp|udp)|graph|isr)' -- Vladislav V. Prodan System & Network Administrator support.od.ua From owner-freebsd-stable@FreeBSD.ORG Sun Sep 21 17:07:01 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 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3F8E9C6B; Sun, 21 Sep 2014 17:07:00 +0000 (UTC) Date: Sun, 21 Sep 2014 13:06:56 -0400 From: Glen Barber To: freebsd-stable@FreeBSD.org Subject: FreeBSD 10.1-BETA2 Now Available Message-ID: <20140921170656.GA87551@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, 21 Sep 2014 17:07:01 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The second 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. 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-BETA1 and 10.1-BETA2 include: o UEFI-capable memory stick images and CDROM/DVDROM images are now build by default for the 10.1-RELEASE cycle. o The gssapi_krb5 library is now included in the gssapi(3) build. o The default motd(5) text has been changed to clarify the included information and including references to additional resources. o A potential crash in ctld(8) has been fixed when a getaddrinfo(3) call fails. o Fix Denial of Service in TCP packet processing. [SA-14:19.tcp] o Support for Promise TX8660 8-port 3Gbps HBA has been added. o A crash in clang(1) triggered by debuginfo has been fixed. o The kern.features sysctl(8) will now report if SCTP is available in the running kernel. o Parsing IPv6 nameserver lines in unbound(8) has been fixed. o A crash in pam(3) has been fixed if neither PAM_RHOST or PAM_TTY are set. o Several bug fixes and improvements to the vt(4) driver have been merged from FreeBSD-Current. o The bsdinstall(8) screen prompting if the user would like to use a chroot(8) shell within the newly-installed system for further configuration now defaults to 'No.' o Several optimizations to the math(3) library have been merged, including new implementations for C99 functions expl(), coshl(), sinhl(), tanhl(), erfl() and erfcl(). Pre-installed virtual machine images for 10.1-BETA2 are also available for amd64 and i386 architectures. The images are located here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/10.1-BETA2/ 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 add /dist/packages/freebsd:10:*:*/All/pkg-*.txz 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 the Subversion, 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-BETA2 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-BETA2 amd64 GENERIC: SHA256 (FreeBSD-10.1-BETA2-amd64-bootonly.iso) = 7f5a12b9b7884663d6b7b9afe16bffc92d701ee05ada3835b18a2ef6d3b72879 SHA256 (FreeBSD-10.1-BETA2-amd64-bootonly.iso.xz) = 68b039c3dd2c826b2128fa74b0bfd77b40f5783db636a7aacc03daaed461f9fb SHA256 (FreeBSD-10.1-BETA2-amd64-disc1.iso) = ac8505cfd22f1ad1dcc34b959498c335f60e33cdddaaea9a7bb67c82dac41bee SHA256 (FreeBSD-10.1-BETA2-amd64-disc1.iso.xz) = 8fdaf1759aee6090e842474928b5a82c8e67fa8652c268f9222d8c256fd5ab77 SHA256 (FreeBSD-10.1-BETA2-amd64-dvd1.iso) = 9c2b8a5dfddf906e28f2b7d43e586d87b89dd98c43101ecc8c0ebadf0d07bb7e SHA256 (FreeBSD-10.1-BETA2-amd64-dvd1.iso.xz) = 371ca4996018180df9c39db43ae3ea22dbb97523738db294fdb97e2c842caca5 SHA256 (FreeBSD-10.1-BETA2-amd64-memstick.img) = 50e796968c314b83a3d7cab285471a0c833909ce4ec52fd8bb8f180af896f1f4 SHA256 (FreeBSD-10.1-BETA2-amd64-memstick.img.xz) = 4899999b2cf6744da3c139ab66b1000c258801d193d6bc625f87a666d5c42892 SHA256 (FreeBSD-10.1-BETA2-amd64-mini-memstick.img) = 4f1a6bb4478e9cfd618093e633ef3774a521c64a374dfd41da44c69ed5a1504a SHA256 (FreeBSD-10.1-BETA2-amd64-mini-memstick.img.xz) = e4bdc44d3e4c6e375c895ad9b1a3b57b20f0d02fc5d325d392fb196c5275a232 SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-bootonly.iso) = 7c192a065b3e8c3e80641ae93ac0a8bc494ca7aacdbef40f07b48dd58a6ecf10 SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-bootonly.iso.xz) = 04aec14179bd295148ce331609a1de2dd72bfa2536db1c8b463533700f574dad SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-disc1.iso) = 3b3cf97803aee98490c3d7836b1a4030fa092e93e456d88d14d465d3f4902d37 SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-disc1.iso.xz) = 13427eb41271f8e4d3df9d99c49c8f567aaf465c7830348d439422a35d48a138 SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-dvd1.iso) = 6d45e116fc6193a5f6a40fc5767b1924b70ad651b0b71add137045e13ab2318a SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-dvd1.iso.xz) = 471c6f4fcc09939f86c99f693bf1124a75e681a8134e7e30457e273a59cd46be SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-memstick.img) = 1a6610ad213c2ea767992a636909ad9213d7592d61107938ca95ef2dd6d41d6f SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-memstick.img.xz) = 19f3c156ad194e4dfb11c381bb574b2841b10bafbe79c017faa32c7cc586e4c0 SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-mini-memstick.img) = 4fc441cf56a5ab73c88baabb5fd15b7859d5cd4dfdee1d682da01c337bdd8926 SHA256 (FreeBSD-10.1-BETA2-amd64-uefi-mini-memstick.img.xz) = bec330932511c6c2d492562f22747dad61b56737d90199b843e5bb0090105ea9 MD5 (FreeBSD-10.1-BETA2-amd64-bootonly.iso) = 88c006bf81740b4b92b42b9a26b2c5c5 MD5 (FreeBSD-10.1-BETA2-amd64-bootonly.iso.xz) = 756c71d4068b16a587471533ffa450d4 MD5 (FreeBSD-10.1-BETA2-amd64-disc1.iso) = 7a07133b804edb95d46fda1fc285bc2c MD5 (FreeBSD-10.1-BETA2-amd64-disc1.iso.xz) = de3df90ba76f9ec96ca0607cba55da72 MD5 (FreeBSD-10.1-BETA2-amd64-dvd1.iso) = 167ed4e254992f43627eab9ceeab9701 MD5 (FreeBSD-10.1-BETA2-amd64-dvd1.iso.xz) = 88865c5aab80c013825bb00fdf3288fe MD5 (FreeBSD-10.1-BETA2-amd64-memstick.img) = 4db5a2f5de71636e5c6051853657571f MD5 (FreeBSD-10.1-BETA2-amd64-memstick.img.xz) = 962229a3d73a61e564a3345f24f51ee0 MD5 (FreeBSD-10.1-BETA2-amd64-mini-memstick.img) = 6533f1829d8dc26277aacaa083af2caa MD5 (FreeBSD-10.1-BETA2-amd64-mini-memstick.img.xz) = 7cb93e82284fd81d21de372a1834799d MD5 (FreeBSD-10.1-BETA2-amd64-uefi-bootonly.iso) = 0b02d42c06348a2ba8682cb1843d106a MD5 (FreeBSD-10.1-BETA2-amd64-uefi-bootonly.iso.xz) = 40046d3afed5fd7de696bab2b9dfb287 MD5 (FreeBSD-10.1-BETA2-amd64-uefi-disc1.iso) = bab03112af3d54855eb87d2857e0b7ed MD5 (FreeBSD-10.1-BETA2-amd64-uefi-disc1.iso.xz) = af8ec822ec3c99fbb1773b3bcb229036 MD5 (FreeBSD-10.1-BETA2-amd64-uefi-dvd1.iso) = 4e34d8aa58196e7227f490f67c0a5444 MD5 (FreeBSD-10.1-BETA2-amd64-uefi-dvd1.iso.xz) = 8a2e1819d7118778bae15597e7248189 MD5 (FreeBSD-10.1-BETA2-amd64-uefi-memstick.img) = f3b27613f1fc242e04e72508430af08c MD5 (FreeBSD-10.1-BETA2-amd64-uefi-memstick.img.xz) = 5c0cbec31f2cea0425ac15a1449d8804 MD5 (FreeBSD-10.1-BETA2-amd64-uefi-mini-memstick.img) = 8f082039e9d302c7be612687ed6b607e MD5 (FreeBSD-10.1-BETA2-amd64-uefi-mini-memstick.img.xz) = e79f0fb14bf6528b852b3419098f28fc o 10.1-BETA2 i386 GENERIC: SHA256 (FreeBSD-10.1-BETA2-i386-bootonly.iso) = 05a4a929c46d2fb4102b886f4d7a40a4ceeb2bf267076783f7e30046f05636b5 SHA256 (FreeBSD-10.1-BETA2-i386-bootonly.iso.xz) = 64ef923dc35d9ebc6860be77dca9c75afda86fe377932cd35d1e94e7308c959f SHA256 (FreeBSD-10.1-BETA2-i386-disc1.iso) = ac2d175973a4cfb256ee0c2b3d7f27e6dd5d391928d1396a6f6d58d96c0f37eb SHA256 (FreeBSD-10.1-BETA2-i386-disc1.iso.xz) = dcab4d16a6c03d6ee7a44ec585d71106bb310e6258f3dd58a6cd8f4e600f7489 SHA256 (FreeBSD-10.1-BETA2-i386-dvd1.iso) = 02bd4f2f7360f83b1113dab2222e1779959a4e093710662039d4d9b3133a31a2 SHA256 (FreeBSD-10.1-BETA2-i386-dvd1.iso.xz) = 119ab19432df5fbcb9f7e9e0b064956502ab5cee76c9155231111774fa111daa SHA256 (FreeBSD-10.1-BETA2-i386-memstick.img) = 4e0d45519f0b95412834b89a6cc43ae6b32ee43727fac0a0c44c7e88bc28b43d SHA256 (FreeBSD-10.1-BETA2-i386-memstick.img.xz) = d4f5237cc8ab4478f8a0e00a437e46280c5bcec85ddcacb915b7b5b128518d98 SHA256 (FreeBSD-10.1-BETA2-i386-mini-memstick.img) = 67e57c246105bd24e3e23a7d0d4ed6089bc95ed4611bab6141df1f5c81d30bb8 SHA256 (FreeBSD-10.1-BETA2-i386-mini-memstick.img.xz) = bb45d1966cfdf511c765a02cb7514577fa6bba37236ea66d18e4a04df0af5597 MD5 (FreeBSD-10.1-BETA2-i386-bootonly.iso) = a4647d960c713047e6d6144df46e040b MD5 (FreeBSD-10.1-BETA2-i386-bootonly.iso.xz) = 50bc30271491c1f3414835e1ee9ca4f7 MD5 (FreeBSD-10.1-BETA2-i386-disc1.iso) = 4dbdfd191d006240dc65b41bee7e3900 MD5 (FreeBSD-10.1-BETA2-i386-disc1.iso.xz) = 9c74af0ad65e9066274a19377cf941ed MD5 (FreeBSD-10.1-BETA2-i386-dvd1.iso) = d7740af1476803cadbcbf72cec90393a MD5 (FreeBSD-10.1-BETA2-i386-dvd1.iso.xz) = 7d989f3a41f75b059f7f005370c794de MD5 (FreeBSD-10.1-BETA2-i386-memstick.img) = 37f53bc4db7592889c53830086dcb125 MD5 (FreeBSD-10.1-BETA2-i386-memstick.img.xz) = ada623c23e88101f81763062ea2f366a MD5 (FreeBSD-10.1-BETA2-i386-mini-memstick.img) = b758b33fb5ed320c5438957770eb54fc MD5 (FreeBSD-10.1-BETA2-i386-mini-memstick.img.xz) = 00c2d3496aa2bc85f791b39a893f67a4 o 10.1-BETA2 ia64 GENERIC: SHA256 (FreeBSD-10.1-BETA2-ia64-bootonly.iso) = 4ff94b27fce75bfa2e05d4f0082790921563083ca438dd0836d1bbd6eb4930ce SHA256 (FreeBSD-10.1-BETA2-ia64-bootonly.iso.xz) = 4cd02c9de2fbcf2c8514c1905d3bf24a6009fc44376e739490d28ffc6a64e473 SHA256 (FreeBSD-10.1-BETA2-ia64-disc1.iso) = 6544ac4d4ddd0b80507da3ef7c889a3dfc7393aeed1fc39d7ea2c14cbe2aaf44 SHA256 (FreeBSD-10.1-BETA2-ia64-disc1.iso.xz) = 38fccfbf92a510bac0c5337258b03738d28d58f9b5c357600b8efe2f5b5929ff SHA256 (FreeBSD-10.1-BETA2-ia64-memstick.img) = 0e55faaa08ed4d48282620337459dba7772325131a23134bfc02b8f153506aa0 SHA256 (FreeBSD-10.1-BETA2-ia64-memstick.img.xz) = 31a877dd4d16a817154e113e51c83c39ff45f1e75b0cf9429e0d0e77cc3d2310 SHA256 (FreeBSD-10.1-BETA2-ia64-mini-memstick.img) = f898d10dddbcc98b4fd6fcea6eadf969ed9f59a1396d6071cdc7326b4eda9315 SHA256 (FreeBSD-10.1-BETA2-ia64-mini-memstick.img.xz) = dcbdde4abba734b5698d4f75421e547a4778b48195067e7e0c39ff6388acdb69 MD5 (FreeBSD-10.1-BETA2-ia64-bootonly.iso) = 079385fea2e0fdc54179e764ed2c5b0b MD5 (FreeBSD-10.1-BETA2-ia64-bootonly.iso.xz) = 893434f4b92f91354a82353fc95db103 MD5 (FreeBSD-10.1-BETA2-ia64-disc1.iso) = c194b96de751cdd3d27ba7de4ac79e0c MD5 (FreeBSD-10.1-BETA2-ia64-disc1.iso.xz) = a5bf9973ad4c81dc1f8ec2a128caef9b MD5 (FreeBSD-10.1-BETA2-ia64-memstick.img) = 729c1f865dbed2eeabac40bbd0a3683f MD5 (FreeBSD-10.1-BETA2-ia64-memstick.img.xz) = 2e017e95311ad7ae1fe0b041b4c88e64 MD5 (FreeBSD-10.1-BETA2-ia64-mini-memstick.img) = f56dc5602775664167e9fcb064a3b0cc MD5 (FreeBSD-10.1-BETA2-ia64-mini-memstick.img.xz) = 0bb5deb04c1aac2cea69880400a5a87d o 10.1-BETA2 powerpc GENERIC: SHA256 (FreeBSD-10.1-BETA2-powerpc-bootonly.iso) = 95e8cd399a7c6fcffac0b93e28db597aa6471e3d0fc9bdc05cdfe2f50fe65350 SHA256 (FreeBSD-10.1-BETA2-powerpc-bootonly.iso.xz) = d3314d30b3c33c06916555cc37949b17056073b9823939b7084498dd4c109a73 SHA256 (FreeBSD-10.1-BETA2-powerpc-disc1.iso) = 8c46c3c13b4a4ba486f9de24cf6e9e22f73b341929ef30bfc7dbf1c39d43bf2d SHA256 (FreeBSD-10.1-BETA2-powerpc-disc1.iso.xz) = 8ce89799f4e4462fd5571d5a01fcd09ee7f61792feb6b4c320b65be18a21db0a SHA256 (FreeBSD-10.1-BETA2-powerpc-memstick.img) = b2c176be657381e8df1c5d35c2aa375040809e47d1049d6c1f7139ef36fb7cf7 SHA256 (FreeBSD-10.1-BETA2-powerpc-memstick.img.xz) = feff738bbd05de33b16c5f526ba87e728e07677948d248e8f0d7728ccc2d2733 SHA256 (FreeBSD-10.1-BETA2-powerpc-mini-memstick.img) = 556297c7005d2852d66123e0ab4cb44c3a6667ab04badc2dca16b26316d2e6a0 SHA256 (FreeBSD-10.1-BETA2-powerpc-mini-memstick.img.xz) = 52a2fd3e0095977db7b935a662dc94f3a047b3a55ff0f613d2e6526f973949cc MD5 (FreeBSD-10.1-BETA2-powerpc-bootonly.iso) = 562a9b893796404fabcd24673670337d MD5 (FreeBSD-10.1-BETA2-powerpc-bootonly.iso.xz) = 2b6c7c289a5c27690cdc79a7a67d5d71 MD5 (FreeBSD-10.1-BETA2-powerpc-disc1.iso) = bdd3f18f6cde1963c6f3f57195af9ae6 MD5 (FreeBSD-10.1-BETA2-powerpc-disc1.iso.xz) = d43593be3dffd6b9bf32ee7ec645da14 MD5 (FreeBSD-10.1-BETA2-powerpc-memstick.img) = 782fa735335218a2373326645e6477dc MD5 (FreeBSD-10.1-BETA2-powerpc-memstick.img.xz) = 1ced9447fbd4dd41f09c0296378c3da7 MD5 (FreeBSD-10.1-BETA2-powerpc-mini-memstick.img) = 0262074f76f517ae70407b41a4582807 MD5 (FreeBSD-10.1-BETA2-powerpc-mini-memstick.img.xz) = 778f6a215ff7ee7436620dd6dda61cd3 o 10.1-BETA2 powerpc64 GENERIC64: SHA256 (FreeBSD-10.1-BETA2-powerpc-powerpc64-bootonly.iso) = c9bf704ee1aa829a7ffc1dfc94d435dbe2f32402f6cd9d66098f38ea729b7e26 SHA256 (FreeBSD-10.1-BETA2-powerpc-powerpc64-bootonly.iso.xz) = f662a41cd198480cbfa5a06a9b7261d3b09a32178287b5d9a362b93e22a73be8 SHA256 (FreeBSD-10.1-BETA2-powerpc-powerpc64-disc1.iso) = f6696e71238d4d32081acba8f8b70f3420cfe1d67b8452a2c858abb070f43055 SHA256 (FreeBSD-10.1-BETA2-powerpc-powerpc64-disc1.iso.xz) = fe506cc6159cb69f920bce39381c72ea4399eb7fb1e61f9075e30956e996e7c1 SHA256 (FreeBSD-10.1-BETA2-powerpc-powerpc64-memstick.img) = 483216cb911d8fb3cdcadebfa2079cb318107cda90b0484db0c22ee451afcca4 SHA256 (FreeBSD-10.1-BETA2-powerpc-powerpc64-memstick.img.xz) = c3bde3b44a1c4c3deef4b52a963a7382b0a141d7732434d90e78bf4d81d88a19 SHA256 (FreeBSD-10.1-BETA2-powerpc-powerpc64-mini-memstick.img) = b8a1e6ecec4281b27e4670952e6936174adf228ec92cc01069eec603651c82c0 SHA256 (FreeBSD-10.1-BETA2-powerpc-powerpc64-mini-memstick.img.xz) = a24db10c176d67635db06186a76a5c8b42bbf30e1ea84c1549a152ab9746bb64 MD5 (FreeBSD-10.1-BETA2-powerpc-powerpc64-bootonly.iso) = 9c3d5a02da7c97991d8e1eeaa1422ea3 MD5 (FreeBSD-10.1-BETA2-powerpc-powerpc64-bootonly.iso.xz) = 828b3f92341fc23ef865277e079ba5cb MD5 (FreeBSD-10.1-BETA2-powerpc-powerpc64-disc1.iso) = c764bf6058e318362e741ed79e189d06 MD5 (FreeBSD-10.1-BETA2-powerpc-powerpc64-disc1.iso.xz) = bc707ceb622c6f4e064498059c892cd3 MD5 (FreeBSD-10.1-BETA2-powerpc-powerpc64-memstick.img) = 4b0892eff07611c18cb25859e912de07 MD5 (FreeBSD-10.1-BETA2-powerpc-powerpc64-memstick.img.xz) = 2d14461892b6511ffaae3c1a20f0cc19 MD5 (FreeBSD-10.1-BETA2-powerpc-powerpc64-mini-memstick.img) = b56e343831a0cc833ae91f0602573eb2 MD5 (FreeBSD-10.1-BETA2-powerpc-powerpc64-mini-memstick.img.xz) = b05fbaee144ff9737054e4c780f06b07 o 10.1-BETA2 sparc64 GENERIC: SHA256 (FreeBSD-10.1-BETA2-sparc64-bootonly.iso) = 703fea0ca9bdeae9759b97aefab193179550ee752749c1c86b07787d7d530160 SHA256 (FreeBSD-10.1-BETA2-sparc64-bootonly.iso.xz) = 40dd41cb0b8b0621636620938c20efc3d999efe5a8ac4648271f8db70f7afee5 SHA256 (FreeBSD-10.1-BETA2-sparc64-disc1.iso) = afefcb26c15ae93a26e5a57fa43780f55dc6b73d7b6ba20d7f8396e8ec69beea SHA256 (FreeBSD-10.1-BETA2-sparc64-disc1.iso.xz) = a4b45265c7714f8f551c825a2700e4c96c67cb7abf7185f03f3dbdddd9ec669f MD5 (FreeBSD-10.1-BETA2-sparc64-bootonly.iso) = 192a1578f5dd3804c7cb660f68af66c7 MD5 (FreeBSD-10.1-BETA2-sparc64-bootonly.iso.xz) = e411e2b30d8b2eda378c5a2ac6f0b19a MD5 (FreeBSD-10.1-BETA2-sparc64-disc1.iso) = 32160614a8b9e95f4b965a390e817869 MD5 (FreeBSD-10.1-BETA2-sparc64-disc1.iso.xz) = 93613926360dea52e25e06efa3aa29d5 o 10.1-BETA2 armv6 BEAGLEBONE: SHA256 (FreeBSD-10.1-BETA2-arm-armv6-BEAGLEBONE.img.bz2) = 1133475e1dbef4ed958c69e58f331da52d69de555a6ecef1c17fbcad38f80096 MD5 (FreeBSD-10.1-BETA2-arm-armv6-BEAGLEBONE.img.bz2) = 56f4af523f8b04cd6e77b0d4063e7b67 o 10.1-BETA2 armv6 RPI-B: SHA256 (FreeBSD-10.1-BETA2-arm-armv6-RPI-B.img.bz2) = 24e3badbff8a676c7a1a94d8b6770ddc59559a5279e57e239300448088ccd3bb MD5 (FreeBSD-10.1-BETA2-arm-armv6-RPI-B.img.bz2) = ace4e9a0a62bb57c878e3a8b693bc3f2 o 10.1-BETA2 armv6 PANDABOARD: SHA256 (FreeBSD-10.1-BETA2-arm-armv6-PANDABOARD.img.bz2) = eab5e0de21cf5c1ed174c79c31052c23174add6d97fe2a905c008be8b30a0696 MD5 (FreeBSD-10.1-BETA2-arm-armv6-PANDABOARD.img.bz2) = dd8eb1eead2f3aded312efb4b81a0250 o 10.1-BETA2 armv6 WANDBOARD-QUAD: SHA256 (FreeBSD-10.1-BETA2-arm-armv6-WANDBOARD-QUAD.img.bz2) = f9f32ca93e15f4799b7c1fc95bf1fc261155a5a047d4ffe57395f91f206cd951 MD5 (FreeBSD-10.1-BETA2-arm-armv6-WANDBOARD-QUAD.img.bz2) = 230d178b169bb6c3a72652cf5fee16bf o 10.1-BETA2 armv6 ZEDBOARD: SHA256 (FreeBSD-10.1-BETA2-arm-armv6-ZEDBOARD.img.bz2) = 01411cf8c0998536ce4cb28cad22459ed51a7674f06bb3407ca09908f24b3e7a MD5 (FreeBSD-10.1-BETA2-arm-armv6-ZEDBOARD.img.bz2) = 122c8d4c4afc829246b0f80927e1d39e == VM IMAGE CHECKSUMS == o 10.1-BETA2 amd64: SHA256 (FreeBSD-10.1-BETA2-amd64.qcow2.xz) = 6a3fd025549b758d16e6f140c5018292dbeeb208f1fce46d835bd75245694e3b SHA256 (FreeBSD-10.1-BETA2-amd64.raw.xz) = 969225dac5a0b473f352ed4088cd1b1184eb0f7ceec6b99de8704e8850ddf4f5 SHA256 (FreeBSD-10.1-BETA2-amd64.vhd.xz) = 88a4860f0f6c047c153c3471d0458862dd3e434a127c1e42d4995bf7c3cdcb31 SHA256 (FreeBSD-10.1-BETA2-amd64.vmdk.xz) = 1f8c6d76f48b5efc21efd9c9567cf56e5e8bd174242212f3c00658315f06e86b MD5 (FreeBSD-10.1-BETA2-amd64.qcow2.xz) = a4de54eed70f0be5cbdf76b8af3b5a0d MD5 (FreeBSD-10.1-BETA2-amd64.raw.xz) = 8ce2087a5278e517de945f23ddcc6223 MD5 (FreeBSD-10.1-BETA2-amd64.vhd.xz) = 6727119670e91e7c3c6d487c7eea45e9 MD5 (FreeBSD-10.1-BETA2-amd64.vmdk.xz) = af345d07ef7fb9edb2929dc7d306c449 o 10.1-BETA2 i386: SHA256 (FreeBSD-10.1-BETA2-i386.qcow2.xz) = 6fd33a7d04978a73c58cdbc06cd66351c6d8e1fc35a9ce0246a94d2d7ebb771e SHA256 (FreeBSD-10.1-BETA2-i386.raw.xz) = d481a06058ee98ffbd8371cd903effa7ec5c304f0c39564a65f8034a2da467bb SHA256 (FreeBSD-10.1-BETA2-i386.vhd.xz) = e8311cfb354ad30945ca8da444a3bdaf5c2199c4aa954461e630a4de4d5854ba SHA256 (FreeBSD-10.1-BETA2-i386.vmdk.xz) = 1cee8300d9cd1c8ad80e30deb5af953b40f3d519962e02737a56b312b4d369f9 MD5 (FreeBSD-10.1-BETA2-i386.qcow2.xz) = 2e7494edfa5fc839728793e29f3a0bac MD5 (FreeBSD-10.1-BETA2-i386.raw.xz) = fd7b8e6cb861e4986ba7fdde60fc3c2e MD5 (FreeBSD-10.1-BETA2-i386.vhd.xz) = 20867fea4dd1e6f9e54b3d314090ca59 MD5 (FreeBSD-10.1-BETA2-i386.vmdk.xz) = 9ebad3bc6e104f72fd60c8a7399403f6 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 iQIcBAEBCAAGBQJUHwWwAAoJELls3eqvi17QhiQP/1IOEwsL9rqC+F1UJYlTEYqK f4CGaG+w/USKaHJs1INc1H3ibHv7QGsxvMTbGzopk/uVfCDF7HZcKCQBk9S4XroV V5/GtdLcg9kfr1A5Iz5+BBddIjYd35VqRoWaOtK1W7bJJvl8W5AZkE/W5Q1+EqKw x7w2v/GEtI+4VojOvTaar8JEWwV78cDh/K8kAU6K5DicQoHbCtUXedw9rjgJI2J+ Gplc9ZrpQpanJSijdtj1YHej0OzGLCIQ4Qp914VCFq6zf5zjBm5JUEbX2bglpRTf V7lz5KouAV77MgaVyijXCWxPnZGEsue3atI7eKHDSaW1W8vd36lxs9mg2ovG6ecH KuMHlx5ohnRJMSDM/Y/dpZgc02wnFh86ea51WllW1JdzQeyC/ZohXhFrB6/djiZ6 8vQCS/LZ4eZL0LPEdvNY/oZfzbmLIpslqLVp1tLc5G5BkiiWLV3y3JdRsyJ3NRYd /rFZ6QbAFW7CMOFCyoRlLnvtVIOgZLxuoi9K5+L3/lev7JNbgPNN8VsZYeGL/R1y WKeT0ucKQOasqKWWXWu42evJ3hm8kVzLA64K0RyewXYeBqChk/KYlufRNfLOe0gN SkBNLiRHhD7b6fMpd2XrqmYEIonXvvnaoA5NRBVB/Qz1lzfMyuIMT69es6Q9/gXm RaKwFV5PkCZWOAnXp5yw =pyMp -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sun Sep 21 21:31:38 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BCBDC706; Sun, 21 Sep 2014 21:31:38 +0000 (UTC) Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (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 75EF8B7F; Sun, 21 Sep 2014 21:31:38 +0000 (UTC) Received: by mail-ie0-f172.google.com with SMTP id rp18so4377597iec.17 for ; Sun, 21 Sep 2014 14:31:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ntMTbqZvTUyh5ZGilMf7ygv8ENi6TTptiS7LWIeFnWY=; b=pcDUE+bOL3BJR47vNb6lDAfzFOfk9rQkQ+SLWVmDzF4vHOS/OYhfQWQRw3TDCW7rCc p6kLSM1HnFZ2eFSLzYYuRCHT0HECdO0lTQexOZj+6F4tJdln/CAE03/uX5i4Ak5RwmeT YMdBNSE3//44mrLAAaMonQ+UunqBhQb2y572cSUbzUiDXN3nsC04ywhmwDrTM0UUQipR PXkkmNGk9G+k75swxuS7k/zSUCf4VWj/QZJ/1ApiHIq4BN1m2HVHP3r6lOohLrVYc7Ow trRQ8vuFvUnpfC+yO9iYMPyUuqob4x3p1vrU2vfQ3cz62Bq3mjWVbmt1ZteaP0rRC6mQ Ii2g== MIME-Version: 1.0 X-Received: by 10.42.120.72 with SMTP id e8mr454457icr.64.1411335097804; Sun, 21 Sep 2014 14:31:37 -0700 (PDT) Received: by 10.50.87.130 with HTTP; Sun, 21 Sep 2014 14:31:37 -0700 (PDT) In-Reply-To: <1411259605.674669006.339g4pd4@frv35.fwdcdn.com> References: <1411259605.674669006.339g4pd4@frv35.fwdcdn.com> Date: Sun, 21 Sep 2014 14:31:37 -0700 Message-ID: Subject: Re: FreeBSD 10 network performance problems 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 Cc: qingli@freebsd.org, kmacy@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: Sun, 21 Sep 2014 21:31:38 -0000 Thank you for your answers Adrian and Vladislav. Adrian: I read this paper, http://conferences.sigcomm.org/sigcomm/2009/workshops/presto/papers/p37.pdf, and I left with the impression that the locking contentions on *rtentry* have been solved some time around FreeBSD 8 release with the new routing architecture and flowtable. I was wondering if this is really the case or maybe I am dealing with an edge-case here. I cc Qing Li and Kip Macy for further visibility and comments (original report at http://lists.freebsd.org/pipermail/freebsd-stable/2014-September/080170.html). On the other hand https://wiki.freebsd.org/NetworkPerformanceTuning advises: "*Do not use FLOWTABLE. It is still untested (2012-02-23).*" Is that still the case? As mentioned previously I tried this kernel option earlier and it had no effect. Additionally, on https://wiki.freebsd.org/NewNetworking I saw that there are still open items with regards to "*rtentry locking*" and "*Contention between CPUs when forwarding between multi-queue interfaces*". Not quite sure if this is what I am dealing with. I also wonder if this lock contention is something new or I am dealing with some strange edge-case. I read that people are able to push 10Gbit/s on FreeBSD 9.2 (https://calomel.org/network_performance.html). Anybody else seeing this around 4-5Gbit/s ? Vladislav: Here are the details that you requested (freshly booted system): # pciconf -lv | grep -A 4 ix\[0-9\] ix0@pci0:5:0:0: class=0x020000 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82599EB 10-Gigabit SFI/SFP+ Network Connection' class = network subclass = ethernet ix1@pci0:5:0:1: class=0x020000 card=0x00038086 chip=0x10fb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82599EB 10-Gigabit SFI/SFP+ Network Connection' class = network subclass = ethernet # netstat -m 100358/50182/150540 mbufs in use (current/cache/total) 2048/47288/49336/1526116 mbuf clusters in use (current/cache/total/max) 2048/47287 mbuf+clusters out of packet secondary zone in use (current/cache) 0/7/7/763057 4k (page size) jumbo clusters in use (current/cache/total/max) 98300/11/98311/226091 9k jumbo clusters in use (current/cache/total/max) 0/0/0/127176 16k jumbo clusters in use (current/cache/total/max) 913885K/107248K/1021134K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile # ngctl list | wc -l 2 # sysctl -a | egrep 'net.(inet.(tcp|udp)|graph|isr)' net.inet.tcp.rfc1323: 1 net.inet.tcp.mssdflt: 536 net.inet.tcp.keepidle: 7200000 net.inet.tcp.keepintvl: 75000 net.inet.tcp.sendspace: 32768 net.inet.tcp.recvspace: 65536 net.inet.tcp.keepinit: 75000 net.inet.tcp.delacktime: 100 net.inet.tcp.v6mssdflt: 1220 net.inet.tcp.cc.algorithm: newreno net.inet.tcp.cc.available: newreno net.inet.tcp.hostcache.cachelimit: 15360 net.inet.tcp.hostcache.hashsize: 512 net.inet.tcp.hostcache.bucketlimit: 30 net.inet.tcp.hostcache.count: 6 net.inet.tcp.hostcache.expire: 3600 net.inet.tcp.hostcache.prune: 300 net.inet.tcp.hostcache.purge: 0 net.inet.tcp.log_in_vain: 0 net.inet.tcp.blackhole: 0 net.inet.tcp.delayed_ack: 1 net.inet.tcp.drop_synfin: 0 net.inet.tcp.rfc3042: 1 net.inet.tcp.rfc3390: 1 net.inet.tcp.experimental.initcwnd10: 1 net.inet.tcp.rfc3465: 1 net.inet.tcp.abc_l_var: 2 net.inet.tcp.ecn.enable: 0 net.inet.tcp.ecn.maxretries: 1 net.inet.tcp.insecure_rst: 0 net.inet.tcp.recvbuf_auto: 1 net.inet.tcp.recvbuf_inc: 16384 net.inet.tcp.recvbuf_max: 2097152 net.inet.tcp.path_mtu_discovery: 1 net.inet.tcp.tso: 1 net.inet.tcp.sendbuf_auto: 1 net.inet.tcp.sendbuf_inc: 8192 net.inet.tcp.sendbuf_max: 2097152 net.inet.tcp.reass.maxsegments: 95400 net.inet.tcp.reass.cursegments: 0 net.inet.tcp.reass.overflows: 0 net.inet.tcp.sack.enable: 1 net.inet.tcp.sack.maxholes: 128 net.inet.tcp.sack.globalmaxholes: 65536 net.inet.tcp.sack.globalholes: 0 net.inet.tcp.minmss: 216 net.inet.tcp.log_debug: 0 net.inet.tcp.tcbhashsize: 262144 net.inet.tcp.do_tcpdrain: 1 net.inet.tcp.pcbcount: 17 net.inet.tcp.icmp_may_rst: 1 net.inet.tcp.isn_reseed_interval: 0 net.inet.tcp.soreceive_stream: 0 net.inet.tcp.syncookies: 1 net.inet.tcp.syncookies_only: 0 net.inet.tcp.syncache.bucketlimit: 30 net.inet.tcp.syncache.cachelimit: 15375 net.inet.tcp.syncache.count: 0 net.inet.tcp.syncache.hashsize: 512 net.inet.tcp.syncache.rexmtlimit: 3 net.inet.tcp.syncache.rst_on_sock_fail: 1 net.inet.tcp.msl: 30000 net.inet.tcp.rexmit_min: 30 net.inet.tcp.rexmit_slop: 200 net.inet.tcp.always_keepalive: 1 net.inet.tcp.fast_finwait2_recycle: 0 net.inet.tcp.finwait2_timeout: 60000 net.inet.tcp.keepcnt: 8 net.inet.tcp.rexmit_drop_options: 0 net.inet.tcp.per_cpu_timers: 0 net.inet.tcp.timer_race: 0 net.inet.tcp.maxtcptw: 27767 net.inet.tcp.nolocaltimewait: 0 net.inet.udp.checksum: 1 net.inet.udp.maxdgram: 9216 net.inet.udp.recvspace: 42080 net.inet.udp.log_in_vain: 0 net.inet.udp.blackhole: 0 net.isr.dispatch: direct net.isr.maxthreads: 1 net.isr.bindthreads: 0 net.isr.maxqlimit: 10240 net.isr.defaultqlimit: 256 net.isr.maxprot: 16 net.isr.numthreads: 1 net.graph.threads: 12 net.graph.maxalloc: 4096 net.graph.maxdata: 512 net.graph.abi_version: 12 net.graph.msg_version: 8 net.graph.maxdgram: 20480 net.graph.recvspace: 20480 net.graph.family: 32 net.graph.data.proto: 1 net.graph.control.proto: 2 Once again, I am ready to provide additional metrics and run more tests upon request. Thank you, Rumen Telbizov From owner-freebsd-stable@FreeBSD.ORG Sun Sep 21 22:08: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8ECBBCF4; Sun, 21 Sep 2014 22:08:19 +0000 (UTC) Received: from mail-yh0-x22c.google.com (mail-yh0-x22c.google.com [IPv6:2607:f8b0:4002:c01::22c]) (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 3E9B2EC7; Sun, 21 Sep 2014 22:08:19 +0000 (UTC) Received: by mail-yh0-f44.google.com with SMTP id v1so1630988yhn.3 for ; Sun, 21 Sep 2014 15:08:18 -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=dmBhZSC78EwNJsKyoqjA6HE7QYe8JY4Ci3LK5SASJHs=; b=AWaHJxqyQGN3s9B1MNeChkleQuUZVwCZYxUvnc3alyWgugoetxUXdrEb3LBr0VFKF0 dWAQptBuv9WkKAXcWTZNtWga+2qSCWrHEUnfHH3lnfq/zVrGRjBZbm2S1yVg+OxOa9Uo E0FX/VQhbckqdWWkZRIOn68To4SjeJ3yu9NWXFejD605vZPC/LWi9ZOx0fiu7uedGT6N zryLaqC6r56dO1iYF0oqmiwbsT0iThwmquTR9Tuy6h6e8rnXGUu1tg6Y/WWM9JWjVssn M6/XRijO+Sem7rm1OR0vf33eE5Tt9YQhUuL+rHtnVcknb2cld0JIdk0098hRZNb8FujY J2+g== MIME-Version: 1.0 X-Received: by 10.236.133.65 with SMTP id p41mr38752yhi.73.1411337298222; Sun, 21 Sep 2014 15:08:18 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.170.82.197 with HTTP; Sun, 21 Sep 2014 15:08:18 -0700 (PDT) In-Reply-To: References: <1411259605.674669006.339g4pd4@frv35.fwdcdn.com> Date: Sun, 21 Sep 2014 15:08:18 -0700 X-Google-Sender-Auth: ROzXCVXLzuSGASnSUoZvHLxFwwY Message-ID: Subject: Re: FreeBSD 10 network performance problems From: "K. Macy" To: Rumen Telbizov Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Tom Elite , "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: Sun, 21 Sep 2014 22:08:19 -0000 What you're dealing with is hardly an edge case. Most people don't need to push more than a couple of Gbps in production. Flowtable is hardly "untested." However, it has been a source of friction at times because it can be somewhat brittle, having limits on the number of cache entries that it can store that are frequently too low for people with very large numbers of active flows. Without raising this limit substantially these systems will fail in a rather spectacular fashion. Additionally, flowtable was not written with the intent of being a routing cache. It was developed to support stateful multipath routing for load balancing. In its current incarnation, stripped of much of the code for its initial purpose, it's really just a band-aid around locking problems in routing. That said, the handful of commercial users of FreeBSD that do have large amounts of traffic (10s of Gbps) per system that I personally know of all have flowtable enabled. Unfortunately, at least in terms of what is in HEAD, little has been done to fix the contention that flowtable works around. For your purposes the response that Adrian gave you is the closest to "optimal." I hope that helps. -K On Sun, Sep 21, 2014 at 2:31 PM, Rumen Telbizov wrote: > Thank you for your answers Adrian and Vladislav. > > Adrian: > I read this paper, > http://conferences.sigcomm.org/sigcomm/2009/workshops/presto/papers/p37.pdf, > and I left with the impression that the locking contentions on *rtentry* > have been solved some time around FreeBSD 8 release with the new routing > architecture and flowtable. I was wondering if this is really the case or > maybe I am dealing with an edge-case here. I cc Qing Li and Kip Macy for > further visibility and comments (original report at > http://lists.freebsd.org/pipermail/freebsd-stable/2014-September/080170.html). > > On the other hand https://wiki.freebsd.org/NetworkPerformanceTuning > advises: "*Do not use FLOWTABLE. It is still untested (2012-02-23).*" Is > that still the case? As mentioned previously I tried this kernel option > earlier and it had no effect. > > Additionally, on https://wiki.freebsd.org/NewNetworking I saw that there > are still open items with regards to "*rtentry locking*" and "*Contention > between CPUs when forwarding between multi-queue interfaces*". Not quite > sure if this is what I am dealing with. > > I also wonder if this lock contention is something new or I am dealing > with some strange edge-case. I read that people are able to push 10Gbit/s > on FreeBSD 9.2 (https://calomel.org/network_performance.html). Anybody > else seeing this around 4-5Gbit/s ? > > > Vladislav: > Here are the details that you requested (freshly booted system): > # pciconf -lv | grep -A 4 ix\[0-9\] > ix0@pci0:5:0:0: class=0x020000 card=0x00038086 chip=0x10fb8086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = '82599EB 10-Gigabit SFI/SFP+ Network Connection' > class = network > subclass = ethernet > ix1@pci0:5:0:1: class=0x020000 card=0x00038086 chip=0x10fb8086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = '82599EB 10-Gigabit SFI/SFP+ Network Connection' > class = network > subclass = ethernet > > # netstat -m > 100358/50182/150540 mbufs in use (current/cache/total) > 2048/47288/49336/1526116 mbuf clusters in use (current/cache/total/max) > 2048/47287 mbuf+clusters out of packet secondary zone in use > (current/cache) > 0/7/7/763057 4k (page size) jumbo clusters in use (current/cache/total/max) > 98300/11/98311/226091 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/127176 16k jumbo clusters in use (current/cache/total/max) > 913885K/107248K/1021134K bytes allocated to network (current/cache/total) > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for mbufs delayed (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters delayed (4k/9k/16k) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > > # ngctl list | wc -l > 2 > > # sysctl -a | egrep 'net.(inet.(tcp|udp)|graph|isr)' > net.inet.tcp.rfc1323: 1 > net.inet.tcp.mssdflt: 536 > net.inet.tcp.keepidle: 7200000 > net.inet.tcp.keepintvl: 75000 > net.inet.tcp.sendspace: 32768 > net.inet.tcp.recvspace: 65536 > net.inet.tcp.keepinit: 75000 > net.inet.tcp.delacktime: 100 > net.inet.tcp.v6mssdflt: 1220 > net.inet.tcp.cc.algorithm: newreno > net.inet.tcp.cc.available: newreno > net.inet.tcp.hostcache.cachelimit: 15360 > net.inet.tcp.hostcache.hashsize: 512 > net.inet.tcp.hostcache.bucketlimit: 30 > net.inet.tcp.hostcache.count: 6 > net.inet.tcp.hostcache.expire: 3600 > net.inet.tcp.hostcache.prune: 300 > net.inet.tcp.hostcache.purge: 0 > net.inet.tcp.log_in_vain: 0 > net.inet.tcp.blackhole: 0 > net.inet.tcp.delayed_ack: 1 > net.inet.tcp.drop_synfin: 0 > net.inet.tcp.rfc3042: 1 > net.inet.tcp.rfc3390: 1 > net.inet.tcp.experimental.initcwnd10: 1 > net.inet.tcp.rfc3465: 1 > net.inet.tcp.abc_l_var: 2 > net.inet.tcp.ecn.enable: 0 > net.inet.tcp.ecn.maxretries: 1 > net.inet.tcp.insecure_rst: 0 > net.inet.tcp.recvbuf_auto: 1 > net.inet.tcp.recvbuf_inc: 16384 > net.inet.tcp.recvbuf_max: 2097152 > net.inet.tcp.path_mtu_discovery: 1 > net.inet.tcp.tso: 1 > net.inet.tcp.sendbuf_auto: 1 > net.inet.tcp.sendbuf_inc: 8192 > net.inet.tcp.sendbuf_max: 2097152 > net.inet.tcp.reass.maxsegments: 95400 > net.inet.tcp.reass.cursegments: 0 > net.inet.tcp.reass.overflows: 0 > net.inet.tcp.sack.enable: 1 > net.inet.tcp.sack.maxholes: 128 > net.inet.tcp.sack.globalmaxholes: 65536 > net.inet.tcp.sack.globalholes: 0 > net.inet.tcp.minmss: 216 > net.inet.tcp.log_debug: 0 > net.inet.tcp.tcbhashsize: 262144 > net.inet.tcp.do_tcpdrain: 1 > net.inet.tcp.pcbcount: 17 > net.inet.tcp.icmp_may_rst: 1 > net.inet.tcp.isn_reseed_interval: 0 > net.inet.tcp.soreceive_stream: 0 > net.inet.tcp.syncookies: 1 > net.inet.tcp.syncookies_only: 0 > net.inet.tcp.syncache.bucketlimit: 30 > net.inet.tcp.syncache.cachelimit: 15375 > net.inet.tcp.syncache.count: 0 > net.inet.tcp.syncache.hashsize: 512 > net.inet.tcp.syncache.rexmtlimit: 3 > net.inet.tcp.syncache.rst_on_sock_fail: 1 > net.inet.tcp.msl: 30000 > net.inet.tcp.rexmit_min: 30 > net.inet.tcp.rexmit_slop: 200 > net.inet.tcp.always_keepalive: 1 > net.inet.tcp.fast_finwait2_recycle: 0 > net.inet.tcp.finwait2_timeout: 60000 > net.inet.tcp.keepcnt: 8 > net.inet.tcp.rexmit_drop_options: 0 > net.inet.tcp.per_cpu_timers: 0 > net.inet.tcp.timer_race: 0 > net.inet.tcp.maxtcptw: 27767 > net.inet.tcp.nolocaltimewait: 0 > net.inet.udp.checksum: 1 > net.inet.udp.maxdgram: 9216 > net.inet.udp.recvspace: 42080 > net.inet.udp.log_in_vain: 0 > net.inet.udp.blackhole: 0 > net.isr.dispatch: direct > net.isr.maxthreads: 1 > net.isr.bindthreads: 0 > net.isr.maxqlimit: 10240 > net.isr.defaultqlimit: 256 > net.isr.maxprot: 16 > net.isr.numthreads: 1 > net.graph.threads: 12 > net.graph.maxalloc: 4096 > net.graph.maxdata: 512 > net.graph.abi_version: 12 > net.graph.msg_version: 8 > net.graph.maxdgram: 20480 > net.graph.recvspace: 20480 > net.graph.family: 32 > net.graph.data.proto: 1 > net.graph.control.proto: 2 > > Once again, I am ready to provide additional metrics and run more tests > upon request. > > Thank you, > Rumen Telbizov > From owner-freebsd-stable@FreeBSD.ORG Sun Sep 21 22:19:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 553D4EB7 for ; Sun, 21 Sep 2014 22:19:55 +0000 (UTC) Received: from frv191.fwdcdn.com (frv191.fwdcdn.com [212.42.77.191]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 12540FA8 for ; Sun, 21 Sep 2014 22:19:55 +0000 (UTC) Received: from [10.10.1.30] (helo=frv196.fwdcdn.com) by frv191.fwdcdn.com with esmtp ID 1XVpTq-000OIw-IB for freebsd-stable@freebsd.org; Mon, 22 Sep 2014 01:19:42 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-Id:Cc:To:Subject:From:Date; bh=x+b/z+TgMZBy7fVQB2U2gd+Tr7LEInFJm14AlgPuNtM=; b=ok0bqshjdg6OiTYXjpp4+FzjRmkAlX3nwuy6L4k0wVbcMGqWqZoeiZzQnBulumWL+O1Z/20T4xZSMfFQE6h8UiU3/FE2fQkKqzy4BNz1LfuxSBsfz1nXG+/eG59bcmYQA/9JH56NU0w0n54vA6OeQ6UxVb9rEDIVVrm6V241xWM=; Received: from [10.10.10.35] (helo=frv35.fwdcdn.com) by frv196.fwdcdn.com with smtp ID 1XVpTb-000AYr-Cp for freebsd-stable@freebsd.org; Mon, 22 Sep 2014 01:19:27 +0300 Date: Mon, 22 Sep 2014 01:19:26 +0300 From: Vladislav Prodan Subject: Re[2]: FreeBSD 10 network performance problems To: Rumen Telbizov X-Mailer: mail.ukr.net 5.0 Message-Id: <1411337035.63493935.by6bew01@frv35.fwdcdn.com> In-Reply-To: References: <1411259605.674669006.339g4pd4@frv35.fwdcdn.com> MIME-Version: 1.0 Received: from universite@ukr.net by frv35.fwdcdn.com; Mon, 22 Sep 2014 01:19:26 +0300 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary Content-Disposition: inline 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: Sun, 21 Sep 2014 22:19:55 -0000 --- Original message --- From: "Rumen Telbizov" Date: 22 September 2014, 00:31:51 > Thank you for your answers Adrian and Vladislav. > > Vladislav: > Here are the details that you requested (freshly booted system): > Once again, I am ready to provide additional metrics and run more tests > upon request. > > Thank you, > Rumen Telbizov 1) Try to add to the config /boot/loader.conf : net.isr.defaultqlimit=2048 net.isr.maxqlimit=40960 2) Try to add to the config /etc/sysctl.conf : net.inet.tcp.recvbuf_inc=524288 net.inet.tcp.recvbuf_max=16777216 net.inet.tcp.sendbuf_inc=524288 net.inet.tcp.sendbuf_max=16777216 net.inet.tcp.sendspace=65536 3) On the network card turn off TSO, rxcsum and txcsum ifconfig ix0 -rxcsum -tso -txcsum lro -- Vladislav V. Prodan System & Network Administrator support.od.ua From owner-freebsd-stable@FreeBSD.ORG Sun Sep 21 22:51:14 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 40C17368 for ; Sun, 21 Sep 2014 22:51:14 +0000 (UTC) Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::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 06C0D2A2 for ; Sun, 21 Sep 2014 22:51:13 +0000 (UTC) Received: by mail-oa0-f53.google.com with SMTP id eb12so3330119oac.40 for ; Sun, 21 Sep 2014 15:51:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=3i1rrgWou1sFGqTOsqpWwtis0sSpv6/tAOZ7Ug6gi6g=; b=aadZ+lt6UmFIATxwDxiNZBpP9oZBNXxrQmjJrVtsS7tOyRep44csyEwSQdxv0vs63X +cR7/UNcUxsxA8GgebP9H33iRZmmWS2+8V1oV8CE+reZB5C0mcPjzBgsoRgAerqJZ0JZ aP6GyrrstCgUel0OX0PCTIb8vHY/QlMnLfHAIX3/a7iMoG7+vZHhvA/l57eM/YiZdsbd 0szgbWLZdyUxQEObtEM/6wpII2fR28LW5eZbFJ2F8jDtw4mYuQrkP08ZJl2UhswIIgC0 ah6E3uSHnCZhohYBuyEGtv1j+XPqfEx1S8BeVtk4lcl4xnmdi8qJw9dJC/sk2gUuLiNB zmbA== MIME-Version: 1.0 X-Received: by 10.60.220.169 with SMTP id px9mr4544750oec.67.1411339872335; Sun, 21 Sep 2014 15:51:12 -0700 (PDT) Received: by 10.182.228.51 with HTTP; Sun, 21 Sep 2014 15:51:12 -0700 (PDT) In-Reply-To: References: Date: Mon, 22 Sep 2014 00:51:12 +0200 Message-ID: Subject: Re: FreeBSD 10 network performance problems From: Oliver Pinter To: Rumen Telbizov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: Sun, 21 Sep 2014 22:51:14 -0000 On 9/20/14, Rumen Telbizov wrote: > Hello everyone, > > I am in the process of upgrading our main PF firewalls from 9.2-RC4 to > 10.1-BETA1 (r271684) and as part of the process I have been testing the > forwarding capability of FreeBSD 10 (pf firewall disabled) to have a > base-line and find any bottlenecks on a 10GbE network. > > My tests show that for the first 3-4Gbit/s of traffic things are great an= d > then the machine simply "hits the wall" at around 4-5Gbit/s of traffic. > There's no gradual degradation but a hard drop to 0% idle and 50-50% spli= t > of system and interrupt CPU load. I ran some diagnostics and I was hoping > someone could point me in the right direction as to what is happening and > what I could do to improve the situation. The details I have collected so > far are below: > > I run multiple iperf tcp multithreaded instances to generate traffic whic= h > traverses the firewall. As mentioned above for the first 3-4Gbit/s traffi= c > the machine doesn't even break a sweat. > > *top header* during this load when things are good: > CPU 0: 0.0% user, 0.0% nice, 0.0% system, 27.6% interrupt, 72.4% idle > CPU 1: 0.0% user, 0.0% nice, 0.0% system, 27.6% interrupt, 72.4% idle > CPU 2: 0.0% user, 0.0% nice, 0.0% system, 8.7% interrupt, 91.3% idle > CPU 3: 0.0% user, 0.0% nice, 0.0% system, 17.3% interrupt, 82.7% idle > CPU 4: 0.0% user, 0.0% nice, 0.0% system, 12.6% interrupt, 87.4% idle > CPU 5: 0.0% user, 0.0% nice, 0.0% system, 4.7% interrupt, 95.3% idle > CPU 6: 0.0% user, 0.0% nice, 0.0% system, 13.4% interrupt, 86.6% idle > CPU 7: 0.0% user, 0.0% nice, 0.0% system, 26.0% interrupt, 74.0% idle > CPU 8: 0.0% user, 0.0% nice, 0.0% system, 16.5% interrupt, 83.5% idle > CPU 9: 0.0% user, 0.0% nice, 0.0% system, 1.6% interrupt, 98.4% idle > CPU 10: 0.0% user, 0.0% nice, 0.0% system, 19.7% interrupt, 80.3% idle > CPU 11: 0.0% user, 0.0% nice, 0.0% system, 7.1% interrupt, 92.9% idle > Full output at http://pastebin.com/gaaisXV8 > > *bmon* at the same time: > Interfaces =E2=94=82 RX bps pps %=E2=94=82 = TX bps > pps % > ix0 =E2=94=82 240.33MiB 242.20K =E2=94=82 = 221.41MiB 236.68K > ix1 =E2=94=82 246.51MiB 248.80K =E2=94=82 = 261.61MiB 250.95K > >lagg0 =E2=94=82 483.45MiB 492.42K =E2=94=82 = 479.54MiB 488.02K > > MiB (RX > Bytes/second) MiB (TX > Bytes/second) > 499.17 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 496.49 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 415.98 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 413.74 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 332.78 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 331.00 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 249.59 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 248.25 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 166.39 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 165.50 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 83.20 > |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| 82.75 > |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 1 5 10 15 20 25 30 35 40 45 50 55 > 60 1 5 10 15 20 25 30 35 40 45 50 55 = 60 > K (RX > Packets/second) K (TX > Packets/second) > 508.27 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 505.14 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 423.56 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 420.95 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 338.85 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 336.76 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 254.14 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 252.57 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 169.42 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 168.38 |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 84.71 > |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| 84.19 > |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| > 1 5 10 15 20 25 30 35 40 45 50 55 > 60 1 5 10 15 20 25 30 35 40 45 50 55 = 60 > > To profile it without having it degrade sooner I reduced traffic to 2Gbit= /s > and ran dtrace hotkernel and lock profiling. Here are the results: > > */usr/share/dtrace/toolkit/hotkernel* for 60 seconds: > kernel`__mtx_lock_flags 5812 0.8% > kernel`__mtx_unlock_flags 7200 1.0% > kernel`acpi_cpu_c1 7799 1.1% > kernel`__rw_rlock 11196 1.5% > kernel`spinlock_exit 14547 2.0% > kernel`cpu_idle 166700 22.8% > kernel`sched_idletd 461883 63.1% > Full output at http://pastebin.com/w7WfFwPG > > *lock profiling* for 60 seconds: > $ head -n 2 good-locks ; cat good-locks | sort -n -k 4 | tail -n6 > debug.lock.prof.stats: > max wait_max total wait_total count avg wait_avg > cnt_hold cnt_lock name > 22 24 94378 18481 264549 0 > 0 0 18639 /usr/src/sys/kern/sched_ule.c:886 (spin mutex:sched > lock 10) > 22 24 112366 20360 219179 0 > 0 0 17220 /usr/src/sys/kern/sched_ule.c:888 (spin mutex:sched > lock 2) > 18 319 3486 22352 4233 0 > 5 0 1640 /usr/src/sys/kern/subr_taskqueue.c:344 (sleep > mutex:taskqueue) > 26 66 3219768 204875 14616220 0 > 0 0 133154 /usr/src/sys/net/route.c:439 (sleep mutex:rtentry) > 25 90 1923012 2353820 14615738 0 > 0 0 1562097 /usr/src/sys/netinet/ip_fastfwd.c:593 (sleep > mutex:rtentry) > 26 91 1398443 2391458 14616137 0 > 0 0 1604332 /usr/src/sys/netinet/in_rmx.c:114 (sleep mutex:rtentr= y) > Full output at http://pastebin.com/qiG3ZuAH > > Again, above measurements demonstrate the state of the good/healthy syste= m > under moderate traffic load of 3-4Gbit/s with pf disabled and fast > forwarding enabled. Here are the same measurements when I add an addition= al > 1Gbit/s of traffic. The point when performance tanks varies between > 4-5Gbit/s but it's always sudden, without any gradual degradation but > instead idle simply drops down to 0. Let's take a look: > > *top header* during this load when things are bad: > CPU 0: 0.0% user, 0.0% nice, 44.6% system, 55.4% interrupt, 0.0% idle > CPU 1: 0.0% user, 0.0% nice, 15.1% system, 84.9% interrupt, 0.0% idle > CPU 2: 0.0% user, 0.0% nice, 59.0% system, 40.3% interrupt, 0.7% idle > CPU 3: 0.0% user, 0.0% nice, 57.6% system, 42.4% interrupt, 0.0% idle > CPU 4: 0.0% user, 0.0% nice, 34.5% system, 63.3% interrupt, 2.2% idle > CPU 5: 0.0% user, 0.0% nice, 51.8% system, 48.2% interrupt, 0.0% idle > CPU 6: 0.0% user, 0.0% nice, 33.8% system, 66.2% interrupt, 0.0% idle > CPU 7: 0.7% user, 0.0% nice, 49.6% system, 49.6% interrupt, 0.0% idle > CPU 8: 0.0% user, 0.0% nice, 66.2% system, 33.8% interrupt, 0.0% idle > CPU 9: 0.0% user, 0.0% nice, 35.3% system, 64.7% interrupt, 0.0% idle > CPU 10: 0.0% user, 0.0% nice, 54.7% system, 45.3% interrupt, 0.0% idle > CPU 11: 0.0% user, 0.0% nice, 34.5% system, 65.5% interrupt, 0.0% idle > Full output at http://pastebin.com/9an9ZWv2 > > *bmon *at the same time shows inconsistent performance with big dips: > Interfaces =E2=94=82 RX bps pps %=E2=94=82 = TX bps > pps % > ix0 =E2=94=82 153.89MiB 151.53K =E2=94=82 = 179.69MiB 159.91K > ix1 =E2=94=82 176.56MiB 161.29K =E2=94=82 = 145.17MiB 148.13K > >lagg0 =E2=94=82 327.23MiB 333.05K =E2=94=82 = 322.14MiB 328.13K > > MiB (RX > Bytes/second) MiB > (TX Bytes/second) > 657.86 > ..............|............................................. > 648.60 ..............|............................................. > 548.21 > ..............|............................................. > 540.50 ..............|............................................. > 438.57 > ...........|..|.........................|.....|.......|..|.. > 432.40 ...........|..|.........................|.....|.......|..|.. > 328.93 > |..||||..||||.||...||..|||.||.|.|||||||||.|||||||||.||||||.. > 324.30 |..||||..||||.||...||..|||.||.|.|||||||||.|||||||||.||||||.. > 219.29 > |..||||..||||.||..|||.||||.||.|||||||||||.|||||||||.||||||.. > 216.20 |..||||..||||.||..|||.||||.||.|||||||||||.|||||||||.||||||.. > 109.64 > |.|||||..||||.||..|||.||||.||.|||||||||||.|||||||||.||||||.. > 108.10 |.|||||..||||.||..|||.||||.||.|||||||||||.|||||||||.||||||.. > 1 5 10 15 20 25 30 35 40 45 50 55 > 60 1 5 10 15 20 25 30 35 40 45 50 > 55 60 > K (RX > Packets/second) K > (TX Packets/second) > 670.41 > ..............|............................................. > 660.27 ..............|............................................. > 558.67 > ..............|............................................. > 550.22 ..............|............................................. > 446.94 > ...........|..|.........................|.....|.......|..|.. > 440.18 ...........|..|.........................|.....|.......|..|.. > 335.20 > |..||||..||||.||...||..|||.||.|.|||||||||.|||||||||.||||||.. > 330.13 |..||||..||||.||...||..|||.||.|.|||||||||.|||||||||.||||||.. > 223.47 > |..||||..||||.||..|||.||||.||.|||||||||||.|||||||||.||||||.. > 220.09 |..||||..||||.||..|||.||||.||.|||||||||||.|||||||||.||||||.. > 111.73 > |.|||||..||||.||..|||.||||.||.|||||||||||.|||||||||.||||||.. > 110.04 |.|||||..||||.||..|||.||||.||.|||||||||||.|||||||||.||||||.. > 1 5 10 15 20 25 30 35 40 45 50 55 > 60 1 5 10 15 20 25 30 35 40 45 50 > 55 60 > > */usr/share/dtrace/toolkit/hotkernel* for 60 seconds: > kernel`_rw_runlock_cookie 7709 1.1% > kernel`__rw_rlock 11182 1.6% > kernel`ip_fastforward 12231 1.7% > kernel`__mtx_lock_flags 22004 3.1% > kernel`__mtx_unlock_flags 35614 5.0% > kernel`__mtx_lock_sleep 560768 78.5% > Full output at http://pastebin.com/NurKwkWL > > *lock profiling* for 60 seconds: > $ head -n 2 bad-locks ; cat bad-locks | sort -n -k 4 | tail -n6 > debug.lock.prof.stats: > max wait_max total wait_total count avg wait_avg > cnt_hold cnt_lock name > 401766 191987 1857397 194162 179 10376 1084 > 0 2 /usr/src/sys/kern/kern_sysctl.c:1601 (sx:sysctl mem) > 21064 207907 62556 249066 396 157 628 > 0 3 /usr/src/sys/kern/kern_sysctl.c:1499 (sleep mutex:Giant) > 1 370663 17 372573 86 0 4332 > 0 2 /usr/src/sys/kern/kern_exit.c:429 (sx:allproc) > 14 648 8856844 46296098 15513956 0 2 0 > 1467849 /usr/src/sys/net/route.c:439 (sleep mutex:rtentry) > 15 958 13107581 252445472 15513486 0 16 0 > 9444644 /usr/src/sys/netinet/ip_fastfwd.c:593 (sleep mutex:rtentry) > 12 779 12500816 286324556 15513872 0 18 0 > 9788497 /usr/src/sys/netinet/in_rmx.c:114 (sleep mutex:rtentry) > Full output at http://pastebin.com/d54QmP13 > > System hardware is: 12 x E5-2440 @ 2.40GHz, 24GB RAM, Dual port fiber > Intel(R) PRO/10GbE in lacp lagg > System configuration details available at http://pastebin.com/tPvs1MeD > > It seems to me like heavy lock contention but I don't understand why it > happens in such an abrupt manner after a given threshold. > Other things I tried: > > - Upgrade ix (ixgbe) driver to the latest from Intel (2.5.25) - for so= me > reason I cannot send any packets out > - enable flowtables - no difference > > Any help is highly appreciated. I could provide further details and run > additional tests upon request. > > Regrads, > -- > Rumen Telbizov > Unix Systems Administrator Try to reenable the idle ticks. I observed similar problem with em driver. sysctl kern.eventtimer.idletick=3D1 sysctl kern.eventtimer.periodic=3D1 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Sun Sep 21 23:53:53 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3F54FE97; Sun, 21 Sep 2014 23:53:53 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id 2B617AD0; Sun, 21 Sep 2014 23:53:52 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NC90033ZZW87F00@hades.sorbs.net>; Sun, 21 Sep 2014 16:57:46 -0700 (PDT) Message-id: <541F6507.70904@sorbs.net> Date: Mon, 22 Sep 2014 01:53:43 +0200 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: ports@FreeBSD.org Subject: Re: [HEADSUP] pkg(8) is now the only package management tool References: <20140901195520.GB77917@ivaldir.etoilebsd.net> <54050D07.4010404@sorbs.net> In-reply-to: <54050D07.4010404@sorbs.net> Cc: pkg@FreeBSD.org, stable@FreeBSD.org, current@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: Sun, 21 Sep 2014 23:53:53 -0000 Michelle Sullivan wrote: > Baptiste Daroussin wrote: > >> Hi all, >> >> The ports tree has been modified to only support pkg(8) as package management >> system for all supported version of FreeBSD. >> >> if you were still using pkg_install (pkg_* tools) you will have to upgrade your >> system. >> >> The simplest way is >> cd /usr/ports/ports-mgmt/pkg >> make install >> then run >> pkg2ng >> >> So despite being told 'use the quarterly, patches can be applied to it if requested' and updating ports I maintain asking specifically for the patches to be merged... Still all broken (though patches applied to HEAD)... Nice one... -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 06:29:26 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7495E78D; Mon, 22 Sep 2014 06:29:26 +0000 (UTC) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (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 BA4DD18F; Mon, 22 Sep 2014 06:29:25 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id n12so372274wgh.11 for ; Sun, 21 Sep 2014 23:29:24 -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=a157o+BUVJu1m4KnfEP55AShoehOTzsefYrtyn8m/yU=; b=NNBej8EJx89FIHqMa5Gg38fCTvCdglNxionLqAjBk6YfkaNESjxy2bCWy5HAMwdlkQ GbwnacCu4QUQR4S8S9xz0VRXN68UAF8xO6jxvJGj6vEaqxRGc2L9g0IzisvE3Byj8Q1v hQXth2okTLQICcfqoQb/TTNCFBT/s91BfFvAs2ihm4O9jHU2LjSJLf5o8pJpqTz3DYBG diUdAQrJ+ppUhElETDSit8iciG9L/ne0DrcVdVCqDzcEj30YGrMmcNG4Wfrwod4jmiKp RLSU/CDL2g8vlK3K/eAywZDYxRQ8wGV0BMOgUlxM1XS51PJUlxYS3r6UsuPG92rRFXbx n0sw== MIME-Version: 1.0 X-Received: by 10.180.9.144 with SMTP id z16mr13022764wia.26.1411367363952; Sun, 21 Sep 2014 23:29:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.106.199 with HTTP; Sun, 21 Sep 2014 23:29:23 -0700 (PDT) In-Reply-To: References: <1411259605.674669006.339g4pd4@frv35.fwdcdn.com> Date: Sun, 21 Sep 2014 23:29:23 -0700 X-Google-Sender-Auth: qmF0m72FZf7JGMAKdyLsWxHQCTc Message-ID: Subject: Re: FreeBSD 10 network performance problems From: Adrian Chadd To: "K. Macy" Content-Type: text/plain; charset=UTF-8 Cc: Rumen Telbizov , Tom Elite , "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, 22 Sep 2014 06:29:26 -0000 Hi! On 21 September 2014 15:08, K. Macy wrote: > What you're dealing with is hardly an edge case. Most people don't need to > push more than a couple of Gbps in production. > > Flowtable is hardly "untested." However, it has been a source of friction > at times because it can be somewhat brittle, having limits on the number of > cache entries that it can store that are frequently too low for people with > very large numbers of active flows. Without raising this limit > substantially these systems will fail in a rather spectacular fashion. > Additionally, flowtable was not written with the intent of being a routing > cache. It was developed to support stateful multipath routing for load > balancing. In its current incarnation, stripped of much of the code for its > initial purpose, it's really just a band-aid around locking problems in > routing. That said, the handful of commercial users of FreeBSD that do have > large amounts of traffic (10s of Gbps) per system that I personally know of > all have flowtable enabled. > > Unfortunately, at least in terms of what is in HEAD, little has been done > to fix the contention that flowtable works around. For your purposes the > response that Adrian gave you is the closest to "optimal." Gleb and I spent a bunch of time late last year and early this year finding and fixing a lot of the corner cases with Flowtable handling. I'm pretty sure that it'll behave predictably and reliably for people now. If it doesn't then please file PRs. It's no longer some corner of the codebase that isn't well understood. At least two people besides the author (Gleb and I) understand what it is, how it works and how it ties into things. What's missing is someone sitting down and adding flowtable support to the rest of the forwarding path(s). It shouldn't be too hard - as long as you have an mbuf that has the IPv4/IPv6 header setup as that's what flowtable currently expects when doing lookups - but it has to be done. So I thoroughly recommend someone who has the test setup and the desire to do so and post results. I have enough equipment now to test this out and develop it but I'm really busy doing work, wireless RSS stuff. So I just don't have the spare cycles to do it. I do think it'll be a pretty simple task. In theory - once you have the flowtable code working correctly in the forwarding path you shouldn't see any rtentry lock contention except during route changes (which will invalidate flowtable entries and cause normal routing table lookups until the flowtable has all the route entries in question.) -a From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 07:33: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C0DC8F35; Mon, 22 Sep 2014 07:33:52 +0000 (UTC) Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com [195.16.151.151]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7674CA3E; Mon, 22 Sep 2014 07:33:51 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop04.sare.net (Postfix) with ESMTPSA id EADD29DC919; Mon, 22 Sep 2014 09:33:42 +0200 (CEST) Subject: Re: getting to 4K disk blocks in ZFS Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <20140920000636.GD51285@in-addr.com> Date: Mon, 22 Sep 2014 09:33:39 +0200 Content-Transfer-Encoding: 7bit Message-Id: <1640F942-D90E-46A0-BC18-ED0B73561E6F@sarenet.es> References: <540FF3C4.6010305@ish.com.au> <54114029.3060507@FreeBSD.org> <2128347.Ah5i0RTCvp@overcee.wemm.org> <541230F1.3060402@digiware.nl> <7D0869A9-C114-4C4F-877A-3FB26AD7737D@scsiguy.com> <607F83CE25104CE09C74935BA9E26485@multiplay.co.uk> <541CBD5B.8050603@denninger.net> <20140920000636.GD51285@in-addr.com> To: Gary Palmer X-Mailer: Apple Mail (2.1283) Cc: Steven Hartland , Stable Stable , 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: Mon, 22 Sep 2014 07:33:52 -0000 On Sep 20, 2014, at 2:06 AM, Gary Palmer wrote: > If I tell smartctl to ignore it's database it still says it's a 4k In my case, Samsung 840 EVO SSDs connected to a SAS backplane, pass6: ATA-9 SATA 3.x device pass6: 600.000MB/s transfers, Command Queueing Enabled protocol ATA/ATAPI-9 SATA 3.x device model Samsung SSD 840 EVO 1TB firmware revision EXT0BB0Q serial number S1D9NEADA08556K WWN 50025388500ae92b cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 268435455 sectors LBA48 supported 1953525168 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM non-rotating even though it has a 4K quirk da6 at mpr0 bus 0 scbus0 target 30 lun 0 da6: Fixed Direct Access SCSI-6 device da6: Serial Number S1D9NEADA08556K da6: 600.000MB/s transfers da6: Command Queueing enabled da6: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C) da6: quirks=0x8<4K> smartctl reports the same, 512 logical/physical smartctl 6.3 2014-07-26 r3976 [FreeBSD 10.1-BETA1 amd64] (local build) Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Samsung based SSDs Device Model: Samsung SSD 840 EVO 1TB Serial Number: S1D9NEADA08556K LU WWN Device Id: 5 002538 8500ae92b Firmware Version: EXT0BB0Q User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Mon Sep 22 09:34:24 2014 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, NOT FROZEN [SEC1] From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 12:10:12 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C98087B3; Mon, 22 Sep 2014 12:10:12 +0000 (UTC) Received: from mailout06.t-online.de (mailout06.t-online.de [194.25.134.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 865B7C2E; Mon, 22 Sep 2014 12:10:12 +0000 (UTC) Received: from fwd16.aul.t-online.de (fwd16.aul.t-online.de [172.20.26.243]) by mailout06.t-online.de (Postfix) with SMTP id 1DF7F44D460; Mon, 22 Sep 2014 14:10:04 +0200 (CEST) Received: from [192.168.119.10] (XLtQT6ZAQh5vn+3boH63ziuZO38FWvsFKxcBhmIhzQGlLwXHcU30Dyvlfihfw0hgnj@[84.154.118.168]) by fwd16.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1XW2RJ-0rEt5E0; Mon, 22 Sep 2014 14:09:57 +0200 Message-ID: <54201192.5080906@freebsd.org> Date: Mon, 22 Sep 2014 14:09:54 +0200 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Gyrd Thane Lange , freebsd-current@freebsd.org Subject: Re: [patch] syscons/vt keymap: Norwegian country code conflicts with default value References: <20140921183936.03617590@onyx.thanelange.no> In-Reply-To: <20140921183936.03617590@onyx.thanelange.no> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-ID: XLtQT6ZAQh5vn+3boH63ziuZO38FWvsFKxcBhmIhzQGlLwXHcU30Dyvlfihfw0hgnj X-TOI-MSGID: 514bd1c8-1bb9-4619-9413-10a360754b0b Cc: freebsd-stable 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, 22 Sep 2014 12:10:12 -0000 Am 21.09.2014 um 18:39 schrieb Gyrd Thane Lange: > Hi, > > Recent changes in keymap namning for syscons/vt to use shorter names > has exposed a conflict with the value "no" both used as country code > for Norway and as a default value indicating that no keymap is set. > > The attached patch proposes to use "" (empty string) as default value > instead. Hi Gyrd, thank you for reporting the issue! I have just committed a slightly different patch to -CURRENT and plan to merge it to 10-STABLE in time for the next BETA. You may want to check-out r271958 ... The approach I have chosen it to let "NO" continue to stand for "do not load any keymap", while "no" is now recognized as equivalent to "no.kbd". The new semantics of the keymap parameter in rc.conf are: keymap='' ==> do not load any keymap (unchanged) keymap=NO ==> do not load any keymap (unchanged) keymap=no ==> load Norwegian keymap (new) This may still catch people that have edited rc.conf to use "no" in the meaning "no keymap" by accident, but I see no other approach that better complies with POLA ... An alternative to a MFC to 10-STABLE (and 10.1) might be to mention this specific case in the release notes (and to suggest "keymap=no.kbd" as a work-around). But I'll try to get approval for the MFC in time for 10.1-BETA3 ... Regards, STefan From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 16:11:43 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 70726576 for ; Mon, 22 Sep 2014 16:11:43 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (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 36F58E3A for ; Mon, 22 Sep 2014 16:11:43 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.9/8.14.9) with ESMTP id s8MGBgM5023540 for ; Mon, 22 Sep 2014 16:11:42 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.9/8.14.9/Submit) id s8MGBgY8023537 for stable@FreeBSD.org; Mon, 22 Sep 2014 16:11:42 GMT (envelope-from bdrewery) Received: (qmail 42361 invoked from network); 22 Sep 2014 11:11:38 -0500 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 22 Sep 2014 11:11:38 -0500 Message-ID: <54204A33.3070700@FreeBSD.org> Date: Mon, 22 Sep 2014 11:11:31 -0500 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Michelle Sullivan , ports@FreeBSD.org Subject: Re: [HEADSUP] pkg(8) is now the only package management tool References: <20140901195520.GB77917@ivaldir.etoilebsd.net> <54050D07.4010404@sorbs.net> <541F6507.70904@sorbs.net> In-Reply-To: <541F6507.70904@sorbs.net> OpenPGP: id=6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="j9M15kmcleetDPhw7XHuDmKAXdcSBPCre" Cc: pkg@FreeBSD.org, stable@FreeBSD.org, current@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, 22 Sep 2014 16:11:43 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --j9M15kmcleetDPhw7XHuDmKAXdcSBPCre Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 9/21/2014 6:53 PM, Michelle Sullivan wrote: > Michelle Sullivan wrote: >> Baptiste Daroussin wrote: >> =20 >>> Hi all, >>> >>> The ports tree has been modified to only support pkg(8) as package ma= nagement >>> system for all supported version of FreeBSD. >>> >>> if you were still using pkg_install (pkg_* tools) you will have to up= grade your >>> system. >>> >>> The simplest way is >>> cd /usr/ports/ports-mgmt/pkg >>> make install >>> then run=20 >>> pkg2ng >>> >>> =20 >=20 > So despite being told 'use the quarterly, patches can be applied to it > if requested' and updating ports I maintain asking specifically for the= > patches to be merged... >=20 > Still all broken (though patches applied to HEAD)... Nice one... >=20 Which ports and PR? --=20 Regards, Bryan Drewery --j9M15kmcleetDPhw7XHuDmKAXdcSBPCre Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJUIEo2AAoJEDXXcbtuRpfP58wIAJ1zYr4wC8ZuH9Quqci4SiIJ /7+fYYEFL32zUqBIYpEJuZaE8Gz8LlUqydRxbfay9bcDWTypLFlSkQ21Ryr/SjY3 okoe9eXB/RaSzTaKNaDiJCK/DFdyPViXYPCIc8YvppTr46wyzYSwzRXlFezS8x7/ nQi4l8tfwcn1VQQkkfMCQiJKN6DepofrK1Jw1qA4ZHV4MQ5XW+NA0zdhEENCD/O5 voIXmIi7g+zTOS0ODZ1yVLiVZ9fqspEP5y4rM/IM1yrSqzOBB4ByYchURZOWnViz IrtOOqu6g+rkORucwtF8fPAlxXzkc8TKVchJoOUI/uQ4Dp5iJodgUYQH5U1PA8o= =tx7X -----END PGP SIGNATURE----- --j9M15kmcleetDPhw7XHuDmKAXdcSBPCre-- From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 17:28:53 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17A2A8ED; Mon, 22 Sep 2014 17:28:53 +0000 (UTC) Received: from mailrelay010.isp.belgacom.be (mailrelay010.isp.belgacom.be [195.238.6.177]) by mx1.freebsd.org (Postfix) with ESMTP id 5B1E6A2C; Mon, 22 Sep 2014 17:28:52 +0000 (UTC) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnIGAC5YIFRR8bfp/2dsb2JhbABggw6BIArSIAGBDRcBeYQEAQEEOhwjEAsOCgklDyoeBhOIQgGyApI9AReQBgeESwEEnRWVU4IegUU7L4JKAQEB Received: from 233.183-241-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.241.183.233]) by relay.skynet.be with ESMTP; 22 Sep 2014 19:28:45 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.14.9/8.14.9) with ESMTP id s8MHSiHF004814; Mon, 22 Sep 2014 19:28:44 +0200 (CEST) (envelope-from tijl@FreeBSD.org) Date: Mon, 22 Sep 2014 19:28:44 +0200 From: Tijl Coosemans To: Stefan Esser Subject: Re: [patch] syscons/vt keymap: Norwegian country code conflicts with default value Message-ID: <20140922192844.7de1bb6b@kalimero.tijl.coosemans.org> In-Reply-To: <54201192.5080906@freebsd.org> References: <20140921183936.03617590@onyx.thanelange.no> <54201192.5080906@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Gyrd Thane Lange , freebsd-current@freebsd.org, freebsd-stable 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, 22 Sep 2014 17:28:53 -0000 On Mon, 22 Sep 2014 14:09:54 +0200 Stefan Esser wrote: > Am 21.09.2014 um 18:39 schrieb Gyrd Thane Lange: > > Hi, > > > > Recent changes in keymap namning for syscons/vt to use shorter names > > has exposed a conflict with the value "no" both used as country code > > for Norway and as a default value indicating that no keymap is set. > > > > The attached patch proposes to use "" (empty string) as default value > > instead. > > Hi Gyrd, > > thank you for reporting the issue! > > I have just committed a slightly different patch to -CURRENT and plan > to merge it to 10-STABLE in time for the next BETA. > > You may want to check-out r271958 ... > > > The approach I have chosen it to let "NO" continue to stand for "do > not load any keymap", while "no" is now recognized as equivalent to > "no.kbd". > > > The new semantics of the keymap parameter in rc.conf are: > > keymap='' ==> do not load any keymap (unchanged) > keymap=NO ==> do not load any keymap (unchanged) > keymap=no ==> load Norwegian keymap (new) > > This may still catch people that have edited rc.conf to use "no" in > the meaning "no keymap" by accident, but I see no other approach that > better complies with POLA ... Maybe NONE. It's already being used in a number of cases. From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 18:11:05 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7AB5758F; Mon, 22 Sep 2014 18:11:05 +0000 (UTC) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (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 299C1EF5; Mon, 22 Sep 2014 18:11:05 +0000 (UTC) Received: by mail-ig0-f176.google.com with SMTP id hn15so3208738igb.15 for ; Mon, 22 Sep 2014 11:11:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z+VHVqff8dslmYkWAEaIeBgmXxtg5QuGXZEKPvidAmM=; b=rXDN19LtMZuGm/FP/FIKlk96uzxUK5OKESQ6aODvWLWr8rThZq4tUBC4VXEfr4NijN 8PpLVLqyxjrYSx9O7bEJU9mVzHxpnXbDzKXRYVMornCvdb2DRQxs+Q2gVMgZDTIS3vMP zbxKnnNxwtoTZHV7VaPOxtc9agJIlzMzmtvPO+go+UKus1ilbTbjmT9+MvaO/m4qkOec PnkqesEEjxawfaPohO0C5n3IFcsQTlI7a7vJ50l93Snqhit+a/I99K0LGXPR6PqUgREt QXct5eMIaYr3uBuwlNkNE8Yr8kgMzUvooJsm6izR2LeGAihEiSz/FXT0DOYqlgZStbG0 NkDg== MIME-Version: 1.0 X-Received: by 10.43.151.5 with SMTP id kq5mr2435548icc.87.1411409464533; Mon, 22 Sep 2014 11:11:04 -0700 (PDT) Received: by 10.50.87.130 with HTTP; Mon, 22 Sep 2014 11:11:04 -0700 (PDT) In-Reply-To: References: <1411259605.674669006.339g4pd4@frv35.fwdcdn.com> Date: Mon, 22 Sep 2014 11:11:04 -0700 Message-ID: Subject: Re: FreeBSD 10 network performance problems From: Rumen Telbizov To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Tom Elite , "freebsd-stable@freebsd.org" , "K. Macy" 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, 22 Sep 2014 18:11:05 -0000 Thank you all for the answers and directions. I tried all of the suggested changes to sysctl.conf and loader.conf settings above - they made no difference whatsoever. I believe they might help in certain situations but will improve things marginally. What I am dealing with is a pretty hard and sudden drop of performance due to lock contention. Adrian: What you're saying makes sense. If we can avoid the locking completely, this problem might go away. I'll see if I can get some help and try to tackle this challenge. Cheers, Rumen Telbizov On Sun, Sep 21, 2014 at 11:29 PM, Adrian Chadd wrote: > Hi! > > On 21 September 2014 15:08, K. Macy wrote: > > What you're dealing with is hardly an edge case. Most people don't need > to > > push more than a couple of Gbps in production. > > > > Flowtable is hardly "untested." However, it has been a source of friction > > at times because it can be somewhat brittle, having limits on the number > of > > cache entries that it can store that are frequently too low for people > with > > very large numbers of active flows. Without raising this limit > > substantially these systems will fail in a rather spectacular fashion. > > Additionally, flowtable was not written with the intent of being a > routing > > cache. It was developed to support stateful multipath routing for load > > balancing. In its current incarnation, stripped of much of the code for > its > > initial purpose, it's really just a band-aid around locking problems in > > routing. That said, the handful of commercial users of FreeBSD that do > have > > large amounts of traffic (10s of Gbps) per system that I personally know > of > > all have flowtable enabled. > > > > Unfortunately, at least in terms of what is in HEAD, little has been done > > to fix the contention that flowtable works around. For your purposes the > > response that Adrian gave you is the closest to "optimal." > > Gleb and I spent a bunch of time late last year and early this year > finding and fixing a lot of the corner cases with Flowtable handling. > > I'm pretty sure that it'll behave predictably and reliably for people > now. If it doesn't then please file PRs. It's no longer some corner of > the codebase that isn't well understood. At least two people besides > the author (Gleb and I) understand what it is, how it works and how it > ties into things. > > What's missing is someone sitting down and adding flowtable support to > the rest of the forwarding path(s). It shouldn't be too hard - as long > as you have an mbuf that has the IPv4/IPv6 header setup as that's what > flowtable currently expects when doing lookups - but it has to be > done. > > So I thoroughly recommend someone who has the test setup and the > desire to do so and post results. I have enough equipment now to test > this out and develop it but I'm really busy doing work, wireless RSS > stuff. So I just don't have the spare cycles to do it. > > I do think it'll be a pretty simple task. > > In theory - once you have the flowtable code working correctly in the > forwarding path you shouldn't see any rtentry lock contention except > during route changes (which will invalidate flowtable entries and > cause normal routing table lookups until the flowtable has all the > route entries in question.) > > > > -a > -- Rumen Telbizov Unix Systems Administrator From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 19:21:49 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E2AD7B38; Mon, 22 Sep 2014 19:21:49 +0000 (UTC) Received: from mailout04.t-online.de (mailout04.t-online.de [194.25.134.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F483A92; Mon, 22 Sep 2014 19:21:49 +0000 (UTC) Received: from fwd24.aul.t-online.de (fwd24.aul.t-online.de [172.20.26.129]) by mailout04.t-online.de (Postfix) with SMTP id CCB6336769A; Mon, 22 Sep 2014 21:15:25 +0200 (CEST) Received: from [192.168.119.10] (X7AZigZZQh2eqVyBZuJx9r9NqoPALGJ1aIP9sE8xnOZivG2OtG9w3-xJ8ZJbOeNwHB@[84.154.118.168]) by fwd24.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-SHA encrypted) esmtp id 1XW951-1J2CaO0; Mon, 22 Sep 2014 21:15:23 +0200 Message-ID: <54207548.2010906@freebsd.org> Date: Mon, 22 Sep 2014 21:15:20 +0200 From: Stefan Esser User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Tijl Coosemans Subject: Re: [patch] syscons/vt keymap: Norwegian country code conflicts with default value References: <20140921183936.03617590@onyx.thanelange.no> <54201192.5080906@freebsd.org> <20140922192844.7de1bb6b@kalimero.tijl.coosemans.org> In-Reply-To: <20140922192844.7de1bb6b@kalimero.tijl.coosemans.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-ID: X7AZigZZQh2eqVyBZuJx9r9NqoPALGJ1aIP9sE8xnOZivG2OtG9w3-xJ8ZJbOeNwHB X-TOI-MSGID: 2e1c4859-7c55-4392-b730-90e921824b81 Cc: Gyrd Thane Lange , freebsd-current@freebsd.org, freebsd-stable 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, 22 Sep 2014 19:21:50 -0000 Am 22.09.2014 um 19:28 schrieb Tijl Coosemans: > On Mon, 22 Sep 2014 14:09:54 +0200 Stefan Esser wrote: >> Am 21.09.2014 um 18:39 schrieb Gyrd Thane Lange: >>> Hi, >>> >>> Recent changes in keymap namning for syscons/vt to use shorter names >>> has exposed a conflict with the value "no" both used as country code >>> for Norway and as a default value indicating that no keymap is set. >>> >>> The attached patch proposes to use "" (empty string) as default value >>> instead. >> >> Hi Gyrd, >> >> thank you for reporting the issue! >> >> I have just committed a slightly different patch to -CURRENT and plan >> to merge it to 10-STABLE in time for the next BETA. >> >> You may want to check-out r271958 ... >> >> >> The approach I have chosen it to let "NO" continue to stand for "do >> not load any keymap", while "no" is now recognized as equivalent to >> "no.kbd". >> >> >> The new semantics of the keymap parameter in rc.conf are: >> >> keymap='' ==> do not load any keymap (unchanged) >> keymap=NO ==> do not load any keymap (unchanged) >> keymap=no ==> load Norwegian keymap (new) >> >> This may still catch people that have edited rc.conf to use "no" in >> the meaning "no keymap" by accident, but I see no other approach that >> better complies with POLA ... > > Maybe NONE. It's already being used in a number of cases. This was one of the alternatives, which I considered before the commit. Reasons for my choice of "no" vs. "NO" (and not "NONE"): 1) NO is the default (in defaults/rc.conf) and may have found its way into individual rc.conf files. I wanted to preserve its meaning. 2) Tools like bsdconfig need to be made version aware and to use NO for releases before 10.1 and NONE for 10.1 and later. IIRC, the use of NONE in rc.conf should be limited to cases that need a value besides NO (e.g. in the case of sendmail_enable, where both NO and NONE have special meaning). If there are no strong arguments against the patch that I committed, I'd like to MFC it to -STABLE. But if there are better alternatives (and I do not think that "NONE" is better, sorry), I'd like to hear about them in time for BETA3 ... Regards, STefan From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 19:41:28 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 35A80744; Mon, 22 Sep 2014 19:41:28 +0000 (UTC) Received: from bouvier.getmail.no (bouvier.getmail.no [84.210.184.8]) by mx1.freebsd.org (Postfix) with ESMTP id B095DCCB; Mon, 22 Sep 2014 19:41:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id E5D0240518; Mon, 22 Sep 2014 21:35:27 +0200 (CEST) Received: from bouvier.getmail.no ([127.0.0.1]) by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id b1W6-s1m4Jue; Mon, 22 Sep 2014 21:35:27 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id 7D28840591; Mon, 22 Sep 2014 21:35:27 +0200 (CEST) X-Virus-Scanned: amavisd-new at bouvier.get.c.bitbit.net Received: from bouvier.getmail.no ([127.0.0.1]) by localhost (bouvier.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id xQPwuIU_cre9; Mon, 22 Sep 2014 21:35:27 +0200 (CEST) Received: from onyx.thanelange.no (cm-84.208.179.208.getinternet.no [84.208.179.208]) by bouvier.getmail.no (Postfix) with ESMTP id A668840518; Mon, 22 Sep 2014 21:35:26 +0200 (CEST) Date: Mon, 22 Sep 2014 21:35:24 +0200 From: Gyrd Thane Lange To: Tijl Coosemans Subject: Re: [patch] syscons/vt keymap: Norwegian country code conflicts with default value Message-ID: <20140922213524.3b95b9a5@onyx.thanelange.no> In-Reply-To: <20140922192844.7de1bb6b@kalimero.tijl.coosemans.org> References: <20140921183936.03617590@onyx.thanelange.no> <54201192.5080906@freebsd.org> <20140922192844.7de1bb6b@kalimero.tijl.coosemans.org> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable stable , freebsd-current@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, 22 Sep 2014 19:41:28 -0000 On Mon, 22 Sep 2014 19:28:44 +0200 Tijl Coosemans wrote: > On Mon, 22 Sep 2014 14:09:54 +0200 Stefan Esser > wrote: > > Am 21.09.2014 um 18:39 schrieb Gyrd Thane Lange: > > > Hi, > > > > > > Recent changes in keymap namning for syscons/vt to use shorter > > > names has exposed a conflict with the value "no" both used as > > > country code for Norway and as a default value indicating that no > > > keymap is set. > > > > > > The attached patch proposes to use "" (empty string) as default > > > value instead. > > > > Hi Gyrd, > > > > thank you for reporting the issue! > > > > I have just committed a slightly different patch to -CURRENT and > > plan to merge it to 10-STABLE in time for the next BETA. > > > > You may want to check-out r271958 ... > > > > > > The approach I have chosen it to let "NO" continue to stand for "do > > not load any keymap", while "no" is now recognized as equivalent to > > "no.kbd". Thanks! That'll get the keymap working. > > The new semantics of the keymap parameter in rc.conf are: > > > > keymap='' ==> do not load any keymap (unchanged) > > keymap=NO ==> do not load any keymap (unchanged) > > keymap=no ==> load Norwegian keymap (new) > > > > This may still catch people that have edited rc.conf to use "no" in > > the meaning "no keymap" by accident, but I see no other approach > > that better complies with POLA ... > > Maybe NONE. It's already being used in a number of cases. My original patch suggested an empty string '', and I still favour that. That is already an accepted value for "no keyboard specified" and thus requires no code change to work. The keyboard setting next to keymap already use an empty string for a default value, so there is already precedent. Using NONE still risks the possibility of colliding with a valid file name in the future, but anything is better than NO. In general I think the use of NO as a default value should only be used when there exists a complementing YES value. In any case, whatever new default value (either empty or NONE) should be documented in defaults/rc.conf as the preferred way, in order to stop more users placing NO in the keymap setting. Additionally we can provide a warning in the syscons script for users that have used "NO" (capital case). Gyrd ^_^ From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 23:10:28 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AE81DA9F; Mon, 22 Sep 2014 23:10:28 +0000 (UTC) Received: from smtpout1.timeweb.ru (smtpout1.timeweb.ru [92.53.117.15]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5F4D776C; Mon, 22 Sep 2014 23:10:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=amdmi3.ru; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=B6Z3FikSfrl55baKNfiUysZCDcmpPt43pbYapnh6iJI=; b=Y/YQ1zHiBahOdDhUq18BoXiWIap5N11ByQnUwu+dl/YBDhPmzxncJv3NLEYDt+twFi5ef2Gi79D8Ispx/BTlt8NCd2ZHusDlaCSWXnvk6NnYXgVhBElx2kwvKkG8OqzxyA9SfM+Ob35wQj+EMyAcSgFtprU73oIgtFihbQqvnNQ=; Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XWCkL-0005h1-FB; Tue, 23 Sep 2014 03:10:17 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 0E8C1FC9; Tue, 23 Sep 2014 03:10:17 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id DD4F826785; Tue, 23 Sep 2014 03:10:16 +0400 (MSK) Date: Tue, 23 Sep 2014 03:10:16 +0400 From: Dmitry Marakasov To: freebsd-stable@FreeBSD.org Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <20140922231016.GA1301@hades.panopticon> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20140228154328.GA13454@hades.panopticon> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@freebsd.org, Dimitry Andric 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, 22 Sep 2014 23:10:28 -0000 * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > > > I've been getting some failure mails from pkg building cluster related > > > to clang crashes: > > > > > > http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2014-02-28_01h43m56s/logs/arx-libertatis-1.0.3_2.log > > > http://beefy1.isc.freebsd.org/bulk/head-i386-default/2014-02-21_03h01m36s/logs/supertuxkart-0.8.1.log > > > > > > At first I thought they'll go away with clang 3.4, but recently I've > > > added HEAD jail to my tinderbox and reproduced these. Also a reason > > > of crashes become apparent: c++ eats all available memoty (15G RSS > > > in my case). > > > > > > I though of investigating these further, but wanted to check if it's > > > already known first. > > > > There are a few known OOM bugs in 3.4, but from the logs it is not > > immediately apparent if you are hitting those, or if they are new bugs. > > Note that it affects both 3.3 and 3.4. I think it was triggered by > something unrelated to clang update, maybe libc++ update. > > > To be able to figure that out, we need the files mentioned in clang's > > diagnostic messages, e.g. for arx-libertatis: > > > > /tmp/Input-XkKTNq.cpp > > /tmp/Input-XkKTNq.sh > > Here's one from arx-libertatis: > > http://people.freebsd.org/~amdmi3/clang-eats-mem-bug.tar.bz2 > > The bug is reproducible on my 10.x with both system clang 3.3 (after > removing -vectorize-loops -vectorize-slp options) and with clang 3.4 > from ports. I'll just remind that this is still an issue, and it's getting into 10.1. Could we maybe disable compiler features with lead to these crashes? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 05:32:50 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5559BC5; Tue, 23 Sep 2014 05:32:50 +0000 (UTC) Received: from smtp1.tnnet.fi (smtp1.tnnet.fi [IPv6:2001:40e8:10:11:89:236:117:164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.tnnet.fi", Issuer "Go Daddy Secure Certification Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B79AE27; Tue, 23 Sep 2014 05:32:50 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.tnnet.fi (Postfix) with ESMTP id DE265181AE7; Tue, 23 Sep 2014 08:32:36 +0300 (EEST) X-Virus-Scanned: amavisd-new at tnnet.fi Received: from smtp1.tnnet.fi ([127.0.0.1]) by localhost (mx2.tnnet.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fL8BKzVn0ncW; Tue, 23 Sep 2014 08:32:34 +0300 (EEST) Received: from [192.168.0.2] (unknown [213.185.47.6]) by smtp1.tnnet.fi (Postfix) with ESMTP id 5B3EE1812CE; Tue, 23 Sep 2014 08:32:34 +0300 (EEST) Message-ID: <542105A3.4090507@iki.fi> Date: Tue, 23 Sep 2014 08:31:15 +0300 From: Pasi Parviainen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Dmitry Marakasov Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> In-Reply-To: <20140922231016.GA1301@hades.panopticon> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Dimitry Andric , freebsd-toolchain@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: Tue, 23 Sep 2014 05:32:50 -0000 On 23.9.2014 2:10, Dmitry Marakasov wrote: > * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: > >>>> I've been getting some failure mails from pkg building cluster related >>>> to clang crashes: >>>> >>>> http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2014-02-28_01h43m56s/logs/arx-libertatis-1.0.3_2.log >>>> http://beefy1.isc.freebsd.org/bulk/head-i386-default/2014-02-21_03h01m36s/logs/supertuxkart-0.8.1.log >>>> >>>> At first I thought they'll go away with clang 3.4, but recently I've >>>> added HEAD jail to my tinderbox and reproduced these. Also a reason >>>> of crashes become apparent: c++ eats all available memoty (15G RSS >>>> in my case). >>>> >>>> I though of investigating these further, but wanted to check if it's >>>> already known first. >>> >>> There are a few known OOM bugs in 3.4, but from the logs it is not >>> immediately apparent if you are hitting those, or if they are new bugs. >> >> Note that it affects both 3.3 and 3.4. I think it was triggered by >> something unrelated to clang update, maybe libc++ update. >> >>> To be able to figure that out, we need the files mentioned in clang's >>> diagnostic messages, e.g. for arx-libertatis: >>> >>> /tmp/Input-XkKTNq.cpp >>> /tmp/Input-XkKTNq.sh >> >> Here's one from arx-libertatis: >> >> http://people.freebsd.org/~amdmi3/clang-eats-mem-bug.tar.bz2 >> >> The bug is reproducible on my 10.x with both system clang 3.3 (after >> removing -vectorize-loops -vectorize-slp options) and with clang 3.4 >> from ports. > > I'll just remind that this is still an issue, and it's getting into > 10.1. Could we maybe disable compiler features with lead to these > crashes? > This seems to be same issue as in http://llvm.org/bugs/show_bug.cgi?id=20893 for which there is patch review going on http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/236415.html. Your test case is reproducible with the trunk of llvm/clang and the patch in review resolves it. Other workaround is to disable generation of debug information by removing -g flag. Pasi From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 07:11:56 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D22D0D4A for ; Tue, 23 Sep 2014 07:11:56 +0000 (UTC) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) (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 6A76E9BC for ; Tue, 23 Sep 2014 07:11:56 +0000 (UTC) Received: by mail-we0-f174.google.com with SMTP id w62so3575947wes.5 for ; Tue, 23 Sep 2014 00:11:54 -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=b+J0PWeSeZQXDiAJluihJnIVnqWGWfFUyfzRXiEdCFY=; b=HKPMi10oBT+O9ePhrYIdVD/WCvPaHavAXdcw2WnmYCQEbcPmHFLVe1bLN3UxX/bEvg saGNNb/DgbM1Pb78WwJG+n9T3CvbfA705juq8QMDqvG7H2mkI50mDAWkM/7abdTXpRN7 C+TBHmn0XRz5b63qqz6Onag1LUSxWJ8YJdtzUaSapURFTcomt40HbrGekON7Ha9PTja4 QWV4ricWIIVD29WRAxZk6o+nAX/7ag6gRxb2kDQI3JCVToU8EkGs0De3urOEEFOx47eT 35i8k4bNIEvgYFALA0QUNs1Oppli23mBaPyiaRI5TViq9bI6R/cJQB15q4SRDhCv45yh smjA== MIME-Version: 1.0 X-Received: by 10.194.88.167 with SMTP id bh7mr392353wjb.129.1411456314446; Tue, 23 Sep 2014 00:11:54 -0700 (PDT) Received: by 10.194.165.40 with HTTP; Tue, 23 Sep 2014 00:11:54 -0700 (PDT) Date: Tue, 23 Sep 2014 09:11:54 +0200 Message-ID: Subject: pkg 1.3.8 requested but not available? From: Cristiano Deana To: FreeBSD Stable Mailing List Content-Type: text/plain; charset=UTF-8 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, 23 Sep 2014 07:11:57 -0000 Hi, I was updating some installed port, when this happen: root:/tmp # uname -rms FreeBSD 9.3-RELEASE amd64 root:/tmp # portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. Ports tree hasn't changed since last snapshot. No updates needed. Ports tree is already up to date. root:/tmp # pkg update Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. root:/tmp # pkg info pkg pkg-1.3.7 Name : pkg Version : 1.3.7 Installed on : Tue Sep 2 09:25:53 CEST 2014 Origin : ports-mgmt/pkg Architecture : freebsd:9:x86:64 Prefix : /usr/local Categories : ports-mgmt Licenses : BSD2CLAUSE Maintainer : portmgr@FreeBSD.org WWW : http://wiki.freebsd.org/pkgng Comment : Package manager Shared Libs provided: libpkg.so.3 Flat size : 8.14MiB Description : Package management tool WWW: http://wiki.freebsd.org/pkgng root:/tmp # portupgrade -nr dbus ---> Session started at: Tue, 23 Sep 2014 09:08:37 +0200 ** Port marked as IGNORE: devel/dbus: pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. You must upgrade pkg(8) first ** Port marked as IGNORE: devel/eggdbus: pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. You must upgrade pkg(8) first ** Port marked as IGNORE: sysutils/policykit: pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. You must upgrade pkg(8) first ** Port marked as IGNORE: devel/gconf2: pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. You must upgrade pkg(8) first ** Port marked as IGNORE: devel/dbus-glib: pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. You must upgrade pkg(8) first ** Port marked as IGNORE: sysutils/polkit: pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. You must upgrade pkg(8) first ** Port marked as IGNORE: devel/dconf: pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. You must upgrade pkg(8) first ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) - devel/dbus (marked as IGNORE) - devel/eggdbus (marked as IGNORE) - sysutils/policykit (marked as IGNORE) - devel/gconf2 (marked as IGNORE) - devel/dbus-glib (marked as IGNORE) - sysutils/polkit (marked as IGNORE) - devel/dconf (marked as IGNORE) ---> Packages processed: 0 done, 7 ignored, 0 skipped and 0 failed ---> Session ended at: Tue, 23 Sep 2014 09:08:37 +0200 (consumed 00:00:00) root:/tmp # portupgrade pkg root:/tmp # pkg upgrade pkg Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking integrity... done (0 conflicting) Your packages are up to date. root:/tmp # what am I missing? -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 08:34:05 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21C4AF84 for ; Tue, 23 Sep 2014 08:34:05 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (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 A27531AC for ; Tue, 23 Sep 2014 08:34:04 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id fb4so4143627wid.4 for ; Tue, 23 Sep 2014 01:34:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=yu95iJRRNSCuKPmEseqa2R5J22i71zPMgyLxpOUbMfg=; b=S13tRCZflm09UQMGiwkLoJMSrLFtBctOMw0Qo4zmb4ZeF6ZJA3oDG2i2E17xOoxvnf yY7cfcAz8Z6O/+FreG7XFsnduYlUFNibbUKB2TdBUWy9mBqcq0FnFS20QIr8zRCGqPx8 4K1l6k7GR8VIhbRNk8kole48vAD6imTJyFdiuuddd5cnyA+evxyMXJcm6DGzEBcMGAn2 2ssYCYof5m9a86FmGI1+/AsN5onPETaH15ojIkE2Y6+aqE9EtyQ6XgOo+e2u0LBY1y9L IFIP+ZJPGVMHoLAITM4Ie7Km6HnoqT9orKQvx5xNBzX865xuyzrkpCWl2vIM0wLF0S3J vS7g== X-Received: by 10.180.91.133 with SMTP id ce5mr20662440wib.62.1411461242682; Tue, 23 Sep 2014 01:34:02 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id u10sm1440178wix.2.2014.09.23.01.34.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Sep 2014 01:34:01 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 23 Sep 2014 10:33:59 +0200 From: Baptiste Daroussin To: Cristiano Deana Subject: Re: pkg 1.3.8 requested but not available? Message-ID: <20140923083359.GA20383@ivaldir.etoilebsd.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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: Tue, 23 Sep 2014 08:34:05 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 23, 2014 at 09:11:54AM +0200, Cristiano Deana wrote: > Hi, I was updating some installed port, when this happen: >=20 > root:/tmp # uname -rms > FreeBSD 9.3-RELEASE amd64 >=20 > root:/tmp # portsnap fetch update > Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. > Fetching snapshot tag from ec2-eu-west-1.portsnap.freebsd.org... done. > Ports tree hasn't changed since last snapshot. > No updates needed. > Ports tree is already up to date. >=20 > root:/tmp # pkg update > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. >=20 > root:/tmp # pkg info pkg > pkg-1.3.7 > Name : pkg > Version : 1.3.7 > Installed on : Tue Sep 2 09:25:53 CEST 2014 > Origin : ports-mgmt/pkg > Architecture : freebsd:9:x86:64 > Prefix : /usr/local > Categories : ports-mgmt > Licenses : BSD2CLAUSE > Maintainer : portmgr@FreeBSD.org > WWW : http://wiki.freebsd.org/pkgng > Comment : Package manager > Shared Libs provided: > libpkg.so.3 > Flat size : 8.14MiB > Description : > Package management tool >=20 > WWW: http://wiki.freebsd.org/pkgng >=20 > root:/tmp # portupgrade -nr dbus > ---> Session started at: Tue, 23 Sep 2014 09:08:37 +0200 > ** Port marked as IGNORE: devel/dbus: > pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > You must upgrade pkg(8) first > ** Port marked as IGNORE: devel/eggdbus: > pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > You must upgrade pkg(8) first > ** Port marked as IGNORE: sysutils/policykit: > pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > You must upgrade pkg(8) first > ** Port marked as IGNORE: devel/gconf2: > pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > You must upgrade pkg(8) first > ** Port marked as IGNORE: devel/dbus-glib: > pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > You must upgrade pkg(8) first > ** Port marked as IGNORE: sysutils/polkit: > pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > You must upgrade pkg(8) first > ** Port marked as IGNORE: devel/dconf: > pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > You must upgrade pkg(8) first > ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) > - devel/dbus (marked as IGNORE) > - devel/eggdbus (marked as IGNORE) > - sysutils/policykit (marked as IGNORE) > - devel/gconf2 (marked as IGNORE) > - devel/dbus-glib (marked as IGNORE) > - sysutils/polkit (marked as IGNORE) > - devel/dconf (marked as IGNORE) > ---> Packages processed: 0 done, 7 ignored, 0 skipped and 0 failed > ---> Session ended at: Tue, 23 Sep 2014 09:08:37 +0200 (consumed 00:00:0= 0) >=20 > root:/tmp # portupgrade pkg >=20 > root:/tmp # pkg upgrade pkg > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > Checking integrity... done (0 conflicting) > Your packages are up to date. >=20 > root:/tmp # >=20 > what am I missing? You are using portupgrade so first upgrade pkg with portupgrade regards, Bapt --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlQhMHcACgkQ8kTtMUmk6EwOGwCbB4tPs897etFHed2UxHfVx81r c5EAn0gbRCaJkLirQlWnPDl+EHVqVOAA =DulG -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 08:55:57 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 42BFE6DC; Tue, 23 Sep 2014 08:55:57 +0000 (UTC) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (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 7EC4B63C; Tue, 23 Sep 2014 08:55:56 +0000 (UTC) Received: from mh0.gentlemail.de (mh0.gentlemail.de [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id s8N8tqix074200; Tue, 23 Sep 2014 10:55:52 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 91F8E3EDC; Tue, 23 Sep 2014 10:55:52 +0200 (CEST) Message-ID: <54213597.1070905@omnilan.de> Date: Tue, 23 Sep 2014 10:55:51 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Stefan Esser Subject: Re: option *KB*_DFLT_KEYMAP and *map.h in sys/conf/files References: <54158866.2050901@omnilan.de> <5416BF7A.1080301@freebsd.org> <5416F0B1.1020200@omnilan.de> <5417D137.6030303@freebsd.org> In-Reply-To: <5417D137.6030303@freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigAA223CE85BD6B27E4B93C2E0" X-Greylist: ACL 119 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Tue, 23 Sep 2014 10:55:52 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) 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: Tue, 23 Sep 2014 08:55:57 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigAA223CE85BD6B27E4B93C2E0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Bez=C3=BCglich Stefan Esser's Nachricht vom 16.09.2014 07:57 (localtime)= : > =E2=80=A6 > Yes, it seems that nobody compiles non-standard keyboards into the > kernel. I tried again, but neither the traditional way to build the > kernel (with "config") nor "make buildkernel" in /usr/src created > the required include file(s) "atkbdmap.h" or "ukbdmap.h" seem to work > on -CURRENT. > > I do not have time to diagnose this problem, though Trying to help out=E2=80=A6 I went to a -current machine and found no problems compiling a kernel with non-default keymap, besides the limitations discussed. I prepared a simple patch, which enables the usage of any valid keymap name, regardless of the building machine's active console. Also, it uses the keymaps from sources instead of the ones installed on the building machine. I opened a bug report for that: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193865 Don't know if component kern is really best choice=E2=80=A6 Maybe "conf" = matches better? Can you review/comment? Thanks, -Harry --------------enigAA223CE85BD6B27E4B93C2E0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlQhNZcACgkQLDqVQ9VXb8h5cgCgxLCBC9Gohxi9X4rd209KYzFG mCoAoMiNfNxSBZxLLUaApXUXep78f5a4 =Yxm4 -----END PGP SIGNATURE----- --------------enigAA223CE85BD6B27E4B93C2E0-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:02:22 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D00B9A5; Tue, 23 Sep 2014 09:02:22 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id 5363B774; Tue, 23 Sep 2014 09:02:20 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NCC0057UJYET300@hades.sorbs.net>; Tue, 23 Sep 2014 02:06:15 -0700 (PDT) Message-id: <54213713.7020200@sorbs.net> Date: Tue, 23 Sep 2014 11:02:11 +0200 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Baptiste Daroussin Subject: Re: pkg 1.3.8 requested but not available? References: <20140923083359.GA20383@ivaldir.etoilebsd.net> In-reply-to: <20140923083359.GA20383@ivaldir.etoilebsd.net> Cc: "ports@freebsd.org" , Cristiano Deana , 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: Tue, 23 Sep 2014 09:02:22 -0000 Baptiste Daroussin wrote: > >> root:/tmp # portupgrade -nr dbus >> ---> Session started at: Tue, 23 Sep 2014 09:08:37 +0200 >> ** Port marked as IGNORE: devel/dbus: >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. >> You must upgrade pkg(8) first >> ** Port marked as IGNORE: devel/eggdbus: >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. >> You must upgrade pkg(8) first >> ** Port marked as IGNORE: sysutils/policykit: >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. >> You must upgrade pkg(8) first >> ** Port marked as IGNORE: devel/gconf2: >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. >> You must upgrade pkg(8) first >> ** Port marked as IGNORE: devel/dbus-glib: >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. >> You must upgrade pkg(8) first >> ** Port marked as IGNORE: sysutils/polkit: >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. >> You must upgrade pkg(8) first >> ** Port marked as IGNORE: devel/dconf: >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. >> You must upgrade pkg(8) first >> ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) >> - devel/dbus (marked as IGNORE) >> - devel/eggdbus (marked as IGNORE) >> - sysutils/policykit (marked as IGNORE) >> - devel/gconf2 (marked as IGNORE) >> - devel/dbus-glib (marked as IGNORE) >> - sysutils/polkit (marked as IGNORE) >> - devel/dconf (marked as IGNORE) >> ---> Packages processed: 0 done, 7 ignored, 0 skipped and 0 failed >> ---> Session ended at: Tue, 23 Sep 2014 09:08:37 +0200 (consumed 00:00:00) >> >> root:/tmp # portupgrade pkg >> >> root:/tmp # pkg upgrade pkg >> Updating FreeBSD repository catalogue... >> FreeBSD repository is up-to-date. >> All repositories are up-to-date. >> Checking integrity... done (0 conflicting) >> Your packages are up to date. >> >> root:/tmp # >> >> what am I missing? >> > > You are using portupgrade so first upgrade pkg with portupgrade > > Just a thought here - why (like .rpm and .deb - and the reason I hate them so much) are you making the package manager version a dependency of a package? I can understand if there are new features that you may need to use a later version to get those features, but making a package dependent on the package manager rather than displaying a warning that a feature is missing is the brain dead way that plagues upgrades for redhat and debian. Of course if your intent is to make FreeBSD into another Linux distro just with a different kernel, continue. -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:09:30 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0A14ABCF; Tue, 23 Sep 2014 09:09:30 +0000 (UTC) Received: from smtp.peterschmitt.fr (smtp.peterschmitt.fr [IPv6:2a01:4f8:a0:72c8:4224::1]) by mx1.freebsd.org (Postfix) with ESMTP id BF60A7CC; Tue, 23 Sep 2014 09:09:29 +0000 (UTC) Received: from [192.168.0.83] (unknown [82.226.113.5]) by smtp.peterschmitt.fr (Postfix) with ESMTPSA id 8764020534; Tue, 23 Sep 2014 11:09:18 +0200 (CEST) Message-ID: <542138B9.3060600@peterschmitt.fr> Date: Tue, 23 Sep 2014 11:09:13 +0200 From: Florent Peterschmitt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.0 MIME-Version: 1.0 To: Michelle Sullivan Subject: Re: pkg 1.3.8 requested but not available? References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> In-Reply-To: <54213713.7020200@sorbs.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HcUuCwhc1mkWxjT1tLs7tBgJAUgPfvA7O" Cc: "ports@freebsd.org" , 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: Tue, 23 Sep 2014 09:09:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --HcUuCwhc1mkWxjT1tLs7tBgJAUgPfvA7O Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Le 23/09/2014 11:02, Michelle Sullivan a =E9crit : > Baptiste Daroussin wrote: >> [...] >> You are using portupgrade so first upgrade pkg with portupgrade >> >> =20 >=20 > Just a thought here - why (like .rpm and .deb - and the reason I hate > them so much) are you making the package manager version a dependency o= f > a package? I can understand if there are new features that you may nee= d > to use a later version to get those features, but making a package > dependent on the package manager rather than displaying a warning that = a > feature is missing is the brain dead way that plagues upgrades for > redhat and debian. Of course if your intent is to make FreeBSD into > another Linux distro just with a different kernel, continue. >=20 What is the problem of upgrading the package manager first and then upgrade the rest of the world without any problem? --HcUuCwhc1mkWxjT1tLs7tBgJAUgPfvA7O Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUITi5AAoJEFr01BkajbiB+EUP/2lUsEn9NGuQH9PtmVN6SZLX v18urrZi5ExHYQ+PqUvTsNul35z02ri9X/OBuNhjJrdfMPmm+RRuD3RuseE0+Pj1 OEPT5UHPRHhfoIVAetu8Qnpc95rzlr8TI6GfrHwj6VlWkOJNX8sog+yklWDXIY2g nh/rfUKOI5+753Cht9ghNm7qlBlSVF5W2F45gkNMKzaUh0GrFBt/HbQGoATK0OA7 vMQyCwdcCLp+ld0X09VBwFvK60XL2b/Nvei/rQFAixM+1VgdLNxzInb7hy9cs4B9 B+xqbTpvEXjH69r5nxV5VHbmFMoWfBO4/anwdDcT9MObWB28qoW/fyMQreNUcMot LIFpADQ2rgvKeCa/blf6jgfD/dUq5GjiBB1Dz6NcqZ8pHqMoTrKLeRlRgHQ6noG9 30l3xFOiCEzf1HfpNo5QcE19ZIEHvGb0Zm5bLIeEFsst+s19c8M6WoijJVy7MAwr A12xIBiE8Sd/q2JIed+awiD0kuReqFx2rD0wBlU975FZqZfcWX71HDNTfZjOmktW pNSvhNmpTeD8lssa38Qj+l81knhA3kHPt6YzsEcB1pAtFK6dHghSWex/7oFxuAWO Aoj3xd7vgyfO7V/kcuXqBydWA0jvHdGtpA+cTylFY+NlB1kzbgbtZZNUrkoMH5Nj 4XPjgaaZ2nv/KKAZHxNl =BoMt -----END PGP SIGNATURE----- --HcUuCwhc1mkWxjT1tLs7tBgJAUgPfvA7O-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:09:44 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0307DD4B; Tue, 23 Sep 2014 09:09:44 +0000 (UTC) Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::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 5D0797DA; Tue, 23 Sep 2014 09:09:43 +0000 (UTC) Received: by mail-we0-f173.google.com with SMTP id x48so2781368wes.18 for ; Tue, 23 Sep 2014 02:09:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=bnIELgvLK89KVaH7MmBY0vrMK0EY1gbBmllLoW2aA8g=; b=CfL1sgXIUe6cBTgMrPvFsgPMVo6Ic5oZUOlhwfK+jqOi9Rbdmt7zYgKbmp0Nl4Fq9R UG6kVs9xGBg/st+bi/N6g6scmpR8TLg+yrb+IYENo2v/dEtsXRRzE0EBUCb3GzI+muqs TL/MA0qdFsLaMlUJwBCIykcgDTA8lP3Dtq99PyCOU5hFfBW9MS2kL0foV72LLqB1S0HV newY5IykoMqQpFoRcPbIZmUv8XxEUpMTToBpBMWiN1gAEFD+NTJAFoBZt5vlMHSawn4O faRuMQMtoMClRHygj7vSiHq/c/FfsCAKt5en4Sc6Y+DHkOZbmOMgA/4mFlnPdLfDceoI e5dQ== X-Received: by 10.194.81.230 with SMTP id d6mr26942791wjy.49.1411463381491; Tue, 23 Sep 2014 02:09:41 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id mc4sm1541989wic.6.2014.09.23.02.09.39 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Sep 2014 02:09:40 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 23 Sep 2014 11:09:38 +0200 From: Baptiste Daroussin To: Michelle Sullivan Subject: Re: pkg 1.3.8 requested but not available? Message-ID: <20140923090937.GB20383@ivaldir.etoilebsd.net> References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="R3G7APHDIzY6R/pk" Content-Disposition: inline In-Reply-To: <54213713.7020200@sorbs.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "ports@freebsd.org" , Cristiano Deana , 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: Tue, 23 Sep 2014 09:09:44 -0000 --R3G7APHDIzY6R/pk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 23, 2014 at 11:02:11AM +0200, Michelle Sullivan wrote: > Baptiste Daroussin wrote: > > > >> root:/tmp # portupgrade -nr dbus > >> ---> Session started at: Tue, 23 Sep 2014 09:08:37 +0200 > >> ** Port marked as IGNORE: devel/dbus: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: devel/eggdbus: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: sysutils/policykit: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: devel/gconf2: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: devel/dbus-glib: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: sysutils/polkit: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: devel/dconf: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) > >> - devel/dbus (marked as IGNORE) > >> - devel/eggdbus (marked as IGNORE) > >> - sysutils/policykit (marked as IGNORE) > >> - devel/gconf2 (marked as IGNORE) > >> - devel/dbus-glib (marked as IGNORE) > >> - sysutils/polkit (marked as IGNORE) > >> - devel/dconf (marked as IGNORE) > >> ---> Packages processed: 0 done, 7 ignored, 0 skipped and 0 failed > >> ---> Session ended at: Tue, 23 Sep 2014 09:08:37 +0200 (consumed 00:0= 0:00) > >> > >> root:/tmp # portupgrade pkg > >> > >> root:/tmp # pkg upgrade pkg > >> Updating FreeBSD repository catalogue... > >> FreeBSD repository is up-to-date. > >> All repositories are up-to-date. > >> Checking integrity... done (0 conflicting) > >> Your packages are up to date. > >> > >> root:/tmp # > >> > >> what am I missing? > >> =20 > > > > You are using portupgrade so first upgrade pkg with portupgrade > > > > =20 >=20 > Just a thought here - why (like .rpm and .deb - and the reason I hate > them so much) are you making the package manager version a dependency of > a package? I can understand if there are new features that you may need > to use a later version to get those features, but making a package > dependent on the package manager rather than displaying a warning that a > feature is missing is the brain dead way that plagues upgrades for > redhat and debian. Of course if your intent is to make FreeBSD into > another Linux distro just with a different kernel, continue. >=20 There are new feature, that is why, the required version will be only bumped when there will be new features used by the ports tree, not on every pkg bu= mp regards, Bapt --R3G7APHDIzY6R/pk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlQhONEACgkQ8kTtMUmk6EzAwgCdFw+yPFQtsiD/UUc3QMVgkm88 KvwAn3nDosHwtoKhi5IfFZsL9lugY/Xn =gncm -----END PGP SIGNATURE----- --R3G7APHDIzY6R/pk-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:42:34 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0C1F5AD4; Tue, 23 Sep 2014 09:42:34 +0000 (UTC) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (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 72647BF9; Tue, 23 Sep 2014 09:42:33 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id q5so4637474wiv.10 for ; Tue, 23 Sep 2014 02:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=B+bBQmUsiccHAV4lOVp3sQUM57pNJ5TFSG1/62Rouic=; b=jOHwrE4pZj7jdw01LWonNVBI7bwHXaydK4wHu6sLbqZoR6iYKGte2gbuqHVvCJJfZ4 UHJN9mUmt3t5ViUJ8rsf+6EJRGQYsyLOcdjEhV/7FIdnmuNeNJm3MNtOQ6s9FrjbGUX3 62QMjtK+yiNiD/z1G6MtGaIGCokgUnuAjJ8g1Pt0CXFFnkRxQWHwxgyifhU17EAvnqUp XzdscWmIkbepplx+/d8uC9FNvuUHm3o+1WYFs1/ET8bCOAULjq3jp1Z/xijqW1PCrDBL P79uDD1Z/BO+Quml3TMlRDOYq7c4bkuiWh93A6uYo8TdxTdenbsbjtLwXMpDYJYTdJnJ +O1A== MIME-Version: 1.0 X-Received: by 10.194.191.135 with SMTP id gy7mr26404112wjc.39.1411465351669; Tue, 23 Sep 2014 02:42:31 -0700 (PDT) Received: by 10.194.165.40 with HTTP; Tue, 23 Sep 2014 02:42:31 -0700 (PDT) In-Reply-To: <20140923083359.GA20383@ivaldir.etoilebsd.net> References: <20140923083359.GA20383@ivaldir.etoilebsd.net> Date: Tue, 23 Sep 2014 11:42:31 +0200 Message-ID: Subject: Re: pkg 1.3.8 requested but not available? From: Cristiano Deana To: Baptiste Daroussin Content-Type: text/plain; charset=UTF-8 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: Tue, 23 Sep 2014 09:42:34 -0000 On Tue, Sep 23, 2014 at 10:33 AM, Baptiste Daroussin wrote: Hi Baptiste, >> root:/tmp # portupgrade pkg >> >> root:/tmp # pkg upgrade pkg >> Updating FreeBSD repository catalogue... >> FreeBSD repository is up-to-date. >> All repositories are up-to-date. >> Checking integrity... done (0 conflicting) >> Your packages are up to date. > You are using portupgrade so first upgrade pkg with portupgrade I already tried to. It seems like there isn't any pkg-1.3.8 -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:44:10 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2DCA8F9B; Tue, 23 Sep 2014 09:44:10 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id 84F37C29; Tue, 23 Sep 2014 09:44:07 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=windows-1252 Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NCC00584LW6T300@hades.sorbs.net>; Tue, 23 Sep 2014 02:48:08 -0700 (PDT) Message-id: <542140E4.6050605@sorbs.net> Date: Tue, 23 Sep 2014 11:44:04 +0200 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Florent Peterschmitt Subject: Re: pkg 1.3.8 requested but not available? References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> <542138B9.3060600@peterschmitt.fr> In-reply-to: <542138B9.3060600@peterschmitt.fr> Cc: "ports@freebsd.org" , 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: Tue, 23 Sep 2014 09:44:10 -0000 Florent Peterschmitt wrote: > Le 23/09/2014 11:02, Michelle Sullivan a écrit : > >> Baptiste Daroussin wrote: >> >>> [...] >>> You are using portupgrade so first upgrade pkg with portupgrade >>> >>> >>> >> Just a thought here - why (like .rpm and .deb - and the reason I hate >> them so much) are you making the package manager version a dependency of >> a package? I can understand if there are new features that you may need >> to use a later version to get those features, but making a package >> dependent on the package manager rather than displaying a warning that a >> feature is missing is the brain dead way that plagues upgrades for >> redhat and debian. Of course if your intent is to make FreeBSD into >> another Linux distro just with a different kernel, continue. >> >> > > What is the problem of upgrading the package manager first and then > upgrade the rest of the world without any problem? > > Not disagreeing with you... but making dependencies like this leads to everything relying on the package manager being a particular version.. which in my opinion is wrong... the package manager is not part of the software you're installing... and shouldn't be part of a dependency tree - particularly when building your own ports. *Every* time a Redhat and Debian system screwed up that I have had, was caused by the package manager needing to be updated before a particular package, then all the other dependent packages needed to be upgraded, and the libraries and you end up with the catch 22 of the package manager can't be installed because the package manager is too old and you end up with a half working system that needs to be re-installed because you needed to apply a security fix to a perl module....! Now FreeBSD has one advantage (currently) ... the package manager is not part of the OS, it in itself is a port.. however that has half changed already and in what, another month? it's going to be part of the OS... Yeah sure keep building pkg-static so it can be installed independently, but be aware that one does not want to get into dependency loops or having to upgrade everything just for one security fix - particularly when working with the ports tree and not the package manager... some people have production servers that need a security fix, not an upgrade of everything. -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:54: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 98B317BD for ; Tue, 23 Sep 2014 09:54:52 +0000 (UTC) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) (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 26D45D6B for ; Tue, 23 Sep 2014 09:54:52 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id t60so4302779wes.37 for ; Tue, 23 Sep 2014 02:54:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=LMhgQiCJjLrQGPS3wvqrIfGcRd8nWx3DH/ToGoU52z0=; b=VMyWW2a+Hc80yRIH8sE2aKy5G20hAq/Lu0MZcJJIxl5UgdlvPdsJDY+k+y/xTWH4ti mS3J8ffyZ3gULQ0YgVRQLzG5DdodkpkWE9ZVOiOq96J0dS4si2RUElZFk6Zp9esnmA6v oJn4uQNIJt1C5DtTKycWBUxa366IaVXfsnz32sSRgkG1Dn5VaQFRFUqGpw7S/X2j7kWY Oq1KGiCXQ2ELss8CtWKrQmOG9JK0Bkk+vYwVkx3ujwtXw6tq/HpdFV3NLj7EWFE99wiw 3DY9p3S1DunVGyUHmTOqEjRJ729FUgWd6YeapgDUN45arVmtQv2fLuuQI3vqECmQbCla MS6Q== X-Received: by 10.194.186.178 with SMTP id fl18mr26670478wjc.8.1411466090302; Tue, 23 Sep 2014 02:54:50 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id hi4sm15251858wjb.46.2014.09.23.02.54.48 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Sep 2014 02:54:49 -0700 (PDT) Sender: Baptiste Daroussin Date: Tue, 23 Sep 2014 11:54:47 +0200 From: Baptiste Daroussin To: Cristiano Deana Subject: Re: pkg 1.3.8 requested but not available? Message-ID: <20140923095447.GC20383@ivaldir.etoilebsd.net> References: <20140923083359.GA20383@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="JWEK1jqKZ6MHAcjA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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: Tue, 23 Sep 2014 09:54:52 -0000 --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 23, 2014 at 11:42:31AM +0200, Cristiano Deana wrote: > On Tue, Sep 23, 2014 at 10:33 AM, Baptiste Daroussin w= rote: >=20 > Hi Baptiste, >=20 > >> root:/tmp # portupgrade pkg > >> > >> root:/tmp # pkg upgrade pkg > >> Updating FreeBSD repository catalogue... > >> FreeBSD repository is up-to-date. > >> All repositories are up-to-date. > >> Checking integrity... done (0 conflicting) > >> Your packages are up to date. >=20 > > You are using portupgrade so first upgrade pkg with portupgrade >=20 > I already tried to. It seems like there isn't any pkg-1.3.8 The commits that have added the warning also have added pkg-1.3.8 into the = ports tree. regards, Bapt --JWEK1jqKZ6MHAcjA Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlQhQ2cACgkQ8kTtMUmk6EwWZgCgiBtXF1Frn3ae+/eRKL7WdUz7 UVkAn0w/McglGV8ne30W+5qL1FObWCLP =FONB -----END PGP SIGNATURE----- --JWEK1jqKZ6MHAcjA-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:55:28 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF2548AC; Tue, 23 Sep 2014 09:55:28 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (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 2E305D7C; Tue, 23 Sep 2014 09:55:28 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id fb4so4262802wid.2 for ; Tue, 23 Sep 2014 02:55:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ugHQCXVcGCVuW7g/CpL4ei/zj0UHa2n4m0tt+Sn2rLI=; b=G8HR8r9CFoUrJkwSB/Gnl702fG70WKizmfYf43/x37YiFkaxkcqUTgW3Pj3Q6/KW5q hy57p0EHFtJ4KSmxOBuyAuywamwBwXQQYHAQjdDBcoxuO/+SPn/qYhDf/A9MrRBOpoep xhjSYiKxAP8vohq93M2bKtDKqNqyu4oK/pG7Mcnt9Zois5bgSjyFHPDkhMDWWMYcwabW AFeUj6/FHwdkaxA4keYyQCXVxmz408Z5+5sd1PCLnPrD4+odV5k2PRUGqSkZJaeEl95Q a4GI5IvB463d66/xBnShzUIe7rMfq2LPA9gekq02+xWG8V1g1SwLo+oZkXztaNBS7syR D8pQ== MIME-Version: 1.0 X-Received: by 10.194.179.73 with SMTP id de9mr10203507wjc.87.1411466126498; Tue, 23 Sep 2014 02:55:26 -0700 (PDT) Received: by 10.194.165.40 with HTTP; Tue, 23 Sep 2014 02:55:26 -0700 (PDT) In-Reply-To: References: <20140923083359.GA20383@ivaldir.etoilebsd.net> Date: Tue, 23 Sep 2014 11:55:26 +0200 Message-ID: Subject: Re: pkg 1.3.8 requested but not available? From: Cristiano Deana To: Baptiste Daroussin Content-Type: text/plain; charset=UTF-8 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: Tue, 23 Sep 2014 09:55:28 -0000 [SOLVED] On Tue, Sep 23, 2014 at 11:42 AM, Cristiano Deana wrote: > On Tue, Sep 23, 2014 at 10:33 AM, Baptiste Daroussin wrote: > > Hi Baptiste, > >>> root:/tmp # portupgrade pkg >>> >>> root:/tmp # pkg upgrade pkg >>> Updating FreeBSD repository catalogue... >>> FreeBSD repository is up-to-date. >>> All repositories are up-to-date. >>> Checking integrity... done (0 conflicting) >>> Your packages are up to date. > >> You are using portupgrade so first upgrade pkg with portupgrade > > I already tried to. It seems like there isn't any pkg-1.3.8 cd /usr/ports/ports-mgmt/pkg && make deinstall reinstall -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:58:21 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2488BAAB; Tue, 23 Sep 2014 09:58:21 +0000 (UTC) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BD52BDAE; Tue, 23 Sep 2014 09:58:19 +0000 (UTC) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id s8N9fmO5078256 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 23 Sep 2014 11:41:52 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-stable@freebsd.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.9/8.14.9) with ESMTP id s8N9fUAl059072; Tue, 23 Sep 2014 16:41:31 +0700 (NOVT) (envelope-from eugen@grosbein.net) Message-ID: <5421404A.7060606@grosbein.net> Date: Tue, 23 Sep 2014 16:41:30 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Baptiste Daroussin , Michelle Sullivan Subject: Re: pkg 1.3.8 requested but not available? References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> <20140923090937.GB20383@ivaldir.etoilebsd.net> In-Reply-To: <20140923090937.GB20383@ivaldir.etoilebsd.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net Cc: "ports@freebsd.org" , Cristiano Deana , 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: Tue, 23 Sep 2014 09:58:21 -0000 On 23.09.2014 16:09, Baptiste Daroussin wrote: >> Just a thought here - why (like .rpm and .deb - and the reason I hate >> them so much) are you making the package manager version a dependency of >> a package? I can understand if there are new features that you may need >> to use a later version to get those features, but making a package >> dependent on the package manager rather than displaying a warning that a >> feature is missing is the brain dead way that plagues upgrades for >> redhat and debian. Of course if your intent is to make FreeBSD into >> another Linux distro just with a different kernel, continue. >> > > There are new feature, that is why, the required version will be only bumped > when there will be new features used by the ports tree, not on every pkg bump Please, please do document what new features resulted in MINIMAL_PKG_VERSION bump. And please, delay bumping of MINIMAL_PKG_VERSION until packages of pkg itself are available from the repo. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 09:59:10 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1359AC39; Tue, 23 Sep 2014 09:59:10 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C45ADDCD; Tue, 23 Sep 2014 09:59:09 +0000 (UTC) Received: from [192.168.2.2] (unknown [77.243.161.229]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 1A5F8B803; Tue, 23 Sep 2014 11:58:58 +0200 (CEST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD From: Dimitry Andric In-Reply-To: <542105A3.4090507@iki.fi> Date: Tue, 23 Sep 2014 11:58:49 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> <542105A3.4090507@iki.fi> To: Pasi Parviainen X-Mailer: Apple Mail (2.1878.6) Cc: Dmitry Marakasov , freebsd-stable@FreeBSD.org, freebsd-toolchain@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: Tue, 23 Sep 2014 09:59:10 -0000 On 23 Sep 2014, at 07:31, Pasi Parviainen = wrote: > On 23.9.2014 2:10, Dmitry Marakasov wrote: >> * Dmitry Marakasov (amdmi3@amdmi3.ru) wrote: >>>>> I've been getting some failure mails from pkg building cluster = related >>>>> to clang crashes: >>>>>=20 >>>>> = http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2014-02-28_01h43m56s= /logs/arx-libertatis-1.0.3_2.log >>>>> = http://beefy1.isc.freebsd.org/bulk/head-i386-default/2014-02-21_03h01m36s/= logs/supertuxkart-0.8.1.log ... >>> http://people.freebsd.org/~amdmi3/clang-eats-mem-bug.tar.bz2 >>>=20 >>> The bug is reproducible on my 10.x with both system clang 3.3 (after >>> removing -vectorize-loops -vectorize-slp options) and with clang 3.4 >>> from ports. >>=20 >> I'll just remind that this is still an issue, and it's getting into >> 10.1. Could we maybe disable compiler features with lead to these >> crashes? >>=20 >=20 > This seems to be same issue as in = http://llvm.org/bugs/show_bug.cgi?id=3D20893 for which there is patch = review going = onhttp://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/236= 415.html. >=20 > Your test case is reproducible with the trunk of llvm/clang and the = patch in review resolves it. Other workaround is to disable generation = of debug information by removing -g flag. Hm, I had assumed this problem was fixed by importing r203311 from upstream llvm trunk, in head r263313. But apparently it is not. The upstream patch seems to fix your specific test case, but it is still in review, so I prefer to wait until it is actually committed, before I import it. -Dimitry From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 10:00: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C16BEE71; Tue, 23 Sep 2014 10:00:12 +0000 (UTC) Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) (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 327F8DFB; Tue, 23 Sep 2014 10:00:12 +0000 (UTC) Received: by mail-we0-f182.google.com with SMTP id u57so2385470wes.13 for ; Tue, 23 Sep 2014 03:00:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qnHp5vzoj0jN3mgoCPhXLB1rdukRegr3YbrmYHvnkxw=; b=eL4rxYDCSVgd9rL0y6snyifZqwJoVrO7Jwb0XJJVNdc46rxcSy5k9p7wBTl7nBNSLZ 2hGLyLOo74DQSdNPGZXQpxWBfUysd7HDM3oYMgnTnwjw25qFKG5cPGN+HbL4qywK6CkJ W5pPIGBd1FMVo8qMK1dJXC/dS46t5Rv7PXDCtknQuQdHyyjUAYsD660iLrG0Sy+H4hVP l2iPtU3fQXM9AZBD+NSGz9TZDvW3N7xiP5Es5cNz4mI/6X4Alg6XmieSliDdjYyM81/K qiNd/lHTqh5is3wp8JlfbuheyPTrvgvVMdBBtnB9c/kvYMzVYM98ncvz9/I3BfK5bFiN 3yZw== MIME-Version: 1.0 X-Received: by 10.194.191.135 with SMTP id gy7mr26507442wjc.39.1411466410497; Tue, 23 Sep 2014 03:00:10 -0700 (PDT) Received: by 10.194.165.40 with HTTP; Tue, 23 Sep 2014 03:00:10 -0700 (PDT) In-Reply-To: <20140923095447.GC20383@ivaldir.etoilebsd.net> References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <20140923095447.GC20383@ivaldir.etoilebsd.net> Date: Tue, 23 Sep 2014 12:00:10 +0200 Message-ID: Subject: Re: pkg 1.3.8 requested but not available? From: Cristiano Deana To: Baptiste Daroussin Content-Type: text/plain; charset=UTF-8 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: Tue, 23 Sep 2014 10:00:12 -0000 On Tue, Sep 23, 2014 at 11:54 AM, Baptiste Daroussin wrote: Hi, > The commits that have added the warning also have added pkg-1.3.8 into the ports > tree. you're right. It was. But neither portupgrade or pkg seems to know about it. As I wrote before, just solved with: cd /usr/ports/ports-mgmt/pkg && make && make deinstall reinstall Thank you -- Cris, member of G.U.F.I Italian FreeBSD User Group http://www.gufi.org/ From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 10:02:22 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BD0B2401; Tue, 23 Sep 2014 10:02:22 +0000 (UTC) Received: from smtp.peterschmitt.fr (gentiane.peterschmitt.fr [213.239.219.91]) by mx1.freebsd.org (Postfix) with ESMTP id 438E8EF5; Tue, 23 Sep 2014 10:02:21 +0000 (UTC) Received: from [192.168.0.83] (unknown [82.226.113.5]) by smtp.peterschmitt.fr (Postfix) with ESMTPSA id 0CC8720637; Tue, 23 Sep 2014 12:02:19 +0200 (CEST) Message-ID: <54214527.4020906@peterschmitt.fr> Date: Tue, 23 Sep 2014 12:02:15 +0200 From: Florent Peterschmitt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.0 MIME-Version: 1.0 To: Michelle Sullivan Subject: Re: pkg 1.3.8 requested but not available? References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> <542138B9.3060600@peterschmitt.fr> <542140E4.6050605@sorbs.net> In-Reply-To: <542140E4.6050605@sorbs.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QpwLMmCkTmvHN9E12hcemchhwEd163U25" Cc: "ports@freebsd.org" , 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: Tue, 23 Sep 2014 10:02:22 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QpwLMmCkTmvHN9E12hcemchhwEd163U25 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Le 23/09/2014 11:44, Michelle Sullivan a =E9crit : > Florent Peterschmitt wrote: >> Le 23/09/2014 11:02, Michelle Sullivan a =E9crit : >> =20 >>> Baptiste Daroussin wrote: >>> =20 >>>> [...] >>>> You are using portupgrade so first upgrade pkg with portupgrade >>>> >>>> =20 >>>> =20 >>> Just a thought here - why (like .rpm and .deb - and the reason I hate= >>> them so much) are you making the package manager version a dependency= of >>> a package? I can understand if there are new features that you may n= eed >>> to use a later version to get those features, but making a package >>> dependent on the package manager rather than displaying a warning tha= t a >>> feature is missing is the brain dead way that plagues upgrades for >>> redhat and debian. Of course if your intent is to make FreeBSD into >>> another Linux distro just with a different kernel, continue. >>> >>> =20 >> >> What is the problem of upgrading the package manager first and then >> upgrade the rest of the world without any problem? >> >> =20 > Not disagreeing with you... but making dependencies like this leads to > everything relying on the package manager being a particular version.. > which in my opinion is wrong... the package manager is not part of the > software you're installing... and shouldn't be part of a dependency tre= e > - particularly when building your own ports. This makes sense. > *Every* time a Redhat and Debian system screwed up that I have had, was= > caused by the package manager needing to be updated before a particular= > package, then all the other dependent packages needed to be upgraded, > and the libraries and you end up with the catch 22 of the package > manager can't be installed because the package manager is too old and > you end up with a half working system that needs to be re-installed > because you needed to apply a security fix to a perl module....! Now > FreeBSD has one advantage (currently) ... the package manager is not > part of the OS, it in itself is a port.. however that has half changed > already and in what, another month? it's going to be part of the OS... Yes but it doesn't manage the system, only port packages. > Yeah sure keep building pkg-static so it can be installed independently= , > but be aware that one does not want to get into dependency loops or > having to upgrade everything just for one security fix - particularly > when working with the ports tree and not the package manager... some > people have production servers that need a security fix, not an upgrade= > of everything. >=20 I'm curious to know how you get into this mess with Debian or RH distros. What version of these distros? And are you sure it is impossible to uprade only the PM (package manager) and keep other packages like they currently are? Never had to reinstall a system for a security upgrade because of dependency loop. Sounds very strange to me. --QpwLMmCkTmvHN9E12hcemchhwEd163U25 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUIUUnAAoJEFr01BkajbiB9RYQALWafBJHKyqqvNSL2yRUdR9a uV0WkdzsVsfz0ripH5BxK1JhEyIOjwHNhsPkvDo4XlEtXeEQmkmHA97RvYxhhy9Y WdbLEJPAOEb3gcFQZtsaFoZHhU6Py73XG60zngP73jjxl0Whm2NpawsYNYfTdOvQ hxHJDww4R5zC1HF3lAktVt/26rwBfdCPeqdMflqK+TB62t9uJUZ2Wo3DB4fQN3oW 6DD7YwgntXiCLQLLc3JbGtKVXOvbSXXqCQxrE6TiYkJ//gidmoF8Ah5/R8zr9fCt UeOn0hGqKlDFBBTM9MJFn4D6avEZd0xzfprWbBXXYetaL3c8RjB7LLHGi5IOOuWV xIGGcsEovZGmV6atkCqpA9ig8CpVzd/VdYGcAR5aACoMG0sfP0Zmezo+W33cqNDX Iy2B9gGgxMwuB0qbZOGOt+MxFjuGDUStdwB42f6pFjPSnjdN247EdqijdVHUxzDU +OXihP1jgWEv6JVnskXCC1wLpc3qx43/+Y74KQwWG8pmNRNRo5H/SvkibriTiIpF yD6oggc3h/Penhw0meTatuhl5NL3Ks4lyFdR9pQbNQFE95blvPeEWCvv8+CjXKM8 MvGMacs3glZ6eJriD1p+ZWdW3lrsqFyW9q7m9u2uvSY4F/3UYPQDuvatBtt2SXa1 9IdqPYef7fQZInelQANU =f0fu -----END PGP SIGNATURE----- --QpwLMmCkTmvHN9E12hcemchhwEd163U25-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 10:20:28 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 70E7AA37; Tue, 23 Sep 2014 10:20:28 +0000 (UTC) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (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 D7979115; Tue, 23 Sep 2014 10:20:27 +0000 (UTC) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id s8NAKQxM075238; Tue, 23 Sep 2014 12:20:26 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id B31F53F13; Tue, 23 Sep 2014 12:20:25 +0200 (CEST) Message-ID: <54214969.50308@omnilan.de> Date: Tue, 23 Sep 2014 12:20:25 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Stefan Esser Subject: Re: option *KB*_DFLT_KEYMAP and *map.h in sys/conf/files References: <54158866.2050901@omnilan.de> <5416BF7A.1080301@freebsd.org> <5416F0B1.1020200@omnilan.de> <5417D137.6030303@freebsd.org> <54213597.1070905@omnilan.de> In-Reply-To: <54213597.1070905@omnilan.de> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF0E76C02811101E3BE75A5F8" X-Greylist: ACL 119 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Tue, 23 Sep 2014 12:20:26 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) 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: Tue, 23 Sep 2014 10:20:28 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF0E76C02811101E3BE75A5F8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Bez=C3=BCglich Harald Schmalzbauer's Nachricht vom 23.09.2014 10:55 (localtime): > Bez=C3=BCglich Stefan Esser's Nachricht vom 16.09.2014 07:57 (localtim= e): >> =E2=80=A6 >> Yes, it seems that nobody compiles non-standard keyboards into the >> kernel. I tried again, but neither the traditional way to build the >> kernel (with "config") nor "make buildkernel" in /usr/src created >> the required include file(s) "atkbdmap.h" or "ukbdmap.h" seem to work >> on -CURRENT. >> >> I do not have time to diagnose this problem, though > Trying to help out=E2=80=A6 > > I went to a -current machine and found no problems compiling a kernel > with non-default keymap, besides the limitations discussed. > I prepared a simple patch, which enables the usage of any valid keymap > name, regardless of the building machine's active console. Also, it use= s > the keymaps from sources instead of the ones installed on the building > machine. > > I opened a bug report for that: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193865 Here was another bug report which is affected: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D153459 This adds KBDMUX_DFLT_KEYMAP option to kernel config. Since kbdmux was enabled by default several years ago, the other _DFLT_KEYMAP options haven't been really useful!!! I've been using swell.k's patch for 3 years without any problems. Can someone take this PR please? Thanks, -Harry --------------enigF0E76C02811101E3BE75A5F8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlQhSWkACgkQLDqVQ9VXb8iJzwCfWjwnSkdY1cYg5BWECypWrlis 2fYAn0XoQ5aYuA1xX5f/qmDyqLwItk3E =CRBQ -----END PGP SIGNATURE----- --------------enigF0E76C02811101E3BE75A5F8-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 11:39:25 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D3CDCE6 for ; Tue, 23 Sep 2014 11:39:25 +0000 (UTC) Received: from cursor.its.uu.se (smtp-out1.uu.se [130.238.7.172]) (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 448B3C65 for ; Tue, 23 Sep 2014 11:39:23 +0000 (UTC) Received: from e-mailfilter02.sunet.se (e-mailfilter02.sunet.se [192.36.171.202]) by cursor.its.uu.se (Postfix) with ESMTP id C838C27F for ; Tue, 23 Sep 2014 13:28:42 +0200 (CEST) Received: from velox.its.uu.se (velox.its.uu.se [130.238.7.74]) by e-mailfilter02.sunet.se (8.14.4/8.14.4/Debian-4) with ESMTP id s8NBSfFa014826 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 23 Sep 2014 13:28:42 +0200 Received: from nyx.uppmax.uu.se (nyx.uppmax.uu.se [130.238.137.40]) by velox.its.uu.se (Postfix) with ESMTP id A204E34BCF for ; Tue, 23 Sep 2014 13:28:41 +0200 (CEST) Message-ID: <54215969.1070303@pean.org> Date: Tue, 23 Sep 2014 13:28:41 +0200 From: =?ISO-8859-1?Q?Peter_Ankerst=E5l?= 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@FreeBSD.org Subject: FreeBSD with Huawei 3g modem. Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040709040602000205060900" X-Bayes-Prob: 0.0001 (Score 0, tokens from: outbound, outbound-uu-se:default, uu-se:default, base:default, @@RPTN) X-Spam-Score: 0.00 () [Tag at 15.00] X-p0f-Info: os=Linux 2.6.x, link=Ethernet or modem X-CanIt-Geo: ip=130.238.137.40; country=SE; region=Uppsala; city=Uppsala; latitude=59.8500; longitude=17.6333; http://maps.google.com/maps?q=59.8500,17.6333&z=6 X-CanItPRO-Stream: outbound-uu-se:outbound (inherits from outbound-uu-se:default, uu-se:default, base:default) X-Canit-Stats-ID: 0aMSzsGwe - 79195b0e18f8 - 20140923 X-Antispam-Training-Forget: https://mailfilter.sunet.se/canit/b.php?i=0aMSzsGwe&m=79195b0e18f8&t=20140923&c=f X-Antispam-Training-Nonspam: https://mailfilter.sunet.se/canit/b.php?i=0aMSzsGwe&m=79195b0e18f8&t=20140923&c=n X-Antispam-Training-Spam: https://mailfilter.sunet.se/canit/b.php?i=0aMSzsGwe&m=79195b0e18f8&t=20140923&c=s X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.36.171.202 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, 23 Sep 2014 11:39:25 -0000 This is a cryptographically signed message in MIME format. --------------ms040709040602000205060900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Hi! Im trying to get a Huawei E3531 to work in FreeBSD. But Im not really=20 sure where to start. I found this:=20 http://technotation.com/2012/08/15/freebsd-and-mobile-broadband/ but=20 havent had any luck cut and pasting here. System: # uname -srm FreeBSD 10.0-RELEASE amd64 When I connect it dmesg says: usb_alloc_device: Found possible auto-install disk (trying next config) ugen0.4: at usbus0 umass0: on usbus= 0 umass0: SCSI over Bulk-Only; quirks =3D 0x0000 umass0:5:0:-1: Attached to scbus5 da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: Serial Number FFFFFFFFFFFFFFFF da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da0: quirks=3D0x2 usbconfig gives this: # usbconfig -u 0 -a 4 dump_device_desc ugen0.4: at usbus0, cfg=3D1 md=3DHOST spd=3DHIGH=20 (480Mbps) pwr=3DON (500mA) bLength =3D 0x0012 bDescriptorType =3D 0x0001 bcdUSB =3D 0x0200 bDeviceClass =3D 0x0000 bDeviceSubClass =3D 0x0000 bDeviceProtocol =3D 0x00ff bMaxPacketSize0 =3D 0x0040 idVendor =3D 0x12d1 idProduct =3D 0x157d bcdDevice =3D 0x0102 iManufacturer =3D 0x0001 iProduct =3D 0x0002 iSerialNumber =3D 0x0003 bNumConfigurations =3D 0x0002 --------------ms040709040602000205060900 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKQDCC BRowggQCoAMCAQICEG0Z6qcZT2ozIuYiMnqqcd4wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNV BAYTAlVTMQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoT FVRoZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3Qu Y29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg RW1haWwwHhcNMTEwNDI4MDAwMDAwWhcNMjAwNTMwMTA0ODM4WjCBkzELMAkGA1UEBhMCR0Ix GzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UE ChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGlj YXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC ggEBAJKEhFtLV5jUXi+LpOFAyKNTWF9mZfEyTvefMn1V0HhMVbdClOD5J3EHxcZppLkyxPFA GpDMJ1Zifxe1cWmu5SAb5MtjXmDKokH2auGj/7jfH0htZUOMKi4rYzh337EXrMLaggLW1DJq 1GdvIBOPXDX65VSAr9hxCh03CgJQU2yVHakQFLSZlVkSMf8JotJM3FLb3uJAAVtIaN3FSrTg 7SQfOq9xXwfjrL8UO7AlcWg99A/WF1hGFYE8aIuLgw9teiFX5jSw2zJ+40rhpVJyZCaRTqWS D//gsWD9Gm9oUZljjRqLpcxCm5t9ImPTqaD8zp6Q30QZ9FxbNboW86eb/8ECAwEAAaOCAUsw ggFHMB8GA1UdIwQYMBaAFImCZ33EnSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBR6E04AdFvG eGNkJ8Ev4qBbvHnFezAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIBADARBgNV HSAECjAIMAYGBFUdIAAwWAYDVR0fBFEwTzBNoEugSYZHaHR0cDovL2NybC51c2VydHJ1c3Qu Y29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRFbWFpbC5jcmwwdAYI KwYBBQUHAQEEaDBmMD0GCCsGAQUFBzAChjFodHRwOi8vY3J0LnVzZXJ0cnVzdC5jb20vVVRO QWRkVHJ1c3RDbGllbnRfQ0EuY3J0MCUGCCsGAQUFBzABhhlodHRwOi8vb2NzcC51c2VydHJ1 c3QuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQCF1r54V1VtM39EUv5C1QaoAQOAivsNsv1Kv/av QUn1G1rF0q0bc24+6SZ85kyYwTAo38v7QjyhJT4KddbQPTmGZtGhm7VNm2+vKGwdr+XqdFqo 2rHA8XV6L566k3nK/uKRHlZ0sviN0+BDchvtj/1gOSBH+4uvOmVIPJg9pSW/ve9g4EnlFsjr P0OD8ODuDcHTzTNfm9C9YGqzO/761Mk6PB/tm/+bSTO+Qik5g+4zaS6CnUVNqGnagBsePdIa XXxHmaWbCG0SmYbWXVcHG6cwvktJRLiQfsrReTjrtDP6oDpdJlieYVUYtCHVmdXgQ0BCML7q peeU0rD+83X5f27nMIIFHjCCBAagAwIBAgIRAMFvE3qCNYFbXz8lkfxnvZgwDQYJKoZIhvcN AQEFBQAwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAO BgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBD T01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwHhcNMTQw MTE3MDAwMDAwWhcNMTUwMTE3MjM1OTU5WjAfMR0wGwYJKoZIhvcNAQkBFg5wZXRlckBwZWFu Lm9yZzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALtXJzxk2+Tt/OsnAPvgIK/M pmd1DFYdqWGl8+/y9YbJbRCDAsFC48xjvwMrO55WSg1j44h2NC7I1w7J/+Y4qYZEwC+P/0cb I2GQY4WzkB8Plpc0HrDpOS6SPKfIIgGuS+tAURMHcLHlDBivtrsWqYg+wJ6ypOcvMBikpFcT ASga4Rb3zMpnE8z198dwRnyDoOJKF9iGBVDZ93613CdC/Fp+H2qve2AA577abiO3xIlamMkb /3IM6MC976rcR7Pnf3sp2ompPGn7m7yhhkut5OxnC83LnrzUVEJM1f3J8mtAWQ0AL5hEPDln OTT6P1Opv6C8eDB9xYQ3zqz0v7PoNjMCAwEAAaOCAd4wggHaMB8GA1UdIwQYMBaAFHoTTgB0 W8Z4Y2QnwS/ioFu8ecV7MB0GA1UdDgQWBBR7JyIkDGIYyCTbDgf48nC5UOPMRzAOBgNVHQ8B Af8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQED BQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYI KwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMFcGA1UdHwRQME4wTKBK oEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9u YW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEBBHwwejBSBggrBgEFBQcwAoZGaHR0 cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1 cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMBkG A1UdEQQSMBCBDnBldGVyQHBlYW4ub3JnMA0GCSqGSIb3DQEBBQUAA4IBAQB0khzkZuMC8o9s 3xvoUbfr/4BcndibN6aDFbOIfwccWqIPMTOqmTakBjtc/N/bzYvFPlk2CmsjFbofuzuuVlKW G+bEjeq4xOsbjWKAmznV1Uw6DtyanWfs8YEU2sdKsHu657A5UZP8CCSpWxpnXAgFNdWszGSC jPw8uzcnKawBUbDHPT/ob/nAnNSYtGyLLqg5zb2qMbcerzHk4Gr1LZKApY122H0NguIPvQTi IF/+oeyhXl8KuBaPFU3kMr4UxIv9sX0KFp1iRjR6eOPAVTqC7TSttB1lhgRImKwU0tXNes1L XuWhgnB3Zr4atHizY+4kw9A0enFL8HNv2ampeTWEMYIEHDCCBBgCAQEwgakwgZMxCzAJBgNV BAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQx GjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1 dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEQDBbxN6gjWBW18/JZH8Z72YMAkG BSsOAwIaBQCgggJHMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X DTE0MDkyMzExMjg0MVowIwYJKoZIhvcNAQkEMRYEFEDtCXOAFgaUFrrxzkp4DmGYtCLGMGwG CSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAO BggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgw gboGCSsGAQQBgjcQBDGBrDCBqTCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIg TWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0 ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBF bWFpbCBDQQIRAMFvE3qCNYFbXz8lkfxnvZgwgbwGCyqGSIb3DQEJEAILMYGsoIGpMIGTMQsw CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxm b3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVu dCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhEAwW8TeoI1gVtfPyWR/Ge9 mDANBgkqhkiG9w0BAQEFAASCAQB4R3C5tV2DSkJ9tKYJNP99evyDPowBgYCKa72aqljNL7Wx yDl8emuBLEzLBoeO4q8XcpJ5X9pkNV3fS79XTFm0sF0Zv+n82qVUac9xv4+5YDjcMOKlHZQ2 5MXhZ3zAv4zYn/uwjWRvlGIa/c4TlBtYxHYxA1EJcDO4zpZtWzlzm1osuLK/4o+/bJdv6U7K uTD07AdwC7seo8cHqRP2GvMTPwPMvS9Su1jEK/8E2xG9jQaoxyjee5fZyksxt5JfgksyvyCS giCRe6zJk5OguSnGX/WPHQvCS9bClaBY/AxXOoWWCVVETrMsroEPLhnHzICP7pBMbc3Y3R/X cOA4EVMPAAAAAAAA --------------ms040709040602000205060900-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 11:45:01 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7958A1F9; Tue, 23 Sep 2014 11:45:01 +0000 (UTC) Received: from smtpout7.timeweb.ru (smtpout7.timeweb.ru [92.53.117.21]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2761ED56; Tue, 23 Sep 2014 11:45:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=amdmi3.ru; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=VjhwBVHyACAK9MgfbNoN9HjfiGxKi9fp4AxfNm4WZ2o=; b=JoY1Q6rM/OzxoEm/SzoikTAJCdrD3t89AZjPD8Z1BMQj9IiD8Yavn5Ia7g4HPg4y4saZehC2DXQwOdzMcB2FCWyxr0R8CC0V/pTKPSyfQLwSBNgFSL/LD61RMCOtnDsjK1od0nIuwJkliMLdougaXFSkkAKXfXAfgZGiHCYJN9k=; Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XWOWX-0004pW-9w; Tue, 23 Sep 2014 15:44:49 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id A6F472CA; Tue, 23 Sep 2014 15:44:48 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 5A88E44755; Tue, 23 Sep 2014 15:44:48 +0400 (MSK) Date: Tue, 23 Sep 2014 15:44:48 +0400 From: Dmitry Marakasov To: Dimitry Andric Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <20140923114447.GB1301@hades.panopticon> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> <542105A3.4090507@iki.fi> <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org, Pasi Parviainen 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, 23 Sep 2014 11:45:01 -0000 * Dimitry Andric (dim@FreeBSD.org) wrote: > > This seems to be same issue as in > > http://llvm.org/bugs/show_bug.cgi?id=20893 for which there is patch > > review going > > on http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/236415.html. > > > > Your test case is reproducible with the trunk of llvm/clang and > > the patch in review resolves it. Other workaround is to disable > > generation of debug information by removing -g flag. > > Hm, I had assumed this problem was fixed by importing r203311 from > upstream llvm trunk, in head r263313. But apparently it is not. > > The upstream patch seems to fix your specific test case, but it is still > in review, so I prefer to wait until it is actually committed, before I > import it. Which worries me is what we do if it's not reviewd until the release. We can't just tell users to "remove -g flag", can't we? -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 11:48: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 15A424E3 for ; Tue, 23 Sep 2014 11:48:24 +0000 (UTC) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9367CD98 for ; Tue, 23 Sep 2014 11:48:23 +0000 (UTC) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id s8NBmBWV078691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 23 Sep 2014 13:48:12 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: freebsd-stable@FreeBSD.org Received: from eg.sd.rdtc.ru (eugen@localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.9/8.14.9) with ESMTP id s8NBmAiD063595; Tue, 23 Sep 2014 18:48:10 +0700 (NOVT) (envelope-from eugen@grosbein.net) Message-ID: <54215DFA.3080500@grosbein.net> Date: Tue, 23 Sep 2014 18:48:10 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: =?UTF-8?B?UGV0ZXIgQW5rZXJzdMOlbA==?= , freebsd-stable@FreeBSD.org Subject: Re: FreeBSD with Huawei 3g modem. References: <54215969.1070303@pean.org> In-Reply-To: <54215969.1070303@pean.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM, T_DATE_IN_FUTURE_96_Q autolearn=no version=3.3.2 X-Spam-Report: * 0.0 T_DATE_IN_FUTURE_96_Q Date: is 4 days to 4 months after Received: * date * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net 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, 23 Sep 2014 11:48:24 -0000 On 23.09.2014 18:28, Peter AnkerstÃ¥l wrote: > Hi! > > Im trying to get a Huawei E3531 to work in FreeBSD. But Im not really > sure where to start. I found this: > http://technotation.com/2012/08/15/freebsd-and-mobile-broadband/ but > havent had any luck cut and pasting here. > > System: > # uname -srm > FreeBSD 10.0-RELEASE amd64 > > When I connect it dmesg says: > usb_alloc_device: Found possible auto-install disk (trying next config) > ugen0.4: at usbus0 > umass0: on usbus0 > umass0: SCSI over Bulk-Only; quirks = 0x0000 > umass0:5:0:-1: Attached to scbus5 > da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: Serial Number FFFFFFFFFFFFFFFF > da0: 40.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present > da0: quirks=0x2 Your modem pretends to be mass-storage device containing Windows drivers. You may need to "kldload u3g" and then to signal it to switch to "modem" mode using command like "camcontrol eject pass0". Some ZTE modems need "usbconfig -d 0.4 add_quirk UQ_MSC_EJECT_ZTESTOR" before camcontrol command, your may need something similar, or not. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 12:32:50 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8EB577CE; Tue, 23 Sep 2014 12:32:50 +0000 (UTC) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::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 F3CB0625; Tue, 23 Sep 2014 12:32:49 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id x13so3757223wgg.28 for ; Tue, 23 Sep 2014 05:32:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YwqfUesiI2HnlkZjZQ1lorjlfNtMaLQwHSi8gnjBHk4=; b=epRI0MXYSed/MEWouuLsvQUtaabLmQzqljQQDhbQxs8LDHrnDKDNQH7DmVQhfnb5mh q3y+G91D8rgoIoIgkzZGajPS+QMmOjjlZePbTBB0fy4sIyWKScoYwlnwAjMPBcOWsu85 FIm6/QvuYl20gMwKyQLeP0eUYqO3EVQJQM/Sj2yB8aSCIkFwjg3uESV7gBFNvePp9gbH qTum2l6alQK5i7r1bPfb6i9wCRV9Dm5THLGQSUAae5OgxKfcsc5SabV+xk935/KGQJxT 5P4egXRmTlxUrOcRjVOVXWr67dCV46OHHNknXYuheHKUOBf37g3xpzJ/5JZGr/ccA58I gV6Q== MIME-Version: 1.0 X-Received: by 10.194.76.195 with SMTP id m3mr2447684wjw.136.1411475567440; Tue, 23 Sep 2014 05:32:47 -0700 (PDT) Received: by 10.217.2.18 with HTTP; Tue, 23 Sep 2014 05:32:47 -0700 (PDT) In-Reply-To: <54214527.4020906@peterschmitt.fr> References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> <542138B9.3060600@peterschmitt.fr> <542140E4.6050605@sorbs.net> <54214527.4020906@peterschmitt.fr> Date: Tue, 23 Sep 2014 08:32:47 -0400 Message-ID: Subject: Re: pkg 1.3.8 requested but not available? From: Brandon Allbery To: Florent Peterschmitt Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "ports@freebsd.org" , FreeBSD Stable Mailing List , Michelle Sullivan 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, 23 Sep 2014 12:32:50 -0000 On Tue, Sep 23, 2014 at 6:02 AM, Florent Peterschmitt < florent@peterschmitt.fr> wrote: > I'm curious to know how you get into this mess with Debian or RH > distros. What version of these distros? > > And are you sure it is impossible to uprade only the PM (package > manager) and keep other packages like they currently are? > > Never had to reinstall a system for a security upgrade because of > dependency loop. Sounds very strange to me. > Debian unstable can be a scary, scary place sometimes. For RH it sounds weird, but maybe Fedora Rawhide gets into such states too. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 12:38:58 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04263DFC for ; Tue, 23 Sep 2014 12:38:58 +0000 (UTC) Received: from man.dat.pl (dat.pl [80.51.155.34]) by mx1.freebsd.org (Postfix) with ESMTP id B8A6574C for ; Tue, 23 Sep 2014 12:38:57 +0000 (UTC) Received: from man.dat.pl (localhost [127.0.0.1]) by man.dat.pl (Postfix) with ESMTP id 66B96D16A4C; Tue, 23 Sep 2014 14:38:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at dat.pl Received: from man.dat.pl ([127.0.0.1]) by man.dat.pl (man.dat.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id DlClTnvMJH2i; Tue, 23 Sep 2014 14:38:48 +0200 (CEST) Message-ID: <542169D6.8090904@dat.pl> Date: Tue, 23 Sep 2014 14:38:46 +0200 From: Maciej Milewski MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: FreeBSD with Huawei 3g modem. References: <54215969.1070303@pean.org> In-Reply-To: <54215969.1070303@pean.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: peter@pean.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: Tue, 23 Sep 2014 12:38:58 -0000 On 23.09.2014 13:28, Peter Ankerst=E5l wrote: > Hi! > > Im trying to get a Huawei E3531 to work in FreeBSD. But Im not really > sure where to start. I found this: > http://technotation.com/2012/08/15/freebsd-and-mobile-broadband/ but > havent had any luck cut and pasting here. > > System: > # uname -srm > FreeBSD 10.0-RELEASE amd64 > > When I connect it dmesg says: > usb_alloc_device: Found possible auto-install disk (trying next config)= > ugen0.4: at usbus0 > umass0: on > usbus0 > umass0: SCSI over Bulk-Only; quirks =3D 0x0000 > umass0:5:0:-1: Attached to scbus5 > da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 > da0: Removable Direct Access SCSI-2 devic= e > da0: Serial Number FFFFFFFFFFFFFFFF > da0: 40.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present= > da0: quirks=3D0x2 > > usbconfig gives this: > > # usbconfig -u 0 -a 4 dump_device_desc > ugen0.4: at usbus0, cfg=3D1 md=3DHOST spd=3DHIGH= > (480Mbps) pwr=3DON (500mA) > > bLength =3D 0x0012 > bDescriptorType =3D 0x0001 > bcdUSB =3D 0x0200 > bDeviceClass =3D 0x0000 > bDeviceSubClass =3D 0x0000 > bDeviceProtocol =3D 0x00ff > bMaxPacketSize0 =3D 0x0040 > idVendor =3D 0x12d1 > idProduct =3D 0x157d > bcdDevice =3D 0x0102 > iManufacturer =3D 0x0001 > iProduct =3D 0x0002 > iSerialNumber =3D 0x0003 > bNumConfigurations =3D 0x0002 > > Peter, cut and paste is the last step(for copying ppp script ;P ) Before that you need to setup your system to recognize that modem. First check if the idProduct is listed in your usbdevs. If not you need to add it similar way like are other. For example E3131 is added like that: root@backup:/usr/src/sys/dev/usb # grep -Hr E3131 * serial/u3g.c: U3G_DEV(HUAWEI, E3131, 0), serial/u3g.c: U3G_DEV(HUAWEI, E3131_INIT, U3GINIT_HUAWEISCSI), usbdevs:product HUAWEI E3131_INIT 0x14fe 3G modem initial usbdevs:product HUAWEI E3131 0x1506 3G modem Then recompile and install kernel and try if that helps. I'm not sure if compiling u3g module is enough that's why I suggested whole kernel recompiling. --=20 Pozdrawiam, Maciej Milewski From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 12:45:58 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D680F180 for ; Tue, 23 Sep 2014 12:45:58 +0000 (UTC) Received: from cursor.its.uu.se (smtp-out1.uu.se [130.238.7.172]) (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 7CE31849 for ; Tue, 23 Sep 2014 12:45:57 +0000 (UTC) Received: from e-mailfilter02.sunet.se (e-mailfilter02.sunet.se [192.36.171.202]) by cursor.its.uu.se (Postfix) with ESMTP id 2EC16230; Tue, 23 Sep 2014 14:45:55 +0200 (CEST) Received: from velox.its.uu.se (velox.its.uu.se [130.238.7.74]) by e-mailfilter02.sunet.se (8.14.4/8.14.4/Debian-4) with ESMTP id s8NCjslU031723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Sep 2014 14:45:54 +0200 Received: from nyx.uppmax.uu.se (nyx.uppmax.uu.se [130.238.137.40]) by velox.its.uu.se (Postfix) with ESMTP id BEA60342AC; Tue, 23 Sep 2014 14:45:53 +0200 (CEST) Message-ID: <54216B81.6030306@pean.org> Date: Tue, 23 Sep 2014 14:45:53 +0200 From: =?windows-1252?Q?Peter_Ankerst=E5l?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Maciej Milewski , freebsd-stable@freebsd.org Subject: Re: FreeBSD with Huawei 3g modem. References: <54215969.1070303@pean.org> <542169D6.8090904@dat.pl> In-Reply-To: <542169D6.8090904@dat.pl> Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050307090601010107000902" X-Bayes-Prob: 0.0001 (Score 0, tokens from: outbound, outbound-uu-se:default, uu-se:default, base:default, @@RPTN) X-Spam-Score: 0.00 () [Tag at 15.00] X-p0f-Info: os=Linux 2.6.x, link=Ethernet or modem X-CanIt-Geo: ip=130.238.137.40; country=SE; region=Uppsala; city=Uppsala; latitude=59.8500; longitude=17.6333; http://maps.google.com/maps?q=59.8500,17.6333&z=6 X-CanItPRO-Stream: outbound-uu-se:outbound (inherits from outbound-uu-se:default, uu-se:default, base:default) X-Canit-Stats-ID: 0aMSAJS9A - 3476e11ea668 - 20140923 X-Antispam-Training-Forget: https://mailfilter.sunet.se/canit/b.php?i=0aMSAJS9A&m=3476e11ea668&t=20140923&c=f X-Antispam-Training-Nonspam: https://mailfilter.sunet.se/canit/b.php?i=0aMSAJS9A&m=3476e11ea668&t=20140923&c=n X-Antispam-Training-Spam: https://mailfilter.sunet.se/canit/b.php?i=0aMSAJS9A&m=3476e11ea668&t=20140923&c=s X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw X-Scanned-By: CanIt (www . roaringpenguin . com) on 192.36.171.202 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, 23 Sep 2014 12:45:58 -0000 This is a cryptographically signed message in MIME format. --------------ms050307090601010107000902 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable On 09/23/2014 02:38 PM, Maciej Milewski wrote: > On 23.09.2014 13:28, Peter Ankerst=E5l wrote: >> Hi! >> >> Im trying to get a Huawei E3531 to work in FreeBSD. But Im not really >> sure where to start. I found this: >> http://technotation.com/2012/08/15/freebsd-and-mobile-broadband/ but >> havent had any luck cut and pasting here. >> >> System: >> # uname -srm >> FreeBSD 10.0-RELEASE amd64 >> >> When I connect it dmesg says: >> usb_alloc_device: Found possible auto-install disk (trying next config= ) >> ugen0.4: at usbus0 >> umass0: on >> usbus0 >> umass0: SCSI over Bulk-Only; quirks =3D 0x0000 >> umass0:5:0:-1: Attached to scbus5 >> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 >> da0: Removable Direct Access SCSI-2 devi= ce >> da0: Serial Number FFFFFFFFFFFFFFFF >> da0: 40.000MB/s transfers >> da0: Attempt to query device size failed: NOT READY, Medium not presen= t >> da0: quirks=3D0x2 >> >> usbconfig gives this: >> >> # usbconfig -u 0 -a 4 dump_device_desc >> ugen0.4: at usbus0, cfg=3D1 md=3DHOST spd=3DHIG= H >> (480Mbps) pwr=3DON (500mA) >> >> bLength =3D 0x0012 >> bDescriptorType =3D 0x0001 >> bcdUSB =3D 0x0200 >> bDeviceClass =3D 0x0000 >> bDeviceSubClass =3D 0x0000 >> bDeviceProtocol =3D 0x00ff >> bMaxPacketSize0 =3D 0x0040 >> idVendor =3D 0x12d1 >> idProduct =3D 0x157d >> bcdDevice =3D 0x0102 >> iManufacturer =3D 0x0001 >> iProduct =3D 0x0002 >> iSerialNumber =3D 0x0003 >> bNumConfigurations =3D 0x0002 >> >> > Peter, > cut and paste is the last step(for copying ppp script ;P ) > Before that you need to setup your system to recognize that modem. > First check if the idProduct is listed in your usbdevs. If not you need= > to add it similar way like are other. > For example E3131 is added like that: > root@backup:/usr/src/sys/dev/usb # grep -Hr E3131 * > serial/u3g.c: U3G_DEV(HUAWEI, E3131, 0), > serial/u3g.c: U3G_DEV(HUAWEI, E3131_INIT, U3GINIT_HUAWEISCSI), > usbdevs:product HUAWEI E3131_INIT 0x14fe 3G modem initial > usbdevs:product HUAWEI E3131 0x1506 3G modem > > Then recompile and install kernel and try if that helps. I'm not sure i= f > compiling u3g module is enough that's why I suggested whole kernel > recompiling. > Yes, this is exactly what I have done, except that I dont know the=20 "INIT" one. And no, I did not recompile the kernel, just u3g. --------------ms050307090601010107000902 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKQDCC BRowggQCoAMCAQICEG0Z6qcZT2ozIuYiMnqqcd4wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNV BAYTAlVTMQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoT FVRoZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3Qu Y29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg RW1haWwwHhcNMTEwNDI4MDAwMDAwWhcNMjAwNTMwMTA0ODM4WjCBkzELMAkGA1UEBhMCR0Ix GzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UE ChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGlj YXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC ggEBAJKEhFtLV5jUXi+LpOFAyKNTWF9mZfEyTvefMn1V0HhMVbdClOD5J3EHxcZppLkyxPFA GpDMJ1Zifxe1cWmu5SAb5MtjXmDKokH2auGj/7jfH0htZUOMKi4rYzh337EXrMLaggLW1DJq 1GdvIBOPXDX65VSAr9hxCh03CgJQU2yVHakQFLSZlVkSMf8JotJM3FLb3uJAAVtIaN3FSrTg 7SQfOq9xXwfjrL8UO7AlcWg99A/WF1hGFYE8aIuLgw9teiFX5jSw2zJ+40rhpVJyZCaRTqWS D//gsWD9Gm9oUZljjRqLpcxCm5t9ImPTqaD8zp6Q30QZ9FxbNboW86eb/8ECAwEAAaOCAUsw ggFHMB8GA1UdIwQYMBaAFImCZ33EnSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBR6E04AdFvG eGNkJ8Ev4qBbvHnFezAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIBADARBgNV HSAECjAIMAYGBFUdIAAwWAYDVR0fBFEwTzBNoEugSYZHaHR0cDovL2NybC51c2VydHJ1c3Qu Y29tL1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRFbWFpbC5jcmwwdAYI KwYBBQUHAQEEaDBmMD0GCCsGAQUFBzAChjFodHRwOi8vY3J0LnVzZXJ0cnVzdC5jb20vVVRO QWRkVHJ1c3RDbGllbnRfQ0EuY3J0MCUGCCsGAQUFBzABhhlodHRwOi8vb2NzcC51c2VydHJ1 c3QuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQCF1r54V1VtM39EUv5C1QaoAQOAivsNsv1Kv/av QUn1G1rF0q0bc24+6SZ85kyYwTAo38v7QjyhJT4KddbQPTmGZtGhm7VNm2+vKGwdr+XqdFqo 2rHA8XV6L566k3nK/uKRHlZ0sviN0+BDchvtj/1gOSBH+4uvOmVIPJg9pSW/ve9g4EnlFsjr P0OD8ODuDcHTzTNfm9C9YGqzO/761Mk6PB/tm/+bSTO+Qik5g+4zaS6CnUVNqGnagBsePdIa XXxHmaWbCG0SmYbWXVcHG6cwvktJRLiQfsrReTjrtDP6oDpdJlieYVUYtCHVmdXgQ0BCML7q peeU0rD+83X5f27nMIIFHjCCBAagAwIBAgIRAMFvE3qCNYFbXz8lkfxnvZgwDQYJKoZIhvcN AQEFBQAwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAO BgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBD T01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwHhcNMTQw MTE3MDAwMDAwWhcNMTUwMTE3MjM1OTU5WjAfMR0wGwYJKoZIhvcNAQkBFg5wZXRlckBwZWFu Lm9yZzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALtXJzxk2+Tt/OsnAPvgIK/M pmd1DFYdqWGl8+/y9YbJbRCDAsFC48xjvwMrO55WSg1j44h2NC7I1w7J/+Y4qYZEwC+P/0cb I2GQY4WzkB8Plpc0HrDpOS6SPKfIIgGuS+tAURMHcLHlDBivtrsWqYg+wJ6ypOcvMBikpFcT ASga4Rb3zMpnE8z198dwRnyDoOJKF9iGBVDZ93613CdC/Fp+H2qve2AA577abiO3xIlamMkb /3IM6MC976rcR7Pnf3sp2ompPGn7m7yhhkut5OxnC83LnrzUVEJM1f3J8mtAWQ0AL5hEPDln OTT6P1Opv6C8eDB9xYQ3zqz0v7PoNjMCAwEAAaOCAd4wggHaMB8GA1UdIwQYMBaAFHoTTgB0 W8Z4Y2QnwS/ioFu8ecV7MB0GA1UdDgQWBBR7JyIkDGIYyCTbDgf48nC5UOPMRzAOBgNVHQ8B Af8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGyMQED BQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYI KwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMFcGA1UdHwRQME4wTKBK oEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9u YW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEBBHwwejBSBggrBgEFBQcwAoZGaHR0 cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1 cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMBkG A1UdEQQSMBCBDnBldGVyQHBlYW4ub3JnMA0GCSqGSIb3DQEBBQUAA4IBAQB0khzkZuMC8o9s 3xvoUbfr/4BcndibN6aDFbOIfwccWqIPMTOqmTakBjtc/N/bzYvFPlk2CmsjFbofuzuuVlKW G+bEjeq4xOsbjWKAmznV1Uw6DtyanWfs8YEU2sdKsHu657A5UZP8CCSpWxpnXAgFNdWszGSC jPw8uzcnKawBUbDHPT/ob/nAnNSYtGyLLqg5zb2qMbcerzHk4Gr1LZKApY122H0NguIPvQTi IF/+oeyhXl8KuBaPFU3kMr4UxIv9sX0KFp1iRjR6eOPAVTqC7TSttB1lhgRImKwU0tXNes1L XuWhgnB3Zr4atHizY+4kw9A0enFL8HNv2ampeTWEMYIEHDCCBBgCAQEwgakwgZMxCzAJBgNV BAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQx GjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1 dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEQDBbxN6gjWBW18/JZH8Z72YMAkG BSsOAwIaBQCgggJHMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X DTE0MDkyMzEyNDU1M1owIwYJKoZIhvcNAQkEMRYEFBiVHiEahGKo2Jy8SFSQNk98oJ+cMGwG CSqGSIb3DQEJDzFfMF0wCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAO BggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgw gboGCSsGAQQBgjcQBDGBrDCBqTCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIg TWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0 ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBF bWFpbCBDQQIRAMFvE3qCNYFbXz8lkfxnvZgwgbwGCyqGSIb3DQEJEAILMYGsoIGpMIGTMQsw CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxm b3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVu dCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhEAwW8TeoI1gVtfPyWR/Ge9 mDANBgkqhkiG9w0BAQEFAASCAQAST1uSzOnVHrvs0FFKpjeGWWQXxdK15Vz+4aMJDHRMhNfn Tqihg6KkLld1fANdp/L1/OMEpM+z+k/kv3708zCflw7Cq+25BEAieANK63ffUEVFaGlud0ny crWoRIZVTJFnDjOyWEESfSWy4WE84+3IFDJfkbjLTaoWqzAH0NsZ2YVTNaf+sGsmlMjaPVuh B2szpZNhoZPuY/DGr2T+lClLV3YkTmuG1ixgI2OFOsm+ZwkJ7vlRVmKk05l+4A8Urj5ibpTv jfTaUdvGtBl8a8pXIASC1jZN1HiPIH6Gpxou9sswHxhBrFuDkam46faD14vt+C5kUroaRHxc /Imyr8QzAAAAAAAA --------------ms050307090601010107000902-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 12:54:21 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E309F493 for ; Tue, 23 Sep 2014 12:54:21 +0000 (UTC) Received: from man.dat.pl (dat.pl [80.51.155.34]) by mx1.freebsd.org (Postfix) with ESMTP id 9EEEA950 for ; Tue, 23 Sep 2014 12:54:20 +0000 (UTC) Received: from man.dat.pl (localhost [127.0.0.1]) by man.dat.pl (Postfix) with ESMTP id 1ADB5D16A4C; Tue, 23 Sep 2014 14:54:20 +0200 (CEST) X-Virus-Scanned: amavisd-new at dat.pl Received: from man.dat.pl ([127.0.0.1]) by man.dat.pl (man.dat.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5puy61ewqwlr; Tue, 23 Sep 2014 14:54:19 +0200 (CEST) Message-ID: <54216D7A.80708@dat.pl> Date: Tue, 23 Sep 2014 14:54:18 +0200 From: Maciej Milewski MIME-Version: 1.0 To: =?windows-1252?Q?Peter_Ankerst=E5l?= , freebsd-stable@freebsd.org Subject: Re: FreeBSD with Huawei 3g modem. References: <54215969.1070303@pean.org> <542169D6.8090904@dat.pl> <54216B81.6030306@pean.org> In-Reply-To: <54216B81.6030306@pean.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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, 23 Sep 2014 12:54:22 -0000 On 23.09.2014 14:45, Peter Ankerstål wrote: > On 09/23/2014 02:38 PM, Maciej Milewski wrote: >> On 23.09.2014 13:28, Peter Ankerstål wrote: >>> Hi! >>> >>> Im trying to get a Huawei E3531 to work in FreeBSD. But Im not really >>> sure where to start. I found this: >>> http://technotation.com/2012/08/15/freebsd-and-mobile-broadband/ but >>> havent had any luck cut and pasting here. >>> >>> System: >>> # uname -srm >>> FreeBSD 10.0-RELEASE amd64 >>> >>> When I connect it dmesg says: >>> usb_alloc_device: Found possible auto-install disk (trying next config) >>> ugen0.4: at usbus0 >>> umass0: on >>> usbus0 >>> umass0: SCSI over Bulk-Only; quirks = 0x0000 >>> umass0:5:0:-1: Attached to scbus5 >>> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 >>> da0: Removable Direct Access SCSI-2 >>> device >>> da0: Serial Number FFFFFFFFFFFFFFFF >>> da0: 40.000MB/s transfers >>> da0: Attempt to query device size failed: NOT READY, Medium not present >>> da0: quirks=0x2 >>> >>> usbconfig gives this: >>> >>> # usbconfig -u 0 -a 4 dump_device_desc >>> ugen0.4: at usbus0, cfg=1 md=HOST spd=HIGH >>> (480Mbps) pwr=ON (500mA) >>> >>> bLength = 0x0012 >>> bDescriptorType = 0x0001 >>> bcdUSB = 0x0200 >>> bDeviceClass = 0x0000 >>> bDeviceSubClass = 0x0000 >>> bDeviceProtocol = 0x00ff >>> bMaxPacketSize0 = 0x0040 >>> idVendor = 0x12d1 >>> idProduct = 0x157d >>> bcdDevice = 0x0102 >>> iManufacturer = 0x0001 >>> iProduct = 0x0002 >>> iSerialNumber = 0x0003 >>> bNumConfigurations = 0x0002 >>> >>> >> Peter, >> cut and paste is the last step(for copying ppp script ;P ) >> Before that you need to setup your system to recognize that modem. >> First check if the idProduct is listed in your usbdevs. If not you need >> to add it similar way like are other. >> For example E3131 is added like that: >> root@backup:/usr/src/sys/dev/usb # grep -Hr E3131 * >> serial/u3g.c: U3G_DEV(HUAWEI, E3131, 0), >> serial/u3g.c: U3G_DEV(HUAWEI, E3131_INIT, U3GINIT_HUAWEISCSI), >> usbdevs:product HUAWEI E3131_INIT 0x14fe 3G modem initial >> usbdevs:product HUAWEI E3131 0x1506 3G modem >> >> Then recompile and install kernel and try if that helps. I'm not sure if >> compiling u3g module is enough that's why I suggested whole kernel >> recompiling. >> > Yes, this is exactly what I have done, except that I dont know the > "INIT" one. > > And no, I did not recompile the kernel, just u3g. > I suspect that INIT is how that modem presents at the first connection before sending any command(like U3GINIT_HUAWEI) It might be that this device needs another initialization string like Huawei E3272. Search archives on mail from 16.09.2014 with Subject: Huawei E3272 tester needed You may find there another hints. -- Pozdrawiam, Maciej Milewski From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 13:00:40 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4146A82A for ; Tue, 23 Sep 2014 13:00:40 +0000 (UTC) Received: from mailhost.netlab.sk (mailhost.netlab.sk [84.245.65.10]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B07DBA56 for ; Tue, 23 Sep 2014 13:00:39 +0000 (UTC) Received: from zeta.dino.sk (fw1.dino.sk [84.245.95.252]) (AUTH: LOGIN milan) by mailhost.netlab.sk with ESMTPA; Tue, 23 Sep 2014 15:00:32 +0200 id 00DD601C.54216EF0.000110AE Date: Tue, 23 Sep 2014 15:00:29 +0200 From: Milan Obuch To: Peter =?ISO-8859-1?Q?Ankerst=E5l?= Subject: Re: FreeBSD with Huawei 3g modem. Message-ID: <20140923150029.5ca8f80b@zeta.dino.sk> In-Reply-To: <54216B81.6030306@pean.org> References: <54215969.1070303@pean.org> <542169D6.8090904@dat.pl> <54216B81.6030306@pean.org> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.22; i386-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, Maciej Milewski 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, 23 Sep 2014 13:00:40 -0000 On Tue, 23 Sep 2014 14:45:53 +0200 Peter Ankerstål wrote: > On 09/23/2014 02:38 PM, Maciej Milewski wrote: > > On 23.09.2014 13:28, Peter Ankerstål wrote: > >> Hi! > >> > >> Im trying to get a Huawei E3531 to work in FreeBSD. But Im not > >> really sure where to start. I found this: > >> http://technotation.com/2012/08/15/freebsd-and-mobile-broadband/ > >> but havent had any luck cut and pasting here. > >> > >> System: > >> # uname -srm > >> FreeBSD 10.0-RELEASE amd64 > >> > >> When I connect it dmesg says: > >> usb_alloc_device: Found possible auto-install disk (trying next > >> config) ugen0.4: at usbus0 > >> umass0: on > >> usbus0 > >> umass0: SCSI over Bulk-Only; quirks = 0x0000 > >> umass0:5:0:-1: Attached to scbus5 > >> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 > >> da0: Removable Direct Access SCSI-2 > >> device da0: Serial Number FFFFFFFFFFFFFFFF > >> da0: 40.000MB/s transfers > >> da0: Attempt to query device size failed: NOT READY, Medium not > >> present da0: quirks=0x2 > >> > >> usbconfig gives this: > >> > >> # usbconfig -u 0 -a 4 dump_device_desc > >> ugen0.4: at usbus0, cfg=1 md=HOST spd=HIGH > >> (480Mbps) pwr=ON (500mA) > >> > >> bLength = 0x0012 > >> bDescriptorType = 0x0001 > >> bcdUSB = 0x0200 > >> bDeviceClass = 0x0000 > >> bDeviceSubClass = 0x0000 > >> bDeviceProtocol = 0x00ff > >> bMaxPacketSize0 = 0x0040 > >> idVendor = 0x12d1 > >> idProduct = 0x157d > >> bcdDevice = 0x0102 > >> iManufacturer = 0x0001 > >> iProduct = 0x0002 > >> iSerialNumber = 0x0003 > >> bNumConfigurations = 0x0002 > >> > >> > > Peter, > > cut and paste is the last step(for copying ppp script ;P ) > > Before that you need to setup your system to recognize that modem. > > First check if the idProduct is listed in your usbdevs. If not you > > need to add it similar way like are other. > > For example E3131 is added like that: > > root@backup:/usr/src/sys/dev/usb # grep -Hr E3131 * > > serial/u3g.c: U3G_DEV(HUAWEI, E3131, 0), > > serial/u3g.c: U3G_DEV(HUAWEI, E3131_INIT, U3GINIT_HUAWEISCSI), > > usbdevs:product HUAWEI E3131_INIT 0x14fe 3G modem initial > > usbdevs:product HUAWEI E3131 0x1506 3G modem > > > > Then recompile and install kernel and try if that helps. I'm not > > sure if compiling u3g module is enough that's why I suggested whole > > kernel recompiling. > > > Yes, this is exactly what I have done, except that I dont know the > "INIT" one. > > And no, I did not recompile the kernel, just u3g. > Hi, I found this page: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1308895 There is something which makes me thinking it is somehow similar to my E3272, which works after mode switch (with port usb_modeswitch, see recent thread on freebsd-current mailing list titled 'Huawei E3272 tester needed') with if_cdce.ko module. It is a wild guess, but maybe it works. Regards, Milan From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 13:05:49 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3430FA2A; Tue, 23 Sep 2014 13:05:49 +0000 (UTC) Received: from tensor.andric.com (unknown [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E0AF3AAC; Tue, 23 Sep 2014 13:05:48 +0000 (UTC) Received: from [192.168.2.2] (unknown [77.243.161.229]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id B972AB803; Tue, 23 Sep 2014 15:05:42 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_DE65C05B-4598-447D-A276-C96632AC7B52"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD From: Dimitry Andric In-Reply-To: <20140923114447.GB1301@hades.panopticon> Date: Tue, 23 Sep 2014 15:05:29 +0200 Message-Id: <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> <542105A3.4090507@iki.fi> <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> <20140923114447.GB1301@hades.panopticon> To: Dmitry Marakasov X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org, Pasi Parviainen 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, 23 Sep 2014 13:05:49 -0000 --Apple-Mail=_DE65C05B-4598-447D-A276-C96632AC7B52 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 23 Sep 2014, at 13:44, Dmitry Marakasov wrote: > * Dimitry Andric (dim@FreeBSD.org) wrote: >=20 >>> This seems to be same issue as in >>> http://llvm.org/bugs/show_bug.cgi?id=3D20893 for which there is = patch >>> review going >>> on = http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/23641= 5.html. >>>=20 >>> Your test case is reproducible with the trunk of llvm/clang and >>> the patch in review resolves it. Other workaround is to disable >>> generation of debug information by removing -g flag. >>=20 >> Hm, I had assumed this problem was fixed by importing r203311 from >> upstream llvm trunk, in head r263313. But apparently it is not. >>=20 >> The upstream patch seems to fix your specific test case, but it is = still >> in review, so I prefer to wait until it is actually committed, before = I >> import it. >=20 > Which worries me is what we do if it's not reviewd until the release. = We > can't just tell users to "remove -g flag", can't we? I don't expect the review to take very long, but this is how it goes with releases. At some point, the release is cut, some bugs don't get fixed, and you will simply have to live with them. In any case, it entirely depends on how many ports it affects. I have the impression it is just a few particular ports having this issue? -Dimitry --Apple-Mail=_DE65C05B-4598-447D-A276-C96632AC7B52 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----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlQhcB4ACgkQsF6jCi4glqOiwgCg82MucrJ2w4sSohXqrG7Yb6jT VwQAn1ueoLb/j54vQEjbTMyhV/d3AqS7 =9Jdh -----END PGP SIGNATURE----- --Apple-Mail=_DE65C05B-4598-447D-A276-C96632AC7B52-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 17:59:31 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 62026F90; Tue, 23 Sep 2014 17:59:31 +0000 (UTC) Received: from smtpout1.timeweb.ru (smtpout1.timeweb.ru [92.53.117.15]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F315A7; Tue, 23 Sep 2014 17:59:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=amdmi3.ru; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=PFr/udPhUhdHcqCxWxva2GKdwN7gKpXdEG7L3eIAd24=; b=OjlLP5PluI9U6UE7lP7I9qfB/ZcR6utZnTyopr0TO/7HDfMAXz4q5shoAR270zRACt0pC01tWMHuYqyAzOAlViatr9A/jskskzOpU84cRe73jisaqiHGPcQX5ouLyUQBSxVek7uGJySgbZJMzTgg79qPuc4QpAm4NhEC3c3LZJI=; Received: from [213.148.20.85] (helo=hive.panopticon) by smtp.timeweb.ru with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1XWUN1-0006qx-8D; Tue, 23 Sep 2014 21:59:23 +0400 Received: from hades.panopticon (hades.panopticon [192.168.0.32]) by hive.panopticon (Postfix) with ESMTP id 93557549; Tue, 23 Sep 2014 21:59:22 +0400 (MSK) Received: by hades.panopticon (Postfix, from userid 1000) id 6DFF619213; Tue, 23 Sep 2014 21:59:22 +0400 (MSK) Date: Tue, 23 Sep 2014 21:59:22 +0400 From: Dmitry Marakasov To: Dimitry Andric Subject: Re: clang (both 3.3 and 3.4) OOM crashes on HEAD Message-ID: <20140923175922.GA98560@hades.panopticon> References: <20140228143606.GD29171@hades.panopticon> <20140228154328.GA13454@hades.panopticon> <20140922231016.GA1301@hades.panopticon> <542105A3.4090507@iki.fi> <98949B82-4109-4628-BE4E-9817D5614D8A@FreeBSD.org> <20140923114447.GB1301@hades.panopticon> <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <0DFE857D-C33C-49BF-BCCE-16E89DB77AF1@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-toolchain@freebsd.org, freebsd-stable@FreeBSD.org, Pasi Parviainen 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, 23 Sep 2014 17:59:31 -0000 * Dimitry Andric (dim@FreeBSD.org) wrote: > >>> This seems to be same issue as in > >>> http://llvm.org/bugs/show_bug.cgi?id=20893 for which there is patch > >>> review going > >>> on http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20140922/236415.html. > >>> > >>> Your test case is reproducible with the trunk of llvm/clang and > >>> the patch in review resolves it. Other workaround is to disable > >>> generation of debug information by removing -g flag. > >> > >> Hm, I had assumed this problem was fixed by importing r203311 from > >> upstream llvm trunk, in head r263313. But apparently it is not. > >> > >> The upstream patch seems to fix your specific test case, but it is still > >> in review, so I prefer to wait until it is actually committed, before I > >> import it. > > > > Which worries me is what we do if it's not reviewd until the release. We > > can't just tell users to "remove -g flag", can't we? > > I don't expect the review to take very long, but this is how it goes > with releases. At some point, the release is cut, some bugs don't get > fixed, and you will simply have to live with them. That seems too critical for me to live with it. > In any case, it entirely depends on how many ports it affects. I have > the impression it is just a few particular ports having this issue? Probably yes, but more important is user's private code which may be also affected. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 18:51:22 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8176E441 for ; Tue, 23 Sep 2014 18:51:22 +0000 (UTC) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 4C806935 for ; Tue, 23 Sep 2014 18:51:22 +0000 (UTC) Received: by mail-oi0-f49.google.com with SMTP id x69so5077446oia.36 for ; Tue, 23 Sep 2014 11:51:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=iplYfYWSI8Bu3ArUEr+CMiNchzjVDv7BSkqg1Aw47qM=; b=gyn1CcvPfmpZXTGwDt8aziVUDPYXd+amEPbWvjlYA6EpFJTmvT8FKhJMoFeOtuYEL6 ogPWn4VgHdtRFMEjEeFKyt1IJkZjawqzjH16K07pOPfLw3DSiCzV56NfevZEPToBDydD TNf/w2K2s+Ija0QaMkYy0do1T0Mmzy7otq+VAF6dlgL/C0tvffijHaxINhvoeQXXqZoi wQwqqcJzR31CVDMYGTMG7bXwx/DzLkTI4U+52euSEZ3wU0KRN6fH8C55yO88iXvFwJ8u FylpZxw6/NkuIoNDL7hA9mb7Ej4X14ZdDmRHCfEH6yOs3X6edb49O0L5TXUcXJdVTBs8 lJzA== MIME-Version: 1.0 X-Received: by 10.182.215.134 with SMTP id oi6mr1758489obc.84.1411498281540; Tue, 23 Sep 2014 11:51:21 -0700 (PDT) Received: by 10.182.228.51 with HTTP; Tue, 23 Sep 2014 11:51:21 -0700 (PDT) In-Reply-To: <54215969.1070303@pean.org> References: <54215969.1070303@pean.org> Date: Tue, 23 Sep 2014 20:51:21 +0200 Message-ID: Subject: Re: FreeBSD with Huawei 3g modem. From: Oliver Pinter To: =?ISO-8859-1?Q?Peter_Ankerst=E5l?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Tue, 23 Sep 2014 18:51:22 -0000 On 9/23/14, Peter Ankerst=E5l wrote: > Hi! > > Im trying to get a Huawei E3531 to work in FreeBSD. But Im not really > sure where to start. I found this: > http://technotation.com/2012/08/15/freebsd-and-mobile-broadband/ but > havent had any luck cut and pasting here. > > System: > # uname -srm > FreeBSD 10.0-RELEASE amd64 > > When I connect it dmesg says: > usb_alloc_device: Found possible auto-install disk (trying next config) > ugen0.4: at usbus0 > umass0: on usbus= 0 > umass0: SCSI over Bulk-Only; quirks =3D 0x0000 > umass0:5:0:-1: Attached to scbus5 > da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 > da0: Removable Direct Access SCSI-2 device > da0: Serial Number FFFFFFFFFFFFFFFF > da0: 40.000MB/s transfers > da0: Attempt to query device size failed: NOT READY, Medium not present > da0: quirks=3D0x2 > > usbconfig gives this: > > # usbconfig -u 0 -a 4 dump_device_desc > ugen0.4: at usbus0, cfg=3D1 md=3DHOST spd=3DHIGH > (480Mbps) pwr=3DON (500mA) > > bLength =3D 0x0012 > bDescriptorType =3D 0x0001 > bcdUSB =3D 0x0200 > bDeviceClass =3D 0x0000 > bDeviceSubClass =3D 0x0000 > bDeviceProtocol =3D 0x00ff > bMaxPacketSize0 =3D 0x0040 > idVendor =3D 0x12d1 > idProduct =3D 0x157d > bcdDevice =3D 0x0102 > iManufacturer =3D 0x0001 > iProduct =3D 0x0002 > iSerialNumber =3D 0x0003 > bNumConfigurations =3D 0x0002 > > > http://hup.hu/node/122403 From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 21:38:54 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A2BAE582 for ; Tue, 23 Sep 2014 21:38:54 +0000 (UTC) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id 66CACC8F for ; Tue, 23 Sep 2014 21:38:53 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id 581D720E7088D; Tue, 23 Sep 2014 21:38:46 +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.9 required=8.0 tests=AWL,BAYES_05,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 A110420E70886; Tue, 23 Sep 2014 21:38:44 +0000 (UTC) Message-ID: From: "Steven Hartland" To: "John Marshall" , References: <20140918235130.GA3070@rwpc15.gfn.riverwillow.net.au> Subject: Re: MFC missing for mfiutil(8) in 10-STABLE Date: Tue, 23 Sep 2014 22:38:42 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; 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, 23 Sep 2014 21:38:54 -0000 ----- Original Message ----- From: "John Marshall" Thanks for the reminder John this has now been done. Regards Steve From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 21:49:41 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB3CD874; Tue, 23 Sep 2014 21:49:41 +0000 (UTC) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::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 56F97D93; Tue, 23 Sep 2014 21:49:39 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id b6so4295337lbj.40 for ; Tue, 23 Sep 2014 14:49:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dKbyHizxswGMMs6buOd1RQFaJd/396VY1iWWtzfE2mc=; b=0R14gmbpQDAVF+LvWbdfTiAzk/K0ngJTni5A2dZI+HM4x/u9GLCaAazBzLZKMnRv8x oVmN4Ztpv6f/8WfJ0nswfDwuiFhLQ64uErneFQXC/hAAYGhAB1uyzRuKOxvy3a0PBTUG umsTJ8O+GIUtEVMAyBedLqTgPa7z1wDdQosWQg/gqpH7ZNq+StI9nKlv/UzMrChfymQv lUziPYvXQmekvFy9A4uENIRNxgYLLS0WplEinlKBUZWydGq6l3Sgli2EF0M8L1varoly NThIKvgNDqAU+Ni8PJkVFAcPdmXRSqCbMWkylvUr8FgKR32YKIjqTf0z8tz3yJ+KF2Kl xNkg== MIME-Version: 1.0 X-Received: by 10.152.170.227 with SMTP id ap3mr2227893lac.15.1411508977225; Tue, 23 Sep 2014 14:49:37 -0700 (PDT) Received: by 10.25.36.70 with HTTP; Tue, 23 Sep 2014 14:49:37 -0700 (PDT) In-Reply-To: <54213713.7020200@sorbs.net> References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> Date: Tue, 23 Sep 2014 14:49:37 -0700 Message-ID: Subject: Re: pkg 1.3.8 requested but not available? From: Patrick Gibson To: Michelle Sullivan Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "ports@freebsd.org" , Baptiste Daroussin , Cristiano Deana , 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: Tue, 23 Sep 2014 21:49:41 -0000 On Tue, Sep 23, 2014 at 2:02 AM, Michelle Sullivan wrote: > Baptiste Daroussin wrote: > > > >> root:/tmp # portupgrade -nr dbus > >> ---> Session started at: Tue, 23 Sep 2014 09:08:37 +0200 > >> ** Port marked as IGNORE: devel/dbus: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: devel/eggdbus: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: sysutils/policykit: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: devel/gconf2: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: devel/dbus-glib: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: sysutils/polkit: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ** Port marked as IGNORE: devel/dconf: > >> pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. > >> You must upgrade pkg(8) first > >> ---> Listing the results (+:done / -:ignored / *:skipped / !:failed) > >> - devel/dbus (marked as IGNORE) > >> - devel/eggdbus (marked as IGNORE) > >> - sysutils/policykit (marked as IGNORE) > >> - devel/gconf2 (marked as IGNORE) > >> - devel/dbus-glib (marked as IGNORE) > >> - sysutils/polkit (marked as IGNORE) > >> - devel/dconf (marked as IGNORE) > >> ---> Packages processed: 0 done, 7 ignored, 0 skipped and 0 failed > >> ---> Session ended at: Tue, 23 Sep 2014 09:08:37 +0200 (consumed > 00:00:00) > >> > >> root:/tmp # portupgrade pkg > >> > >> root:/tmp # pkg upgrade pkg > >> Updating FreeBSD repository catalogue... > >> FreeBSD repository is up-to-date. > >> All repositories are up-to-date. > >> Checking integrity... done (0 conflicting) > >> Your packages are up to date. > >> > >> root:/tmp # > >> > >> what am I missing? > >> > > > > You are using portupgrade so first upgrade pkg with portupgrade > > > > > > Just a thought here - why (like .rpm and .deb - and the reason I hate > them so much) are you making the package manager version a dependency of > a package? I can understand if there are new features that you may need > to use a later version to get those features, but making a package > dependent on the package manager rather than displaying a warning that a > feature is missing is the brain dead way that plagues upgrades for > redhat and debian. Of course if your intent is to make FreeBSD into > another Linux distro just with a different kernel, continue. > > -- > Michelle Sullivan > http://www.mhix.org/ > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > "pkg(8) must be version 1.3.8 or greater, but you have 1.3.7. You must upgrade pkg(8) first" I'm not using portupgrade, and I'm having the same issue. I've run `pkg upgrade pkg` (a command that would be useful to include in the message about needing to upgrade pkg seeing as it's not even in the man page!), but it only updates to 1.3.7. ... Okay, I've found that the latest ports tree has 1.3.8 in ports-mgmt/pkg, so I'm installing it from source. Still baffled why it wasn't working. Was it not sent up to the official pkg servers? Patrick From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 21:53:55 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D413AB2C; Tue, 23 Sep 2014 21:53:55 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (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 1F17BE68; Tue, 23 Sep 2014 21:53:54 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id d1so6096998wiv.3 for ; Tue, 23 Sep 2014 14:53:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rbgCUhPGZydGBjB0zNyYOTQ1bh9U481RfjEWvlcErRE=; b=jbaVTIMYdgB2BLx8/kdZ0PxcxaQQubzRf6WC9wcS5U2bm3ErIPI7S/YLhXf2PtUKNt OymuImaQ2vR6TAxBtENo2IUVUYvTbLuBYI3onE09ovkpG5ft3DBSU8+nRY2qHHn4CI1u JXovx8paMcJdCBW+LO4bSDohdwgkVKFrrWcIznZwtG582+7yKZE63BMVD7WzUB9qfyBa FFqnt80gJqjAwgob3ca2Ek/N117I6IsYJ8Pzh3H0EKaAj1NVhaofzGOezlg2AB9bA88S tPewzYLlSollVNCxUY5SEl56nb2i1q/0rsG13DXqdXlaFcW/s33V6lTIFcJ7EuMNpD33 CoZQ== MIME-Version: 1.0 X-Received: by 10.194.88.195 with SMTP id bi3mr3115184wjb.10.1411509233469; Tue, 23 Sep 2014 14:53:53 -0700 (PDT) Received: by 10.217.2.18 with HTTP; Tue, 23 Sep 2014 14:53:53 -0700 (PDT) In-Reply-To: References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> Date: Tue, 23 Sep 2014 17:53:53 -0400 Message-ID: Subject: Re: pkg 1.3.8 requested but not available? From: Brandon Allbery To: Patrick Gibson Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "ports@freebsd.org" , Baptiste Daroussin , Cristiano Deana , FreeBSD Stable Mailing List , Michelle Sullivan 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, 23 Sep 2014 21:53:56 -0000 On Tue, Sep 23, 2014 at 5:49 PM, Patrick Gibson wrote: > Okay, I've found that the latest ports tree has 1.3.8 in ports-mgmt/pkg, so > I'm installing it from source. Still baffled why it wasn't working. Was it > not sent up to the official pkg servers? > I would guess that, since 1.3.8 needs to rebuild the package database, earlier versions of pkg can't safely install it? The port is likely special in that it uses the just-built pkg to install itself instead of relying on the installed one (otherwise you couldn't bootstrap-install pkg at all). -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 22:35:56 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1AC0C3F8; Tue, 23 Sep 2014 22:35:56 +0000 (UTC) Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (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 23BB4314; Tue, 23 Sep 2014 22:35:54 +0000 (UTC) Received: by mail-lb0-f178.google.com with SMTP id z12so6935907lbi.23 for ; Tue, 23 Sep 2014 15:35:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=e0EB9lF2QICG9x0E3CFr/45+Rh3e4WaQ+kMJklAB+gM=; b=Y9+R4bPx82TuTOHSZKTwSIE7pHyTUlP2qpFc40PSXPr2+34hi104s9OJBMPfmK6mVT It3kGXs2Kv4xliWS5Ue1cSdetnyM7mgbjpNZ4BsS14zF2kEihnQT1Yqd+OAzUE4Gi4GZ 4AkKRpodIdaer3BWlBEb+ScRB48qf7faUtSJ3OHejlL8IrKNSuLi9Jp7ChhA4EtQ8+1U KxyBEPYARb+JthOjXyQAtPmPC/723dr9gods8zlaQ8NGy/7cgHUASxL73hfFa+OJDqtZ T8vvtdznhB/u3XF6zjb13d5oAaAXTNU5wIrm0sX1e8nuGpdpGmHYgUvOvMufbgRlLVae pIPA== MIME-Version: 1.0 X-Received: by 10.152.116.7 with SMTP id js7mr2695434lab.12.1411511752403; Tue, 23 Sep 2014 15:35:52 -0700 (PDT) Received: by 10.25.36.70 with HTTP; Tue, 23 Sep 2014 15:35:52 -0700 (PDT) In-Reply-To: References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> Date: Tue, 23 Sep 2014 15:35:52 -0700 Message-ID: Subject: Re: pkg 1.3.8 requested but not available? From: Patrick Gibson To: Brandon Allbery Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "ports@freebsd.org" , Baptiste Daroussin , Cristiano Deana , FreeBSD Stable Mailing List , Michelle Sullivan 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, 23 Sep 2014 22:35:56 -0000 On Tue, Sep 23, 2014 at 2:53 PM, Brandon Allbery wrote: > > I would guess that, since 1.3.8 needs to rebuild the package database, > earlier versions of pkg can't safely install it? The port is likely special > in that it uses the just-built pkg to install itself instead of relying on > the installed one (otherwise you couldn't bootstrap-install pkg at all). > The port I was trying to install was lang/v8 (3.18.5). I don't see anything in the Makefile that says it needs a particular version of pkg, but maybe it's hidden somewhere else. Either way, something seems broken or not well thought out. This is an up-to-date 10.0 system with a very vanilla configuration. From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 22:40:58 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 54C7D732; Tue, 23 Sep 2014 22:40:58 +0000 (UTC) Received: from spectrum.skysmurf.nl (spectrum.skysmurf.nl [82.95.125.145]) (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 B2155353; Tue, 23 Sep 2014 22:40:57 +0000 (UTC) Received: from spectrum.skysmurf.nl (spectrum.skysmurf.nl [82.95.125.145]) by spectrum.skysmurf.nl (8.14.9/8.14.9) with SMTP id s8NMel8e019547; Wed, 24 Sep 2014 00:40:47 +0200 (CEST) (envelope-from freebsd@skysmurf.nl) Received: by spectrum.skysmurf.nl (sSMTP sendmail emulation); Wed, 24 Sep 2014 00:40:47 +0200 Date: Wed, 24 Sep 2014 00:40:47 +0200 From: "A.J. 'Fonz' van Werven" To: Patrick Gibson Subject: Re: pkg 1.3.8 requested but not available? Message-ID: <20140923224047.GA19527@spectrum.skysmurf.nl> References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.skysmurf.nl/~fonz/fonz_pubkey.asc User-Agent: Mutt/1.5.23 (2014-03-12) Cc: Baptiste Daroussin , FreeBSD Stable Mailing List , "ports@freebsd.org" , Cristiano Deana , Brandon Allbery , Michelle Sullivan 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, 23 Sep 2014 22:40:58 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Patrick Gibson wrote: > Either way, something seems broken or not well thought out. It also appears to have broken Tinderbox, BTW. If I got that wrong, forget I said anything. But if it's right: nice job! AvW --=20 Imbibo, ergo sum. --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUIfbvAAoJEAfP7gJTaCe8BbAP+wch1J1QxbuyY3Y+Ne48JWcc 5E6HcEHrGN2sKOML0sl1mWS+oYtS4S/H7mU1obRFMJQmqXb5rEsom1AmFr9W3au2 8i4ZS7SbXf75UjZ2HByrp5vxWlp9MEv5jeYAjD9iCjZExI9G43OR5iK1M1s3Ml5T I6QPEtr6uRtz+Azpj1sY5JrSqTiwBfKVDyeTbNiqtoEB/KM2oeTew7HJ4mB0BQF+ 7Ll/q4gpqjNJ6J0Sy+9hMB53G8uGBks3+T999HZQ6CnEXqpeS/NT0KlCBnjZ3Qp5 8s0o5PDJCVrlKM2jcPHqwSi4St6ZJyXqrcxrAuipfAgex/gvkphHMJEG1O1Z7pJr Cmlq5EGfMULuINmo4+Ipa/nuLYOY7lvTjHF4qJvlZw0Nt+YJg1RywwmQgiAJg815 tpQD3lX+J99HPERcBF4mlNu7MTpuorN7611OchstsHncEg4AeyzH/YoCP89AmsV0 GHqewTQGxiiPVtjDFt+Xa0l3Y2OhMULdBx3LJQ/oGqvhijrzGlVKv/OxF1u3E+Cc srB8rtHKCo+lPWsbXK7HsjH4D0O0qzMfSaPlfdtY20LTMp/XW+BFc7QlrrRakQ62 BoZS9dpBymeGja8fF8CL1zWVMF62T10b3txh6Hu354ngbuHXiWkJQiVcZQnJjbpF TyXWy8WB5BoMhQe9DBgb =fr7E -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk-- From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 22:41:08 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BCA178AB; Tue, 23 Sep 2014 22:41:08 +0000 (UTC) Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) (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 065A5359; Tue, 23 Sep 2014 22:41:07 +0000 (UTC) Received: by mail-we0-f169.google.com with SMTP id k48so5241703wev.28 for ; Tue, 23 Sep 2014 15:41:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=k/cPHxBcQxBBw4qed8hsDwPRhJDEyytNn1/qf4ZayEs=; b=fHN3A2///w25mg1lGnbUnDZCr6QnpEJeSauXAZ3J4tc2j9EmPKve2ZC50Q9trM2E5T GYbfxdR9Y0DJ/RZeuWDzz+xyYuvWFpKzJMwBNAi61wP6lrRBK7dVHXC6CfKGbSKr/m/4 0ZNGhXWVKc43/09WYCo+vEmtYAteA11Z29GWP0kD7MoEav09avIzhMXSZza4bT2eqtbv oMOVd5cMgENoeCCFDnVh0ycwm4LpXVp6eK9eS7bZL2jVxxC3FRRcreXzfow0dzemY3xC rOiEQItxNRp/a2WcZ0BkTCA0McgCYfEnNAyau4N4RFu7T/l7GgAEjSeVU9MQL1Mfmjdz WBOg== MIME-Version: 1.0 X-Received: by 10.194.120.101 with SMTP id lb5mr3131890wjb.84.1411512064904; Tue, 23 Sep 2014 15:41:04 -0700 (PDT) Received: by 10.217.2.18 with HTTP; Tue, 23 Sep 2014 15:41:04 -0700 (PDT) In-Reply-To: References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> Date: Tue, 23 Sep 2014 18:41:04 -0400 Message-ID: Subject: Re: pkg 1.3.8 requested but not available? From: Brandon Allbery To: Patrick Gibson Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "ports@freebsd.org" , Baptiste Daroussin , Cristiano Deana , FreeBSD Stable Mailing List , Michelle Sullivan 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, 23 Sep 2014 22:41:08 -0000 On Tue, Sep 23, 2014 at 6:35 PM, Patrick Gibson wrote: > The port I was trying to install was lang/v8 (3.18.5). I don't see > anything in the Makefile that says it needs a particular version of pkg, > but maybe it's hidden somewhere else. Either way, something seems broken or > not well thought out. This is an up-to-date 10.0 system with a very vanilla > configuration. I think it's the ports system *itself* that now requires it, not particular ports. Again, see /usr/ports/UPDATING. (That said, I will not argue that ports has shortcomings; it feels rather primitive after years of using MacPorts. But these shortcomings mostly fall out of the ports system itself --- and it's entirely possible that addressing them requires things like the new pkg, given that ports are installed via pkg.) -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@FreeBSD.ORG Tue Sep 23 23:29:39 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 669366C5; Tue, 23 Sep 2014 23:29:39 +0000 (UTC) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (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 B28ECA83; Tue, 23 Sep 2014 23:29:38 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id hz20so9647326lab.1 for ; Tue, 23 Sep 2014 16:29:36 -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=qFWV2/9zd+bibdjRux3FaAt25dEJ3xlJMn8p3IxDcEU=; b=FfVT2+8lK9ciyYJbqBfd0j0VY8HWQwgnYR+e1jlb3jyQJgv1GGHbaaZof5Hm1Ainc8 ZhiePcD3JEUs5u0jk6H2seOcfQ98byyYQiz4b617otxzdcvvOQD78pfL3Y8xI0XZz3A3 +eK6MLagY5ubzqG9t1hX4YG7BXxczrJUGg6XUdz05zUacwpoQ3P4PYeohcSSa6vw6X94 ua93fNkDXwiMPejwXIdBwA9HyKfrf1SOjFPda5z1BNUDLmsNUk2Kby2w8KIBvPcVEtTl T9ZUaKqirVPqt1QDdkzsjJrXOIr/h5hj0hUxNzfMFj0PkKY2UjJGXBiNupDb+Hi9hbNn MfLg== MIME-Version: 1.0 X-Received: by 10.152.29.100 with SMTP id j4mr2524788lah.47.1411514976513; Tue, 23 Sep 2014 16:29:36 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.197.107 with HTTP; Tue, 23 Sep 2014 16:29:36 -0700 (PDT) In-Reply-To: References: <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> Date: Tue, 23 Sep 2014 16:29:36 -0700 X-Google-Sender-Auth: mBebW8003YFF7WdZ6fyMx-1aWnU Message-ID: Subject: Re: pkg 1.3.8 requested but not available? From: Craig Rodrigues To: Patrick Gibson Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "ports@freebsd.org" , 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: Tue, 23 Sep 2014 23:29:39 -0000 On Tue, Sep 23, 2014 at 3:35 PM, Patrick Gibson wrote: > > The port I was trying to install was lang/v8 (3.18.5). I don't see anything > in the Makefile that says it needs a particular version of pkg, but maybe > it's hidden somewhere else. > The MINIMAL_PKG_VERSION variable in /usr/ports/Mk/bsd.port.mk triggers this behavior for all ports. -- Craig From owner-freebsd-stable@FreeBSD.ORG Wed Sep 24 07:10:09 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0C413255 for ; Wed, 24 Sep 2014 07:10:09 +0000 (UTC) Received: from mail.beastielabs.net (unknown [IPv6:2001:888:1227:0:200:24ff:fec9:5934]) (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 BA22FA30 for ; Wed, 24 Sep 2014 07:10:08 +0000 (UTC) Received: from beastie.hotsoft.nl (beastie.hotsoft.nl [IPv6:2001:888:1227:0:219:d1ff:fee8:91eb]) by mail.beastielabs.net (8.14.7/8.14.7) with ESMTP id s8O7A5bm074405 for ; Wed, 24 Sep 2014 09:10:05 +0200 (CEST) (envelope-from hans@beastielabs.net) Message-ID: <54226E4D.1040704@beastielabs.net> Date: Wed, 24 Sep 2014 09:10:05 +0200 From: Hans Ottevanger User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Aitofs: spurious (?) jog messages and zombies from automountd 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: Wed, 24 Sep 2014 07:10:09 -0000 Hi, When accessing a directory for the first time on /net, automounted using the new autofs, I reproducibly get error messages in the log. I have exported a single directory (read/write) from my test server: $ showmount -e soekris Exports list on soekris: /home My client runs 10-STABLE, also known as 10.1-BETA2 these days, updated to r272021. The kernel config is GENERIC minus devices that I do not have, with AUTOFS added. When accessing the server for the first time using: ls /net/soekris/home/hans I get the expected directory listing but immediately also see the following in /var/log/messages: Sep 24 07:39:09 beastie automountd[1554]: child process 2096 terminated with exit status 1 Sep 24 07:39:09 beastie automountd[1554]: child process 2101 terminated with exit status 1 Additionally, a zombie process keep hanging forever: $ pstree 1554 -+= 01554 root /usr/sbin/automountd \--- 02106 root When I wait until the directory is autounmounted and retry the access, the zombie disappears (apparently finally waited for) and I get two others in return: $ pstree 1554 -+= 01554 root /usr/sbin/automountd |--- 02658 root \--- 02663 root and a few extra log messages: Sep 24 08:52:17 beastie automountd[1554]: child process 2106 terminated with exit status 1 Sep 24 08:52:17 beastie automountd[1554]: child process 2653 terminated with exit status 1 Is anyone else seeing this? Do I miss something? Is this expected behavior? Kind regards, Hans From owner-freebsd-stable@FreeBSD.ORG Wed Sep 24 07:38: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 44FAE9E7; Wed, 24 Sep 2014 07:38:24 +0000 (UTC) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (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 C5E38CE8; Wed, 24 Sep 2014 07:38:23 +0000 (UTC) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id s8O7cJiq086430; Wed, 24 Sep 2014 09:38:19 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 0D4A43145; Wed, 24 Sep 2014 09:38:13 +0200 (CEST) Message-ID: <542274E0.9000305@omnilan.de> Date: Wed, 24 Sep 2014 09:38:08 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: FreeBSD Stable , Glen Barber Subject: MFC conf/158171, rc.d/ftp-proxy multiple instances X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6E0041053C5188C161395751" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Wed, 24 Sep 2014 09:38:19 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) 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: Wed, 24 Sep 2014 07:38:24 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6E0041053C5188C161395751 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Hello, this comitt had no MFC reminder set: http://svnweb.freebsd.org/base?view=3Drevision&revision=3D258080 But I guess it's a nice feature which could me merged straight forward. Any chance to bring it into 10.1? Thanks, -Harry --------------enig6E0041053C5188C161395751 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlQidOUACgkQLDqVQ9VXb8iuigCgvBuTD/hG6VTOAcxTXLT37WhF YugAmgJ7yXNp0NvrUd5RgE/u0lKJ7KSh =0PDl -----END PGP SIGNATURE----- --------------enig6E0041053C5188C161395751-- From owner-freebsd-stable@FreeBSD.ORG Wed Sep 24 11:08: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 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A2CB3F0; Wed, 24 Sep 2014 11:08:21 +0000 (UTC) Date: Wed, 24 Sep 2014 07:08:15 -0400 From: Glen Barber To: Harald Schmalzbauer Subject: Re: MFC conf/158171, rc.d/ftp-proxy multiple instances Message-ID: <20140924110815.GA38905@hub.FreeBSD.org> References: <542274E0.9000305@omnilan.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline In-Reply-To: <542274E0.9000305@omnilan.de> 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 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: Wed, 24 Sep 2014 11:08:21 -0000 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 24, 2014 at 09:38:08AM +0200, Harald Schmalzbauer wrote: > Hello, >=20 > this comitt had no MFC reminder set: > http://svnweb.freebsd.org/base?view=3Drevision&revision=3D258080 > But I guess it's a nice feature which could me merged straight forward. >=20 > Any chance to bring it into 10.1? >=20 You should check with the original committer of the change. There may be a reason MFC timeframe was not set. Glen --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUIqYfAAoJELls3eqvi17QS8UP+gISaYequZSWd4cxTqDQkWJE 0okhWNKAMaGVlQ+kUnMoj9OSXRFo4udknvW4i/XH1OyKJE39B3mksAHOBQTQVpJj DnmNVIWoWtudrwAIk/+wxojn4Lbb6jHQZMprIRKPj/LSdrZled1Sdc/zmT8P39rq +KaiNRmO1XyNNym3Eol6a6jiuIWjv/BhNFQbh1W/k0A+Htp9l0H0H/ocMxIcqVAI Npwe92gYcPYRfHFLXNvbAcoMIbcUgp3O+AMdqBYgZtmI3val8RqgYAv5BE9R7w2J Gkmfc8/rBxtRlSZjVhhBo0QommYEgLdxEIKlA9MufgfQyHQqD2PN9rx5htoyWUAj qXCLMWFDJ0EmUXzmXJ+0CoNXQwpbLfNCUdD/94i2sBMP8cDy4iZdY09RC+at9pXd c/866HAIEPivXUTz88EO0YiTrcSj0tU1apMG9gl8dQLKNrYkpMyBkyyV3JGQ/Ccm 1wabC9f5DSf0WsjHyFhLGUVB/aRSVq2ySZYD9/VQ4+SXMxiwENUr8otED8NTDpMd GxxIpsjWAI+8Ifadrb4AXXIuPL0Y4K73ds3dpEmUSUzR6ydJRr15KIdF3LNUA3ec YeZ4NTj+o0cO8HJirKh3W8tLwX8/dP1WEfbFjOQcL2tD0JMudoR1yzs24F6wcIdz kztReflUr6hbx4flm3WC =AIOf -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 09:40: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6938187D; Thu, 25 Sep 2014 09:40:52 +0000 (UTC) Received: from erg.verweg.com (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "erg.verweg.com", Issuer "Verweg Dot Com CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F1792F68; Thu, 25 Sep 2014 09:40:51 +0000 (UTC) Received: from [192.168.199.28] (office.proserve.nl [83.96.170.3]) (authenticated bits=0) by erg.verweg.com (8.14.9/8.14.9) with ESMTP id s8P9elHB009769 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 25 Sep 2014 09:40:48 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host office.proserve.nl [83.96.170.3] claimed to be [192.168.199.28] From: Ruben van Staveren Content-Type: multipart/signed; boundary="Apple-Mail=_6E1288A7-032E-4C1B-91FC-ACB81AE43299"; protocol="application/pgp-signature"; micalg=pgp-sha1 Subject: fdescfs patch for working hierarchical jails Message-Id: <0B3648E9-21DC-4691-A6A9-26DE2C40947B@verweg.com> Date: Thu, 25 Sep 2014 11:40:43 +0200 To: freebsd-jail@freebsd.org, "freebsd-stable@FreeBSD.org Stable" Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (erg.verweg.com [94.142.245.8]); Thu, 25 Sep 2014 09:40:48 +0000 (UTC) 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: Thu, 25 Sep 2014 09:40:52 -0000 --Apple-Mail=_6E1288A7-032E-4C1B-91FC-ACB81AE43299 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, Could a committer have a look at = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192951 ?=20 This enables fdescfs in hierarchical jails, would be nice to have this = for 10.1 Thanks! Best Regards, Ruben van Staveren --Apple-Mail=_6E1288A7-032E-4C1B-91FC-ACB81AE43299 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 - http://gpgtools.org iEYEARECAAYFAlQj4xsACgkQZ88+mcQxRw3kDgCfQwphlrMqxik+95Q3N1k0fYhq 0gAAn1R1us1E0J+tWbs1DZq7YUgDECJQ =21pb -----END PGP SIGNATURE----- --Apple-Mail=_6E1288A7-032E-4C1B-91FC-ACB81AE43299-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 14:54: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CA05C416 for ; Thu, 25 Sep 2014 14:54:33 +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 9104A9AC for ; Thu, 25 Sep 2014 14:54:33 +0000 (UTC) Received: from www.tundraware.com (localhost [127.0.0.1]) by ozzie.tundraware.com (8.14.9/8.14.9) with ESMTP id s8PEsHFq020784 for ; Thu, 25 Sep 2014 09:54:17 -0500 (CDT) (envelope-from tundra@tundraware.com) Received: from 192.168.0.2 (SquirrelMail authenticated user tundra) by www.tundraware.com with HTTP; Thu, 25 Sep 2014 09:54:17 -0500 Message-ID: Date: Thu, 25 Sep 2014 09:54:17 -0500 Subject: 10.1 BETA2 World - Breaks saslauthd From: "Tim Daneliuk" To: freebsd-stable@freebsd.org Reply-To: tundra@tundraware.com User-Agent: SquirrelMail/1.4.23 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [127.0.0.1]); Thu, 25 Sep 2014 09:54:17 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s8PEsHFq020784 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: Thu, 25 Sep 2014 14:54:33 -0000 I've seen this behavior over the last week or two when I try to upgrade to latest stable sources. Currently just installed kernel and world for: /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: 272095 Node Kind: directory Schedule: normal Last Changed Author: peter Last Changed Rev: 272078 Last Changed Date: 2014-09-24 14:30:36 -0500 (Wed, 24 Sep 2014) This breaks saslauthd - it demands a password when sending mail, but then rejects it in every case. If I just install a new kernel, everything is fine. But if I install world, that's when the problem shows up. I've tried a full reinstall of cygnus sasls and the daemon is running. Ideas on how to chase this down/fix, would be appreciated... -- Tim Daneliuk tundra@tundraware.com From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 14:57:56 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 535755A2 for ; Thu, 25 Sep 2014 14:57:56 +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 252C69DC for ; Thu, 25 Sep 2014 14:57:55 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by gateway2.nyi.internal (Postfix) with ESMTP id 24623152E for ; Thu, 25 Sep 2014 10:57:48 -0400 (EDT) Received: from web6 ([10.202.2.216]) by compute2.internal (MEProxy); Thu, 25 Sep 2014 10:57:48 -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=MKra+bxQ1TK2/iJ20fS3cgx2 JSI=; b=PfkBEu8rkQIGWHkpp0Ikp0ZTBxhMKk5/Rf4CICKwkC8JpOyr6qQ2bmON BYv99Zxu0lLDEZG1DyPdq7VhZPiHYGuA2ZeGoMUTQCozxUrLekreOhSS3GdlAT5g dxd4Ktgg5lf787I5zKMm2PCpY+cyqKPzN7+HbymSfQBMEFIbUwI= Received: by web6.nyi.internal (Postfix, from userid 99) id D791A56FA9; Thu, 25 Sep 2014 10:57:47 -0400 (EDT) Message-Id: <1411657067.3412055.171698001.1C4FCF93@webmail.messagingengine.com> X-Sasl-Enc: aa1qiIuY33xe7X66S0CCxGBEMcIh+v3sXJDDCFsc+0pa 1411657067 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: References: Subject: Re: 10.1 BETA2 World - Breaks saslauthd Date: Thu, 25 Sep 2014 09:57:47 -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: Thu, 25 Sep 2014 14:57:56 -0000 On Thu, Sep 25, 2014, at 09:54, Tim Daneliuk wrote: > I've seen this behavior over the last week or two when I try to upgrade > to latest stable sources. Currently just installed kernel and world for: > > /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: 272095 > Node Kind: directory > Schedule: normal > Last Changed Author: peter > Last Changed Rev: 272078 > Last Changed Date: 2014-09-24 14:30:36 -0500 (Wed, 24 Sep 2014) > > This breaks saslauthd - it demands a password when sending mail, but then > rejects it in every case. > > If I just install a new kernel, everything is fine. But if I install > world, that's when the problem shows up. I've tried a full reinstall of > cygnus sasls and the daemon is running. > > Ideas on how to chase this down/fix, would be appreciated... > What version of saslauthd? Also, did you just reinstall it or did you rebuild it? From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 14:59:30 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B80666B1 for ; Thu, 25 Sep 2014 14:59:30 +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 7D12E9FA for ; Thu, 25 Sep 2014 14:59:29 +0000 (UTC) Received: from www.tundraware.com (localhost [127.0.0.1]) by ozzie.tundraware.com (8.14.9/8.14.9) with ESMTP id s8PExKlS020910 for ; Thu, 25 Sep 2014 09:59:20 -0500 (CDT) (envelope-from tundra@tundraware.com) Received: from 192.168.0.2 (SquirrelMail authenticated user tundra) by www.tundraware.com with HTTP; Thu, 25 Sep 2014 09:59:21 -0500 Message-ID: <19e009915c65cb66d41454d67acc540c.squirrel@www.tundraware.com> In-Reply-To: References: Date: Thu, 25 Sep 2014 09:59:21 -0500 Subject: Re: 10.1 BETA2 World - Breaks saslauthd From: "Tim Daneliuk" To: freebsd-stable@freebsd.org Reply-To: tundra@tundraware.com User-Agent: SquirrelMail/1.4.23 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [127.0.0.1]); Thu, 25 Sep 2014 09:59:21 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s8PExKlS020910 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: Thu, 25 Sep 2014 14:59:30 -0000 On Thu, September 25, 2014 9:54 am, Tim Daneliuk wrote: > I've seen this behavior over the last week or two when I try to upgrade > to latest stable sources. Currently just installed kernel and world for: > > /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: 272095 > Node Kind: directory > Schedule: normal > Last Changed Author: peter > Last Changed Rev: 272078 > Last Changed Date: 2014-09-24 14:30:36 -0500 (Wed, 24 Sep 2014) > > This breaks saslauthd - it demands a password when sending mail, but then > rejects it in every case. > > If I just install a new kernel, everything is fine. But if I install > world, that's when the problem shows up. I've tried a full reinstall of > cygnus sasls and the daemon is running. > > Ideas on how to chase this down/fix, would be appreciated... > Oh, and the log message is this: saslauthd[19268]: in openpam_check_error_code(): pam_sm_acct_mgmt(): unexpected return value 12 -- Tim Daneliuk tundra@tundraware.com From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 15:04:51 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 350F29A8; Thu, 25 Sep 2014 15:04:51 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E4EFBAD6; Thu, 25 Sep 2014 15:04:50 +0000 (UTC) Received: from [192.168.2.2] (unknown [77.243.161.229]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 9F0ECB80A; Thu, 25 Sep 2014 17:04:41 +0200 (CEST) Subject: Re: 10.1 BETA2 World - Breaks saslauthd Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_B0D47E19-7B95-4D1F-AF1A-6324FA113E38"; protocol="application/pgp-signature"; micalg=pgp-sha1 From: Dimitry Andric X-Priority: 3 (Normal) In-Reply-To: Date: Thu, 25 Sep 2014 17:04:24 +0200 Message-Id: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> References: To: tundra@tundraware.com X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD stable , =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= 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: Thu, 25 Sep 2014 15:04:51 -0000 --Apple-Mail=_B0D47E19-7B95-4D1F-AF1A-6324FA113E38 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 25 Sep 2014, at 16:54, Tim Daneliuk wrote: > I've seen this behavior over the last week or two when I try to = upgrade > to latest stable sources. Currently just installed kernel and world = for: >=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: 272095 > Node Kind: directory > Schedule: normal > Last Changed Author: peter > Last Changed Rev: 272078 > Last Changed Date: 2014-09-24 14:30:36 -0500 (Wed, 24 Sep 2014) >=20 > This breaks saslauthd - it demands a password when sending mail, but = then > rejects it in every case. >=20 > If I just install a new kernel, everything is fine. But if I install > world, that's when the problem shows up. I've tried a full reinstall = of > cygnus sasls and the daemon is running. >=20 > Ideas on how to chase this down/fix, would be appreciated... It is probably caused by this MFC: = http://svnweb.freebsd.org/changeset/base/271766 To make saslauthd work again, you need to specify a correct PAM policy file in /usr/local/etc/pam.d for your service, most likely "smtp" in this case. E.g., create a file /usr/local/etc/pam.d/smtp, containing at least: auth required pam_unix.so no_warn = try_first_pass account required pam_unix.so session required pam_permit.so password required pam_permit.so Optionally, add a line: auth required pam_group.so luser = group=3Dsmtp-users fail_safe to allow only members of the smtp-users group to authenticate successfully. -Dimitry --Apple-Mail=_B0D47E19-7B95-4D1F-AF1A-6324FA113E38 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----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlQkLwEACgkQsF6jCi4glqMMuwCfU+JtTD/2d5kfZmhnOrYF3Wam XbkAoOBMxBQG1VlthYoVJoWz+dGgEJFI =oFQb -----END PGP SIGNATURE----- --Apple-Mail=_B0D47E19-7B95-4D1F-AF1A-6324FA113E38-- From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 15:08:44 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E116B60; Thu, 25 Sep 2014 15:08:44 +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 C82BAB22; Thu, 25 Sep 2014 15:08:43 +0000 (UTC) Received: from www.tundraware.com (localhost [127.0.0.1]) by ozzie.tundraware.com (8.14.9/8.14.9) with ESMTP id s8PF8VZ3021280; Thu, 25 Sep 2014 10:08:32 -0500 (CDT) (envelope-from tundra@tundraware.com) Received: from 192.168.0.2 (SquirrelMail authenticated user tundra) by www.tundraware.com with HTTP; Thu, 25 Sep 2014 10:08:33 -0500 Message-ID: <181618028862196817dc472e5d382d02.squirrel@www.tundraware.com> In-Reply-To: <1411657067.3412055.171698001.1C4FCF93@webmail.messagingengine.com> References: <1411657067.3412055.171698001.1C4FCF93@webmail.messagingengine.com> Date: Thu, 25 Sep 2014 10:08:33 -0500 Subject: Re: 10.1 BETA2 World - Breaks saslauthd From: "Tim Daneliuk" To: "Mark Felder" Reply-To: tundra@tundraware.com User-Agent: SquirrelMail/1.4.23 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [127.0.0.1]); Thu, 25 Sep 2014 10:08:33 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s8PF8VZ3021280 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No 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: Thu, 25 Sep 2014 15:08:44 -0000 On Thu, September 25, 2014 9:57 am, Mark Felder wrote: > > > On Thu, Sep 25, 2014, at 09:54, Tim Daneliuk wrote: >> I've seen this behavior over the last week or two when I try to upgrade >> to latest stable sources. Currently just installed kernel and world >> for: >> >> /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: 272095 >> Node Kind: directory >> Schedule: normal >> Last Changed Author: peter >> Last Changed Rev: 272078 >> Last Changed Date: 2014-09-24 14:30:36 -0500 (Wed, 24 Sep 2014) >> >> This breaks saslauthd - it demands a password when sending mail, but >> then >> rejects it in every case. >> >> If I just install a new kernel, everything is fine. But if I install >> world, that's when the problem shows up. I've tried a full reinstall >> of >> cygnus sasls and the daemon is running. >> >> Ideas on how to chase this down/fix, would be appreciated... >> > > What version of saslauthd? Also, did you just reinstall it or did you > rebuild it? I removed it and and rebuilt/installed it from the ports tree: cyrus-sasl-2.1.26_9 RFC 2222 SASL (Simple Authentication and Security Layer) cyrus-sasl-saslauthd-2.1.26_1 SASL authentication server for cyrus-sasl2 I then remove these and installed using 'pkg'. Same results. -- Tim Daneliuk tundra@tundraware.com From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 15:12:54 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7C886CB0; Thu, 25 Sep 2014 15:12:54 +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 2807ABF8; Thu, 25 Sep 2014 15:12:53 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.9/8.14.9) with ESMTP id s8PFChrk021462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 25 Sep 2014 10:12:43 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <542430EB.1040804@tundraware.com> Date: Thu, 25 Sep 2014 10:12:43 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: 10.1 BETA2 World - Breaks saslauthd References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> In-Reply-To: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; 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]); Thu, 25 Sep 2014 10:12:43 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s8PFChrk021462 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Cc: FreeBSD stable , =?windows-1252?Q?Dag-Erl?= =?windows-1252?Q?ing_Sm=F8rgrav?= 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: Thu, 25 Sep 2014 15:12:54 -0000 On 09/25/2014 10:04 AM, Dimitry Andric wrote: >> If I just install a new kernel, everything is fine. But if I install >> world, that's when the problem shows up. I've tried a full reinstall of >> cygnus sasls and the daemon is running. >> >> Ideas on how to chase this down/fix, would be appreciated... > > It is probably caused by this MFC: http://svnweb.freebsd.org/changeset/base/271766 > > To make saslauthd work again, you need to specify a correct PAM policy > file in /usr/local/etc/pam.d for your service, most likely "smtp" in > this case. E.g., create a file /usr/local/etc/pam.d/smtp, containing at > least: > > auth required pam_unix.so no_warn try_first_pass > account required pam_unix.so > session required pam_permit.so > password required pam_permit.so > > Optionally, add a line: > > auth required pam_group.so luser group=smtp-users fail_safe > > to allow only members of the smtp-users group to authenticate > successfully. > > -Dimitry > Yup, that worked. Thanks! Now, for those of us less than smart, could you explain why this was necessary in context of that MFC? Thanks very much ... -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 15:18:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C4031D6; Thu, 25 Sep 2014 15:18:55 +0000 (UTC) Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) (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 7F9D0C6F; Thu, 25 Sep 2014 15:18:54 +0000 (UTC) Received: by mail-we0-f172.google.com with SMTP id p10so7726225wes.3 for ; Thu, 25 Sep 2014 08:18:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tzaEC8rLVtzt1FitEMCZM6v6M8j+uuohCNeBig26c+E=; b=y7UuebIHS1E9NEnFKdVjk40kt2NW2IPg3Ei2g8SmSmxR8aq/Tfp+m6HbnpFG+UGGM2 QEsIp1URp4+fMEFPEMFIkshucIQIVIOAlfEkophXtsA+PK7g7uZMHjAXDh+q9d8xBh8y RZfXm48md1EnVG3chX6DEXxH3NVxiBrO0/Gies0qsjgHLJO5KAu37GNLE9EOyvJZv7yA kTbsqjpi4OEaxTXImlOCFk7MiZEzl+s/vBczYvs3ggO17gHPMrJEwGcuXIh/w8mXV/wT pvWH2Wh8AEv1l83DlCFzwCBfeZXw/3lgVmlHEq6ZajC1i584vAe1+59ntH3Ky2jzD3h9 3u+g== MIME-Version: 1.0 X-Received: by 10.180.74.227 with SMTP id x3mr19699764wiv.80.1411658332726; Thu, 25 Sep 2014 08:18:52 -0700 (PDT) Received: by 10.217.127.70 with HTTP; Thu, 25 Sep 2014 08:18:52 -0700 (PDT) In-Reply-To: <542430EB.1040804@tundraware.com> References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <542430EB.1040804@tundraware.com> Date: Thu, 25 Sep 2014 11:18:52 -0400 Message-ID: Subject: Re: 10.1 BETA2 World - Breaks saslauthd From: Brandon Allbery To: Tim Daneliuk Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD stable , Dimitry Andric , =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= 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: Thu, 25 Sep 2014 15:18:55 -0000 On Thu, Sep 25, 2014 at 11:12 AM, Tim Daneliuk wrote: > Yup, that worked. Thanks! Now, for those of us less than smart, could > you explain why this was necessary in context of that MFC? > To me the implication is that before the MFC, PAM had a potentially quite severe security issue involving either incorrect fallback to a default configuration or not correctly handling error returns from a PAM stack --- either of which could result in unauthorized users being permitted access. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 15:28:04 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C60203AA for ; Thu, 25 Sep 2014 15:28:04 +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 96819D6C for ; Thu, 25 Sep 2014 15:28:04 +0000 (UTC) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by gateway2.nyi.internal (Postfix) with ESMTP id 8069B24DA for ; Thu, 25 Sep 2014 11:28:03 -0400 (EDT) Received: from web6 ([10.202.2.216]) by compute2.internal (MEProxy); Thu, 25 Sep 2014 11:28: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=kALd1AFSROGJCXvOsqjZwPwc JDE=; b=Z+goV2Zy+DTdiC7lcbh3myeeYIXI3Mwmns15PHOYPiu0+fAlqCzx8pXe 29902vQ/eUXk7+ThmioG21Oc0Inr53sr00Vc9o6Q5NTW4BOIG6EclmXmaAMZBVm8 WHY90NMN7e+dniPe2s6z33cbiN37KQ8cTLozRdfASXz8U7zjg/w= Received: by web6.nyi.internal (Postfix, from userid 99) id 2D7E757044; Thu, 25 Sep 2014 11:28:03 -0400 (EDT) Message-Id: <1411658883.3420802.171710921.16657E93@webmail.messagingengine.com> X-Sasl-Enc: RYb4YtFafv+II0OKVEhRcILCXI10iQapBaRDauXMSye1 1411658883 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: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> Subject: Re: 10.1 BETA2 World - Breaks saslauthd Date: Thu, 25 Sep 2014 10:28: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: Thu, 25 Sep 2014 15:28:04 -0000 On Thu, Sep 25, 2014, at 10:04, Dimitry Andric wrote: > On 25 Sep 2014, at 16:54, Tim Daneliuk wrote: > > I've seen this behavior over the last week or two when I try to upgrade > > to latest stable sources. Currently just installed kernel and world for: > > > > /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: 272095 > > Node Kind: directory > > Schedule: normal > > Last Changed Author: peter > > Last Changed Rev: 272078 > > Last Changed Date: 2014-09-24 14:30:36 -0500 (Wed, 24 Sep 2014) > > > > This breaks saslauthd - it demands a password when sending mail, but then > > rejects it in every case. > > > > If I just install a new kernel, everything is fine. But if I install > > world, that's when the problem shows up. I've tried a full reinstall of > > cygnus sasls and the daemon is running. > > > > Ideas on how to chase this down/fix, would be appreciated... > > It is probably caused by this MFC: > http://svnweb.freebsd.org/changeset/base/271766 > > To make saslauthd work again, you need to specify a correct PAM policy > file in /usr/local/etc/pam.d for your service, most likely "smtp" in > this case. E.g., create a file /usr/local/etc/pam.d/smtp, containing at > least: > > auth required pam_unix.so no_warn > try_first_pass > account required pam_unix.so > session required pam_permit.so > password required pam_permit.so > > Optionally, add a line: > > auth required pam_group.so luser > group=smtp-users fail_safe > > to allow only members of the smtp-users group to authenticate > successfully. > Hmm sounds like we need a bug report to request that an example pam.d/smtp be provided and an UPDATING entry perhaps. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 15:39: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4A0697EC for ; Thu, 25 Sep 2014 15:39:52 +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 0BA84E80 for ; Thu, 25 Sep 2014 15:39:51 +0000 (UTC) Message-ID: <4490c8c4d489370c7617c0ace9e773be.squirrel@s4bysmmsnraf7eut.onion> Date: Thu, 25 Sep 2014 17:31:49 +0200 Subject: vt(4) "newcons" and 80x25 vty? (tested: 10.1-BETA2) From: beeessdee@ruggedinbox.com To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 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: Thu, 25 Sep 2014 15:39:52 -0000 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? First of all, thanks to ray and the various "ed"s for all the hard work making the newcons/vt(4) modern subsystem. This is very important, and much less appreciated than shiny popular widgets! I very much look forward to when vt(4) has the stability and feature parity with decades-old syscons... plus all the critical new features for non-English language, etc. I just tested in 10.1-BETA2 with following steps; specific questions are below: 1. Drop to loader prompt, "set kern.vty=vt", "boot". 2. Drop from installer to "live system". 3. kldload appropriate kms driver (could also do in step 1). 4. vidfont(1) has bug which prevents selecting Gallant (12x22 biggest font provided). So, use vidcontrol(1) with "-f" switch directly. 5. Try setting LINES and COLS in environment, at least fool the applications... Not working, really. vidcontrol(1) is totally confused about screen modes. I understand this is work in progress. I read every manpage, https://wiki.freebsd.org/Newcons , searched web. Why this is important: If I edit source code in vi(1), my lines will become too long. Other applications expecting the 80x25 or other customary sizes may be confused. Most of all, I want the fonts bigger - as big as fit 80x25 on my physical screen. I have poor eyesight! Quick calc example for optimal font sizing: At the common nowadays resolution of 1366x768, biggest pixel fitting 80x25 will be 17x30. For tty style fonts with 2:1 ratio, this means 15x30 font with 166x18 waste pixels HxW - unless extra pixel row needed after each line, in which case 14x28 font with 246x43 waste pixels. A 12x22 font (as gallant) with extra 1px row spacing results in 113x33 character grid - or if restricted to 80x25 grid (how!?), then 406x193 waste pixels. Questions: A. How to force 80x25 terminal, even if it does not use whole screen? This will be the quick workaround! B. Where are sources for Gallant? What program is used to create it? A brief web search did not reveal this. C. Any work in font besides Gallant? (Sorry, it is matter of taste!) I would try make my own, but I am not font talent. D. Any suggestions from font guys of non-Xorg program to rasterize OpenType fonts, make Metafont rasters into the appropriate format, etc.? E. Side question: Is vgl(3) being supported or replaced with vt(4) newcons? (Have not tested; but at the brief look, it all ioctls changed around.) F. How to set screen resolution, with not working vidcontrol(1)? Suggestions: * Dynamically created raster font, from vector sources, to create at runtime the largest glyphs which will permit 80 columns and 25 lines at the screen's actual resolution. Just like most tex systems automatically run mf when needed. I could maybe play with this, if I have time and the font sources. * Try converting metafont output to the appropriate format. It's already tuned for to give old fashioned pixmap. I will play with this when time permits. I realize, most people just use X. But, please do not forget people who don't like the Xorg bugware disaster. Thanks again for all hard work to make the vt(4) newcons. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 15:50:51 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 11E9FDAB; Thu, 25 Sep 2014 15:50:51 +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 CA42CBA; Thu, 25 Sep 2014 15:50:50 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.9/8.14.9) with ESMTP id s8PFodu1013913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 25 Sep 2014 10:50:39 -0500 (CDT) (envelope-from tundra@tundraware.com) Message-ID: <542439CF.3050003@tundraware.com> Date: Thu, 25 Sep 2014 10:50:39 -0500 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Mark Felder , freebsd-stable@freebsd.org Subject: Re: 10.1 BETA2 World - Breaks saslauthd References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <1411658883.3420802.171710921.16657E93@webmail.messagingengine.com> In-Reply-To: <1411658883.3420802.171710921.16657E93@webmail.messagingengine.com> Content-Type: text/plain; charset=windows-1252; 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]); Thu, 25 Sep 2014 10:50:39 -0500 (CDT) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s8PFodu1013913 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: Thu, 25 Sep 2014 15:50:51 -0000 On 09/25/2014 10:28 AM, Mark Felder wrote: > > Hmm sounds like we need a bug report to request that an example > pam.d/smtp be provided and an UPDATING entry perhaps. -- Done> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193927 Thanks, everyone, for the help ... ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 16:14: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6E7AC473 for ; Thu, 25 Sep 2014 16:14:12 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2DD6E9B4 for ; Thu, 25 Sep 2014 16:14:11 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1XXBg5-0003k1-CB for freebsd-stable@freebsd.org; Thu, 25 Sep 2014 18:14:02 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Subject: Re: vt(4) "newcons" and 80x25 vty? (tested: 10.1-BETA2) References: <4490c8c4d489370c7617c0ace9e773be.squirrel@s4bysmmsnraf7eut.onion> Date: Thu, 25 Sep 2014 18:13:56 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <4490c8c4d489370c7617c0ace9e773be.squirrel@s4bysmmsnraf7eut.onion> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.3.2 X-Scan-Signature: 01ccc3eb840dc35651f50b798cb06ae8 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: Thu, 25 Sep 2014 16:14:12 -0000 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). Regards, Ronald. > > First of all, thanks to ray and the various "ed"s for all the hard work > making the newcons/vt(4) modern subsystem. This is very important, and > much less appreciated than shiny popular widgets! I very much look > forward to when vt(4) has the stability and feature parity with > decades-old syscons... plus all the critical new features for > non-English language, etc. > > I just tested in 10.1-BETA2 with following steps; specific questions are > below: > > 1. Drop to loader prompt, "set kern.vty=vt", "boot". > > 2. Drop from installer to "live system". > > 3. kldload appropriate kms driver (could also do in step 1). > > 4. vidfont(1) has bug which prevents selecting Gallant (12x22 > biggest font provided). So, use vidcontrol(1) with "-f" switch > directly. > > 5. Try setting LINES and COLS in environment, at least fool > the applications... Not working, really. > > vidcontrol(1) is totally confused about screen modes. I understand this > is work in progress. > > I read every manpage, https://wiki.freebsd.org/Newcons , searched web. > > Why this is important: If I edit source code in vi(1), my lines will > become too long. Other applications expecting the 80x25 or other > customary sizes may be confused. Most of all, I want the fonts bigger - > as big as fit 80x25 on my physical screen. I have poor eyesight! > > Quick calc example for optimal font sizing: At the common nowadays > resolution of 1366x768, biggest pixel fitting 80x25 will be 17x30. For > tty style fonts with 2:1 ratio, this means 15x30 font with 166x18 waste > pixels HxW - unless extra pixel row needed after each line, in which > case 14x28 font with 246x43 waste pixels. A 12x22 font (as gallant) > with extra 1px row spacing results in 113x33 character grid - or if > restricted to 80x25 grid (how!?), then 406x193 waste pixels. > > Questions: > > A. How to force 80x25 terminal, even if it does not use > whole screen? This will be the quick workaround! > > B. Where are sources for Gallant? What program is used to > create it? A brief web search did not reveal this. > > C. Any work in font besides Gallant? (Sorry, it is matter > of taste!) I would try make my own, but I am not font > talent. > > D. Any suggestions from font guys of non-Xorg program to > rasterize OpenType fonts, make Metafont rasters into > the appropriate format, etc.? > > E. Side question: Is vgl(3) being supported or replaced with > vt(4) newcons? (Have not tested; but at the brief look, it > all ioctls changed around.) > > F. How to set screen resolution, with not working vidcontrol(1)? > > Suggestions: > > * Dynamically created raster font, from vector sources, to create at > runtime the largest glyphs which will permit 80 columns and 25 lines > at the screen's actual resolution. Just like most tex systems > automatically run mf when needed. I could maybe play with this, if > I have time and the font sources. > > * Try converting metafont output to the appropriate format. It's > already tuned for to give old fashioned pixmap. I will play with this > when time permits. > > I realize, most people just use X. But, please do not forget people who > don't like the Xorg bugware disaster. > > Thanks again for all hard work to make the vt(4) newcons. > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 20:08:47 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AEA0AD10; Thu, 25 Sep 2014 20:08:47 +0000 (UTC) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (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 768E1928; Thu, 25 Sep 2014 20:08:47 +0000 (UTC) Received: by mail-ig0-f177.google.com with SMTP id h3so9073829igd.16 for ; Thu, 25 Sep 2014 13:08:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=QkKzfBTT4MifEVz8i047+yxhqtMZSixfQJXq4EdeEz8=; b=asBj/V2hNMnQSg26w7B1F6lanMee5rRrIrGEsrwUHCiTStCD2XvCjum9L2NAy5GRRo 1ODg8vb3JvJnS8daimWkuOUu/+87XURBW1Q/QnjvkmbBzp4eizpl0SzrYVteYOXYCzEP mi0H9yfgubg6GZ2UPgb6fO7aDfVHH80Kqnyr1WjatGsZevn3AL4++xLk+BifBDLNCVZp H4GnzEq9l152kCPK5p2vb6hO6Lej132Vn/yWREUNkSVgLwtZShzX0nKGmKh3zVUlBXdQ boI+yIIiR6FLLDKkIib3FLCJEgZEkPMmaThzx3ZE06gBB+UgGYxSuBspVf8L9oBT0G5z w2pQ== X-Received: by 10.43.68.206 with SMTP id xz14mr21745171icb.33.1411675726870; Thu, 25 Sep 2014 13:08:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.59.230 with HTTP; Thu, 25 Sep 2014 13:08:25 -0700 (PDT) From: Gabor Radnai Date: Thu, 25 Sep 2014 22:08:25 +0200 Message-ID: Subject: UEFI vs ZFS boot To: freebsd-stable@freebsd.org, freebsd-questions@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: Thu, 25 Sep 2014 20:08:47 -0000 Hi, As per MFC r271563 : Make the root-on-zfs part of the installer warn a user who booted the installer via UEFI that we do not support booting ZFS via UEFI yet Just wondering why missing zfs support as zfs-boot technique/code is available. It is no offense just if someone could give hint if e.g. UEFI works with GPT and gptzfsboot works with GPT why efi loader cannot utilize code from gtpzfsboot to use zfs boot fs directly. Also if not now approximately when it will support zfs? Or there are so many obstacles on road rather makes mid term workaround to use efi + zfs-root-ufs-boot combo? Thanks. From owner-freebsd-stable@FreeBSD.ORG Thu Sep 25 22:53: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8647AEB1 for ; Thu, 25 Sep 2014 22:53:02 +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 22891D24 for ; Thu, 25 Sep 2014 22:53:01 +0000 (UTC) Message-ID: <3d80542ccc73686094ddde4e18465e4a.squirrel@s4bysmmsnraf7eut.onion> In-Reply-To: References: <4490c8c4d489370c7617c0ace9e773be.squirrel@s4bysmmsnraf7eut.onion> Date: Fri, 26 Sep 2014 00:51:11 +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: Thu, 25 Sep 2014 22:53:02 -0000 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. For longer term, when there is time, I like to hack on font system for other goals in my previous mail: Smooth fonts sized right at native/max resolution provided with new(ish) kms driver stack. What a waste to stick to vgamode. Any pointers toward where I should start? Documentation is scarcer than the usual FreeBSD (not a criticism - it is new subsystem!). If "documentation is the source" then I can do that - but it takes yet more time, much more starting from no knowledge of vt(4) subsystem font handling. Better start with manpage or equivalent overview, then read sources... Thanks again. [EOF] > Regards, > Ronald. > > >> >> First of all, thanks to ray and the various "ed"s for all the hard work >> making the newcons/vt(4) modern subsystem. This is very important, and >> much less appreciated than shiny popular widgets! I very much look >> forward to when vt(4) has the stability and feature parity with >> decades-old syscons... plus all the critical new features for >> non-English language, etc. >> >> I just tested in 10.1-BETA2 with following steps; specific questions are >> below: >> >> 1. Drop to loader prompt, "set kern.vty=vt", "boot". >> >> 2. Drop from installer to "live system". >> >> 3. kldload appropriate kms driver (could also do in step 1). >> >> 4. vidfont(1) has bug which prevents selecting Gallant (12x22 >> biggest font provided). So, use vidcontrol(1) with "-f" switch >> directly. >> >> 5. Try setting LINES and COLS in environment, at least fool >> the applications... Not working, really. >> >> vidcontrol(1) is totally confused about screen modes. I understand this >> is work in progress. >> >> I read every manpage, https://wiki.freebsd.org/Newcons , searched web. >> >> Why this is important: If I edit source code in vi(1), my lines will >> become too long. Other applications expecting the 80x25 or other >> customary sizes may be confused. Most of all, I want the fonts bigger - >> as big as fit 80x25 on my physical screen. I have poor eyesight! >> >> Quick calc example for optimal font sizing: At the common nowadays >> resolution of 1366x768, biggest pixel fitting 80x25 will be 17x30. For >> tty style fonts with 2:1 ratio, this means 15x30 font with 166x18 waste >> pixels HxW - unless extra pixel row needed after each line, in which >> case 14x28 font with 246x43 waste pixels. A 12x22 font (as gallant) >> with extra 1px row spacing results in 113x33 character grid - or if >> restricted to 80x25 grid (how!?), then 406x193 waste pixels. >> >> Questions: >> >> A. How to force 80x25 terminal, even if it does not use >> whole screen? This will be the quick workaround! >> >> B. Where are sources for Gallant? What program is used to >> create it? A brief web search did not reveal this. >> >> C. Any work in font besides Gallant? (Sorry, it is matter >> of taste!) I would try make my own, but I am not font >> talent. >> >> D. Any suggestions from font guys of non-Xorg program to >> rasterize OpenType fonts, make Metafont rasters into >> the appropriate format, etc.? >> >> E. Side question: Is vgl(3) being supported or replaced with >> vt(4) newcons? (Have not tested; but at the brief look, it >> all ioctls changed around.) >> >> F. How to set screen resolution, with not working vidcontrol(1)? >> >> Suggestions: >> >> * Dynamically created raster font, from vector sources, to create at >> runtime the largest glyphs which will permit 80 columns and 25 lines >> at the screen's actual resolution. Just like most tex systems >> automatically run mf when needed. I could maybe play with this, if >> I have time and the font sources. >> >> * Try converting metafont output to the appropriate format. It's >> already tuned for to give old fashioned pixmap. I will play with this >> when time permits. >> >> I realize, most people just use X. But, please do not forget people who >> don't like the Xorg bugware disaster. >> >> Thanks again for all hard work to make the vt(4) newcons. >> >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Fri Sep 26 07:08:41 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 748C0673; Fri, 26 Sep 2014 07:08:41 +0000 (UTC) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 34B72827; Fri, 26 Sep 2014 07:08:41 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id EAB4AA737; Fri, 26 Sep 2014 07:08:33 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id 00457386B; Fri, 26 Sep 2014 09:08:34 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Brandon Allbery Subject: Re: 10.1 BETA2 World - Breaks saslauthd References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <542430EB.1040804@tundraware.com> Date: Fri, 26 Sep 2014 09:08:34 +0200 In-Reply-To: (Brandon Allbery's message of "Thu, 25 Sep 2014 11:18:52 -0400") Message-ID: <86ppeieu4t.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Gustau Perez , FreeBSD stable , Tim Daneliuk , Dimitry Andric 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: Fri, 26 Sep 2014 07:08:41 -0000 Brandon Allbery writes: > To me the implication is that before the MFC, PAM had a potentially > quite severe security issue involving either incorrect fallback to a > default configuration or not correctly handling error returns from a > PAM stack --- either of which could result in unauthorized users being > permitted access. No, that's a different issue. This patch fixes a potential segfault (see http://bugs.freebsd.org/83099). However, I have recevied reports that gdm (amongst others) actually want to be able to call pam_login_access without a host or tty. The following patch makes that possible: Index: lib/libpam/modules/pam_login_access/pam_login_access.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- lib/libpam/modules/pam_login_access/pam_login_access.c (revision 272101) +++ lib/libpam/modules/pam_login_access/pam_login_access.c (working copy) @@ -94,8 +94,10 @@ PAM_VERBOSE_ERROR("%s is not allowed to log in on %s", user, tty); } else { - PAM_VERBOSE_ERROR("PAM_RHOST or PAM_TTY required"); - return (PAM_AUTHINFO_UNAVAIL); + PAM_LOG("Checking login.access for user %s", user); + if (login_access(user, "***unknown***") !=3D 0) + return (PAM_SUCCESS); + PAM_VERBOSE_ERROR("%s is not allowed to log in", user); } =20 return (PAM_AUTH_ERR); Please test and report as soon as possible so I can get it into 10. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Fri Sep 26 10:26:34 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 66A608D5 for ; Fri, 26 Sep 2014 10:26:34 +0000 (UTC) Received: from tensor.andric.com (unknown [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B43819E for ; Fri, 26 Sep 2014 10:26:34 +0000 (UTC) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id AF848B80A; Fri, 26 Sep 2014 12:26:28 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_0F1984F4-B35A-4FF7-8A7D-40FD8F8EDBCD"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: 10.1 BETA2 World - Breaks saslauthd From: Dimitry Andric In-Reply-To: <86ppeieu4t.fsf@nine.des.no> Date: Fri, 26 Sep 2014 12:26:17 +0200 Message-Id: <1924A408-DD94-440E-87F5-DFDD74F07BB0@FreeBSD.org> References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <542430EB.1040804@tundraware.com> <86ppeieu4t.fsf@nine.des.no> To: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= X-Mailer: Apple Mail (2.1878.6) Cc: Gustau Perez , Tim Daneliuk , FreeBSD stable , Brandon Allbery 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: Fri, 26 Sep 2014 10:26:34 -0000 --Apple-Mail=_0F1984F4-B35A-4FF7-8A7D-40FD8F8EDBCD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 26 Sep 2014, at 09:08, Dag-Erling Sm=F8rgrav wrote: > Brandon Allbery writes: >> To me the implication is that before the MFC, PAM had a potentially >> quite severe security issue involving either incorrect fallback to a >> default configuration or not correctly handling error returns from a >> PAM stack --- either of which could result in unauthorized users = being >> permitted access. >=20 > No, that's a different issue. This patch fixes a potential segfault > (see http://bugs.freebsd.org/83099). However, I have recevied reports > that gdm (amongst others) actually want to be able to call > pam_login_access without a host or tty. The following patch makes = that > possible: >=20 > Index: lib/libpam/modules/pam_login_access/pam_login_access.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- lib/libpam/modules/pam_login_access/pam_login_access.c = (revision 272101) > +++ lib/libpam/modules/pam_login_access/pam_login_access.c (working = copy) > @@ -94,8 +94,10 @@ > PAM_VERBOSE_ERROR("%s is not allowed to log in on %s", > user, tty); > } else { > - PAM_VERBOSE_ERROR("PAM_RHOST or PAM_TTY required"); > - return (PAM_AUTHINFO_UNAVAIL); > + PAM_LOG("Checking login.access for user %s", user); > + if (login_access(user, "***unknown***") !=3D 0) > + return (PAM_SUCCESS); > + PAM_VERBOSE_ERROR("%s is not allowed to log in", user); > } >=20 > return (PAM_AUTH_ERR); >=20 > Please test and report as soon as possible so I can get it into 10. It works for me. I even tried removing the /usr/local/etc/pam.d/smtpd file, restarting postfix and saslauthd, and it still worked: saslauthd[66602] :do_auth : auth success: [user=3Ddim] = [service=3Dsmtp] [realm=3D] [mech=3Dpam] saslauthd[66602] :do_request : response: OK saslauthd[66603] :get_accept_lock : acquired accept lock -Dimitry --Apple-Mail=_0F1984F4-B35A-4FF7-8A7D-40FD8F8EDBCD 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----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlQlP1IACgkQsF6jCi4glqNQbgCgzrtUrDCgO0mJVeUUkjqhrnqL LSsAoOYVyFA8/GF79ChEtQ7if05/KWbA =G89P -----END PGP SIGNATURE----- --Apple-Mail=_0F1984F4-B35A-4FF7-8A7D-40FD8F8EDBCD-- From owner-freebsd-stable@FreeBSD.ORG Fri Sep 26 11:34:22 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4586BD9C for ; Fri, 26 Sep 2014 11:34:22 +0000 (UTC) Received: from lamora.getmail.no (lamora.getmail.no [84.210.184.7]) by mx1.freebsd.org (Postfix) with ESMTP id C4642BFF for ; Fri, 26 Sep 2014 11:34:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by lamora.getmail.no (Postfix) with ESMTP id 39F787CB0F for ; Fri, 26 Sep 2014 13:24:20 +0200 (CEST) Received: from lamora.getmail.no ([127.0.0.1]) by localhost (lamora.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id K_O_eUaw1ARY for ; Fri, 26 Sep 2014 13:24:19 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by lamora.getmail.no (Postfix) with ESMTP id A63F17C9A9 for ; Fri, 26 Sep 2014 13:24:19 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.8.4 lamora.getmail.no A63F17C9A9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getmail.no; s=8A9C8B4C-D727-11E2-8095-B6466E6B3FA2; t=1411730659; bh=uO3jiUfwhCpv7WLPcC/UBpJ/1Ar9Hz/GkkQsLxKdTm4=; h=Date:From:To:Subject:Message-Id:Mime-Version:Content-Type: Content-Transfer-Encoding; b=kZK/mrPtbVTozEGeI5x6d6rDVTwhjdKNCYQNJ9evgsn7LRzFPCHeJ0RGrlwLorV2K qQYoi4UY6EZ0eM/emxVjYZ9BVhI68npoqbtsLPFlczIx/VZXVT7jSFN3zkpibjPJjg rHISCkXRQxLF9kYMPh5dMOfWuJA2RjNMIFTw1MQc= X-Virus-Scanned: amavisd-new at lamora.get.c.bitbit.net Received: from lamora.getmail.no ([127.0.0.1]) by localhost (lamora.get.c.bitbit.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id twM12OOUHq0z for ; Fri, 26 Sep 2014 13:24:19 +0200 (CEST) Received: from kg-core1.kg4.no (cm-84.215.180.206.getinternet.no [84.215.180.206]) by lamora.getmail.no (Postfix) with ESMTPSA id 7DB3E7CB0F for ; Fri, 26 Sep 2014 13:24:19 +0200 (CEST) Date: Fri, 26 Sep 2014 13:24:19 +0200 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Subject: FreeBSD 8.4-stable: sendmail bug? Message-Id: <20140926132419.4493c61662cdf7ba8893abbc@getmail.no> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd8.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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: Fri, 26 Sep 2014 11:34:22 -0000 Hello, One of my machines recently got updaged to FreeBSD 8.4-stable (using first freebsd-update, then svn + make world. The normal update procedure was run, including mergemaster. It currently runs: root@kg-vm2# uname -a FreeBSD kg-vm2.kg4.no 8.4-STABLE FreeBSD 8.4-STABLE #0 r270837: Sat Aug 30 13:25:23 CEST 2014 root@kg-vm2:/usr/obj/usr/src/sys/GENERIC amd64 After the upgrade, sendmail doesn't want to send mail, resulting in this: root@kg-vm2# mailq /var/spool/mqueue (4 requests) -----Q-ID----- --Size-- -----Q-Time----- ------------Sender/Recipient----------- s8Q56o6W075503 1978 Fri Sep 26 07:06 MAILER-DAEMON (Deferred: Connection refused by kg-vm2.kg4.no.) s8Q56o6X075503 3645 Fri Sep 26 07:06 MAILER-DAEMON (Deferred: Connection refused by kg-vm2.kg4.no.) s8Q113MU075044 290 Fri Sep 26 03:01 (Deferred: Connection refused by kg-vm2.kg4.no.) s8Q1146V075078 1960 Fri Sep 26 03:01 (Deferred: Connection refused by kg-vm2.kg4.no.) Total requests: 4 the funny thing is this: root@kg-vm2# sendmail -q -v Running /var/spool/mqueue/s8Q56o6W075503 (sequence 1 of 4) ... Connecting to local... 220 kg-vm2.kg4.no LMTP ready >>> LHLO kg-vm2.kg4.no 250-kg-vm2.kg4.no 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING >>> MAIL From:<> 250 2.5.0 Ok >>> RCPT To: >>> DATA 250 2.1.5 Ok 354 Go ahead >>> . 250 2.1.5 root Ok ... Sent Running /var/spool/mqueue/s8Q56o6X075503 (sequence 2 of 4) >>> RSET 250 2.0.0 Ok ... Using cached LMTP connection for local... >>> MAIL From:<> 250 2.5.0 Ok >>> RCPT To: >>> DATA 250 2.1.5 Ok 354 Go ahead >>> . 250 2.1.5 root Ok ... Sent Running /var/spool/mqueue/s8Q113MU075044 (sequence 3 of 4) >>> RSET 250 2.0.0 Ok ... Using cached LMTP connection for local... >>> MAIL From: 250 2.5.0 Ok >>> RCPT To: >>> DATA 250 2.1.5 Ok 354 Go ahead >>> . 250 2.1.5 root Ok ... Sent Running /var/spool/mqueue/s8Q1146V075078 (sequence 4 of 4) >>> RSET 250 2.0.0 Ok ... Using cached LMTP connection for local... >>> MAIL From: 250 2.5.0 Ok >>> RCPT To: >>> DATA 250 2.1.5 Ok 354 Go ahead >>> . 250 2.1.5 root Ok ... Sent Closing connection to local >>> QUIT 221 2.0.0 Bye you have mail As far as I can tell, the necessary config files (including those in /etc/mail) are present and correct. It looks to me like the correct sendmail processes are running too: root@kg-vm2# pgrep -lf sendmail 517 sendmail: Queue runner@00:30:00 for /var/spool/clientmqueue 514 sendmail: accepting connections What am I missing? -- Torfinn Ingolfsen From owner-freebsd-stable@FreeBSD.ORG Fri Sep 26 16:01: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08E08D84; Fri, 26 Sep 2014 16:01:08 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 15B8BEEB; Fri, 26 Sep 2014 16:01:05 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA10870; Fri, 26 Sep 2014 18:57:17 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XXXtV-000Nv5-9v; Fri, 26 Sep 2014 18:57:17 +0300 Message-ID: <54258C8B.90709@FreeBSD.org> Date: Fri, 26 Sep 2014 18:55:55 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= Subject: Re: 10.1 BETA2 World - Breaks saslauthd References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <542430EB.1040804@tundraware.com> <86ppeieu4t.fsf@nine.des.no> In-Reply-To: <86ppeieu4t.fsf@nine.des.no> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Dimitry Andric , 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: Fri, 26 Sep 2014 16:01:08 -0000 On 26/09/2014 10:08, Dag-Erling Smørgrav wrote: > Brandon Allbery writes: >> To me the implication is that before the MFC, PAM had a potentially >> quite severe security issue involving either incorrect fallback to a >> default configuration or not correctly handling error returns from a >> PAM stack --- either of which could result in unauthorized users being >> permitted access. > > No, that's a different issue. This patch fixes a potential segfault > (see http://bugs.freebsd.org/83099). However, I have recevied reports > that gdm (amongst others) actually want to be able to call > pam_login_access without a host or tty. The following patch makes that > possible: > > Index: lib/libpam/modules/pam_login_access/pam_login_access.c > =================================================================== > --- lib/libpam/modules/pam_login_access/pam_login_access.c (revision 272101) > +++ lib/libpam/modules/pam_login_access/pam_login_access.c (working copy) > @@ -94,8 +94,10 @@ > PAM_VERBOSE_ERROR("%s is not allowed to log in on %s", > user, tty); > } else { > - PAM_VERBOSE_ERROR("PAM_RHOST or PAM_TTY required"); > - return (PAM_AUTHINFO_UNAVAIL); > + PAM_LOG("Checking login.access for user %s", user); > + if (login_access(user, "***unknown***") != 0) > + return (PAM_SUCCESS); > + PAM_VERBOSE_ERROR("%s is not allowed to log in", user); > } > > return (PAM_AUTH_ERR); > > Please test and report as soon as possible so I can get it into 10. BTW, I think that chatted about this topic (no host, no tty) a long time ago and back then you suggested that PAM_IGNORE could be returned for that combination. I do not know much about PAM, so I can't evaluate neither the current code nor that hypothetical alternative. So, this is just a reminder about some old ideas. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Fri Sep 26 19:43:55 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5587F5D; Fri, 26 Sep 2014 19:43:55 +0000 (UTC) Received: from m2.gritton.org (gritton.org [63.246.134.121]) (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 A1FC6BD8; Fri, 26 Sep 2014 19:43:55 +0000 (UTC) Received: from [192.168.0.34] (c-50-168-192-61.hsd1.ut.comcast.net [50.168.192.61]) (authenticated bits=0) by m2.gritton.org (8.14.9/8.14.9) with ESMTP id s8QJScr7095728; Fri, 26 Sep 2014 19:28:39 GMT (envelope-from jamie@gritton.org) Message-ID: <5425BE60.5020900@gritton.org> Date: Fri, 26 Sep 2014 13:28:32 -0600 From: James Gritton User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-jail@freebsd.org, "freebsd-stable@FreeBSD.org Stable" Subject: Re: fdescfs patch for working hierarchical jails References: <0B3648E9-21DC-4691-A6A9-26DE2C40947B@verweg.com> In-Reply-To: <0B3648E9-21DC-4691-A6A9-26DE2C40947B@verweg.com> Content-Type: text/plain; charset=ISO-8859-1; 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: Fri, 26 Sep 2014 19:43:55 -0000 On 9/25/2014 3:40 AM, Ruben van Staveren wrote: > Hi, > > Could a committer have a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192951 ? > > This enables fdescfs in hierarchical jails, would be nice to have this for 10.1 > > Thanks! > > Best Regards, > Ruben van Staveren This would have to go into current first, and then MFC. Considering 10.1 is getting close to release, I suspect it wouldn't be allowed in. Also, I'm not sure I'd want to implement this in quite the proposed way: it might suffice (from a security viewpoint) to use the existing allow.mount.devfs for mounting fdescfs. - Jamie From owner-freebsd-stable@FreeBSD.ORG Fri Sep 26 22:27:59 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3114AF3F; Fri, 26 Sep 2014 22:27:59 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 2001510A; Fri, 26 Sep 2014 22:27:59 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 604E8804; Fri, 26 Sep 2014 22:27:58 +0000 (UTC) Date: Fri, 26 Sep 2014 22:27:50 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org, mjg@FreeBSD.org Message-ID: <1146345957.0.1411770477782.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Build failed in Jenkins: FreeBSD_stable_10 #793 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: FAILURE 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: Fri, 26 Sep 2014 22:27:59 -0000 See Changes: [mjg] MFC r270993: Fix up proc_realparent to always return correct process. Prior to the change it would always return initproc for non-traced processes. This fixes a regression in inferior(). Approved by: re (marius) ------------------------------------------ [...truncated 224407 lines...] ===> acpi/acpi_ibm (cleandir) --- cleandir_subdir_aic7xxx --- --- cleanobj --- --- cleandir_subdir_alc --- --- cleandir_subdir_acpi --- --- cleanobj --- --- cleandir_subdir_alc --- ===> alc (cleandir) --- cleandir_subdir_acpi --- ===> acpi/acpi_panasonic (cleandir) --- cleanobj --- --- cleandir_subdir_alc --- --- cleanobj --- --- cleandir_subdir_acpi --- ===> acpi/acpi_sony (cleandir) --- cleandir_subdir_aic7xxx --- --- _sub.cleandir --- ===> aic7xxx/ahc/ahc_eisa (cleandir) --- cleandir_subdir_ale --- ===> ale (cleandir) --- cleandir_subdir_acpi --- --- cleanobj --- --- cleandir_subdir_aic7xxx --- --- clean --- rm -f export_syms ahc_eisa.ko ahc_eisa.kld ahc_eisa.o ahc_eisa.ko.debug ahc_eisa.ko.symbols opt_scsi.h opt_cam.h opt_aic7xxx.h eisa_if.h pci_if.h bus_if.h device_if.h --- cleandir_subdir_acpi --- ===> acpi/acpi_toshiba (cleandir) --- cleandir_subdir_ale --- --- cleanobj --- --- cleandir_subdir_aic7xxx --- --- cleanilinks --- rm -f @ machine x86 --- cleandepend --- rm -f .depend GPATH GRTAGS GSYMS GTAGS --- cleanobj --- --- cleandir_subdir_acpi --- --- cleanobj --- --- cleandir_subdir_alq --- --- cleandir_subdir_aic7xxx --- ===> aic7xxx/ahc/ahc_isa (cleandir) --- cleandir_subdir_alq --- ===> alq (cleandir) --- cleandir_subdir_aic7xxx --- --- clean --- rm -f export_syms ahc_isa.ko ahc_isa.kld ahc_isa.o ahc_isa.ko.debug ahc_isa.ko.symbols opt_scsi.h opt_cam.h opt_aic7xxx.h pci_if.h isa_if.h bus_if.h device_if.h --- cleandir_subdir_acpi --- ===> acpi/acpi_video (cleandir) --- cleandir_subdir_aic7xxx --- --- cleanilinks --- rm -f @ machine x86 --- cleandepend --- --- cleandir_subdir_alq --- --- cleanobj --- --- cleandir_subdir_aic7xxx --- rm -f .depend GPATH GRTAGS GSYMS GTAGS --- cleandir_subdir_acpi --- --- cleanobj --- --- cleandir_subdir_aic7xxx --- --- cleanobj --- ===> aic7xxx/ahc/ahc_pci (cleandir) --- cleandir_subdir_acpi --- ===> acpi/acpi_dock (cleandir) --- cleandir_subdir_amdsbwd --- --- cleandir_subdir_aic7xxx --- --- clean --- rm -f export_syms ahc_pci.ko ahc_pci.kld ahc_pci.o aic7xxx_pci.o ahc_pci.ko.debug ahc_pci.ko.symbols opt_scsi.h opt_cam.h opt_aic7xxx.h pci_if.h bus_if.h device_if.h --- cleandir_subdir_amdsbwd --- ===> amdsbwd (cleandir) --- cleandir_subdir_aic7xxx --- --- cleanilinks --- rm -f @ machine x86 --- cleandepend --- rm -f .depend GPATH GRTAGS GSYMS GTAGS --- cleanobj --- ===> aic7xxx/ahd (cleandir) --- cleandir_subdir_acpi --- --- cleanobj --- ===> acpi/acpi_wmi (cleandir) --- cleandir_subdir_amdsbwd --- --- cleanobj --- --- cleandir_subdir_aic7xxx --- --- cleanobj --- --- cleandir_subdir_amdtemp --- ===> amdtemp (cleandir) --- cleandir_subdir_amr --- --- cleandir_subdir_acpi --- --- cleanobj --- --- cleandir_subdir_amr --- ===> amr (cleandir) --- cleandir_subdir_acpi --- ===> acpi/aibs (cleandir) --- cleandir_subdir_amdtemp --- --- cleanobj --- --- cleandir_subdir_an --- ===> an (cleandir) --- cleandir_subdir_acpi --- --- cleanobj --- --- cleandir_subdir_amr --- --- cleanobj --- --- cleandir_subdir_an --- --- cleanobj --- --- cleandir_subdir_amr --- --- _sub.cleandir --- --- cleandir_subdir_aout --- ===> aout (cleandir) --- cleandir_subdir_amr --- ===> amr/amr_cam (cleandir) --- cleandir_subdir_arcmsr --- ===> arcmsr (cleandir) --- cleandir_subdir_amr --- --- clean --- rm -f export_syms amr_cam.ko amr_cam.kld amr_cam.o amr_cam.ko.debug amr_cam.ko.symbols opt_cam.h opt_scsi.h bus_if.h device_if.h --- cleandir_subdir_aout --- --- cleanobj --- --- cleandir_subdir_amr --- --- cleanilinks --- rm -f @ machine x86 --- cleandepend --- --- cleandir_subdir_arcmsr --- --- cleanobj --- --- cleandir_subdir_amr --- rm -f .depend GPATH GRTAGS GSYMS GTAGS --- cleandir_subdir_asmc --- --- cleandir_subdir_amr --- --- cleanobj --- --- cleandir_subdir_asmc --- ===> asmc (cleandir) --- cleandir_subdir_amr --- ===> amr/amr_linux (cleandir) --- cleandir_subdir_ata --- ===> ata (cleandir) --- cleandir_subdir_amr --- --- clean --- rm -f export_syms amr_linux.ko amr_linux.kld amr_linux.o amr_linux.ko.debug amr_linux.ko.symbols bus_if.h device_if.h --- cleanilinks --- --- cleandir_subdir_asmc --- --- cleanobj --- --- cleandir_subdir_amr --- rm -f @ machine x86 --- cleandepend --- rm -f .depend GPATH GRTAGS GSYMS GTAGS --- cleandir_subdir_ath --- --- cleandir_subdir_ata --- --- _sub.cleandir --- ===> ata/atacore (cleandir) --- cleandir_subdir_ath --- ===> ath (cleandir) --- cleandir_subdir_amr --- --- cleanobj --- --- cleandir_subdir_ath_pci --- ===> ath_pci (cleandir) --- cleandir_subdir_ata --- --- cleanobj --- --- cleandir_subdir_ath_pci --- --- cleanobj --- --- cleandir_subdir_ata --- ===> ata/atacard (cleandir) --- cleandir_subdir_autofs --- ===> autofs (cleandir) --- cleandir_subdir_ath --- --- cleanobj --- --- cleandir_subdir_ata --- --- cleanobj --- --- cleandir_subdir_autofs --- --- cleanobj --- --- cleandir_subdir_ata --- ===> ata/ataisa (cleandir) --- cleandir_subdir_bce --- ===> bce (cleandir) --- cleandir_subdir_ata --- --- cleanobj --- ===> ata/atapci (cleandir) --- cleandir_subdir_bce --- --- cleanobj --- --- cleandir_subdir_bfe --- ===> bfe (cleandir) --- cleandir_subdir_ata --- --- cleanobj --- --- cleandir_subdir_bfe --- --- cleanobj --- --- cleandir_subdir_ata --- --- _sub.cleandir --- ===> ata/atapci/chipsets (cleandir) --- _sub.cleandir --- ===> ata/atapci/chipsets/ataacard (cleandir) --- cleanobj --- ===> ata/atapci/chipsets/ataacerlabs (cleandir) --- cleanobj --- ===> ata/atapci/chipsets/ataadaptec (cleandir) --- cleanobj --- rm: fts_read: No such file or directory *** [cleanobj] Error code 1 make[5]: stopped in --- cleandir_subdir_ath --- A failure has been detected in another branch of the parallel make make[4]: stopped in *** [cleandir_subdir_ath] Error code 2 make[3]: stopped in --- cleandir_subdir_ata --- --- _sub.cleandir --- A failure has been detected in another branch of the parallel make make[7]: stopped in *** [_sub.cleandir] Error code 2 make[6]: stopped in 1 error make[6]: stopped in *** [_sub.cleandir] Error code 2 make[5]: stopped in 2 errors make[5]: stopped in *** [_sub.cleandir] Error code 2 make[4]: stopped in 1 error make[4]: stopped in *** [cleandir_subdir_ata] Error code 2 make[3]: stopped in 2 errors make[3]: stopped in *** [modules-cleandir] Error code 2 make[2]: stopped in /usr/obj 1 error make[2]: stopped in /usr/obj *** [buildkernel] Error code 2 make[1]: stopped in 1 error make[1]: stopped in *** [buildkernel] Error code 2 make: stopped in 1 error make: stopped in Build step 'Execute shell' marked build as failure From owner-freebsd-stable@FreeBSD.ORG Fri Sep 26 22:51:32 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 55B40415; Fri, 26 Sep 2014 22:51:32 +0000 (UTC) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id D45E5342; Fri, 26 Sep 2014 22:51:31 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id 0120B20E70890; Fri, 26 Sep 2014 22:51:23 +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=1.5 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 ESMTP id 09DBF20E7088B; Fri, 26 Sep 2014 22:51:20 +0000 (UTC) Message-ID: <20D23455255E407FB8965AEEDA7BF9E2@multiplay.co.uk> From: "Steven Hartland" To: , , References: <1146345957.0.1411770477782.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Re: Build failed in Jenkins: FreeBSD_stable_10 #793 Date: Fri, 26 Sep 2014 23:51:14 +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: Fri, 26 Sep 2014 22:51:32 -0000 Hmm build machines install too old? I thought this error was already fixed? ----- Original Message ----- From: To: ; ; Sent: Friday, September 26, 2014 11:27 PM Subject: Build failed in Jenkins: FreeBSD_stable_10 #793 > See > > Changes: > > [mjg] MFC r270993: > > Fix up proc_realparent to always return correct process. > > Prior to the change it would always return initproc for non-traced processes. > > This fixes a regression in inferior(). > > Approved by: re (marius) > > ------------------------------------------ > [...truncated 224407 lines...] > ===> acpi/acpi_ibm (cleandir) > --- cleandir_subdir_aic7xxx --- > --- cleanobj --- > --- cleandir_subdir_alc --- > --- cleandir_subdir_acpi --- > --- cleanobj --- > --- cleandir_subdir_alc --- > ===> alc (cleandir) > --- cleandir_subdir_acpi --- > ===> acpi/acpi_panasonic (cleandir) > --- cleanobj --- > --- cleandir_subdir_alc --- > --- cleanobj --- > --- cleandir_subdir_acpi --- > ===> acpi/acpi_sony (cleandir) > --- cleandir_subdir_aic7xxx --- > --- _sub.cleandir --- > ===> aic7xxx/ahc/ahc_eisa (cleandir) > --- cleandir_subdir_ale --- > ===> ale (cleandir) > --- cleandir_subdir_acpi --- > --- cleanobj --- > --- cleandir_subdir_aic7xxx --- > --- clean --- > rm -f export_syms ahc_eisa.ko ahc_eisa.kld ahc_eisa.o ahc_eisa.ko.debug ahc_eisa.ko.symbols opt_scsi.h opt_cam.h opt_aic7xxx.h > eisa_if.h pci_if.h bus_if.h device_if.h > --- cleandir_subdir_acpi --- > ===> acpi/acpi_toshiba (cleandir) > --- cleandir_subdir_ale --- > --- cleanobj --- > --- cleandir_subdir_aic7xxx --- > --- cleanilinks --- > rm -f @ machine x86 > --- cleandepend --- > rm -f .depend GPATH GRTAGS GSYMS GTAGS > --- cleanobj --- > --- cleandir_subdir_acpi --- > --- cleanobj --- > --- cleandir_subdir_alq --- > --- cleandir_subdir_aic7xxx --- > ===> aic7xxx/ahc/ahc_isa (cleandir) > --- cleandir_subdir_alq --- > ===> alq (cleandir) > --- cleandir_subdir_aic7xxx --- > --- clean --- > rm -f export_syms ahc_isa.ko ahc_isa.kld ahc_isa.o ahc_isa.ko.debug ahc_isa.ko.symbols opt_scsi.h opt_cam.h opt_aic7xxx.h pci_if.h > isa_if.h bus_if.h device_if.h > --- cleandir_subdir_acpi --- > ===> acpi/acpi_video (cleandir) > --- cleandir_subdir_aic7xxx --- > --- cleanilinks --- > rm -f @ machine x86 > --- cleandepend --- > --- cleandir_subdir_alq --- > --- cleanobj --- > --- cleandir_subdir_aic7xxx --- > rm -f .depend GPATH GRTAGS GSYMS GTAGS > --- cleandir_subdir_acpi --- > --- cleanobj --- > --- cleandir_subdir_aic7xxx --- > --- cleanobj --- > ===> aic7xxx/ahc/ahc_pci (cleandir) > --- cleandir_subdir_acpi --- > ===> acpi/acpi_dock (cleandir) > --- cleandir_subdir_amdsbwd --- > --- cleandir_subdir_aic7xxx --- > --- clean --- > rm -f export_syms ahc_pci.ko ahc_pci.kld ahc_pci.o aic7xxx_pci.o ahc_pci.ko.debug ahc_pci.ko.symbols opt_scsi.h opt_cam.h > opt_aic7xxx.h pci_if.h bus_if.h device_if.h > --- cleandir_subdir_amdsbwd --- > ===> amdsbwd (cleandir) > --- cleandir_subdir_aic7xxx --- > --- cleanilinks --- > rm -f @ machine x86 > --- cleandepend --- > rm -f .depend GPATH GRTAGS GSYMS GTAGS > --- cleanobj --- > ===> aic7xxx/ahd (cleandir) > --- cleandir_subdir_acpi --- > --- cleanobj --- > ===> acpi/acpi_wmi (cleandir) > --- cleandir_subdir_amdsbwd --- > --- cleanobj --- > --- cleandir_subdir_aic7xxx --- > --- cleanobj --- > --- cleandir_subdir_amdtemp --- > ===> amdtemp (cleandir) > --- cleandir_subdir_amr --- > --- cleandir_subdir_acpi --- > --- cleanobj --- > --- cleandir_subdir_amr --- > ===> amr (cleandir) > --- cleandir_subdir_acpi --- > ===> acpi/aibs (cleandir) > --- cleandir_subdir_amdtemp --- > --- cleanobj --- > --- cleandir_subdir_an --- > ===> an (cleandir) > --- cleandir_subdir_acpi --- > --- cleanobj --- > --- cleandir_subdir_amr --- > --- cleanobj --- > --- cleandir_subdir_an --- > --- cleanobj --- > --- cleandir_subdir_amr --- > --- _sub.cleandir --- > --- cleandir_subdir_aout --- > ===> aout (cleandir) > --- cleandir_subdir_amr --- > ===> amr/amr_cam (cleandir) > --- cleandir_subdir_arcmsr --- > ===> arcmsr (cleandir) > --- cleandir_subdir_amr --- > --- clean --- > rm -f export_syms amr_cam.ko amr_cam.kld amr_cam.o amr_cam.ko.debug amr_cam.ko.symbols opt_cam.h opt_scsi.h bus_if.h device_if.h > --- cleandir_subdir_aout --- > --- cleanobj --- > --- cleandir_subdir_amr --- > --- cleanilinks --- > rm -f @ machine x86 > --- cleandepend --- > --- cleandir_subdir_arcmsr --- > --- cleanobj --- > --- cleandir_subdir_amr --- > rm -f .depend GPATH GRTAGS GSYMS GTAGS > --- cleandir_subdir_asmc --- > --- cleandir_subdir_amr --- > --- cleanobj --- > --- cleandir_subdir_asmc --- > ===> asmc (cleandir) > --- cleandir_subdir_amr --- > ===> amr/amr_linux (cleandir) > --- cleandir_subdir_ata --- > ===> ata (cleandir) > --- cleandir_subdir_amr --- > --- clean --- > rm -f export_syms amr_linux.ko amr_linux.kld amr_linux.o amr_linux.ko.debug amr_linux.ko.symbols bus_if.h device_if.h > --- cleanilinks --- > --- cleandir_subdir_asmc --- > --- cleanobj --- > --- cleandir_subdir_amr --- > rm -f @ machine x86 > --- cleandepend --- > rm -f .depend GPATH GRTAGS GSYMS GTAGS > --- cleandir_subdir_ath --- > --- cleandir_subdir_ata --- > --- _sub.cleandir --- > ===> ata/atacore (cleandir) > --- cleandir_subdir_ath --- > ===> ath (cleandir) > --- cleandir_subdir_amr --- > --- cleanobj --- > --- cleandir_subdir_ath_pci --- > ===> ath_pci (cleandir) > --- cleandir_subdir_ata --- > --- cleanobj --- > --- cleandir_subdir_ath_pci --- > --- cleanobj --- > --- cleandir_subdir_ata --- > ===> ata/atacard (cleandir) > --- cleandir_subdir_autofs --- > ===> autofs (cleandir) > --- cleandir_subdir_ath --- > --- cleanobj --- > --- cleandir_subdir_ata --- > --- cleanobj --- > --- cleandir_subdir_autofs --- > --- cleanobj --- > --- cleandir_subdir_ata --- > ===> ata/ataisa (cleandir) > --- cleandir_subdir_bce --- > ===> bce (cleandir) > --- cleandir_subdir_ata --- > --- cleanobj --- > ===> ata/atapci (cleandir) > --- cleandir_subdir_bce --- > --- cleanobj --- > --- cleandir_subdir_bfe --- > ===> bfe (cleandir) > --- cleandir_subdir_ata --- > --- cleanobj --- > --- cleandir_subdir_bfe --- > --- cleanobj --- > --- cleandir_subdir_ata --- > --- _sub.cleandir --- > ===> ata/atapci/chipsets (cleandir) > --- _sub.cleandir --- > ===> ata/atapci/chipsets/ataacard (cleandir) > --- cleanobj --- > ===> ata/atapci/chipsets/ataacerlabs (cleandir) > --- cleanobj --- > ===> ata/atapci/chipsets/ataadaptec (cleandir) > --- cleanobj --- > rm: fts_read: No such file or directory > *** [cleanobj] Error code 1 > > make[5]: stopped in > --- cleandir_subdir_ath --- > A failure has been detected in another branch of the parallel make > > make[4]: stopped in > *** [cleandir_subdir_ath] Error code 2 > > make[3]: stopped in > --- cleandir_subdir_ata --- > --- _sub.cleandir --- > A failure has been detected in another branch of the parallel make > > make[7]: stopped in > *** [_sub.cleandir] Error code 2 > > make[6]: stopped in > 1 error > > make[6]: stopped in > *** [_sub.cleandir] Error code 2 > > make[5]: stopped in > 2 errors > > make[5]: stopped in > *** [_sub.cleandir] Error code 2 > > make[4]: stopped in > 1 error > > make[4]: stopped in > *** [cleandir_subdir_ata] Error code 2 > > make[3]: stopped in > 2 errors > > make[3]: stopped in > *** [modules-cleandir] Error code 2 > > make[2]: stopped in /usr/obj > 1 error > > make[2]: stopped in /usr/obj > *** [buildkernel] Error code 2 > > make[1]: stopped in > 1 error > > make[1]: stopped in > *** [buildkernel] Error code 2 > > make: stopped in > 1 error > > make: stopped in > Build step 'Execute shell' marked build as failure > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 00:02:39 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 365DCC06; Sat, 27 Sep 2014 00:02:39 +0000 (UTC) Received: from mail-vc0-x22c.google.com (mail-vc0-x22c.google.com [IPv6:2607:f8b0:400c:c03::22c]) (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 B0B85C0A; Sat, 27 Sep 2014 00:02:38 +0000 (UTC) Received: by mail-vc0-f172.google.com with SMTP id hy10so10115489vcb.3 for ; Fri, 26 Sep 2014 17:02:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kAcPXjkyiPQCGtVDiLDkNDyzXE9MZjpiyUgrpW2d5t8=; b=Dn7UV/sGYwbUp0iO76b+bjxEUTr0DvDMR8XLvehQIuMGQEcWdg2DdCB7fM0XTeU42h ivwUf5OiuFhhX90HVxUmK2+mLfvSYwPq9UpaN5vJ/ZYI5NxPqvM63BonyBfFvv1oRsdx SC5qVxVRpUIr9IkPBQLh0vHiYqslNvM6HwjjD5lNsbqckd1Yvsb4MeanIFaISKUuI72/ AXV+zX1ztLs46HoypKQtf4htTZgAd/8EOK/Wlm++7FBQl3YS8N8AWi7h0FPinbMV4PH0 sHqrDzsS9Tpx30LuvwAOE5PtymuRZlUkQKU+zA+cdSKUWvHdbcyDUlucaPGX2OFaY1bM hs1w== MIME-Version: 1.0 X-Received: by 10.52.76.130 with SMTP id k2mr15227959vdw.9.1411776157677; Fri, 26 Sep 2014 17:02:37 -0700 (PDT) Received: by 10.220.4.70 with HTTP; Fri, 26 Sep 2014 17:02:37 -0700 (PDT) In-Reply-To: <20D23455255E407FB8965AEEDA7BF9E2@multiplay.co.uk> References: <1146345957.0.1411770477782.JavaMail.jenkins@jenkins-9.freebsd.org> <20D23455255E407FB8965AEEDA7BF9E2@multiplay.co.uk> Date: Sat, 27 Sep 2014 09:32:37 +0930 Message-ID: Subject: Re: Build failed in Jenkins: FreeBSD_stable_10 #793 From: Matt Thyer To: Steven Hartland Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-stable@freebsd.org" , jenkins-admin@freebsd.org, mjg@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: Sat, 27 Sep 2014 00:02:39 -0000 I got this too today (with r272192) and my last build was on 1 Sept at r270905. On 27 September 2014 08:21, Steven Hartland wrote: > Hmm build machines install too old? I thought this error was already fixed? > ----- Original Message ----- From: > To: ; ; > > Sent: Friday, September 26, 2014 11:27 PM > Subject: Build failed in Jenkins: FreeBSD_stable_10 #793 > > > > See > 793/changes> >> >> Changes: >> >> [mjg] MFC r270993: >> >> Fix up proc_realparent to always return correct process. >> >> Prior to the change it would always return initproc for non-traced >> processes. >> >> This fixes a regression in inferior(). >> >> Approved by: re (marius) >> >> ------------------------------------------ >> [...truncated 224407 lines...] >> ===> acpi/acpi_ibm (cleandir) >> --- cleandir_subdir_aic7xxx --- >> --- cleanobj --- >> --- cleandir_subdir_alc --- >> --- cleandir_subdir_acpi --- >> --- cleanobj --- >> --- cleandir_subdir_alc --- >> ===> alc (cleandir) >> --- cleandir_subdir_acpi --- >> ===> acpi/acpi_panasonic (cleandir) >> --- cleanobj --- >> --- cleandir_subdir_alc --- >> --- cleanobj --- >> --- cleandir_subdir_acpi --- >> ===> acpi/acpi_sony (cleandir) >> --- cleandir_subdir_aic7xxx --- >> --- _sub.cleandir --- >> ===> aic7xxx/ahc/ahc_eisa (cleandir) >> --- cleandir_subdir_ale --- >> ===> ale (cleandir) >> --- cleandir_subdir_acpi --- >> --- cleanobj --- >> --- cleandir_subdir_aic7xxx --- >> --- clean --- >> rm -f export_syms ahc_eisa.ko ahc_eisa.kld ahc_eisa.o ahc_eisa.ko.debug >> ahc_eisa.ko.symbols opt_scsi.h opt_cam.h opt_aic7xxx.h eisa_if.h pci_if.h >> bus_if.h device_if.h >> --- cleandir_subdir_acpi --- >> ===> acpi/acpi_toshiba (cleandir) >> --- cleandir_subdir_ale --- >> --- cleanobj --- >> --- cleandir_subdir_aic7xxx --- >> --- cleanilinks --- >> rm -f @ machine x86 >> --- cleandepend --- >> rm -f .depend GPATH GRTAGS GSYMS GTAGS >> --- cleanobj --- >> --- cleandir_subdir_acpi --- >> --- cleanobj --- >> --- cleandir_subdir_alq --- >> --- cleandir_subdir_aic7xxx --- >> ===> aic7xxx/ahc/ahc_isa (cleandir) >> --- cleandir_subdir_alq --- >> ===> alq (cleandir) >> --- cleandir_subdir_aic7xxx --- >> --- clean --- >> rm -f export_syms ahc_isa.ko ahc_isa.kld ahc_isa.o ahc_isa.ko.debug >> ahc_isa.ko.symbols opt_scsi.h opt_cam.h opt_aic7xxx.h pci_if.h isa_if.h >> bus_if.h device_if.h >> --- cleandir_subdir_acpi --- >> ===> acpi/acpi_video (cleandir) >> --- cleandir_subdir_aic7xxx --- >> --- cleanilinks --- >> rm -f @ machine x86 >> --- cleandepend --- >> --- cleandir_subdir_alq --- >> --- cleanobj --- >> --- cleandir_subdir_aic7xxx --- >> rm -f .depend GPATH GRTAGS GSYMS GTAGS >> --- cleandir_subdir_acpi --- >> --- cleanobj --- >> --- cleandir_subdir_aic7xxx --- >> --- cleanobj --- >> ===> aic7xxx/ahc/ahc_pci (cleandir) >> --- cleandir_subdir_acpi --- >> ===> acpi/acpi_dock (cleandir) >> --- cleandir_subdir_amdsbwd --- >> --- cleandir_subdir_aic7xxx --- >> --- clean --- >> rm -f export_syms ahc_pci.ko ahc_pci.kld ahc_pci.o aic7xxx_pci.o >> ahc_pci.ko.debug ahc_pci.ko.symbols opt_scsi.h opt_cam.h opt_aic7xxx.h >> pci_if.h bus_if.h device_if.h >> --- cleandir_subdir_amdsbwd --- >> ===> amdsbwd (cleandir) >> --- cleandir_subdir_aic7xxx --- >> --- cleanilinks --- >> rm -f @ machine x86 >> --- cleandepend --- >> rm -f .depend GPATH GRTAGS GSYMS GTAGS >> --- cleanobj --- >> ===> aic7xxx/ahd (cleandir) >> --- cleandir_subdir_acpi --- >> --- cleanobj --- >> ===> acpi/acpi_wmi (cleandir) >> --- cleandir_subdir_amdsbwd --- >> --- cleanobj --- >> --- cleandir_subdir_aic7xxx --- >> --- cleanobj --- >> --- cleandir_subdir_amdtemp --- >> ===> amdtemp (cleandir) >> --- cleandir_subdir_amr --- >> --- cleandir_subdir_acpi --- >> --- cleanobj --- >> --- cleandir_subdir_amr --- >> ===> amr (cleandir) >> --- cleandir_subdir_acpi --- >> ===> acpi/aibs (cleandir) >> --- cleandir_subdir_amdtemp --- >> --- cleanobj --- >> --- cleandir_subdir_an --- >> ===> an (cleandir) >> --- cleandir_subdir_acpi --- >> --- cleanobj --- >> --- cleandir_subdir_amr --- >> --- cleanobj --- >> --- cleandir_subdir_an --- >> --- cleanobj --- >> --- cleandir_subdir_amr --- >> --- _sub.cleandir --- >> --- cleandir_subdir_aout --- >> ===> aout (cleandir) >> --- cleandir_subdir_amr --- >> ===> amr/amr_cam (cleandir) >> --- cleandir_subdir_arcmsr --- >> ===> arcmsr (cleandir) >> --- cleandir_subdir_amr --- >> --- clean --- >> rm -f export_syms amr_cam.ko amr_cam.kld amr_cam.o amr_cam.ko.debug >> amr_cam.ko.symbols opt_cam.h opt_scsi.h bus_if.h device_if.h >> --- cleandir_subdir_aout --- >> --- cleanobj --- >> --- cleandir_subdir_amr --- >> --- cleanilinks --- >> rm -f @ machine x86 >> --- cleandepend --- >> --- cleandir_subdir_arcmsr --- >> --- cleanobj --- >> --- cleandir_subdir_amr --- >> rm -f .depend GPATH GRTAGS GSYMS GTAGS >> --- cleandir_subdir_asmc --- >> --- cleandir_subdir_amr --- >> --- cleanobj --- >> --- cleandir_subdir_asmc --- >> ===> asmc (cleandir) >> --- cleandir_subdir_amr --- >> ===> amr/amr_linux (cleandir) >> --- cleandir_subdir_ata --- >> ===> ata (cleandir) >> --- cleandir_subdir_amr --- >> --- clean --- >> rm -f export_syms amr_linux.ko amr_linux.kld amr_linux.o >> amr_linux.ko.debug amr_linux.ko.symbols bus_if.h device_if.h >> --- cleanilinks --- >> --- cleandir_subdir_asmc --- >> --- cleanobj --- >> --- cleandir_subdir_amr --- >> rm -f @ machine x86 >> --- cleandepend --- >> rm -f .depend GPATH GRTAGS GSYMS GTAGS >> --- cleandir_subdir_ath --- >> --- cleandir_subdir_ata --- >> --- _sub.cleandir --- >> ===> ata/atacore (cleandir) >> --- cleandir_subdir_ath --- >> ===> ath (cleandir) >> --- cleandir_subdir_amr --- >> --- cleanobj --- >> --- cleandir_subdir_ath_pci --- >> ===> ath_pci (cleandir) >> --- cleandir_subdir_ata --- >> --- cleanobj --- >> --- cleandir_subdir_ath_pci --- >> --- cleanobj --- >> --- cleandir_subdir_ata --- >> ===> ata/atacard (cleandir) >> --- cleandir_subdir_autofs --- >> ===> autofs (cleandir) >> --- cleandir_subdir_ath --- >> --- cleanobj --- >> --- cleandir_subdir_ata --- >> --- cleanobj --- >> --- cleandir_subdir_autofs --- >> --- cleanobj --- >> --- cleandir_subdir_ata --- >> ===> ata/ataisa (cleandir) >> --- cleandir_subdir_bce --- >> ===> bce (cleandir) >> --- cleandir_subdir_ata --- >> --- cleanobj --- >> ===> ata/atapci (cleandir) >> --- cleandir_subdir_bce --- >> --- cleanobj --- >> --- cleandir_subdir_bfe --- >> ===> bfe (cleandir) >> --- cleandir_subdir_ata --- >> --- cleanobj --- >> --- cleandir_subdir_bfe --- >> --- cleanobj --- >> --- cleandir_subdir_ata --- >> --- _sub.cleandir --- >> ===> ata/atapci/chipsets (cleandir) >> --- _sub.cleandir --- >> ===> ata/atapci/chipsets/ataacard (cleandir) >> --- cleanobj --- >> ===> ata/atapci/chipsets/ataacerlabs (cleandir) >> --- cleanobj --- >> ===> ata/atapci/chipsets/ataadaptec (cleandir) >> --- cleanobj --- >> rm: fts_read: No such file or directory >> *** [cleanobj] Error code 1 >> >> make[5]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules/ata/atapci> >> --- cleandir_subdir_ath --- >> A failure has been detected in another branch of the parallel make >> >> make[4]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules/ath> >> *** [cleandir_subdir_ath] Error code 2 >> >> make[3]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules> >> --- cleandir_subdir_ata --- >> --- _sub.cleandir --- >> A failure has been detected in another branch of the parallel make >> >> make[7]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules/ata/atapci/ >> chipsets/ataadaptec> >> *** [_sub.cleandir] Error code 2 >> >> make[6]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules/ata/atapci/chipsets> >> 1 error >> >> make[6]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules/ata/atapci/chipsets> >> *** [_sub.cleandir] Error code 2 >> >> make[5]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules/ata/atapci> >> 2 errors >> >> make[5]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules/ata/atapci> >> *** [_sub.cleandir] Error code 2 >> >> make[4]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules/ata> >> 1 error >> >> make[4]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules/ata> >> *** [cleandir_subdir_ata] Error code 2 >> >> make[3]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules> >> 2 errors >> >> make[3]: stopped in > jenkins/job/FreeBSD_stable_10/ws/sys/modules> >> *** [modules-cleandir] Error code 2 >> >> make[2]: stopped in /usr/obj> FreeBSD_stable_10/ws/sys/GENERIC> >> 1 error >> >> make[2]: stopped in /usr/obj> FreeBSD_stable_10/ws/sys/GENERIC> >> *** [buildkernel] Error code 2 >> >> make[1]: stopped in > jenkins/job/FreeBSD_stable_10/ws/> >> 1 error >> >> make[1]: stopped in > jenkins/job/FreeBSD_stable_10/ws/> >> *** [buildkernel] Error code 2 >> >> make: stopped in > jenkins/job/FreeBSD_stable_10/ws/> >> 1 error >> >> make: stopped in > jenkins/job/FreeBSD_stable_10/ws/> >> Build step 'Execute shell' marked build as failure >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> >> > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 01:28: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9680F68F; Sat, 27 Sep 2014 01:28:50 +0000 (UTC) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 83BF6341; Sat, 27 Sep 2014 01:28:50 +0000 (UTC) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id A733883B; Sat, 27 Sep 2014 01:28:49 +0000 (UTC) Date: Sat, 27 Sep 2014 01:28:48 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org, mjg@FreeBSD.org, dteske@FreeBSD.org Message-ID: <77558872.2.1411781329258.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1146345957.0.1411770477782.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1146345957.0.1411770477782.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: Jenkins build is back to normal : FreeBSD_stable_10 #794 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Jenkins-Job: FreeBSD_stable_10 X-Jenkins-Result: SUCCESS 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: Sat, 27 Sep 2014 01:28:50 -0000 See From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 12:07:05 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4E76F225; Sat, 27 Sep 2014 12:07:05 +0000 (UTC) Received: from erg.verweg.com (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "erg.verweg.com", Issuer "Verweg Dot Com CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BD52F6AB; Sat, 27 Sep 2014 12:07:04 +0000 (UTC) Received: from neon.fritz.box (helium.xs4all.nl [83.163.52.241]) (authenticated bits=0) by erg.verweg.com (8.14.9/8.14.9) with ESMTP id s8RC6n5K035171 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 27 Sep 2014 12:06:52 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host helium.xs4all.nl [83.163.52.241] claimed to be neon.fritz.box Content-Type: multipart/signed; boundary="Apple-Mail=_51722CA5-87C0-401D-87C5-C2B614B2A7A1"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: fdescfs patch for working hierarchical jails From: Ruben van Staveren In-Reply-To: <5425BE60.5020900@gritton.org> Date: Sat, 27 Sep 2014 14:06:49 +0200 Message-Id: <0CF6D1D0-0721-4395-8290-C92C91FEA45C@verweg.com> References: <0B3648E9-21DC-4691-A6A9-26DE2C40947B@verweg.com> <5425BE60.5020900@gritton.org> To: James Gritton X-Mailer: Apple Mail (2.1878.6) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (erg.verweg.com [94.142.245.8]); Sat, 27 Sep 2014 12:07:01 +0000 (UTC) Cc: freebsd-jail@freebsd.org, "freebsd-stable@FreeBSD.org 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: Sat, 27 Sep 2014 12:07:05 -0000 --Apple-Mail=_51722CA5-87C0-401D-87C5-C2B614B2A7A1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Hi James, others, On 26 Sep 2014, at 21:28, James Gritton wrote: > On 9/25/2014 3:40 AM, Ruben van Staveren wrote: >> Hi, >>=20 >> Could a committer have a look at = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192951 ? >>=20 >> This enables fdescfs in hierarchical jails, would be nice to have = this for 10.1 >>=20 >> Thanks! >>=20 >> Best Regards, >> Ruben van Staveren >=20 > This would have to go into current first, and then MFC. Considering > 10.1 is getting close to release, I suspect it wouldn't be allowed in. I agree, probably better to do it that way indeed. > Also, I'm not sure I'd want to implement this in quite the proposed > way: it might suffice (from a security viewpoint) to use the existing > allow.mount.devfs for mounting fdescfs. Wouldn=92t that be misleading? It would be better to mop up the various = pseudofses under the monicker allow.mount.pseudofs. >=20 > - Jamie - Ruben --Apple-Mail=_51722CA5-87C0-401D-87C5-C2B614B2A7A1 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 - http://gpgtools.org iEYEARECAAYFAlQmqFkACgkQZ88+mcQxRw1prgCZAa8lliQyS3sCHuTRU9W8FZqE Ui8AnjCuMGPzDcrDRf/a1NmhMlhcqxgY =J99b -----END PGP SIGNATURE----- --Apple-Mail=_51722CA5-87C0-401D-87C5-C2B614B2A7A1-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 14:04:41 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53BC6C24 for ; Sat, 27 Sep 2014 14:04:41 +0000 (UTC) Received: from smtp.rlwinm.de (smtp.rlwinm.de [IPv6:2a01:4f8:201:31ef::e]) (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 15A02171 for ; Sat, 27 Sep 2014 14:04:41 +0000 (UTC) Received: from hexe.rlwinm.de (unknown [172.22.228.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.rlwinm.de (Postfix) with ESMTPSA id 6A95847D6 for ; Sat, 27 Sep 2014 16:04:36 +0200 (CEST) Message-ID: <5426C3F3.3040404@rlwinm.de> Date: Sat, 27 Sep 2014 16:04:35 +0200 From: Jan Bramkamp User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: 10.1 BETA2 World - Breaks saslauthd References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> In-Reply-To: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 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: Sat, 27 Sep 2014 14:04:41 -0000 On 25.09.2014 17:04, Dimitry Andric wrote: > On 25 Sep 2014, at 16:54, Tim Daneliuk wrote: >> I've seen this behavior over the last week or two when I try to upgrade >> to latest stable sources. Currently just installed kernel and world for: >> >> /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: 272095 >> Node Kind: directory >> Schedule: normal >> Last Changed Author: peter >> Last Changed Rev: 272078 >> Last Changed Date: 2014-09-24 14:30:36 -0500 (Wed, 24 Sep 2014) >> >> This breaks saslauthd - it demands a password when sending mail, but then >> rejects it in every case. >> >> If I just install a new kernel, everything is fine. But if I install >> world, that's when the problem shows up. I've tried a full reinstall of >> cygnus sasls and the daemon is running. >> >> Ideas on how to chase this down/fix, would be appreciated... > > It is probably caused by this MFC: http://svnweb.freebsd.org/changeset/base/271766 > > To make saslauthd work again, you need to specify a correct PAM policy > file in /usr/local/etc/pam.d for your service, most likely "smtp" in > this case. E.g., create a file /usr/local/etc/pam.d/smtp, containing at > least: > > auth required pam_unix.so no_warn try_first_pass > account required pam_unix.so > session required pam_permit.so > password required pam_permit.so > > Optionally, add a line: > > auth required pam_group.so luser group=smtp-users fail_safe > > to allow only members of the smtp-users group to authenticate > successfully. > > -Dimitry > If I remember correctly saslauthd -a pam is hardcoded to always use the PAM service "imap". From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 14:36:48 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87D063B9 for ; Sat, 27 Sep 2014 14:36:48 +0000 (UTC) Received: from tensor.andric.com (unknown [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4263C632 for ; Sat, 27 Sep 2014 14:36:48 +0000 (UTC) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id D6461B80A; Sat, 27 Sep 2014 16:36:42 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_6CB1DFC1-96B3-447A-8244-59311F6836EB"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: 10.1 BETA2 World - Breaks saslauthd From: Dimitry Andric In-Reply-To: <5426C3F3.3040404@rlwinm.de> Date: Sat, 27 Sep 2014 16:36:34 +0200 Message-Id: References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <5426C3F3.3040404@rlwinm.de> To: Jan Bramkamp X-Mailer: Apple Mail (2.1878.6) 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: Sat, 27 Sep 2014 14:36:48 -0000 --Apple-Mail=_6CB1DFC1-96B3-447A-8244-59311F6836EB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 27 Sep 2014, at 16:04, Jan Bramkamp wrote: > On 25.09.2014 17:04, Dimitry Andric wrote: >> On 25 Sep 2014, at 16:54, Tim Daneliuk wrote: ... >>> This breaks saslauthd - it demands a password when sending mail, but = then >>> rejects it in every case. >>>=20 >>> If I just install a new kernel, everything is fine. But if I = install >>> world, that's when the problem shows up. I've tried a full = reinstall of >>> cygnus sasls and the daemon is running. >>>=20 >>> Ideas on how to chase this down/fix, would be appreciated... >>=20 >> It is probably caused by this MFC: = http://svnweb.freebsd.org/changeset/base/271766 >>=20 >> To make saslauthd work again, you need to specify a correct PAM = policy >> file in /usr/local/etc/pam.d for your service, most likely "smtp" in >> this case. ... > If I remember correctly saslauthd -a pam is hardcoded to always use = the > PAM service "imap". No, the service name is received from the SASL client that connects to /var/run/saslauthd/mux. In case of postfix, the default service name is "smtp". Quoting from postconf(5): smtpd_sasl_service (default: smtp) The service name that is passed to the SASL plug-in that is selected with smtpd_sasl_type and smtpd_sasl_path. This feature is available in Postfix 2.11 and later. Prior versions behave as if "smtp" is specified. -Dimitry --Apple-Mail=_6CB1DFC1-96B3-447A-8244-59311F6836EB 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----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlQmy3YACgkQsF6jCi4glqMoNACg6SeSYz7UoXmKKjIQXCDfTHxp /8IAmwRqT7AviPghbA4Kp4cDCi4SvzHr =5WQU -----END PGP SIGNATURE----- --Apple-Mail=_6CB1DFC1-96B3-447A-8244-59311F6836EB-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 15:07:07 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4898DF16; Sat, 27 Sep 2014 15:07:07 +0000 (UTC) Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) (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 B10E8945; Sat, 27 Sep 2014 15:07:06 +0000 (UTC) Received: by mail-we0-f177.google.com with SMTP id t60so10931773wes.22 for ; Sat, 27 Sep 2014 08:07:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3bFCq1eHJBoodA7cmjzmglhfNcBK0uP5HyRWSe01blA=; b=UfWOB5PascSJzAl5xA+AJs5bxtGzXsf4CDXkPXEIhNgb31TnLRXiWh8/rEo92UqJnz xqrvJ+oAGPHFiU/r7ARQq8wSXFC6HWfGysPt0LYO0qFZvJQVUPimNPH/FAGrc49aY+bO 7CY3EKOIBJnsNJjGe9/chohwfGdUZDzNNkrUNVj8jRWJW2JP7LrHkMO0j1oEqUagv4pi KKNkNSX6yX9bzDVve9K9YxEVRzLIqiZ7BNZYryU/4zdBTcRLEPaInCJ3OQkhtEd46HU4 4yZwLBw1h9MGLJPXZWOTSUg879/FyJAXaZBgFmxswmnFKGXyRQmyCKIBitQOuzRXpXtU wbGA== MIME-Version: 1.0 X-Received: by 10.194.76.97 with SMTP id j1mr30511676wjw.40.1411830425009; Sat, 27 Sep 2014 08:07:05 -0700 (PDT) Received: by 10.217.127.70 with HTTP; Sat, 27 Sep 2014 08:07:04 -0700 (PDT) In-Reply-To: References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <5426C3F3.3040404@rlwinm.de> Date: Sat, 27 Sep 2014 11:07:04 -0400 Message-ID: Subject: Re: 10.1 BETA2 World - Breaks saslauthd From: Brandon Allbery To: Dimitry Andric Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-stable , Jan Bramkamp 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: Sat, 27 Sep 2014 15:07:07 -0000 On Sat, Sep 27, 2014 at 10:36 AM, Dimitry Andric wrote: > > If I remember correctly saslauthd -a pam is hardcoded to always use the > > PAM service "imap". > > No, the service name is received from the SASL client that connects to > /var/run/saslauthd/mux. In case of postfix, the default service name is > "smtp". Quoting from postconf(5): > saslauthd isn't the core SASL entry point; it's a hack to export traditional password stores as SASL providers to cyrus-sasl. Last I checked, it didn't actually receive the service name from SASL. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 16:12: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7524D38; Sat, 27 Sep 2014 16:12:17 +0000 (UTC) Received: from msa04b.plala.or.jp (msa04.plala.or.jp [IPv6:2400:7800:0:5010::4]) by mx1.freebsd.org (Postfix) with ESMTP id 501ABF1C; Sat, 27 Sep 2014 16:12:16 +0000 (UTC) Received: from i125-201-3-196.s02.a026.ap.plala.or.jp ([125.201.3.196]) by msa04b.plala.or.jp with ESMTP id <20140927161144.OPRU12371.msa04b.plala.or.jp@i125-201-3-196.s02.a026.ap.plala.or.jp>; Sun, 28 Sep 2014 01:11:44 +0900 Date: Sun, 28 Sep 2014 01:11:44 +0900 Message-ID: <861tqxvy9r.wl%poyopoyo@puripuri.plala.or.jp> From: poyopoyo@puripuri.plala.or.jp To: Stefan Ehmann Subject: Re: xzgrep: incomplete results on larger files In-Reply-To: <541DE9FC.2090003@gmx.net> References: <541DE9FC.2090003@gmx.net> Mail-Followup-To: Stefan Ehmann , freebsd-stable@freebsd.org, poyopoyo@puripuri.plala.or.jp User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-2022-JP-2?B?R29qGyQoRCtXGyhC?=) APEL/10.8 Emacs/24.3 (amd64-portbld-freebsd10.0) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-VirusScan: Outbound; msa04b; Sun, 28 Sep 2014 01:11:44 +0900 Cc: freebsd-stable@freebsd.org, Gabor Kovesdan 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: Sat, 27 Sep 2014 16:12:18 -0000 This persists for at least 2.5 years. http://docs.FreeBSD.org/cgi/mid.cgi?86k43pb0sc.wl%poyopoyo (author Cc'd) At Sat, 20 Sep 2014 22:56:28 +0200, 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). > From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 16:18:41 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B5636231; Sat, 27 Sep 2014 16:18:41 +0000 (UTC) Received: from m2.gritton.org (gritton.org [63.246.134.121]) (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 80379FAC; Sat, 27 Sep 2014 16:18:41 +0000 (UTC) Received: from [192.168.0.34] (c-50-168-192-61.hsd1.ut.comcast.net [50.168.192.61]) (authenticated bits=0) by m2.gritton.org (8.14.9/8.14.9) with ESMTP id s8RGId5f005950; Sat, 27 Sep 2014 16:18:39 GMT (envelope-from jamie@gritton.org) Message-ID: <5426E358.9070005@gritton.org> Date: Sat, 27 Sep 2014 10:18:32 -0600 From: James Gritton User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-jail@freebsd.org, "freebsd-stable@FreeBSD.org Stable" Subject: Re: fdescfs patch for working hierarchical jails References: <0B3648E9-21DC-4691-A6A9-26DE2C40947B@verweg.com> <5425BE60.5020900@gritton.org> <0CF6D1D0-0721-4395-8290-C92C91FEA45C@verweg.com> In-Reply-To: <0CF6D1D0-0721-4395-8290-C92C91FEA45C@verweg.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit 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: Sat, 27 Sep 2014 16:18:41 -0000 On 9/27/2014 6:06 AM, Ruben van Staveren wrote: > Hi James, others, > > On 26 Sep 2014, at 21:28, James Gritton wrote: > >> On 9/25/2014 3:40 AM, Ruben van Staveren wrote: >>> Hi, >>> >>> Could a committer have a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192951 ? >>> >>> This enables fdescfs in hierarchical jails, would be nice to have this for 10.1 >>> >>> Thanks! >>> >>> Best Regards, >>> Ruben van Staveren >> This would have to go into current first, and then MFC. Considering >> 10.1 is getting close to release, I suspect it wouldn't be allowed in. > I agree, probably better to do it that way indeed. > >> Also, I'm not sure I'd want to implement this in quite the proposed >> way: it might suffice (from a security viewpoint) to use the existing >> allow.mount.devfs for mounting fdescfs. > Wouldn’t that be misleading? It would be better to mop up the various pseudofses under the monicker allow.mount.pseudofs. My thinking is that fdescfs is practically the same as what devfs already offers - just more descriptors in /dev/fd than the basic three. I can't see why allowing one wouldn't be akin to allowing the other. In fact, I fail to understand why it was made a separate filesystem in the first place. Perhaps someone on the sec team will tell me otherwise when I ask (which I ought to do before forging ahead). - Jamie From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 19:12:04 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 2112AE6 for ; Sat, 27 Sep 2014 19:12:04 +0000 (UTC) Received: from tensor.andric.com (unknown [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D0590687 for ; Sat, 27 Sep 2014 19:12:03 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::a5ea:262e:f10f:f714] (unknown [IPv6:2001:7b8:3a7:0:a5ea:262e:f10f:f714]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 4AB57B80A; Sat, 27 Sep 2014 21:11:58 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_12FE3C37-ABC9-48B5-98CE-1B08B948281B"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: 10.1 BETA2 World - Breaks saslauthd From: Dimitry Andric In-Reply-To: Date: Sat, 27 Sep 2014 21:11:40 +0200 Message-Id: <433B3FD3-55B1-4FF1-BD4E-10A0EC6CEC50@FreeBSD.org> References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <5426C3F3.3040404@rlwinm.de> To: Brandon Allbery X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-stable , Jan Bramkamp 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: Sat, 27 Sep 2014 19:12:04 -0000 --Apple-Mail=_12FE3C37-ABC9-48B5-98CE-1B08B948281B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 27 Sep 2014, at 17:07, Brandon Allbery wrote: > On Sat, Sep 27, 2014 at 10:36 AM, Dimitry Andric = wrote: > > If I remember correctly saslauthd -a pam is hardcoded to always use = the > > PAM service "imap". >=20 > No, the service name is received from the SASL client that connects to > /var/run/saslauthd/mux. In case of postfix, the default service name = is > "smtp". Quoting from postconf(5): >=20 > saslauthd isn't the core SASL entry point; it's a hack to export = traditional password stores as SASL providers to cyrus-sasl. Last I = checked, it didn't actually receive the service name from SASL. Well, last I checked it did, and it even logs the service name. :) -Dimitry --Apple-Mail=_12FE3C37-ABC9-48B5-98CE-1B08B948281B 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----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlQnC/cACgkQsF6jCi4glqMG4wCgpvwc4Ro1tlDaNdKRw+7LUO0W 0IoAn35w2WpyyP2r7Zi+hVACniX+05zL =X3YR -----END PGP SIGNATURE----- --Apple-Mail=_12FE3C37-ABC9-48B5-98CE-1B08B948281B-- From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 19:17:26 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 062095D5; Sat, 27 Sep 2014 19:17:26 +0000 (UTC) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (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 6CCBD6EC; Sat, 27 Sep 2014 19:17:25 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id n3so1146440wiv.15 for ; Sat, 27 Sep 2014 12:17:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uGML/agdpwfOAlj1KGTTwWTvhDPMbp/jr/MBW8liCr4=; b=NUoq1J0jYLFyGEhTWHPTbdcF2ae/WfR4IalHPUqsEci+fpJQKH3X2rFhS0CGEY6Ivr dcBm2zEcmBPhkCfSXP4X6r46tE+k7akzIEhU7kxSDptE6oZezOInc6GI8HAozN63nLLH hNJ5CpEZAC5HJr7izyvzmXARyLzmc0xdk/3kIkLqg5OMvEI5UoVrpdikszcTT1PkLwkm b3++bPKuAXhmRfTkMJ29GrUDQB/3mBinWxplU6BvY++GxYKReJQgGlpsCGhCN19Wz3MR TnzLK3prh3zmfAO2zqhAUjgTLdea5sz+DDLpSYkxb/mIXOnsWaNi/ydG1glsCye60ZY3 rEBQ== MIME-Version: 1.0 X-Received: by 10.180.208.13 with SMTP id ma13mr35594553wic.53.1411845443618; Sat, 27 Sep 2014 12:17:23 -0700 (PDT) Received: by 10.217.127.70 with HTTP; Sat, 27 Sep 2014 12:17:23 -0700 (PDT) In-Reply-To: <433B3FD3-55B1-4FF1-BD4E-10A0EC6CEC50@FreeBSD.org> References: <3DA4B666-AB81-4F25-ABAE-DDC163F41E20@FreeBSD.org> <5426C3F3.3040404@rlwinm.de> <433B3FD3-55B1-4FF1-BD4E-10A0EC6CEC50@FreeBSD.org> Date: Sat, 27 Sep 2014 15:17:23 -0400 Message-ID: Subject: Re: 10.1 BETA2 World - Breaks saslauthd From: Brandon Allbery To: Dimitry Andric Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-stable , Jan Bramkamp 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: Sat, 27 Sep 2014 19:17:26 -0000 On Sat, Sep 27, 2014 at 3:11 PM, Dimitry Andric wrote: > > saslauthd isn't the core SASL entry point; it's a hack to export > traditional password stores as SASL providers to cyrus-sasl. Last I > checked, it didn't actually receive the service name from SASL. > > Well, last I checked it did, and it even logs the service name. :) What I left out is that the last time I checked was something like 10 years ago, before everything was migrated to using Kerberos. :) (Come to think of it, "cyrus-sasl" might be a hint about that; cyrus-sasl v1 has been dead for a longish time, the current one is cyrus-sasl2. Although saslauthd is itself a slightly more general version of the hack v1 used.) -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 23:22:41 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 60DC1F0E; Sat, 27 Sep 2014 23:22:41 +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 364ECF26; Sat, 27 Sep 2014 23:22:40 +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 s8RNMo8L073840; Sat, 27 Sep 2014 16:22:56 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: (from www@localhost) by udns.ultimatedns.net (8.14.5/8.14.5/Submit) id s8RNMi0A073839; Sat, 27 Sep 2014 16:22:44 -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; Sat, 27 Sep 2014 16:22:44 -0700 (PDT) Message-ID: Date: Sat, 27 Sep 2014 16:22:44 -0700 (PDT) Subject: dmesg seems broken From: "Chris H" To: "freebsd amd64" , "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: Sat, 27 Sep 2014 23:22:41 -0000 Greetings, I'm building RELENG_9 recently. I installed, and updated source, last night. I've just built world, and kernel. After (and before) kernel install. I've found I'm missing from 14 to 40 lines from the top of the dmesg(8) output. In either /var/log/messages, and in /var/run/dmesg.boot. Where can I get that information? Where was it sent? Why am I not allowed to view it? Thank you for all your time, and consideration. --Chris From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 23:24:15 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 B5DDD1CE; Sat, 27 Sep 2014 23:24:15 +0000 (UTC) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::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 0941AF51; Sat, 27 Sep 2014 23:24:14 +0000 (UTC) Received: by mail-wi0-f181.google.com with SMTP id z2so1327603wiv.2 for ; Sat, 27 Sep 2014 16:24:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CAenBsjdh42J9mdaUXmiroC1QPBZMgq9CWLAtAt7TWo=; b=uBEud711i7muAQ35o3pEUvqovrMmuAVobLG4FOu9ugRBljyC4N58m+GjmKgR5Wn1Z1 chHeAlfHH40INqF0++70J7U7zazWeBO99sHqm9fMek611GrbnEG/D0iU6qd08zANPgz7 Ac6EeJ5PtQBY3FFu1NtUdIEVyrteG144wKon2AKT2GzOGF3pwA1tvqRY/yxLN1piZ5Vk qBIln+QmLGQq5jnmopBSCDcL+WpvUdctVy75Wh+T5VcR9rDps1hps5uwaIgIXi4+0tAW jl3ln/juT4veWKISr8S/yQweBzOg6f4ahaJ35ZOMOIP8oMX1tjfJXtKpLRCYM63N+yhv Ei7g== MIME-Version: 1.0 X-Received: by 10.194.142.209 with SMTP id ry17mr34131323wjb.57.1411860253273; Sat, 27 Sep 2014 16:24:13 -0700 (PDT) Received: by 10.217.127.70 with HTTP; Sat, 27 Sep 2014 16:24:13 -0700 (PDT) In-Reply-To: References: Date: Sat, 27 Sep 2014 19:24:13 -0400 Message-ID: Subject: Re: dmesg seems broken From: Brandon Allbery To: Chris H Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Sat, 27 Sep 2014 23:24:15 -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? -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 23:29:57 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 1BC182E2; Sat, 27 Sep 2014 23:29:57 +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 5D1F7F6D; Sat, 27 Sep 2014 23:29:56 +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 s8RNU4I4074495; Sat, 27 Sep 2014 16:30:10 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) Received: (from www@localhost) by udns.ultimatedns.net (8.14.5/8.14.5/Submit) id s8RNTxBs074489; Sat, 27 Sep 2014 16:29:59 -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; Sat, 27 Sep 2014 16:29:59 -0700 (PDT) Message-ID: In-Reply-To: References: Date: Sat, 27 Sep 2014 16:29:59 -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: Sat, 27 Sep 2014 23:29:57 -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? Odd. I'm only using GENERIC modified to not contain any hardware I'm not using. I've made zero changes to alter buffer(s). As I also mentioned; this too was the case from GENERIC that came on the install media. 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-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Sat Sep 27 23:39:32 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 CFB2265D for ; Sat, 27 Sep 2014 23:39:32 +0000 (UTC) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id A687BDD for ; Sat, 27 Sep 2014 23:39:32 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id B948C1F6D6 for ; Sat, 27 Sep 2014 19:39:25 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SwdfU1sEtP0y for ; Sat, 27 Sep 2014 19:39:25 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <54274AAC.60602@egr.msu.edu> Date: Sat, 27 Sep 2014 19:39:24 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: dmesg seems broken References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 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: Sat, 27 Sep 2014 23:39:32 -0000 On 09/27/2014 19:29, Chris H wrote: >> 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? > Odd. I'm only using GENERIC modified to not contain any > hardware I'm not using. I've made zero changes to alter > buffer(s). > As I also mentioned; this too was the case from GENERIC > that came on the install media. > > 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-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > Increase kern.msgbufsize in /boot/loader.conf or MSGBUF_SIZE in your kernel config. Were you booting with -v or did the standard dmesg content just grow too large?