From owner-freebsd-stable@FreeBSD.ORG Sun Jul 14 09:59:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 86A7FF91 for ; Sun, 14 Jul 2013 09:59:57 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [94.23.254.147]) by mx1.freebsd.org (Postfix) with ESMTP id 53ECEB7B for ; Sun, 14 Jul 2013 09:59:56 +0000 (UTC) Received: from roxette.lamaiziere.net (232.176.97.84.rev.sfr.net [84.97.176.232]) by smtp.lamaiziere.net (Postfix) with ESMTPA id 3871E5B52 for ; Sun, 14 Jul 2013 11:59:55 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by roxette.lamaiziere.net (Postfix) with ESMTP id 66551B09F for ; Sun, 14 Jul 2013 11:59:54 +0200 (CEST) Date: Sun, 14 Jul 2013 11:59:53 +0200 From: Patrick Lamaiziere To: freebsd-stable@freebsd.org Subject: (9.2) panic under disk load (gam_server / knlist_remove_kq) Message-ID: <20130714115953.1afd6e90@davenulle.org> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 14 Jul 2013 09:59:57 -0000 9.2 PRERELEASE (today) / amd64 Hello, I'm seeing a panic while trying to build a poudriere repository. As far I can see it always happens when gam_server is started (ie xfce is running) and under disk load (poudriere bulk build) : (That is something new, the box was pretty stable) the complete crash dump (core.0.txt) is here: http://user.lamaiziere.net/patrick/panic_gam_server.txt Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 02 fault virtual address = 0x58 fault code = supervisor read data, page not present Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 02 fault virtual address = 0x58 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff808f1bf1 stack pointer = 0x28:0xffffff8108e12a40 frame pointer = 0x28:0xffffff8108e12a70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 23557 (gam_server) trap number = 12 panic: page fault cpuid = 1 ... #0 doadump (textdump=) at pcpu.h:234 234 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:234 #1 0xffffffff8092e4d6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 #2 0xffffffff8092e9d7 in panic (fmt=0x1
) at /usr/src/sys/kern/kern_shutdown.c:637 #3 0xffffffff80d13030 in trap_fatal (frame=0xc, eva=) at /usr/src/sys/amd64/amd64/trap.c:879 #4 0xffffffff80d13391 in trap_pfault (frame=0xffffff8108e12990, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:795 #5 0xffffffff80d13944 in trap (frame=0xffffff8108e12990) at /usr/src/sys/amd64/amd64/trap.c:463 #6 0xffffffff80cfcc73 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:232 #7 0xffffffff808f1bf1 in knlist_remove_kq (knl=0x30, kn=0xfffffe003b70b280, knlislocked=0, kqislocked=0) at /usr/src/sys/kern/kern_event.c:1847 #8 0xffffffff808f4a5b in knote_fdclose (td=0xfffffe0009a34490, fd=9924) at /usr/src/sys/kern/kern_event.c:2065 #9 0xffffffff808ea573 in kern_close (td=0xfffffe0009a34490, fd=9924) at /usr/src/sys/kern/kern_descrip.c:1250 #10 0xffffffff80d127da in amd64_syscall (td=0xfffffe0009a34490, traced=0) at subr_syscall.c:135 #11 0xffffffff80cfcf57 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:391 #12 0x00000008019e9a9c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Thanks, regards From owner-freebsd-stable@FreeBSD.ORG Sun Jul 14 14:33:57 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9AF3C7F4 for ; Sun, 14 Jul 2013 14:33:57 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [94.23.254.147]) by mx1.freebsd.org (Postfix) with ESMTP id 3593F2BC for ; Sun, 14 Jul 2013 14:33:56 +0000 (UTC) Received: from roxette.lamaiziere.net (232.176.97.84.rev.sfr.net [84.97.176.232]) by smtp.lamaiziere.net (Postfix) with ESMTPA id 46A445BA0 for ; Sun, 14 Jul 2013 16:33:55 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by roxette.lamaiziere.net (Postfix) with ESMTP id 8E49FB07C for ; Sun, 14 Jul 2013 16:33:54 +0200 (CEST) Date: Sun, 14 Jul 2013 16:33:53 +0200 From: Patrick Lamaiziere To: freebsd-stable@freebsd.org Subject: Re: (9.2) panic under disk load (gam_server / knlist_remove_kq) Message-ID: <20130714163353.2367a6a4@davenulle.org> In-Reply-To: <20130714115953.1afd6e90@davenulle.org> References: <20130714115953.1afd6e90@davenulle.org> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 14 Jul 2013 14:33:57 -0000 Le Sun, 14 Jul 2013 11:59:53 +0200, Patrick Lamaiziere a écrit : Hello, > 9.2 PRERELEASE (today) / amd64 > > Hello, > > I'm seeing a panic while trying to build a poudriere repository. > > As far I can see it always happens when gam_server is started (ie > xfce is running) and under disk load (poudriere bulk build) : > (That is something new, the box was pretty stable) > > the complete crash dump (core.0.txt) is here: > http://user.lamaiziere.net/patrick/panic_gam_server.txt With WITNESS and ASSERTION on, I see a warning that looks related : Jul 14 16:23:29 roxette kernel: WARNING: destroying knlist w/ knotes on it! and the box panics just after this. Also there are too LOR just before the panic, I don't know it there are related or not : Jul 14 16:23:29 roxette kernel: lock order reversal: Jul 14 16:23:29 roxette kernel: 1st 0xfffffe0013335878 zfs (zfs) @ /usr/src/sys/kern/vfs_mount.c:1240 Jul 14 16:23:29 roxette kernel: 2nd 0xfffffe00495a5488 syncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:2335 Jul 14 16:23:29 roxette kernel: KDB: stack backtrace: Jul 14 16:23:29 roxette kernel: #0 0xffffffff8094bc36 at kdb_backtrace+0x66 Jul 14 16:23:29 roxette kernel: #1 0xffffffff809603be at _witness_debugger+0x2e Jul 14 16:23:29 roxette kernel: #2 0xffffffff80961a95 at witness_checkorder+0x865 Jul 14 16:23:29 roxette kernel: #3 0xffffffff808f8e21 at __lockmgr_args+0x1161 Jul 14 16:23:29 roxette kernel: #4 0xffffffff8099f739 at vop_stdlock+0x39 Jul 14 16:23:29 roxette kernel: #5 0xffffffff80d93593 at VOP_LOCK1_APV+0xe3 Jul 14 16:23:29 roxette kernel: #6 0xffffffff809c0727 at _vn_lock+0x47 Jul 14 16:23:29 roxette kernel: #7 0xffffffff809b42d8 at vputx+0x328 Jul 14 16:23:29 roxette kernel: #8 0xffffffff809a88d4 at dounmount+0x294 Jul 14 16:23:29 roxette kernel: #9 0xffffffff809a914e at sys_unmount+0x3ce Jul 14 16:23:29 roxette kernel: #10 0xffffffff80cec439 at amd64_syscall+0x2f9 Jul 14 16:23:29 roxette kernel: #11 0xffffffff80cd6d57 at Xfast_syscall+0xf7 Jul 14 16:23:29 roxette kernel: lock order reversal: Jul 14 16:23:29 roxette kernel: 1st 0xfffffe006e1eac68 ufs (ufs) @ /usr/src/sys/modules/nullfs/../../fs/nullfs/null_vnops.c:620 Jul 14 16:23:29 roxette kernel: 2nd 0xffffffff813ebda0 allproc (allproc) @ /usr/src/sys/kern/kern_descrip.c:2822 Jul 14 16:23:29 roxette kernel: KDB: stack backtrace: Jul 14 16:23:29 roxette kernel: #0 0xffffffff8094bc36 at kdb_backtrace+0x66 Jul 14 16:23:29 roxette kernel: #1 0xffffffff809603be at _witness_debugger+0x2e Jul 14 16:23:29 roxette kernel: #2 0xffffffff80961a95 at witness_checkorder+0x865 Jul 14 16:23:29 roxette kernel: #3 0xffffffff8091b1fa at _sx_slock+0x5a Jul 14 16:23:29 roxette kernel: #4 0xffffffff808d30ff at mountcheckdirs+0x3f Jul 14 16:23:29 roxette kernel: #5 0xffffffff809a891f at dounmount+0x2df Jul 14 16:23:29 roxette kernel: #6 0xffffffff809a914e at sys_unmount+0x3ce Jul 14 16:23:29 roxette kernel: #7 0xffffffff80cec439 at amd64_syscall+0x2f9 Jul 14 16:23:29 roxette kernel: #8 0xffffffff80cd6d57 at Xfast_syscall+0xf7 Jul 14 16:23:29 roxette kernel: WARNING: destroying knlist w/ knotes on it! Thanks, regards From owner-freebsd-stable@FreeBSD.ORG Sun Jul 14 15:01:39 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9D001C76 for ; Sun, 14 Jul 2013 15:01:39 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 65FBD385 for ; Sun, 14 Jul 2013 15:01:39 +0000 (UTC) Received: by mail-vc0-f175.google.com with SMTP id hr11so8579298vcb.6 for ; Sun, 14 Jul 2013 08:01:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=I5kJy21mDXK9tZhO0DoPNl/CIlVyTUdTfYfpLFJSJXY=; b=kt0gJAQ03sl8+dMGrJG24r4ZytFxyjWoGuwRo51P6YLFIm+utHb9W3JRk9nmPtDiHu QEVdso2fxToNXLr4rqGUVhtZKUM2Sls4o81ESYJw3gjrmdqFlLfBuTdVE/A5O4hzJ08Y WzH12agnTTA5du49G67IebJNiTOoaLiP8lKVHJpjxrTimhlUiYA4lb/u17FJfWe62YmW wKNPQY/SKAsEV+maYHR6U1MD9an3kwL76fKt1yDzPwMoPRj196t9TELYvUS2WyfHzjSq yA7yqIBnuhoXSs0haWvh+/Dd/GtJMuarcmUy6CyshauPfDaW22F6eSXmfkHMF9gbw1Jl PLFw== MIME-Version: 1.0 X-Received: by 10.220.20.3 with SMTP id d3mr27620883vcb.55.1373814098732; Sun, 14 Jul 2013 08:01:38 -0700 (PDT) Received: by 10.220.92.196 with HTTP; Sun, 14 Jul 2013 08:01:38 -0700 (PDT) Date: Sun, 14 Jul 2013 17:01:38 +0200 Message-ID: Subject: Is ATH_ENABLE_11N supposed to work on 9-stable? From: Thomas Zander To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 14 Jul 2013 15:01:39 -0000 Hi, from the mailing lists I couldn't figure out whether 11n is supposed to work on stable since the existing mail threads seem to focus on current exclusively. And since the option exists in the stable kernel code as well, albeit neither in GENERIC nor in NOTES, I thought I could give it a try anyway. I had some partial success. Test in station mode, WPA2 associated properly, light traffic (browsing the web) seems to work okay as well. However as soon as I try to really push some data through it, e.g. rsync large files, the card drops all network traffic until I disassociate and re-associate with the access point again (e.g. netif restart). If 11N is just not ready in -stable yet, it's not a problem, but if it's supposed to work, I'd begin to collect debugging information. So, is it supposed to work on a 9-stable as of today? Best regards Riggs From owner-freebsd-stable@FreeBSD.ORG Sun Jul 14 16:41:06 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7B3B3181 for ; Sun, 14 Jul 2013 16:41:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by mx1.freebsd.org (Postfix) with ESMTP id 1759189C for ; Sun, 14 Jul 2013 16:41:05 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id ey16so2109041wid.16 for ; Sun, 14 Jul 2013 09:41:04 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=3wcwjr9msRs6YGKQ0QfQUC9AqZVmS8DVOhrHLk2Z+IM=; b=dEENtoAIvMyNqYN8kK8sDQ4qD+u3NxlMVuoSAFBXtGbQC6DhMTGxm+spmngGIAM+Qg nguweZtMa5lc5wP/XAACjjvLRiuNujuOFFNd7at5m7uZ2526CwSMfei2ZXVPeikkWBE2 BoHT09GXKDNVOqDW7HRFHQ2NSNJ+0f764F1d6/hFmhrOZUIkGZcqSKOSPUr818xYUPMp Im27uHjfaRXXg1665gMW2cEE+x8F7HxiLqM68urt+ADFimy9eW7AI0EpE4oYVF24EbPA 4GxF6zI/5uKbNPtsg4CFKxo7GJeddZy6EkeMEIwpDc4LRJpftJLKHNA1AA+Bu6hunF6e b0Mg== MIME-Version: 1.0 X-Received: by 10.180.37.133 with SMTP id y5mr6606899wij.30.1373820064746; Sun, 14 Jul 2013 09:41:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Sun, 14 Jul 2013 09:41:04 -0700 (PDT) In-Reply-To: References: Date: Sun, 14 Jul 2013 09:41:04 -0700 X-Google-Sender-Auth: pmBYmMgM2m0N79A_VOJziyQL0qQ Message-ID: Subject: Re: Is ATH_ENABLE_11N supposed to work on 9-stable? From: Adrian Chadd To: Thomas Zander Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 14 Jul 2013 16:41:06 -0000 Nope. It's a -10 thing. -adrian On 14 July 2013 08:01, Thomas Zander wrote: > Hi, > > from the mailing lists I couldn't figure out whether 11n is supposed > to work on stable since the existing mail threads seem to focus on > current exclusively. > > And since the option exists in the stable kernel code as well, albeit > neither in GENERIC nor in NOTES, I thought I could give it a try > anyway. > > I had some partial success. Test in station mode, WPA2 associated > properly, light traffic (browsing the web) seems to work okay as well. > However as soon as I try to really push some data through it, e.g. > rsync large files, the card drops all network traffic until I > disassociate and re-associate with the access point again (e.g. netif > restart). > > If 11N is just not ready in -stable yet, it's not a problem, but if > it's supposed to work, I'd begin to collect debugging information. > > So, is it supposed to work on a 9-stable as of today? > > Best regards > Riggs > _______________________________________________ > 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 Jul 14 17:14:30 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 837218C0 for ; Sun, 14 Jul 2013 17:14:30 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5]) by mx1.freebsd.org (Postfix) with ESMTP id CEF169E6 for ; Sun, 14 Jul 2013 17:14:29 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.7/8.14.7) with ESMTP id r6EHEO52014389 for ; Mon, 15 Jul 2013 00:14:25 +0700 (NOVT) (envelope-from eugen@grosbein.net) Message-ID: <51E2DC6B.2090605@grosbein.net> Date: Mon, 15 Jul 2013 00:14:19 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130415 Thunderbird/17.0.5 MIME-Version: 1.0 To: FreeBSD Stable Subject: script(1), cfmakeraw() and Ctrl-Z Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 14 Jul 2013 17:14:30 -0000 Hi! I've noted that commands like "script -qa /tmp/log sleep 100" cannot be suspended with Ctrl-Z keys. The reason is call to cfmakeraw() in script.c - if I comment it out, Ctrl-Z starts to work as expected. portupgrade uses script(1) so build/install process cannot be suspended too. (I'm building libreoffice-4.04 now) The function cfmakeraw() is used since CVS revision 1.1 when script was imported with other "BSD 4.4 Lite Usr.bin Sources". Is cfmakeraw() really needed? Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Sun Jul 14 20:25:54 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A262573A for ; Sun, 14 Jul 2013 20:25:54 +0000 (UTC) (envelope-from torfinn.ingolfsen@getmail.no) Received: from bouvier.getmail.no (bouvier.getmail.no [84.210.184.8]) by mx1.freebsd.org (Postfix) with ESMTP id 587C229C for ; Sun, 14 Jul 2013 20:25:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id 0010E42729 for ; Sun, 14 Jul 2013 22:19:20 +0200 (CEST) X-Spam-Flag: NO X-Spam-Score: -2.78 X-Spam-Level: X-Spam-Status: No, score=-2.78 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_UNKNOWN_ORIGIN=0.01] autolearn=no Authentication-Results: bouvier.get.c.bitbit.net (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=getmail.no 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 XBFbQ42c3RkJ for ; Sun, 14 Jul 2013 22:19:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by bouvier.getmail.no (Postfix) with ESMTP id A3C2642740 for ; Sun, 14 Jul 2013 22:19:20 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.7.1 bouvier.getmail.no A3C2642740 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=getmail.no; s=8A9C8B4C-D727-11E2-8095-B6466E6B3FA2; t=1373833160; bh=oi+pGMBcHkgGYu9sh3w/DJ9GFUjnyiu2JwYbLDqLdYs=; h=Date:From:To:Subject:Message-Id:Mime-Version:Content-Type: Content-Transfer-Encoding; b=XxJsqaj+lwCZ5TikzF5M3P7xf0HZNOPuUcoF5X/mpgAYFI3WfmRJ56yXAzBtFk2RU AZMEoeTqNULQl6kzVPrvp8ubYBCytucbjuBvOv/NLBuHOZ/5g2t1b+zr8NEbo7S3KA r8lCprNzSO8ClEtBQhF9stAS3jZgF+z3oH5d+w2Q= X-Virus-Scanned: amavisd-new at 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 OvnNmS3VJXLB for ; Sun, 14 Jul 2013 22:19:20 +0200 (CEST) Received: from kg-v2.kg4.no (cm-84.215.180.206.getinternet.no [84.215.180.206]) by bouvier.getmail.no (Postfix) with ESMTPSA id 68C3A42729 for ; Sun, 14 Jul 2013 22:19:20 +0200 (CEST) Date: Sun, 14 Jul 2013 22:19:16 +0200 From: Torfinn Ingolfsen To: freebsd-stable@freebsd.org Subject: There is an error in chmod(1) Message-Id: <20130714221916.fb8d444d23d5f266cde7e04b@getmail.no> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.17; amd64-portbld-freebsd8.3) 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.14 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, 14 Jul 2013 20:25:54 -0000 There is an error in the chmod(1) man page. tingo@kg-v2$ uname -a FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 23:50:55 CEST 2012 root@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 tingo@kg-v2$ apropos ^sticky sticky(7) - sticky text and append-only directories tingo@kg-v2$ man 1 chmod | grep sticky 1000 (the sticky bit). See chmod(2) and sticky(8). t The sticky bit. setmode(3), symlink(7), chown(8), mount(8), sticky(8) HTH -- Torfinn Ingolfsen From owner-freebsd-stable@FreeBSD.ORG Sun Jul 14 20:44:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 07374C0F; Sun, 14 Jul 2013 20:44:28 +0000 (UTC) (envelope-from thomas.e.zander@googlemail.com) Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id AE9DF396; Sun, 14 Jul 2013 20:44:27 +0000 (UTC) Received: by mail-vc0-f170.google.com with SMTP id hf12so8875653vcb.15 for ; Sun, 14 Jul 2013 13:44:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FPIoX2l52V4AgAjHlp/bgELlPFiZ5t7h7hbI/qJyR5Q=; b=wV0FYsUMWGu/cVTodP/H/Gt7IfIIM1ILxbVTEeEaXXUpqcar7xTSo6zoNHwLWvz0Wx 1XFWgiZ2MLHK60IyxcA1x02K6cSQIswRQmZIRzrRZ6aAzFpInjw+6OLjCjh8EzyUmEFu z1YS/U0VdhSzhu/SpPQreEMsLOt1ZoJQjWg5EdgbrRwIy72NfkJHxKftuUwHr5uJLzJU kJCqRhldKNOMW2g6kylOCt3WqvUHYoor/PMt6/rS3NC03edsDYjEuZMBrlCgEI1ThrSX QavZ0GSZnDm2bRTwDyMQP2W9yO74Lr0ttMCmwPHRIlRAl+gFPsesBnvO5KZ9/CrMoFQJ fRwA== MIME-Version: 1.0 X-Received: by 10.52.236.199 with SMTP id uw7mr23685189vdc.18.1373834667214; Sun, 14 Jul 2013 13:44:27 -0700 (PDT) Received: by 10.220.92.196 with HTTP; Sun, 14 Jul 2013 13:44:27 -0700 (PDT) In-Reply-To: References: Date: Sun, 14 Jul 2013 22:44:27 +0200 Message-ID: Subject: Re: Is ATH_ENABLE_11N supposed to work on 9-stable? From: Thomas Zander To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 14 Jul 2013 20:44:28 -0000 On 14 July 2013 18:41, Adrian Chadd wrote: > Nope. It's a -10 thing. Okay, thanks for clarifying. Riggs From owner-freebsd-stable@FreeBSD.ORG Sun Jul 14 21:37:35 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8FE9AA3C for ; Sun, 14 Jul 2013 21:37:35 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id 58246ED for ; Sun, 14 Jul 2013 21:37:35 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id B273C35931A; Sun, 14 Jul 2013 23:37:34 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 9929C28494; Sun, 14 Jul 2013 23:37:34 +0200 (CEST) Date: Sun, 14 Jul 2013 23:37:34 +0200 From: Jilles Tjoelker To: Eugene Grosbein Subject: Re: script(1), cfmakeraw() and Ctrl-Z Message-ID: <20130714213734.GB30708@stack.nl> References: <51E2DC6B.2090605@grosbein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51E2DC6B.2090605@grosbein.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 14 Jul 2013 21:37:35 -0000 On Mon, Jul 15, 2013 at 12:14:19AM +0700, Eugene Grosbein wrote: > I've noted that commands like "script -qa /tmp/log sleep 100" > cannot be suspended with Ctrl-Z keys. The reason is call to cfmakeraw() > in script.c - if I comment it out, Ctrl-Z starts to work as expected. > portupgrade uses script(1) so build/install process cannot be suspended too. > (I'm building libreoffice-4.04 now) > The function cfmakeraw() is used since CVS revision 1.1 when script > was imported with other "BSD 4.4 Lite Usr.bin Sources". > Is cfmakeraw() really needed? The cfmakeraw() call ensures that the processes running within script get all control characters. For example, you can suspend a job in the inner shell using Ctrl+Z. This indeed makes it impossible to suspend script itself. -- Jilles Tjoelker From owner-freebsd-stable@FreeBSD.ORG Sun Jul 14 21:58:59 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 37B75E6E for ; Sun, 14 Jul 2013 21:58:59 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by mx1.freebsd.org (Postfix) with ESMTP id C96C5185 for ; Sun, 14 Jul 2013 21:58:58 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id p58so9400195wes.40 for ; Sun, 14 Jul 2013 14:58:56 -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=3JgZlB42e7/3cAmrwwirgSOLZLx/YFYVB+GNMfbdz7M=; b=WC0zxLjPiX6Zn7qy1vo4lJX56dDz7qVeBIyiSkSTSz43CFj7JMdi5kEyzagRSfke8k bqBZbsJo+WnfZ0ADyNlPhesqcunOyT9mdC+2wVf1wVhvMJf7NLRqMtQmg6UQ0A1X3iGD Y9ckZsUIoIBN+Qgx25K3dWx6TscItqas+Vr6IqA9Noaq5ATc/biPW3zJZ/sG3cd9LFD6 h/cVXDnPPWRvV3uCN7dh2tGiXQh4u+RXDVFOrpZR7okkbg2d0Qm58IFy6GEL8G0Z5MUh aDzv3V9SxzmPPWy/6oSuXiARZYZLMdqHGH8EdKSwI8jQ7WfZ1C8WrogrKzC9HK+7tVpt aM2A== MIME-Version: 1.0 X-Received: by 10.194.87.9 with SMTP id t9mr24713497wjz.39.1373839136568; Sun, 14 Jul 2013 14:58:56 -0700 (PDT) Received: by 10.216.82.70 with HTTP; Sun, 14 Jul 2013 14:58:56 -0700 (PDT) In-Reply-To: <20130714221916.fb8d444d23d5f266cde7e04b@getmail.no> References: <20130714221916.fb8d444d23d5f266cde7e04b@getmail.no> Date: Mon, 15 Jul 2013 01:58:56 +0400 Message-ID: Subject: Re: There is an error in chmod(1) From: Sergey Kandaurov To: Torfinn Ingolfsen Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 14 Jul 2013 21:58:59 -0000 On 15 July 2013 00:19, Torfinn Ingolfsen wrote: > There is an error in the chmod(1) man page. > tingo@kg-v2$ uname -a > FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 23:50:55 CEST 2012 > root@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 > tingo@kg-v2$ apropos ^sticky > sticky(7) - sticky text and append-only directories > tingo@kg-v2$ man 1 chmod | grep sticky > 1000 (the sticky bit). See chmod(2) and sticky(8). > t The sticky bit. > setmode(3), symlink(7), chown(8), mount(8), sticky(8) > This was fixed in head (and appeared in 9.x) but never merged to 8. I just merged the related change to 8-STABLE (the stable/8 branch). Thanks for reporting! -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 04:45:26 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 648E51F2 for ; Mon, 15 Jul 2013 04:45:26 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5]) by mx1.freebsd.org (Postfix) with ESMTP id 16A047F1 for ; Mon, 15 Jul 2013 04:45:24 +0000 (UTC) Received: from eg.sd.rdtc.ru (localhost [127.0.0.1]) by eg.sd.rdtc.ru (8.14.7/8.14.7) with ESMTP id r6F4jLLp021170; Mon, 15 Jul 2013 11:45:21 +0700 (NOVT) (envelope-from eugen@grosbein.net) Message-ID: <51E37E5C.5020301@grosbein.net> Date: Mon, 15 Jul 2013 11:45:16 +0700 From: Eugene Grosbein User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130415 Thunderbird/17.0.5 MIME-Version: 1.0 To: Jilles Tjoelker Subject: Re: script(1), cfmakeraw() and Ctrl-Z References: <51E2DC6B.2090605@grosbein.net> <20130714213734.GB30708@stack.nl> In-Reply-To: <20130714213734.GB30708@stack.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 04:45:26 -0000 On 15.07.2013 04:37, Jilles Tjoelker wrote: > On Mon, Jul 15, 2013 at 12:14:19AM +0700, Eugene Grosbein wrote: >> I've noted that commands like "script -qa /tmp/log sleep 100" >> cannot be suspended with Ctrl-Z keys. The reason is call to cfmakeraw() >> in script.c - if I comment it out, Ctrl-Z starts to work as expected. > >> portupgrade uses script(1) so build/install process cannot be suspended too. >> (I'm building libreoffice-4.04 now) > >> The function cfmakeraw() is used since CVS revision 1.1 when script >> was imported with other "BSD 4.4 Lite Usr.bin Sources". > >> Is cfmakeraw() really needed? > > The cfmakeraw() call ensures that the processes running within script > get all control characters. For example, you can suspend a job in the > inner shell using Ctrl+Z. This indeed makes it impossible to suspend > script itself. Is it possible to achieve same effect of passing other control characters but Ctrl-Z? So, it would be possible suspend long-running portupgrade. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 06:38:46 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EDB28B9A for ; Mon, 15 Jul 2013 06:38:46 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 646A4BC6 for ; Mon, 15 Jul 2013 06:38:46 +0000 (UTC) Received: (qmail 72441 invoked from network); 15 Jul 2013 07:28:39 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 15 Jul 2013 07:28:39 -0000 Message-ID: <51E398F3.40008@freebsd.org> Date: Mon, 15 Jul 2013 08:38:43 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Alfred Perlstein Subject: Re: status of autotuning freebsd for 9.2 References: <51D90B9B.9080209@ixsystems.com> <51D92826.1070707@freebsd.org> <51E1061F.3050804@ixsystems.com> In-Reply-To: <51E1061F.3050804@ixsystems.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, re@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 06:38:47 -0000 On 13.07.2013 09:47, Alfred Perlstein wrote: > Andre, we have a number of people running this patch in the following configurations: > > 6-8GB ram + 10gigE ethernet using iozone over NFS. As you haven't seen any problems yet I've asked RE to green light the MFC. -- Andre > We're rolling it into the PCBSD rolling update as well. I'm thinking it makes sense to roll this > into the 9.2 release to give us more scalability. > > -Alfred > > > On 7/7/13 1:34 AM, Andre Oppermann wrote: >> On 07.07.2013 08:32, Alfred Perlstein wrote: >>> Andre, >>> >>> Are you going to have time to MFC things from -current for auto-tuning -stable before 9.2? >> >> I simply ran out of time on Friday and MFCing such a big change requires >> more testing. >> >>> I fear (maybe unnecessarily?) that we are about to ship yet another release that can't do basic >>> 10gigE when sufficient memory exists. >> >> There was some debate with myself whether such a behavior changing MFC >> would be appropriate for a mid-stream stable release. I guess yes, though >> a number of people who currently set the parameters manually would have >> to remove their tuning settings. >> >>> If you don't have time, then let me know and I'll see what I can do. >> >> Can you help me with with testing? >> > > From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 07:05:10 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A81A5327 for ; Mon, 15 Jul 2013 07:05:10 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 1651CC82 for ; Mon, 15 Jul 2013 07:05:09 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id r6F755hs067896; Mon, 15 Jul 2013 17:05:05 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 15 Jul 2013 17:05:05 +1000 (EST) From: Ian Smith To: Sergey Kandaurov Subject: Re: There is an error in chmod(1) In-Reply-To: Message-ID: <20130715165549.Q12860@sola.nimnet.asn.au> References: <20130714221916.fb8d444d23d5f266cde7e04b@getmail.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org, Torfinn Ingolfsen X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 07:05:10 -0000 On Mon, 15 Jul 2013 01:58:56 +0400, Sergey Kandaurov wrote: > On 15 July 2013 00:19, Torfinn Ingolfsen wrote: > > There is an error in the chmod(1) man page. > > tingo@kg-v2$ uname -a > > FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 23:50:55 CEST 2012 > > root@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 > > tingo@kg-v2$ apropos ^sticky > > sticky(7) - sticky text and append-only directories > > tingo@kg-v2$ man 1 chmod | grep sticky > > 1000 (the sticky bit). See chmod(2) and sticky(8). > > t The sticky bit. > > setmode(3), symlink(7), chown(8), mount(8), sticky(8) > > > > This was fixed in head (and appeared in 9.x) but never merged to 8. > I just merged the related change to 8-STABLE (the stable/8 branch). > Thanks for reporting! At least on 8-STABLE the residual error was only in chmod(1) .. back on 8.2-R - and at least back to 5.5-STABLE - it really was sticky(8) :) cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 07:39:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 50729C78 for ; Mon, 15 Jul 2013 07:39:28 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by mx1.freebsd.org (Postfix) with ESMTP id E074EDC8 for ; Mon, 15 Jul 2013 07:39:27 +0000 (UTC) Received: by mail-we0-f179.google.com with SMTP id w59so9926965wes.10 for ; Mon, 15 Jul 2013 00:39:27 -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=VvJEWT/9HO9bgaET1gihW/YodzxuNXG8veoE/jkaKpU=; b=asgIxb3tNJEjZO3h/S5cKBdMhjmg1AbMzb0GRgQEKztsrwIEZdgEjpntuQix14hhMl n6Fp308o+RujwVxdTuonSyktWPR3Y9+rj4rPAT/gSHJ/SFqBElK/oLZxWDcE8G7a6O3D hHtPLj1kMmztk6PMWs+o/pAC1/SGzqUYKEwg1Q5bMdjyyjAw/gr1VNPGhgs6GxclRiSJ nIKSmP+8Md9Ln9gY7v13g32k6B4K40vVihyRTi8XE8P4ovb8ncuXYCaSneweh8ufoyHJ p7iA+9SPvoMutkQwcitopJlV+VoajeptqROVHri2cXER7fd62uZ2LeoIIcLteJn2zN6c MtOw== MIME-Version: 1.0 X-Received: by 10.194.87.9 with SMTP id t9mr25761266wjz.39.1373873966963; Mon, 15 Jul 2013 00:39:26 -0700 (PDT) Received: by 10.216.82.70 with HTTP; Mon, 15 Jul 2013 00:39:26 -0700 (PDT) In-Reply-To: <20130715165549.Q12860@sola.nimnet.asn.au> References: <20130714221916.fb8d444d23d5f266cde7e04b@getmail.no> <20130715165549.Q12860@sola.nimnet.asn.au> Date: Mon, 15 Jul 2013 11:39:26 +0400 Message-ID: Subject: Re: There is an error in chmod(1) From: Sergey Kandaurov To: Ian Smith Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, Torfinn Ingolfsen X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 07:39:28 -0000 On 15 July 2013 11:05, Ian Smith wrote: > On Mon, 15 Jul 2013 01:58:56 +0400, Sergey Kandaurov wrote: > > On 15 July 2013 00:19, Torfinn Ingolfsen wrote: > > > There is an error in the chmod(1) man page. > > > tingo@kg-v2$ uname -a > > > FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 23:50:55 CEST 2012 > > > root@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 > > > tingo@kg-v2$ apropos ^sticky > > > sticky(7) - sticky text and append-only directories > > > tingo@kg-v2$ man 1 chmod | grep sticky > > > 1000 (the sticky bit). See chmod(2) and sticky(8). > > > t The sticky bit. > > > setmode(3), symlink(7), chown(8), mount(8), sticky(8) > > > > > > > This was fixed in head (and appeared in 9.x) but never merged to 8. > > I just merged the related change to 8-STABLE (the stable/8 branch). > > Thanks for reporting! > > At least on 8-STABLE the residual error was only in chmod(1) .. back on > 8.2-R - and at least back to 5.5-STABLE - it really was sticky(8) :) Yep. It was once moved to sticky(7) to match NetBSD and common sense. -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 10:02:35 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B56864B1 for ; Mon, 15 Jul 2013 10:02:35 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-bk0-x22c.google.com (mail-bk0-x22c.google.com [IPv6:2a00:1450:4008:c01::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 4CA93CB8 for ; Mon, 15 Jul 2013 10:02:35 +0000 (UTC) Received: by mail-bk0-f44.google.com with SMTP id 6so4586350bkj.31 for ; Mon, 15 Jul 2013 03:02:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=FMt5L3DxFtO7MU7tGMhetL03ADjH1/VzyB0DGUlYJOw=; b=g5qt7DwOZIg049PXvXsskQki565mWKvCRo+ScPREmoSP7ihUMh4cO8eMQwIbU7lkge 7t+SehvOJOKnX8mqp2VsA2GGbK2GT99IiquHDCS2qB3RgI57EhqC6FC6DVsFj0AN9zE6 E8G9eI3AqMnJHmbpmRN4cA+4h3OWjTTDV/H+7zgwHVDT2sTJvXULipReehS50mE6pc/o 89kNQkYMfoaEMDEqA0sdfBbHbOElaOwOd6vTR9Bey40g04869stdOPJdByI7C8qVgOHK 2SiJbDhIfYaQAlWSJZj4GblcbScy5HMa3vnFcMyEsB6WZjnGQN02jeiBVRDPqx3IHDIm BsSA== X-Received: by 10.205.113.205 with SMTP id ex13mr7674861bkc.104.1373882554443; Mon, 15 Jul 2013 03:02:34 -0700 (PDT) Received: from [192.168.1.129] (schavemaker.nl. [213.84.84.186]) by mx.google.com with ESMTPSA id qw6sm11874646bkb.4.2013.07.15.03.02.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Jul 2013 03:02:33 -0700 (PDT) Message-ID: <51E3C8B7.7000801@gmail.com> Date: Mon, 15 Jul 2013 12:02:31 +0200 From: Johan Hendriks User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable Subject: Supermicro and FreeBSD 9.2 PRERELEASE make_dev_physpath_alias: WARNING 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.14 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, 15 Jul 2013 10:02:35 -0000 We use basic supermicro cases for our storage servers in combination with a LSI 9211-8i controller in IT mode. Since 9.1 or shortly there after we get for every disk we attach to the SAS backplane the following error. make_dev_physpath_alias: WARNING - Unable to alias gptid/abb586f5-da8d-11e2-aaaf-00259061b51a to enc@n500304800122877d/type@0/slot@f/elmdesc@Slot_15/gptid/abb586f5-da8d-11e2-aaaf-00259061b51a - path too long. I know it does not harm the operation, but every time the server boots or when we add a disk i get a little scared when i see WRNINGS passing by. Is there a way to supress these WARNINGS, or is there something i can do about it. I know on 9.0 i do not get these messages.! gr Johan Hendriks From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 11:06:51 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4F3E9F81 for ; Mon, 15 Jul 2013 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 29E2FFD2 for ; Mon, 15 Jul 2013 11:06:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6FB6p2i084593 for ; Mon, 15 Jul 2013 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6FB6oDn084591 for freebsd-stable@FreeBSD.org; Mon, 15 Jul 2013 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Jul 2013 11:06:50 GMT Message-Id: <201307151106.r6FB6oDn084591@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-stable@FreeBSD.org Subject: Current problem reports assigned to freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 11:06:51 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 11:10:06 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 807CB9B1; Mon, 15 Jul 2013 11:10:06 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by mx1.freebsd.org (Postfix) with ESMTP id ED8C01E9; Mon, 15 Jul 2013 11:10:05 +0000 (UTC) Received: by mail-wg0-f46.google.com with SMTP id c11so9870304wgh.1 for ; Mon, 15 Jul 2013 04:10: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=9BZuoZ1dKmGdXlDtrOH0A8oFT40Pv6bjS1FA41GPjyM=; b=sH3OUBRO6UueGwj03ULa7qwt8QNOTscgFPfvsrJUWyZspVShRLUYKz8OXxQV/jSu9G xU7kih5AZp/m/AXLe/qz4rqFoy4i0da490BPRI8S8GcWZ+AbY6zHvw/M/iAu8lvUFREj hEBBs+DhGzPW3oTXg7uUtHZqKS+kbtVjzfnJ0en3J8zJV1XDWnmw5raVGUVdhqc7+uHh oYCgkj4gYtlnrSI1gcPPNdLVC15jef+mUmdiz+hQcDAztmyM67P32xwRJ7LcsazDvqkB x0HBt21JmSFLyZsM4aqB+g/VfmCsE8s+QMUTi4r5SXRuFmjace0oxoIpKkkdHz4qSvmD rkfA== MIME-Version: 1.0 X-Received: by 10.194.87.9 with SMTP id t9mr26366828wjz.39.1373886604876; Mon, 15 Jul 2013 04:10:04 -0700 (PDT) Received: by 10.216.82.70 with HTTP; Mon, 15 Jul 2013 04:10:04 -0700 (PDT) In-Reply-To: <51E3C8B7.7000801@gmail.com> References: <51E3C8B7.7000801@gmail.com> Date: Mon, 15 Jul 2013 15:10:04 +0400 Message-ID: Subject: Re: Supermicro and FreeBSD 9.2 PRERELEASE make_dev_physpath_alias: WARNING From: Sergey Kandaurov To: Johan Hendriks Content-Type: text/plain; charset=ISO-8859-1 Cc: Alexander Motin , freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 11:10:06 -0000 On 15 July 2013 14:02, Johan Hendriks wrote: > We use basic supermicro cases for our storage servers in combination with a > LSI 9211-8i controller in IT mode. > > Since 9.1 or shortly there after we get for every disk we attach to the SAS > backplane the following error. > > make_dev_physpath_alias: WARNING - Unable to alias > gptid/abb586f5-da8d-11e2-aaaf-00259061b51a to > enc@n500304800122877d/type@0/slot@f/elmdesc@Slot_15/gptid/abb586f5-da8d-11e2-aaaf-00259061b51a > - path too long. > > I know it does not harm the operation, but every time the server boots or > when we add a disk i get a little scared when i see WRNINGS passing by. > > Is there a way to supress these WARNINGS, or is there something i can do > about it. This is because the name is longer than SPECNAMELEN. You barely can do anything with it. The warning is hidden under bootverbose in 10-CURRENT, and I think it should be merged to stable/9 before 9.2 release. Meantime you can manually apply this change: http://svnweb.freebsd.org/changeset/base/235899 > I know on 9.0 i do not get these messages.! That's odd. AFAIK the feature had appeared in 9.0. -- wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 11:34:11 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A12D1D2E for ; Mon, 15 Jul 2013 11:34:11 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 29306313 for ; Mon, 15 Jul 2013 11:34:10 +0000 (UTC) Received: by mail-lb0-f173.google.com with SMTP id v1so9301640lbd.4 for ; Mon, 15 Jul 2013 04:34:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=mxTm7j7UtOBiQghl7fG4zSC0BJZucLrVH8bAK6CA1kU=; b=k/S3m3/GOMazL0NmUEgJqM+dBmD2Ehqd/e9PMv12vWbkjCjUZGCZ1KsIGFULZIYgif v7+tu6vRV5FYgztXEpdDj58pZBY3EAPEWafN6AvldKsW+35dHaXj7F/1SoqQPGkvSKtn htyeUyf7aO6/Amd3H+pLmb2qq0r4g/gK0t1mhFAwjsinZ8Up0MsQ7lClHre3114xoqC4 evsR9GIS4csrf4otYAX991BUjK8oMgits4K0R3NdBnbUym2yxkh5yycRQeN5Cb4WLtHX zZVmsgGYGHxqhzlHnMwwj+yYYFwDDS6fmbRHto8mYKwSFyPvdeD0fDKlkJjg0Jj17IG1 ygcQ== X-Received: by 10.152.28.199 with SMTP id d7mr24621495lah.67.1373888049833; Mon, 15 Jul 2013 04:34:09 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPSA id et10sm18277307lbc.6.2013.07.15.04.34.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Jul 2013 04:34:08 -0700 (PDT) Sender: Alexander Motin Message-ID: <51E3DE2D.80908@FreeBSD.org> Date: Mon, 15 Jul 2013 14:34:05 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130616 Thunderbird/17.0.6 MIME-Version: 1.0 To: Sergey Kandaurov Subject: Re: Supermicro and FreeBSD 9.2 PRERELEASE make_dev_physpath_alias: WARNING References: <51E3C8B7.7000801@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Johan Hendriks , freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 11:34:11 -0000 On 15.07.2013 14:10, Sergey Kandaurov wrote: > On 15 July 2013 14:02, Johan Hendriks wrote: >> We use basic supermicro cases for our storage servers in combination with a >> LSI 9211-8i controller in IT mode. >> >> Since 9.1 or shortly there after we get for every disk we attach to the SAS >> backplane the following error. >> >> make_dev_physpath_alias: WARNING - Unable to alias >> gptid/abb586f5-da8d-11e2-aaaf-00259061b51a to >> enc@n500304800122877d/type@0/slot@f/elmdesc@Slot_15/gptid/abb586f5-da8d-11e2-aaaf-00259061b51a >> - path too long. >> >> I know it does not harm the operation, but every time the server boots or >> when we add a disk i get a little scared when i see WRNINGS passing by. >> >> Is there a way to supress these WARNINGS, or is there something i can do >> about it. > > This is because the name is longer than SPECNAMELEN. > You barely can do anything with it. The warning is hidden under bootverbose > in 10-CURRENT, and I think it should be merged to stable/9 before 9.2 release. > Meantime you can manually apply this change: > > http://svnweb.freebsd.org/changeset/base/235899 Thank you for the reminder, sent MFC request. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 12:44:33 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7FD80BCF for ; Mon, 15 Jul 2013 12:44:33 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 2106887F for ; Mon, 15 Jul 2013 12:44:32 +0000 (UTC) Received: (qmail 74158 invoked from network); 15 Jul 2013 13:34:23 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 15 Jul 2013 13:34:23 -0000 Message-ID: <51E3EEAA.3040106@freebsd.org> Date: Mon, 15 Jul 2013 14:44:26 +0200 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Alfred Perlstein Subject: Re: status of autotuning freebsd for 9.2 References: <51D90B9B.9080209@ixsystems.com> <51D92826.1070707@freebsd.org> <51E1061F.3050804@ixsystems.com> <51E398F3.40008@freebsd.org> In-Reply-To: <51E398F3.40008@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, re@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 12:44:33 -0000 On 15.07.2013 08:38, Andre Oppermann wrote: > On 13.07.2013 09:47, Alfred Perlstein wrote: >> Andre, we have a number of people running this patch in the following configurations: >> >> 6-8GB ram + 10gigE ethernet using iozone over NFS. > > As you haven't seen any problems yet I've asked RE to green light > the MFC. RE has rejected the MFC out of fears for unexpected regressions. -- Andre From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 12:48:41 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C8DF5D20; Mon, 15 Jul 2013 12:48:41 +0000 (UTC) (envelope-from alfred@ixsystems.com) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) by mx1.freebsd.org (Postfix) with ESMTP id B00B28B2; Mon, 15 Jul 2013 12:48:41 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id 47B3E6811C; Mon, 15 Jul 2013 05:48:41 -0700 (PDT) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 14947-04; Mon, 15 Jul 2013 05:48:41 -0700 (PDT) Received: from Alfreds-MacBook-Pro-9.local (c-67-180-208-218.hsd1.ca.comcast.net [67.180.208.218]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id CBD2A68117; Mon, 15 Jul 2013 05:48:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ixsystems.com; s=newknight0; t=1373892521; bh=idSKgPkfUDZhRcW+9g7cEJQB5Tr6hxRf0MEoZiru0oc=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=fPTdW8e5S9WbTaIKMDmB+UMCfnKcB6h4mzoj24/pf/71+MnBWLsIKo84eaH39cnkc 90iZZg5WyRhxEdrOkUoX7MakK1MxPo2VV5zd48GcBTbIslEs/keLme5pCYXmpqq2zx vVVxf0mIX5tp7qrNP6j6Ppx//usrcvPjVQmV/3XE= Message-ID: <51E3EFA8.1050606@ixsystems.com> Date: Mon, 15 Jul 2013 05:48:40 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Andre Oppermann Subject: Re: status of autotuning freebsd for 9.2 References: <51D90B9B.9080209@ixsystems.com> <51D92826.1070707@freebsd.org> <51E1061F.3050804@ixsystems.com> <51E398F3.40008@freebsd.org> <51E3EEAA.3040106@freebsd.org> In-Reply-To: <51E3EEAA.3040106@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, re@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 12:48:41 -0000 On 7/15/13 5:44 AM, Andre Oppermann wrote: > On 15.07.2013 08:38, Andre Oppermann wrote: >> On 13.07.2013 09:47, Alfred Perlstein wrote: >>> Andre, we have a number of people running this patch in the >>> following configurations: >>> >>> 6-8GB ram + 10gigE ethernet using iozone over NFS. >> >> As you haven't seen any problems yet I've asked RE to green light >> the MFC. > > RE has rejected the MFC out of fears for unexpected regressions. > That is unfortunate. I guess re@ doesn't understand that FreeBSD 9.2 will be unusable out of the box for doing 10gigE for more than a few microseconds. Can we not just do my original patch that has the check for 64bit pointers before unscaling maxusers? That would be dirt simple and just work with minimal risk. -- Alfred Perlstein VP Software Engineering, iXsystems From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 14:13:04 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E427643B; Mon, 15 Jul 2013 14:13:04 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) by mx1.freebsd.org (Postfix) with ESMTP id BCC2DCC4; Mon, 15 Jul 2013 14:13:04 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:120e:1:1:c57c:729]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id CE5B68C77; Mon, 15 Jul 2013 14:13:02 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us CE5B68C77 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 15 Jul 2013 10:13:00 -0400 From: Glen Barber To: Alfred Perlstein Subject: Re: status of autotuning freebsd for 9.2 Message-ID: <20130715141300.GA1986@glenbarber.us> References: <51D90B9B.9080209@ixsystems.com> <51D92826.1070707@freebsd.org> <51E1061F.3050804@ixsystems.com> <51E398F3.40008@freebsd.org> <51E3EEAA.3040106@freebsd.org> <51E3EFA8.1050606@ixsystems.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <51E3EFA8.1050606@ixsystems.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: re@freebsd.org, stable@freebsd.org, Andre Oppermann X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 14:13:05 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 15, 2013 at 05:48:40AM -0700, Alfred Perlstein wrote: > On 7/15/13 5:44 AM, Andre Oppermann wrote: > >On 15.07.2013 08:38, Andre Oppermann wrote: > >>On 13.07.2013 09:47, Alfred Perlstein wrote: > >>>Andre, we have a number of people running this patch in the > >>>following configurations: > >>> > >>>6-8GB ram + 10gigE ethernet using iozone over NFS. > >> > >>As you haven't seen any problems yet I've asked RE to green light > >>the MFC. > > > >RE has rejected the MFC out of fears for unexpected regressions. > > >=20 > That is unfortunate. I guess re@ doesn't understand that FreeBSD > 9.2 will be unusable out of the box for doing 10gigE for more than a > few microseconds. >=20 > Can we not just do my original patch that has the check for 64bit > pointers before unscaling maxusers? That would be dirt simple and > just work with minimal risk. >=20 IMHO, this is considered a new feature, and not a critical bug fix. re@ asked from the start of the code slush to avoid new features, and at this point, it is too late. It is not worth introducing possible regressions, which will only delay the 9.2-RELEASE. Glen --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJR5ANsAAoJEFJPDDeguUajOxYIAJUFkAiKl7sIhoDkg2cWiZ+y 0cMSEOpGtrMnG6BBVcHe48fQgmPHfWXK7C9lB/6s34dIh3aGGacJ/RbcmV7FF95g 0gBiIRxh7srCqZi8Yjo5M0qZtdUkHLH5jlH6SMIfBV0WfX6t5NgUFgZCMGypJ0bg 628AP5LtRpoPkXQ1Xv2f0DZjrVNHY2kTYG+8AKZ0Mk2ul5bReHOwUSEyGOk/iqGN FgOzpo3u9+WoigX53WV5AsQ9567F1lo9ImHXw4bvp549SA2W0cYJZF1ww+snVxxr S3MVS2eu+RbXJ4iY8HIZC4IPo/Aa8PfPsTXdB1Yv3pWgGVbkTzUoH3/t5XbCdME= =YFyv -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 14:16:57 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E7D286F9; Mon, 15 Jul 2013 14:16:57 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by mx1.freebsd.org (Postfix) with ESMTP id 8F1C6D1F; Mon, 15 Jul 2013 14:16:57 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id i4so15436641oah.38 for ; Mon, 15 Jul 2013 07:16:57 -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=OyLeYY4lNUUHgDcIcmRpKfKgVdUpoa9IL31846Qh2xk=; b=tZAceOkF3XqI2u6mbFVSPBLFSvBU3Foy4gQBD//JpnUS31oP/x8nCPmuBfbbRc0sdg TYazE7xi12sOdnql9zshwQSoM1FaB1BkyasZId4QvuTfc6QN+0h/ftCOavmZL9GzuCNS IzrTNgWL2dnGLH533dFUzQ1lEfcm4TxJzMJ+Hl8bpyFH9GtfrKZr1W+oR9nrgaYIh+t3 vSYea5Iml2dt6JDp1sTe8eBAwmOIZQA+k+7thWzezU8J6iiSP34buhdmb5L5lFAO222W TsTjdzx/l64mS2jEouGaPwyOq1hUI9OTd9sR/5rupsYUKYkcHV3v7E4FCi4zWtMil2dh ZM/g== MIME-Version: 1.0 X-Received: by 10.182.50.200 with SMTP id e8mr44189007obo.35.1373897817075; Mon, 15 Jul 2013 07:16:57 -0700 (PDT) Received: by 10.76.90.197 with HTTP; Mon, 15 Jul 2013 07:16:56 -0700 (PDT) In-Reply-To: <20130715141300.GA1986@glenbarber.us> References: <51D90B9B.9080209@ixsystems.com> <51D92826.1070707@freebsd.org> <51E1061F.3050804@ixsystems.com> <51E398F3.40008@freebsd.org> <51E3EEAA.3040106@freebsd.org> <51E3EFA8.1050606@ixsystems.com> <20130715141300.GA1986@glenbarber.us> Date: Mon, 15 Jul 2013 10:16:56 -0400 Message-ID: Subject: Re: status of autotuning freebsd for 9.2 From: Outback Dingo To: Glen Barber Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Andre Oppermann , stable@freebsd.org, re@freebsd.org, Alfred Perlstein X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 14:16:58 -0000 On Mon, Jul 15, 2013 at 10:13 AM, Glen Barber wrote: > On Mon, Jul 15, 2013 at 05:48:40AM -0700, Alfred Perlstein wrote: > > On 7/15/13 5:44 AM, Andre Oppermann wrote: > > >On 15.07.2013 08:38, Andre Oppermann wrote: > > >>On 13.07.2013 09:47, Alfred Perlstein wrote: > > >>>Andre, we have a number of people running this patch in the > > >>>following configurations: > > >>> > > >>>6-8GB ram + 10gigE ethernet using iozone over NFS. > > >> > > >>As you haven't seen any problems yet I've asked RE to green light > > >>the MFC. > > > > > >RE has rejected the MFC out of fears for unexpected regressions. > > > > > > > That is unfortunate. I guess re@ doesn't understand that FreeBSD > > 9.2 will be unusable out of the box for doing 10gigE for more than a > > few microseconds. > > > > Can we not just do my original patch that has the check for 64bit > > pointers before unscaling maxusers? That would be dirt simple and > > just work with minimal risk. > > > > IMHO, this is considered a new feature, and not a critical bug fix. re@ > asked from the start of the code slush to avoid new features, and at > this point, it is too late. It is not worth introducing possible > regressions, which will only delay the 9.2-RELEASE. > Its kinda sad that it wount be MFC'd though I understand, it does help 10Gbe environments Id give it a vote, and its perceived to have possible regressions, though it might need more testing other then a handful of users..... we can always patch........ until its MFCd > > Glen > > From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 14:26:54 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AD76AAFE for ; Mon, 15 Jul 2013 14:26:54 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 46A59DD6 for ; Mon, 15 Jul 2013 14:26:54 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id l18so10066047wgh.26 for ; Mon, 15 Jul 2013 07:26:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=c1Im6WUA8R2KdwqxR6fsGWHgbDd797JclhGXYdXIcgc=; b=nogOq7NepbTrzSg8dq/NiR7G1ccRrFViJMRbnHvxOG+g1moYLNtr16p4ZsW5oXNIMK fvyqIsJqFLxzwStTO/2IGIpZ/r4Qyf7p6tTQlpccQMj7L3DtAjm/QHGTIa1Jp3LWyRPg eo6eI8xxlezSFj2+pbvpkUnBBReI8RrxclmLHY2q4Zl627npL8bkqQzUQnhyCtxh7Qiu RfNK92H6FARxu2n9ejEoNrk59lDQqL/6MKycqtm3VXsYNN6i9FH9ocu7Ov4p0DL32y6l DGVADrozNaxtetyk7+79t6u5hlEvNV3OMuKdb2NsrbQrg2JwucpUT6GzO1S9B5VzQFvf lvvg== X-Received: by 10.180.75.80 with SMTP id a16mr9246984wiw.3.1373898413493; Mon, 15 Jul 2013 07:26:53 -0700 (PDT) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by mx.google.com with ESMTPSA id b14sm21275131wic.8.2013.07.15.07.26.51 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 15 Jul 2013 07:26:52 -0700 (PDT) Date: Mon, 15 Jul 2013 16:26:47 +0200 From: Mateusz Guzik To: Patrick Lamaiziere Subject: Re: (9.2) panic under disk load (gam_server / knlist_remove_kq) Message-ID: <20130715142647.GA9293@dft-labs.eu> References: <20130714115953.1afd6e90@davenulle.org> <20130714163353.2367a6a4@davenulle.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20130714163353.2367a6a4@davenulle.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 14:26:54 -0000 On Sun, Jul 14, 2013 at 04:33:53PM +0200, Patrick Lamaiziere wrote: > Le Sun, 14 Jul 2013 11:59:53 +0200, > Patrick Lamaiziere a écrit : > > Hello, > > > 9.2 PRERELEASE (today) / amd64 > > > > Hello, > > > > I'm seeing a panic while trying to build a poudriere repository. > > > > As far I can see it always happens when gam_server is started (ie > > xfce is running) and under disk load (poudriere bulk build) : > > (That is something new, the box was pretty stable) > > > > the complete crash dump (core.0.txt) is here: > > http://user.lamaiziere.net/patrick/panic_gam_server.txt > > With WITNESS and ASSERTION on, I see a warning that looks related : > > Jul 14 16:23:29 roxette kernel: WARNING: destroying knlist w/ knotes on it! > > and the box panics just after this. > can you switch that printf to a panic and paste backtrace? -- Mateusz Guzik From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 15:24:10 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8D540C71; Mon, 15 Jul 2013 15:24:10 +0000 (UTC) (envelope-from alfred@ixsystems.com) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) by mx1.freebsd.org (Postfix) with ESMTP id 70D842F2; Mon, 15 Jul 2013 15:24:10 +0000 (UTC) Received: from localhost (mail.ixsystems.com [10.2.55.1]) by mail.iXsystems.com (Postfix) with ESMTP id 403CD66CB0; Mon, 15 Jul 2013 08:24:10 -0700 (PDT) Received: from mail.iXsystems.com ([10.2.55.1]) by localhost (mail.ixsystems.com [10.2.55.1]) (maiad, port 10024) with ESMTP id 35653-09; Mon, 15 Jul 2013 08:24:10 -0700 (PDT) Received: from Alfreds-MacBook-Pro-9.local (c-67-180-208-218.hsd1.ca.comcast.net [67.180.208.218]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id C3D0E66CAA; Mon, 15 Jul 2013 08:24:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ixsystems.com; s=newknight0; t=1373901849; bh=lm1xqMslw/vkqtOWWn8bNFmy27CaLFWBhKmQIk/jk7A=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=R6GpuCapTQ7CnVlG0dNHthX55IJuI8jHdsVMQiCjIM8dxlz5bw0U9OIr4s7KwYv4b QEO5FzMfwqQ2hqySxGpW9/A8LaUlLrgG2N8kFT0wHcWDUiM9G4n7pqg/bfd32rZHCk 8Zl9XGEprif/Pc/53eJAHYRF5P8KSx2lHHhwWGD0= Message-ID: <51E41419.3040503@ixsystems.com> Date: Mon, 15 Jul 2013 08:24:09 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Glen Barber Subject: Re: status of autotuning freebsd for 9.2 References: <51D90B9B.9080209@ixsystems.com> <51D92826.1070707@freebsd.org> <51E1061F.3050804@ixsystems.com> <51E398F3.40008@freebsd.org> <51E3EEAA.3040106@freebsd.org> <51E3EFA8.1050606@ixsystems.com> <20130715141300.GA1986@glenbarber.us> In-Reply-To: <20130715141300.GA1986@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andre Oppermann , stable@freebsd.org, re@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 15:24:10 -0000 On 7/15/13 7:13 AM, Glen Barber wrote: > On Mon, Jul 15, 2013 at 05:48:40AM -0700, Alfred Perlstein wrote: >> On 7/15/13 5:44 AM, Andre Oppermann wrote: >>> On 15.07.2013 08:38, Andre Oppermann wrote: >>>> On 13.07.2013 09:47, Alfred Perlstein wrote: >>>>> Andre, we have a number of people running this patch in the >>>>> following configurations: >>>>> >>>>> 6-8GB ram + 10gigE ethernet using iozone over NFS. >>>> As you haven't seen any problems yet I've asked RE to green light >>>> the MFC. >>> RE has rejected the MFC out of fears for unexpected regressions. >>> >> That is unfortunate. I guess re@ doesn't understand that FreeBSD >> 9.2 will be unusable out of the box for doing 10gigE for more than a >> few microseconds. >> >> Can we not just do my original patch that has the check for 64bit >> pointers before unscaling maxusers? That would be dirt simple and >> just work with minimal risk. >> > IMHO, this is considered a new feature, and not a critical bug fix. re@ > asked from the start of the code slush to avoid new features, and at > this point, it is too late. It is not worth introducing possible > regressions, which will only delay the 9.2-RELEASE. > > Glen > OK, then we need a release notes telling people a sane value for nmbclusters and friends so that they know how to make 10gigE work. I'll poll my team for a value if someone else has one, that would be even better. -- Alfred Perlstein VP Software Engineering, iXsystems From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 16:50:18 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D2DED192 for ; Mon, 15 Jul 2013 16:50:18 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [94.23.254.147]) by mx1.freebsd.org (Postfix) with ESMTP id 6DE13A80 for ; Mon, 15 Jul 2013 16:50:18 +0000 (UTC) Received: from roxette.lamaiziere.net (232.176.97.84.rev.sfr.net [84.97.176.232]) by smtp.lamaiziere.net (Postfix) with ESMTPA id D1EF25DC8; Mon, 15 Jul 2013 18:50:10 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by roxette.lamaiziere.net (Postfix) with ESMTP id 4D568B0B5; Mon, 15 Jul 2013 18:50:10 +0200 (CEST) Date: Mon, 15 Jul 2013 18:50:09 +0200 From: Patrick Lamaiziere To: Mateusz Guzik Subject: Re: (9.2) panic under disk load (gam_server / knlist_remove_kq) Message-ID: <20130715185009.052d7614@davenulle.org> In-Reply-To: <20130715142647.GA9293@dft-labs.eu> References: <20130714115953.1afd6e90@davenulle.org> <20130714163353.2367a6a4@davenulle.org> <20130715142647.GA9293@dft-labs.eu> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 16:50:19 -0000 Le Mon, 15 Jul 2013 16:26:47 +0200, Mateusz Guzik a écrit : Hello, > > > I'm seeing a panic while trying to build a poudriere repository. > > > > > > As far I can see it always happens when gam_server is started (ie > > > xfce is running) and under disk load (poudriere bulk build) : > > > (That is something new, the box was pretty stable) > > > > > > the complete crash dump (core.0.txt) is here: > > > http://user.lamaiziere.net/patrick/panic_gam_server.txt > > > > With WITNESS and ASSERTION on, I see a warning that looks related : > > > > Jul 14 16:23:29 roxette kernel: WARNING: destroying knlist w/ > > knotes on it! > > > > and the box panics just after this. > > > > can you switch that printf to a panic and paste backtrace? Yes the full core.txt : http://user.lamaiziere.net/patrick/panic_knlist_wknotes.txt panic: WARNING: destroying knlist w/ knotes on it! Unread portion of the kernel message buffer: lock order reversal: 1st 0xfffffe00b678c098 ufs (ufs) @ /usr/src/sys/modules/nullfs/../../fs/nullfs/null_vnops.c:620 2nd 0xffffffff813ebda0 allproc (allproc) @ /usr/src/sys/kern/kern_descrip.c:2822 KDB: stack backtrace: #0 0xffffffff8094bc26 at kdb_backtrace+0x66 #1 0xffffffff809603ae at _witness_debugger+0x2e #2 0xffffffff80961a85 at witness_checkorder+0x865 #3 0xffffffff8091b1ea at _sx_slock+0x5a #4 0xffffffff808d30ff at mountcheckdirs+0x3f #5 0xffffffff809a890f at dounmount+0x2df #6 0xffffffff809a913e at sys_unmount+0x3ce #7 0xffffffff80cec429 at amd64_syscall+0x2f9 #8 0xffffffff80cd6d47 at Xfast_syscall+0xf7 panic: WARNING: destroying knlist w/ knotes on it! cpuid = 3 KDB: stack backtrace: #0 0xffffffff8094bc26 at kdb_backtrace+0x66 #1 0xffffffff80912da8 at panic+0x1d8 #2 0xffffffff808db269 at knlist_destroy+0x39 #3 0xffffffff809afd7e at destroy_vpollinfo+0x1e #4 0xffffffff809b13ef at vdropl+0x18f #5 0xffffffff809b404c at vputx+0xac #6 0xffffffff8299ce13 at null_reclaim+0x103 #7 0xffffffff80d912eb at VOP_RECLAIM_APV+0xdb #8 0xffffffff809b20a2 at vgonel+0x112 #9 0xffffffff809b4cd9 at vflush+0x2b9 #10 0xffffffff8299bbb3 at nullfs_unmount+0x43 #11 0xffffffff809a8982 at dounmount+0x352 #12 0xffffffff809a913e at sys_unmount+0x3ce #13 0xffffffff80cec429 at amd64_syscall+0x2f9 #14 0xffffffff80cd6d47 at Xfast_syscall+0xf7 Uptime: 4m47s Dumping 915 out of 3544 MB:..2%..11%..21%..32%..41%..51%..62%..72%..81%..91% #0 doadump (textdump=) at pcpu.h:234 234 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:234 #1 0xffffffff80913354 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 #2 0xffffffff80912d79 in panic (fmt=0x1
) at /usr/src/sys/kern/kern_shutdown.c:637 #3 0xffffffff808db269 in knlist_destroy (knl=) at /usr/src/sys/kern/kern_event.c:1961 #4 0xffffffff809afd7e in destroy_vpollinfo (vi=0xfffffe007ffec690) at /usr/src/sys/kern/vfs_subr.c:3583 #5 0xffffffff809b13ef in vdropl (vp=0xfffffe00b678c000) at /usr/src/sys/kern/vfs_subr.c:2530 #6 0xffffffff809b404c in vputx (vp=0xfffffe00b678c000, func=2) at /usr/src/sys/kern/vfs_subr.c:2358 #7 0xffffffff8299ce13 in ?? () #8 0xffffffff8299d510 in ?? () #9 0xfffffe00000002ec in ?? () #10 0xffffff81090b8750 in ?? () #11 0x0000000000000246 in ?? () #12 0xfffffe002af55000 in ?? () #13 0xffffffff81576950 in w_locklistdata () #14 0xffffffff81322ce0 in pmc___lock_failed () #15 0xffffffff8299d8a0 in ?? () #16 0xffffff81090b87b0 in ?? () #17 0x0000000000000000 in ?? () (kgdb) Thanks, regards From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 18:10:02 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 563572C1; Mon, 15 Jul 2013 18:10:02 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-ve0-x233.google.com (mail-ve0-x233.google.com [IPv6:2607:f8b0:400c:c01::233]) by mx1.freebsd.org (Postfix) with ESMTP id 0601AE32; Mon, 15 Jul 2013 18:10:01 +0000 (UTC) Received: by mail-ve0-f179.google.com with SMTP id d10so10160180vea.38 for ; Mon, 15 Jul 2013 11:10:01 -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=B4CBxGQ4eUEE/D3Ftct1l47abaUIfMX6NrezKQdA/Xk=; b=DOSqV7YBT3wGRfxFMyBOfyMmjk+kz8V1JvRwjF6jWs5wOiR0zOnw4T0d8LSQdznKvD e6MaWCxJzT9KnbaIA/I2Xb1W8cvJBoo/dRPsSOfueKR1qs49vx713yu/J4o85uZ1V6iZ +KRBhrVM4BaT9fjENG8vDTEkbSHylXvujFcQeCE+4xpVatmT9inKwvXiSNrFsg/55hxX hWnapw1TTdtRPJWT9/3BA0W3MHN3rMEWHiu/ZMOuQu53MM2x9ErJuaOT0nDofk7krqdI eU17FLL1+mjSYJ8P4uX+upaZ3qykLG8Rai8DZTschZrrjj6p5GHMTVAvCVI7R98NjDAy VkQQ== MIME-Version: 1.0 X-Received: by 10.220.191.5 with SMTP id dk5mr28749372vcb.47.1373911801408; Mon, 15 Jul 2013 11:10:01 -0700 (PDT) Received: by 10.58.249.1 with HTTP; Mon, 15 Jul 2013 11:10:01 -0700 (PDT) In-Reply-To: References: <51E3C8B7.7000801@gmail.com> Date: Mon, 15 Jul 2013 20:10:01 +0200 Message-ID: Subject: Re: Supermicro and FreeBSD 9.2 PRERELEASE make_dev_physpath_alias: WARNING From: Johan Hendriks To: Sergey Kandaurov Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Alexander Motin , freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 18:10:02 -0000 Op maandag 15 juli 2013 schreef Sergey Kandaurov (pluknet@gmail.com) het volgende: > On 15 July 2013 14:02, Johan Hendriks > > wrote: > > We use basic supermicro cases for our storage servers in combination > with a > > LSI 9211-8i controller in IT mode. > > > > Since 9.1 or shortly there after we get for every disk we attach to the > SAS > > backplane the following error. > > > > make_dev_physpath_alias: WARNING - Unable to alias > > gptid/abb586f5-da8d-11e2-aaaf-00259061b51a to > > enc@n500304800122877d/type@0/slot@f/elmdesc@Slot_15 > /gptid/abb586f5-da8d-11e2-aaaf-00259061b51a > > - path too long. > > > > I know it does not harm the operation, but every time the server boots or > > when we add a disk i get a little scared when i see WRNINGS passing by. > > > > Is there a way to supress these WARNINGS, or is there something i can do > > about it. > > This is because the name is longer than SPECNAMELEN. > You barely can do anything with it. The warning is hidden under bootverbose > in 10-CURRENT, and I think it should be merged to stable/9 before 9.2 > release. > Meantime you can manually apply this change: > > http://svnweb.freebsd.org/changeset/base/235899 > > > I know on 9.0 i do not get these messages.! > That's odd. AFAIK the feature had appeared in 9.0. > > Well i am sure these messages started after 9.0 I have one 9.0 machine left which does not show them. All the others are upgraded and started to show these warnings. Thanks for your time. Regards Johan > -- > wbr, > pluknet > From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 18:51:16 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4AA30E92 for ; Mon, 15 Jul 2013 18:51:16 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) by mx1.freebsd.org (Postfix) with ESMTP id 145E06E for ; Mon, 15 Jul 2013 18:51:15 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6FIp91o011180 for ; Mon, 15 Jul 2013 14:51:09 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Mon, 15 Jul 2013 14:51:09 -0400 (EDT) Date: Mon, 15 Jul 2013 14:51:09 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: freebsd-stable@FreeBSD.org Subject: LDAP authentication confusion Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 18:51:16 -0000 There's an article on LDAP authentication on FreeBSD here: http://www.freebsd.org/doc/en/articles/ldap-auth/article.html#client I'm confused as to why pam_ldap and nss_ldap do not need /etc/pam.d entries, as described in the above link in section 3.1.1. Meaning, I do not have any ldap entries in my /etc/pam.d/ or even /usr/local/etc/pam.d/ and ldap logins work (console, ssh, telnet, ftp). $ grep -i ldap /etc/pam.d/* $ grep -i ldap /usr/local/etc/pam.d/* What am I missing? $ uname -v FreeBSD slrtr1 9.1-STABLE FreeBSD 9.1-STABLE #0 r250347... $ uname -m amd64 $ cat /etc/nsswitch.conf group: files ldap hosts: files dns networks: files passwd: files ldap shells: files services: files protocols: files rpc: files -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 18:54:18 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 693C417B for ; Mon, 15 Jul 2013 18:54:18 +0000 (UTC) (envelope-from mloftis@wgops.com) Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id E5D21DB for ; Mon, 15 Jul 2013 18:54:17 +0000 (UTC) Received: by mail-la0-f50.google.com with SMTP id ep20so5303522lab.37 for ; Mon, 15 Jul 2013 11:54:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wgops.com; s=gm01; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=BEI+59UXW+uJW3X1lYc6HvwIQh5VEHfJTe5gRJP3eBI=; b=RBwP0e3wEQB31LKxND+ED3KJNeOY6w4NLAhfc2iMk6KAUU5mouG/iXpQ3xFc7HVPZU ujZAFO9q8nJzTy7mrJRPeGVuoI5U1iBNOPwtohYi0uOT65vpu4j8wYdE+7+gaX+GIfAp ecpEsAeZywxHIx5gz+sNwxK/hcCw+mnjqsGAM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=BEI+59UXW+uJW3X1lYc6HvwIQh5VEHfJTe5gRJP3eBI=; b=DGbZxe8xi8JbXfZ2UND3DLYnu5Bgphi6MyCo/nJO8fXmCHD8YdkLp0PV2M/OI69bJX clY1Bc+zE0gGKT5rYooZVqb3Pr0ZcyWXumw4hle7PwkpBZX9FFbtkUqIld3jMJr/Tfbw FxBUm6iq4evNcrK2kH/ImB290wvYS8DPADZ+uEoK5ntVyDsrH808oYArzdY2VmhLD2Qn MwM71emsq8kjcfiuDP8+DWvSWQBkjlT2YQZYZl6b7u2HHkavjBtwEhxwBZhLgGWkzWSU NDZwJWg9kkIdTY9K1aoTMInUfOblvlIJYh7p8TGfLmgaKU2jviRuR5o4DCllkYT6IhTY fnKg== MIME-Version: 1.0 X-Received: by 10.112.159.169 with SMTP id xd9mr24828948lbb.43.1373914456677; Mon, 15 Jul 2013 11:54:16 -0700 (PDT) Received: by 10.112.151.66 with HTTP; Mon, 15 Jul 2013 11:54:16 -0700 (PDT) In-Reply-To: References: Date: Mon, 15 Jul 2013 11:54:16 -0700 Message-ID: Subject: Re: LDAP authentication confusion From: Michael Loftis To: Daniel Eischen Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmJl1Xt9hK6VlNAK09jTrGoVbZwsMoO2QlgxoTAOHgz4xl9W0npVGNjITG++KX+Xi5QEPM6 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 18:54:18 -0000 nss_ldap fulfills most of the get*ent calls, thus based on the bits of your configuration you've exposed I think you're ending up with that behavior and not using pam_ldap at all. Instead the authentication is happening via nsswitch fulfilling getpwent() call's (the passwd: files ldap line in nsswitch.conf) On Mon, Jul 15, 2013 at 11:51 AM, Daniel Eischen wrote: > There's an article on LDAP authentication on FreeBSD here: > > http://www.freebsd.org/doc/en/articles/ldap-auth/article.html#client > > I'm confused as to why pam_ldap and nss_ldap do not need > /etc/pam.d entries, as described in the above link in > section 3.1.1. Meaning, I do not have any ldap entries > in my /etc/pam.d/ or even /usr/local/etc/pam.d/ and > ldap logins work (console, ssh, telnet, ftp). > > $ grep -i ldap /etc/pam.d/* > $ grep -i ldap /usr/local/etc/pam.d/* > > What am I missing? > > $ uname -v > FreeBSD slrtr1 9.1-STABLE FreeBSD 9.1-STABLE #0 r250347... > $ uname -m > amd64 > $ cat /etc/nsswitch.conf > group: files ldap > hosts: files dns > networks: files > passwd: files ldap > shells: files > services: files > protocols: files > rpc: files > > -- > DE > _______________________________________________ > 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" -- "Genius might be described as a supreme capacity for getting its possessors into trouble of all kinds." -- Samuel Butler From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 19:09:48 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D794E5DB for ; Mon, 15 Jul 2013 19:09:48 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) by mx1.freebsd.org (Postfix) with ESMTP id 9902B1B7 for ; Mon, 15 Jul 2013 19:09:48 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6FJ9lYH032275; Mon, 15 Jul 2013 15:09:47 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Mon, 15 Jul 2013 15:09:47 -0400 (EDT) Date: Mon, 15 Jul 2013 15:09:47 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Michael Loftis Subject: Re: LDAP authentication confusion In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 19:09:48 -0000 On Mon, 15 Jul 2013, Michael Loftis wrote: > nss_ldap fulfills most of the get*ent calls, thus based on the bits of > your configuration you've exposed I think you're ending up with that > behavior and not using pam_ldap at all. Instead the authentication is > happening via nsswitch fulfilling getpwent() call's (the passwd: files > ldap line in nsswitch.conf) Ok, thanks. But shouldn't the documentation be changed to reflect that? > On Mon, Jul 15, 2013 at 11:51 AM, Daniel Eischen wrote: >> There's an article on LDAP authentication on FreeBSD here: >> >> http://www.freebsd.org/doc/en/articles/ldap-auth/article.html#client >> >> I'm confused as to why pam_ldap and nss_ldap do not need >> /etc/pam.d entries, as described in the above link in >> section 3.1.1. Meaning, I do not have any ldap entries >> in my /etc/pam.d/ or even /usr/local/etc/pam.d/ and >> ldap logins work (console, ssh, telnet, ftp). >> >> $ grep -i ldap /etc/pam.d/* >> $ grep -i ldap /usr/local/etc/pam.d/* >> >> What am I missing? >> >> $ uname -v >> FreeBSD slrtr1 9.1-STABLE FreeBSD 9.1-STABLE #0 r250347... >> $ uname -m >> amd64 >> $ cat /etc/nsswitch.conf >> group: files ldap >> hosts: files dns >> networks: files >> passwd: files ldap >> shells: files >> services: files >> protocols: files >> rpc: files -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 19:15:56 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id ED7F99E7 for ; Mon, 15 Jul 2013 19:15:56 +0000 (UTC) (envelope-from feld@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id C6D8B229 for ; Mon, 15 Jul 2013 19:15:56 +0000 (UTC) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0B13C2153E for ; Mon, 15 Jul 2013 15:15:53 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Mon, 15 Jul 2013 15:15:54 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=igmwOP12rDbdatq8MmaHA88B0gc=; b=Owhqf mwsdMeliI+ckAR39hCpbpmH7GNyZuJg1Pqx/1JH5nBzt5jjeSLAmaotRTBALyppA qrew3ramikIRvu9JMQfdi2qP2HWsZi0MeETRoDmb7kz+iYdaPupYOSQubQ57wByB r4eSGKqHUPIZYef20oN3qcNAv3qKHUEwGyI/RA= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id EA236B00003; Mon, 15 Jul 2013 15:15:52 -0400 (EDT) Message-Id: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> X-Sasl-Enc: IF6e0mXixqSbf0DzbeU3YbLh0pPPhIGadoswJ1ZTvKzd 1373915752 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-bdcdd1cb Subject: Re: LDAP authentication confusion Date: Mon, 15 Jul 2013 14:15:52 -0500 In-Reply-To: References: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 19:15:57 -0000 On Mon, Jul 15, 2013, at 14:09, Daniel Eischen wrote: > > Ok, thanks. But shouldn't the documentation be changed > to reflect that? > Whoa, I need to test this now, as we are used to being able to turn this on/off by editing /etc/pam.d/system and sshd From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 19:19:54 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CA253B87 for ; Mon, 15 Jul 2013 19:19:54 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:140:72e1::ac16:e45e]) by mx1.freebsd.org (Postfix) with ESMTP id 93DB0273 for ; Mon, 15 Jul 2013 19:19:54 +0000 (UTC) Received: from hexe.rlwinm.de (p4FE67BC6.dip0.t-ipconnect.de [79.230.123.198]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id D63E61169A for ; Mon, 15 Jul 2013 19:16:20 +0000 (UTC) Message-ID: <51E44B55.6030005@rlwinm.de> Date: Mon, 15 Jul 2013 21:19:49 +0200 From: Jan Bramkamp User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130707 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: LDAP authentication confusion References: In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 19:19:54 -0000 On 15.07.2013 21:09, Daniel Eischen wrote:> On Mon, 15 Jul 2013, Michael Loftis wrote: > >> nss_ldap fulfills most of the get*ent calls, thus based on the bits of >> your configuration you've exposed I think you're ending up with that >> behavior and not using pam_ldap at all. Instead the authentication is >> happening via nsswitch fulfilling getpwent() call's (the passwd: files >> ldap line in nsswitch.conf) > > Ok, thanks. But shouldn't the documentation be changed > to reflect that? More than that. In my opinion it should be updated by replacing nss_ldap and pam_ldap with nss-pam-ldapd which splits the job of both into a shared daemon talking to the LDAP server and small stubs linked into the NSS / PAM using process talking to the local daemon. This allows useable timeout handling and client certificates with save permissions. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 19:25:04 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9D6A0E37 for ; Mon, 15 Jul 2013 19:25:04 +0000 (UTC) (envelope-from feld@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 75C802C2 for ; Mon, 15 Jul 2013 19:25:04 +0000 (UTC) Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id EEEFC21379 for ; Mon, 15 Jul 2013 15:25:03 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute1.internal (MEProxy); Mon, 15 Jul 2013 15:25:03 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=R3eG+8n1AUWVBUV1neiFvrRaSwY=; b=Ba0 8Xs5f8VNtoiQhUQPEyPrFxYeIVhk7ZI1T1uqYqd+FF9wKbzM3Zm31yO9zu79Yv5X x3yvXGzTOv0PBf/ow6QfdjT7wJ79pYHkfGoMcIar8NgBwTxrxci4xoGAvrlNjLWU 0PrW/c6X1/iI0nQyqr2SGu3sHCTvGvwPdOqhumh4= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id D4696B00003; Mon, 15 Jul 2013 15:25:03 -0400 (EDT) Message-Id: <1373916303.17449.140661255966229.44609E69@webmail.messagingengine.com> X-Sasl-Enc: smnRErBnemUGJoKkCEyJQU8e0kq+m6W91JqTLZLMwEDZ 1373916303 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-bdcdd1cb In-Reply-To: <51E44B55.6030005@rlwinm.de> References: <51E44B55.6030005@rlwinm.de> Subject: Re: LDAP authentication confusion Date: Mon, 15 Jul 2013 14:25:03 -0500 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 19:25:04 -0000 On Mon, Jul 15, 2013, at 14:19, Jan Bramkamp wrote: > > More than that. In my opinion it should be updated by replacing nss_ldap > and pam_ldap with nss-pam-ldapd which splits the job of both into a > shared daemon talking to the LDAP server and small stubs linked into the > NSS / PAM using process talking to the local daemon. This allows useable > timeout handling and client certificates with save permissions. > And if the daemon ever crashes, we can't login to our customer servers (assuming they nuked our local account because they have root access). That's the one issue I have with that daemon and why we haven't migrated to it. We should re-evaluate it, though. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 19:35:22 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2FE55182 for ; Mon, 15 Jul 2013 19:35:22 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:140:72e1::ac16:e45e]) by mx1.freebsd.org (Postfix) with ESMTP id EC2C134B for ; Mon, 15 Jul 2013 19:35:21 +0000 (UTC) Received: from hexe.rlwinm.de (p4FE67BC6.dip0.t-ipconnect.de [79.230.123.198]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id B6E3D116A1 for ; Mon, 15 Jul 2013 19:31:54 +0000 (UTC) Message-ID: <51E44EFA.2090207@rlwinm.de> Date: Mon, 15 Jul 2013 21:35:22 +0200 From: Jan Bramkamp User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130707 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: LDAP authentication confusion References: <51E44B55.6030005@rlwinm.de> <1373916303.17449.140661255966229.44609E69@webmail.messagingengine.com> In-Reply-To: <1373916303.17449.140661255966229.44609E69@webmail.messagingengine.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 19:35:22 -0000 On 15.07.2013 21:25, Mark Felder wrote:> On Mon, Jul 15, 2013, at 14:19, Jan Bramkamp wrote: >> >> More than that. In my opinion it should be updated by replacing nss_ldap >> and pam_ldap with nss-pam-ldapd which splits the job of both into a >> shared daemon talking to the LDAP server and small stubs linked into the >> NSS / PAM using process talking to the local daemon. This allows useable >> timeout handling and client certificates with save permissions. >> > > And if the daemon ever crashes, we can't login to our customer servers > (assuming they nuked our local account because they have root access). > > That's the one issue I have with that daemon and why we haven't migrated > to it. We should re-evaluate it, though. In that case run nslcd in foreground with some kind of watchdog. Their are several examples of this in the ports tree e.g. daemontools. So far i never ran into this problem because nslcd on any of my production systems. I prefer nss-pam-ldapd over nss_ldap + pam_ldap because: - It doesn't link libldap, liblber, libsasl, libssl etc. into nearly every process. - It keeps the LDAP connection open reducing the latency (important with DHE-RSA ciphersuites). - It handles timeouts in one place instead of timing out in every process. This doesn't change the fact that the nslcd daemon is a single point of failure for all LDAP accesses over NSS and PAM. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 19:44:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1FEAA789 for ; Mon, 15 Jul 2013 19:44:41 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) by mx1.freebsd.org (Postfix) with ESMTP id D3D8B651 for ; Mon, 15 Jul 2013 19:44:40 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6FJid5w002028; Mon, 15 Jul 2013 15:44:39 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Mon, 15 Jul 2013 15:44:39 -0400 (EDT) Date: Mon, 15 Jul 2013 15:44:39 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Jan Bramkamp Subject: Re: LDAP authentication confusion In-Reply-To: <51E44B55.6030005@rlwinm.de> Message-ID: References: <51E44B55.6030005@rlwinm.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 19:44:41 -0000 On Mon, 15 Jul 2013, Jan Bramkamp wrote: > On 15.07.2013 21:09, Daniel Eischen wrote:> On Mon, 15 Jul 2013, Michael > Loftis wrote: >> >>> nss_ldap fulfills most of the get*ent calls, thus based on the bits of >>> your configuration you've exposed I think you're ending up with that >>> behavior and not using pam_ldap at all. Instead the authentication is >>> happening via nsswitch fulfilling getpwent() call's (the passwd: files >>> ldap line in nsswitch.conf) >> >> Ok, thanks. But shouldn't the documentation be changed >> to reflect that? > > More than that. In my opinion it should be updated by replacing nss_ldap > and pam_ldap with nss-pam-ldapd which splits the job of both into a > shared daemon talking to the LDAP server and small stubs linked into the > NSS / PAM using process talking to the local daemon. This allows useable > timeout handling and client certificates with save permissions. I tried nss-pam-ldapd and it doesn't work for me. I'm not doing anything strange, as you can see by my configuration. It would try to talk to the LDAP server, but would fail. I'm not sure it was correctly picking up the proxyagent password in my /usr/local/etc/nslcd.conf. It was definitely parsing it though, as that is where the LDAP server is defined. I switched to using pam_ldap and nss_ldap, and it worked without any problem. -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 19:49:52 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 37F0AA35 for ; Mon, 15 Jul 2013 19:49:52 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [46.4.89.243]) by mx1.freebsd.org (Postfix) with ESMTP id EFD206C5 for ; Mon, 15 Jul 2013 19:49:51 +0000 (UTC) Received: from hexe.rlwinm.de (p4FE67BC6.dip0.t-ipconnect.de [79.230.123.198]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id 4CF4B116A9 for ; Mon, 15 Jul 2013 19:46:24 +0000 (UTC) Message-ID: <51E45260.3050803@rlwinm.de> Date: Mon, 15 Jul 2013 21:49:52 +0200 From: Jan Bramkamp User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130707 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: LDAP authentication confusion References: <51E44B55.6030005@rlwinm.de> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 19:49:52 -0000 On 15.07.2013 21:44, Daniel Eischen wrote: > On Mon, 15 Jul 2013, Jan Bramkamp wrote: > >> On 15.07.2013 21:09, Daniel Eischen wrote:> On Mon, 15 Jul 2013, Michael >> Loftis wrote: >>> >>>> nss_ldap fulfills most of the get*ent calls, thus based on the bits of >>>> your configuration you've exposed I think you're ending up with that >>>> behavior and not using pam_ldap at all. Instead the authentication is >>>> happening via nsswitch fulfilling getpwent() call's (the passwd: files >>>> ldap line in nsswitch.conf) >>> >>> Ok, thanks. But shouldn't the documentation be changed >>> to reflect that? >> >> More than that. In my opinion it should be updated by replacing nss_ldap >> and pam_ldap with nss-pam-ldapd which splits the job of both into a >> shared daemon talking to the LDAP server and small stubs linked into the >> NSS / PAM using process talking to the local daemon. This allows useable >> timeout handling and client certificates with save permissions. > > I tried nss-pam-ldapd and it doesn't work for me. I'm not > doing anything strange, as you can see by my configuration. > It would try to talk to the LDAP server, but would fail. > I'm not sure it was correctly picking up the proxyagent > password in my /usr/local/etc/nslcd.conf. It was definitely > parsing it though, as that is where the LDAP server is > defined. I switched to using pam_ldap and nss_ldap, and > it worked without any problem. > This is my basic nscld.conf: uid nslcd gid nslcd # fail over to auth2 if required uri ldap://auth1.example.org uri ldap://auth2.example.org base dc=example,dc=org scope sub base group ou=groups,dc=example,dc=org base passwd ou=users,dc=example,dc=org scope group onelevel scope hosts sub filter group (|(objectClass=posixGroup)(objectClass=posixGroupOfNames)) # allow groups of DNs bind_timelimit 15 timelimit 5 idle_timelimit 3600 ssl start_tls tls_reqcert hard tls_cacertdir /usr/local/etc/openldap/ca tls_cacertfile /usr/local/etc/openldap/ca/ca-cert.pem tls_ciphers DHE-RSA-AES256-GCM-SHA384 # requires OpenSSL from ports use DHE-RSA-AES256-SHA otherwise tls_cert /usr/local/etc/nslcd.crt tls_key /usr/local/etc/nslcd.key sasl_mech EXTERNAL sasl_realm EXAMPLE.ORG From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 19:51:16 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CAD93B71; Mon, 15 Jul 2013 19:51:16 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) by mx1.freebsd.org (Postfix) with ESMTP id 90AD06ED; Mon, 15 Jul 2013 19:51:16 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6FJpFqq008440; Mon, 15 Jul 2013 15:51:15 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Mon, 15 Jul 2013 15:51:15 -0400 (EDT) Date: Mon, 15 Jul 2013 15:51:15 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Mark Felder Subject: Re: LDAP authentication confusion In-Reply-To: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> Message-ID: References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 19:51:16 -0000 On Mon, 15 Jul 2013, Mark Felder wrote: > On Mon, Jul 15, 2013, at 14:09, Daniel Eischen wrote: >> >> Ok, thanks. But shouldn't the documentation be changed >> to reflect that? > > Whoa, I need to test this now, as we are used to being able to turn this > on/off by editing /etc/pam.d/system and sshd Wouldn't it be easier just to edit /etc/nsswitch.conf anyway? -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 19:53:46 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DC30ACC9; Mon, 15 Jul 2013 19:53:46 +0000 (UTC) (envelope-from feld@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id B27D477A; Mon, 15 Jul 2013 19:53:46 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id BCCDF21167; Mon, 15 Jul 2013 15:53:45 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute2.internal (MEProxy); Mon, 15 Jul 2013 15:53:45 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=uvUZdvtfzUlKKs1nTiOANlUiV4Q=; b=ivu4k Jd1Faduuwy2ls7F3K5sQoUts0rvjXZnCl9btIg+WBL3sHX42H1Kf0MlMaXLe/E20 ygRRAjOg5jo7OC9i3PXED2dd6XP7k0Tr3XGaXWXgMcxW46/a5MTiGAimTuTYZ4hR 6dRKystAVa9ksY+fQMQ2jX9OjtKwC6HYN3Sc6U= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 99C58B00003; Mon, 15 Jul 2013 15:53:45 -0400 (EDT) Message-Id: <1373918025.26584.140661255976885.04071858@webmail.messagingengine.com> X-Sasl-Enc: GWPSEWaVzlMJBRTY1fbDkuX4x0PNTK2Xgifmj2WF/TpB 1373918025 From: Mark Felder To: Daniel Eischen MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-bdcdd1cb Subject: Re: LDAP authentication confusion Date: Mon, 15 Jul 2013 14:53:45 -0500 In-Reply-To: References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 19:53:46 -0000 On Mon, Jul 15, 2013, at 14:51, Daniel Eischen wrote: > > Wouldn't it be easier just to edit /etc/nsswitch.conf > anyway? > Yes, but bad things happen if you're upgrading a server and there are library changes but you've left it in the pam.d/* files. I guess I wasn't very specific. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 20:18:20 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0FE9B441 for ; Mon, 15 Jul 2013 20:18:20 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) by mx1.freebsd.org (Postfix) with ESMTP id B0C228C2 for ; Mon, 15 Jul 2013 20:18:19 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6FKIIWt033400; Mon, 15 Jul 2013 16:18:18 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Mon, 15 Jul 2013 16:18:18 -0400 (EDT) Date: Mon, 15 Jul 2013 16:18:18 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Jan Bramkamp Subject: Re: LDAP authentication confusion In-Reply-To: <51E45260.3050803@rlwinm.de> Message-ID: References: <51E44B55.6030005@rlwinm.de> <51E45260.3050803@rlwinm.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 20:18:20 -0000 On Mon, 15 Jul 2013, Jan Bramkamp wrote: > On 15.07.2013 21:44, Daniel Eischen wrote: >> On Mon, 15 Jul 2013, Jan Bramkamp wrote: >> >>> On 15.07.2013 21:09, Daniel Eischen wrote:> On Mon, 15 Jul 2013, Michael >>> Loftis wrote: >>>> >>>>> nss_ldap fulfills most of the get*ent calls, thus based on the bits of >>>>> your configuration you've exposed I think you're ending up with that >>>>> behavior and not using pam_ldap at all. Instead the authentication is >>>>> happening via nsswitch fulfilling getpwent() call's (the passwd: files >>>>> ldap line in nsswitch.conf) >>>> >>>> Ok, thanks. But shouldn't the documentation be changed >>>> to reflect that? >>> >>> More than that. In my opinion it should be updated by replacing nss_ldap >>> and pam_ldap with nss-pam-ldapd which splits the job of both into a >>> shared daemon talking to the LDAP server and small stubs linked into the >>> NSS / PAM using process talking to the local daemon. This allows useable >>> timeout handling and client certificates with save permissions. >> >> I tried nss-pam-ldapd and it doesn't work for me. I'm not >> doing anything strange, as you can see by my configuration. >> It would try to talk to the LDAP server, but would fail. >> I'm not sure it was correctly picking up the proxyagent >> password in my /usr/local/etc/nslcd.conf. It was definitely >> parsing it though, as that is where the LDAP server is >> defined. I switched to using pam_ldap and nss_ldap, and >> it worked without any problem. >> > > This is my basic nscld.conf: Thanks, mine is simpler. I just tried again. $ sudo grep -v "^#" /usr/local/etc/nslcd.conf | sort -u base dc=foo,dc=bar,dc=com binddn cn=proxyagent,dc=foo,dc=bar,dc=com bindpw <...> gid nslcd uid nslcd uri ldap://192.168.3.96/ Everything else is default. All the entries above match the respective settings I used in the working ldap.conf and nss_ldap.conf. We're using Oracle DSEE7 (nee Sun Java Directory Server). -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 21:19:05 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5A8A75F5 for ; Mon, 15 Jul 2013 21:19:05 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:140:72e1::ac16:e45e]) by mx1.freebsd.org (Postfix) with ESMTP id 236F4B2F for ; Mon, 15 Jul 2013 21:19:05 +0000 (UTC) Received: from hexe.rlwinm.de (p4FE67BC6.dip0.t-ipconnect.de [79.230.123.198]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id F16D0116C2 for ; Mon, 15 Jul 2013 21:15:34 +0000 (UTC) Message-ID: <51E46747.7070705@rlwinm.de> Date: Mon, 15 Jul 2013 23:19:03 +0200 From: Jan Bramkamp User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130707 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: LDAP authentication confusion References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 21:19:05 -0000 On 15.07.2013 21:51, Daniel Eischen wrote: > > Wouldn't it be easier just to edit /etc/nsswitch.conf > anyway? PAM and NSS switch are two different subsystems. NSS is just for resource lookups (users, groups, hosts, ...). PAM is for access control. With ldap in nsswitch.conf for users and groups you can lookup a LDAP user but the user can't log into $service through PAM. This requires pam_ldap.so in pam.d/$service. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 21:34:07 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 523DE9A2; Mon, 15 Jul 2013 21:34:07 +0000 (UTC) (envelope-from taku@tackymt.homeip.net) Received: from basalt.tackymt.homeip.net (basalt.tackymt.homeip.net [IPv6:2001:470:fd92:0:20d:61ff:fecc:2253]) by mx1.freebsd.org (Postfix) with ESMTP id 0A67CC06; Mon, 15 Jul 2013 21:34:06 +0000 (UTC) Received: from basalt.tackymt.homeip.net (localhost [127.0.0.1]) by basalt.tackymt.homeip.net (Postfix) with ESMTP id EE23D83C6; Tue, 16 Jul 2013 06:34:04 +0900 (JST) X-Virus-Scanned: amavisd-new at tackymt.homeip.net Received: from localhost by basalt.tackymt.homeip.net (amavisd-new, unix socket) with ESMTP id bXgCPpQpZiX0; Tue, 16 Jul 2013 06:34:00 +0900 (JST) Received: from biotite.tackymt.homeip.net (biotite.tackymt.homeip.net [IPv6:2001:470:fd92:0:216:cfff:febc:1472]) by basalt.tackymt.homeip.net (Postfix) with ESMTPSA; Tue, 16 Jul 2013 06:33:59 +0900 (JST) Date: Tue, 16 Jul 2013 06:35:12 +0900 From: Taku YAMAMOTO To: Adrian Chadd Subject: Re: USB ports on Lenovo T400 do not work after a suspend/resume Message-Id: <20130716063512.d48fcc385a64619952a52a66@tackymt.homeip.net> In-Reply-To: References: <20130621220013.X55167@sola.nimnet.asn.au> <20130626152833.M78748@sola.nimnet.asn.au> <20130626195154.GK88288@e-new.0x20.net> <20130627213331.W26984@sola.nimnet.asn.au> <20130630233640.Y23789@sola.nimnet.asn.au> <20130707204957.GD88288@e-new.0x20.net> <20130708140804.R26496@sola.nimnet.asn.au> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.17; i386-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Tue__16_Jul_2013_06_35_12_+0900_D2=g_ngqTKSdEOy3" Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org, Ian Smith , freebsd-usb@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 21:34:07 -0000 This is a multi-part message in MIME format. --Multipart=_Tue__16_Jul_2013_06_35_12_+0900_D2=g_ngqTKSdEOy3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit This reminds me of my local patch which I wrote and forgot about deep in the git :) This hack was required to have working USB ports on X61 after resume, but I'm not sure whether it's still required because I don't have X61 handy anymore... On Mon, 8 Jul 2013 11:09:20 -0700 Adrian Chadd wrote: > On 7 July 2013 22:00, Ian Smith wrote: > > > Checking one more point .. do the USB ports come up ok if you originally > > boot with nothing plugged in? If so (or if not), does that local APIC > > Yes. > > > error message appear the same then too? > > > > > No > > > -adrian > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" -- -|-__ $B;3K\!!Bs(B / YAMAMOTO, Taku | __ < - A chicken is an egg's way of producing more eggs. - --Multipart=_Tue__16_Jul_2013_06_35_12_+0900_D2=g_ngqTKSdEOy3 Content-Type: text/plain; name="acpi_psw-usb.patch" Content-Disposition: attachment; filename="acpi_psw-usb.patch" Content-Transfer-Encoding: 7bit commit 5df85bbf9a02f5bd116bc8520aba2d6b4ee1b2fb Author: Taku YAMAMOTO Date: Thu Feb 14 01:07:22 2013 +0900 Fix GPE handling on sleeping. (found on X61) diff --git a/sys/dev/acpica/acpi.c b/sys/dev/acpica/acpi.c index da252c4..2ccf08a 100644 --- a/sys/dev/acpica/acpi.c +++ b/sys/dev/acpica/acpi.c @@ -2905,6 +2905,8 @@ acpi_wake_sleep_prep(ACPI_HANDLE handle, int sstate) if (acpi_parse_prw(handle, &prw) != 0) return (ENXIO); dev = acpi_get_device(handle); + if (dev == NULL || (acpi_get_flags(dev) & ACPI_FLAG_WAKE_ENABLED) == 0) + return (0); /* * The destination sleep state must be less than (i.e., higher power) @@ -2918,7 +2920,7 @@ acpi_wake_sleep_prep(ACPI_HANDLE handle, int sstate) if (bootverbose) device_printf(dev, "wake_prep disabled wake for %s (S%d)\n", acpi_name(handle), sstate); - } else if (dev && (acpi_get_flags(dev) & ACPI_FLAG_WAKE_ENABLED) != 0) { + } else { acpi_pwr_wake_enable(handle, 1); acpi_SetInteger(handle, "_PSW", 1); if (bootverbose) --Multipart=_Tue__16_Jul_2013_06_35_12_+0900_D2=g_ngqTKSdEOy3-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 21:39:03 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D28EDB49 for ; Mon, 15 Jul 2013 21:39:03 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) by mx1.freebsd.org (Postfix) with ESMTP id 99A13C3D for ; Mon, 15 Jul 2013 21:39:03 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6FLd2Vw045446; Mon, 15 Jul 2013 17:39:02 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Mon, 15 Jul 2013 17:39:02 -0400 (EDT) Date: Mon, 15 Jul 2013 17:39:02 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Jan Bramkamp Subject: Re: LDAP authentication confusion In-Reply-To: <51E46747.7070705@rlwinm.de> Message-ID: References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> <51E46747.7070705@rlwinm.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 21:39:03 -0000 On Mon, 15 Jul 2013, Jan Bramkamp wrote: > On 15.07.2013 21:51, Daniel Eischen wrote: >> >> Wouldn't it be easier just to edit /etc/nsswitch.conf >> anyway? > PAM and NSS switch are two different subsystems. NSS is just for > resource lookups (users, groups, hosts, ...). PAM is for access control. > > With ldap in nsswitch.conf for users and groups you can lookup a LDAP > user but the user can't log into $service through PAM. This requires > pam_ldap.so in pam.d/$service. Minor correction. "This requires the ldap PAM library (pam_ldap.so) to be installed." No pam.d entries seem to be needed. None seem to be necessary on Solaris 10 either. -- DE From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 22:53:16 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 69FDA67A for ; Mon, 15 Jul 2013 22:53:16 +0000 (UTC) (envelope-from mauzo@anubis.morrow.me.uk) Received: from isis.morrow.me.uk (isis.morrow.me.uk [204.109.63.142]) by mx1.freebsd.org (Postfix) with ESMTP id 47979F49 for ; Mon, 15 Jul 2013 22:53:15 +0000 (UTC) Received: from anubis.morrow.me.uk (host31-52-186-205.range31-52.btcentralplus.com [31.52.186.205]) (Authenticated sender: mauzo) by isis.morrow.me.uk (Postfix) with ESMTPSA id 1FB65450B6 for ; Mon, 15 Jul 2013 22:47:55 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.7.4 isis.morrow.me.uk 1FB65450B6 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=morrow.me.uk; s=dkim201101; t=1373928476; bh=YeeptrqA7JfEieo9u70Pn9q8ZcREU/3975g+CNo8PTA=; h=Date:From:To:Subject:References:In-Reply-To; b=TnFFvLiacBOOLiIYu7VeR+fxkRrO2BkBzqZicJHBia9YWGyUtL8Ti55BNSAZA9IiR 0BcvfHWqGysQ3HHv/AQKfQ2lQ1059K41eolwD2A6QKRly3iFqH2gEQgXwvB8LXHdAG lv4mp7XEIn2ps9xGBHpcZvarD0b+daaMKPtdHutk= X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.97.6 at isis.morrow.me.uk Received: by anubis.morrow.me.uk (Postfix, from userid 5001) id E82CEBD1D; Mon, 15 Jul 2013 23:47:52 +0100 (BST) Date: Mon, 15 Jul 2013 23:47:52 +0100 From: Ben Morrow To: freebsd-stable@freebsd.org Subject: Re: LDAP authentication confusion Message-ID: <20130715224748.GA45649@anubis.morrow.me.uk> References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51E46747.7070705@rlwinm.de> X-Newsgroups: gmane.os.freebsd.stable Organization: morrow.me.uk User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 22:53:16 -0000 Quoth Jan Bramkamp : > On 15.07.2013 21:51, Daniel Eischen wrote: > > > > Wouldn't it be easier just to edit /etc/nsswitch.conf > > anyway? > PAM and NSS switch are two different subsystems. NSS is just for > resource lookups (users, groups, hosts, ...). PAM is for access control. > > With ldap in nsswitch.conf for users and groups you can lookup a LDAP > user but the user can't log into $service through PAM. This requires > pam_ldap.so in pam.d/$service. The default pam_unix.so calls getpwent, so if nss_ldap returns cryptable passwords in its result I think pam_unix can authenticate against those. This is not the same as authenticating by LDAP bind, but may end up accepting the same passwords. Ben From owner-freebsd-stable@FreeBSD.ORG Mon Jul 15 23:07:46 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EA85D8B2 for ; Mon, 15 Jul 2013 23:07:46 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [46.4.89.243]) by mx1.freebsd.org (Postfix) with ESMTP id AD7D1FCD for ; Mon, 15 Jul 2013 23:07:46 +0000 (UTC) Received: from hexe.rlwinm.de (p4FE67BC6.dip0.t-ipconnect.de [79.230.123.198]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id 895F1116E0 for ; Mon, 15 Jul 2013 23:04:18 +0000 (UTC) Message-ID: <51E480C3.50008@rlwinm.de> Date: Tue, 16 Jul 2013 01:07:47 +0200 From: Jan Bramkamp User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130707 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: LDAP authentication confusion References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> <20130715224748.GA45649@anubis.morrow.me.uk> In-Reply-To: <20130715224748.GA45649@anubis.morrow.me.uk> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 15 Jul 2013 23:07:47 -0000 On 16.07.2013 00:47, Ben Morrow wrote: > Quoth Jan Bramkamp : >> On 15.07.2013 21:51, Daniel Eischen wrote: >>> >>> Wouldn't it be easier just to edit /etc/nsswitch.conf >>> anyway? >> PAM and NSS switch are two different subsystems. NSS is just for >> resource lookups (users, groups, hosts, ...). PAM is for access control. >> >> With ldap in nsswitch.conf for users and groups you can lookup a LDAP >> user but the user can't log into $service through PAM. This requires >> pam_ldap.so in pam.d/$service. > > The default pam_unix.so calls getpwent, so if nss_ldap returns cryptable > passwords in its result I think pam_unix can authenticate against those. > > This is not the same as authenticating by LDAP bind, but may end up > accepting the same passwords. If you want every process to read your hashed passwords and you use non-portable crypt hashes it could work. The correct solution would be authenticate users by LDAP binds without allowing anyone to read the password or to use the {SASL} password style and authenticate users against Kerberos with saslauthd. Just don't let you users play with passwords. Either your password policy allows dumb users to pick trivial password or it forces complex password structures on them resulting in post-it notes with passwords around every second desk. From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 01:44:04 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1CDF3EB5; Tue, 16 Jul 2013 01:44:04 +0000 (UTC) (envelope-from pali.gabor@gmail.com) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by mx1.freebsd.org (Postfix) with ESMTP id C084F765; Tue, 16 Jul 2013 01:44:03 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id wc20so128981obb.4 for ; Mon, 15 Jul 2013 18:44:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=eiU0bHWt2PPCjM/f+XHAGONCb7ChhI/9TwJD/Gh0hHc=; b=g+wwmm2u5iOxvdmqubZhGD8TRdKg+iqd0w6wGLi0Fafcq7s2cfuT1C1CLJkObkHX8j QQRpox7WcciSYk/Jz1D0b+HcklzIzG8xoWUH68Fg8jYv0B2wPw7i47NZGDLZhDVdpDmd +bgHpBL2WqvHEYPjjBAaL7+4uNtIxabmD0HcU9xi50snWwL2t5gfn4841T6oMh9gKfOw qlnhPmE6O9nIyHewnR0UA1T3fmMBt293aBoSmHCpvoGu28ZDPLIOSLlzIzvoa2UmMibs gvMRxyhrZa0tKVnbOueagKJCtIXxt9DpmDG9ZSmKtKPz143HGkj+LCXWQClb4W0llE7+ Gkkw== MIME-Version: 1.0 X-Received: by 10.182.134.229 with SMTP id pn5mr45889080obb.9.1373939043000; Mon, 15 Jul 2013 18:44:03 -0700 (PDT) Sender: pali.gabor@gmail.com Received: by 10.182.27.101 with HTTP; Mon, 15 Jul 2013 18:44:02 -0700 (PDT) Date: Tue, 16 Jul 2013 02:44:02 +0100 X-Google-Sender-Auth: wu2nkY5cC1bAM12UNUjwBy24gyY Message-ID: Subject: FreeBSD Quarterly Status Report, April-June, 2013 From: Gabor Pali To: hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: stable@freebsd.org, current@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 01:44:04 -0000 FreeBSD Quarterly Status Report, April-June 2013 Introduction This report covers FreeBSD-related projects between April and June, 2013. This is the second of four reports planned for 2013. The last three months have been very active for the FreeBSD developer community, including events such as BSDCan and the FreeBSD Developer Summit collocated with it (covered in a separate report, see the BSDCan Developer Summit Special) and BSD-Day 2013. It has also seen improvements from the top to the bottom of the FreeBSD system. Desktop users will be pleased to note work on improving the state of AMD GPUs and making the console interaction with kernel mode setting -- required for recent xorg drivers -- cleaner and from continued work to make binary packages easier to use. Developers will note continued improvements to our toolchain, with a new debugger being prepared for integration. Server users will benefit from various improvements to virtualization support and scalability in the kernel. Of course, the FreeBSD system is nothing without applications to run atop it, and this quarter has seen some tireless work by members of the ports team to ensure that users have a wide choice of desktop and development environments, with highlights from the GNOME, KDE, Xfce, and Haskell teams in this report. Thanks to all the reporters for the excellent work! This report contains 33 entries and we hope you enjoy reading it. The deadline for submissions covering between July and September, 2013 is October 7th, 2013. __________________________________________________________________ FreeBSD Team Reports * FreeBSD Core Team * FreeBSD Postmaster Team * FreeBSD Release Engineering Team * FreeBSD Security Team Projects * PC-BSD * Virtual Private Systems Kernel * AMD GPU Kernel Mode-setting Support * Improved TCP SYN Cookies * Multi-threaded Pagedaemon * Native iSCSI Stack * Newcons Reboot * Realtek RTL8188CU/RTL8192CU USB Wireless Driver * SDIO Driver * V4L2 Update in the Linuxulator * Wireless Networking Improvements * Xen Support Improvements * ZFS TRIM and Enhanced BIO_DELETE Support Architectures * Intel IOMMU (VT-d, DMAR) Support * Superpages for ARMv7 Userland Programs * bsdconfig(8) and sysrc(8) * bsnmpd(1) Support in hastd(8) * Capsicum * LLDB Debugger Port Ports * FreeBSD Haskell Ports * GNOME/FreeBSD * KDE/FreeBSD * Xfce/FreeBSD * xorg on FreeBSD Documentation * Upgrading the Documentation Set to DocBook 5.0 Events * BSD-Day 2013 Google Summer of Code * New Capsicum Features * Qt and GTK+ Frontends for pkg(8) Miscellaneous * The FreeBSD Foundation __________________________________________________________________ AMD GPU Kernel Mode-setting Support URL: https://wiki.freebsd.org/AMD_GPU Contact: Jean-S=C3=A9bastien P=C3=A9dron Contact: Konstantin Belousov Due to non-FreeBSD-related activities from April to end of June, the project progressed slowly: * Some important problems in TTM were fixed and several others are being worked out. Applications affected by these bugs are non-linear video editing software (which do not use Xv to preview the video) or "screen" of VirtualBox, for instance. * Regarding the locking issue with OpenGL, no work has been done yet. glxgears works but some modern desktop environments or WebGL demos hang. Once TTM bugs described above are fixed, this is the next target. * Patches to Mesa to make it build out-of-the-box were submitted upstream. As of writing, some were committed but not all of them. Additionally, as result of a joint work with Jonathan Gray (of OpenBSD), Mesa should work on FreeBSD, OpenBSD, and hopefully on other BSD flavors without additional patches. Several users tested the driver. Andriy Gapon, Jonathan Gray, and Mark Kettenis (of OpenBSD) submitted patches. kyzh kindly donated several discrete cards from different series. A big thanks to all those contributors! The driver is still not stable enough for a wider call for testers. Open tasks: 1. Write instructions for the wiki to explain how to test the driver. __________________________________________________________________ BSD-Day 2013 URL: http://bsdday.eu/2013 URL: http://www.youtube.com/playlist?list=3DPLJJHfhjb5TOjB-sHRwJBGWd8XA7= nc1gk_ URL: https://picasaweb.google.com/116452848880746560170/BSDDay2013?authk= ey=3DGv1sRgCNvIoMWoxNTRYw Contact: G=C3=A1bor P=C3=A1li The BSD-Day is a now recurring excuse for BSD developers and users to meet up in person, share some beers and talk about what they are working on these days. There was a detour this year to visit the beautiful city of Naples of Italy, the home of pizza. Fortunately, the event has again gained support from numerous and generous sponsors, such as The FreeBSD Foundation, the EMC Corporation, iXsystems, FreeBSDMall, BSD Magazine, and many others which enabled us to cover the costs of travel and accommodation for the speakers. We are really grateful for this. Similarly to the previous years, the whole event started with a dinner in the downtown (somewhere around the Irish Pub) on Friday which suddenly turned into a do-it-yourself pizza-fest. Then it was followed by the Saturday event at the Institute of Biostructures and Bioimaging. There we had a lot of attendees for the associated BSDA exam in the morning -- 8 persons. The event itself had many interesting topics as well, for example moving MCLinker into the BSD world, organization and culture of the FreeBSD Project, the new callout(9) framework, building and testing ports with Poudriere and Tinderbox, FreeBSD in the embedded space, or building reliable VPN networks with OpenBSD. See the links in the report for more. __________________________________________________________________ bsdconfig(8) and sysrc(8) URL: http://druidbsd.sourceforge.net/ Contact: Devin Teske New utilities have been introduced in FreeBSD base system: bsdconfig(8) and sysrc(8). bsdconfig(8) is a replacement for the post-install abilities of deprecated sysinstall(8), while sysrc(8) is a robust utility for managing rc.conf(5) from the command line without a text editor. __________________________________________________________________ bsnmpd(1) Support in hastd(8) Contact: Mikolaj Golub A hastd(8) module for bsnmpd(1) has been committed to FreeBSD head and merged to the stable/8 and stable/9 branches recently. This module makes it possible to monitor and manage hastd(8) via the SNMP protocol. __________________________________________________________________ Capsicum URL: http://www.cl.cam.ac.uk/research/security/capsicum/ URL: https://lists.cam.ac.uk/mailman/listinfo/cl-capsicum-discuss Contact: Pawel Jakub Dawidek Contact: Capsicum Mailing List Capsicum, a lightweight OS capability and sandboxing framework, is being actively worked on. In the last few months the following tasks have been completed: * Committed Capsicum overhaul to FreeBSD head (r247602). This allows to use capability rights in more places, simplifies kernel code and implements ability to limit ioctl(2) and fcntl(2) system calls. * hastd(8) is now using Capsicum for sandboxing, as whitelisting ioctls is possible (r248297). * auditdistd(8) is now using Capsicum for sandboxing, as it is now possible to setup append-only restriction on file descriptor (available in Perforce). * Implemented connectat(2) and bindat(2) system calls for UNIX domain sockets that are allowed in capability mode (r247667). * Implemented chflagsat(2) system call (r248599). * Revised the Casper daemon for application capabilities. * Implemented libcapsicum for application capabilities. * Implemented various Casper services to be able to use more functionality within a sandbox: system.dns, system.pwd, system.grp, system.random, system.filesystem, system.socket, system.sysctl. * Implemented Capsicum sandboxing for kdump(1) (from r251073 to r251167). The version in Perforce also supports sandboxing for the -r flag, using Casper services. * Implemented Capsicum sandboxing for dhclient(8) (from r252612 to r252697). * Implemented Capsicum sandboxing for tcpdump(8) (available in Perforce). * Implemented Capsicum sandboxing for libmagic(3) (available in Perforce). * Implemented the libnv library for name/value pairs handling in the hope of wider adaptation across FreeBSD. For Capsicum-based sandboxing in the FreeBSD base system, the commits referenced above and the provided code aim to serve as examples. We would like to see more FreeBSD tools to be sandboxed -- every tool that can parse data from untrusted sources, for example. This requires deep understanding of how the tool in question works, not necessarily only Capsicum. This work is being sponsored by The FreeBSD Foundation. Open tasks: 1. Get involved, make the Internet finally(!) a secure place. Contact us at the cl-capsicum-discuss mailing list, where we can provide guidelines on how to do sandboxing properly. The fame is there, waiting. __________________________________________________________________ FreeBSD Core Team Contact: FreeBSD Core Team In the second quarter of 2013, the Core Team approved a new Security Officer, Dag-Erling Sm=C3=B8rgrav and his deputy, Xin Li. The Core Team acknowledges Simon Nielsen, the outgoing Security Officer, for his work in the role. Peter Wemm took the lead on the reorganization and administration of the FreeBSD cluster, and with the Core Team's approval, Glen Barber and Ryan Steinmetz were welcomed to the cluster administration team. Based on the recommendation and experiences of Martin Wilke, the Core Team also supported establishing a liaison role between port managers and release engineers in order to improve their communication, especially for preparing releases. The Core Team welcomes Bryan Drewery to this role. Following up on the request from Eitan Adler, the Core Team agreed to remove CVS from the base system, which was soon followed by importing a lightweight version of Subversion tools, implemented by Peter Wemm. There were src commit bits issued for 3 new developers and 1 existing committer received extension in this quarter. __________________________________________________________________ FreeBSD Haskell Ports URL: http://wiki.freebsd.org/Haskell URL: https://github.com/freebsd-haskell/ports/ URL: http://haskell.inf.elte.hu/packages/ Contact: G=C3=A1bor P=C3=A1li Contact: Ashish SHUKLA We are proud to announce that the FreeBSD Haskell Team has updated the Haskell Platform to 2013.2.0.0, GHC to 7.6.3, as well as updated existing ports to their latest stable versions. In this update, we provided experimental support for LLVM-based code generation (disabled by default) to Haskell ports. We also added a number of new ports, which brings their count in the FreeBSD Ports Collection to 402, and now Haskell ports play nicer with portmaster(8)-based upgrades. In cooperation with Konstantin Belousov and Dimitry Andric, we have managed to unbreak the build of GHC on 32-bit 10.x systems, so we have packages for 10.x again. However, it turned out that this bug (in thread signal delivery) can also affect the building process for other platforms as well, which explains some of the strange build breakages our users experienced in the past. We have also learned that there is ongoing work in the GHC upstream which will allow us to provide support for building with Clang natively once GHC 7.8 becomes part of the Haskell Platform. Open tasks: 1. Test experimental Clang/LLVM code generation support to enable it by default. 2. Commit pending Haskell ports to the ports tree. 3. Port more (popular) Cabal packages. __________________________________________________________________ FreeBSD Postmaster Team Contact: FreeBSD Postmaster Team In the second quarter of 2013, the FreeBSD Postmaster Team has implemented the following items that may be interest of the general public: * With help from clusteradm, found that unbound (the resolver used on mx1 and mx2) is configured to perform DNSSEC validation which implies that if a signed zone fails validation, unbound refuses to use the information. This had caused one person to be unable to exchange email with FreeBSD.org until the zone signatures were refreshed. * Created the freebsd-dtrace mailing list, requested by George Neville-Neil. * Resurrected the freebsd-testing mailing list, requested by Garrett Cooper. * Created the freebsd-tex mailing list, requested by Hiroki Sato. * In response to another comment that our message rejection message was unclear in the case that greylisting was the reason, re-worded that message. * Augmented the allowable MIME types for secteam with the following to permit sending encrypted messages: + application/pgp-encrypted + application/pkcs7-encrypted + application/x-pkcs7-encrypted + multipart/encrypted * Began replacing freebsd-mozilla with freebsd-gecko. __________________________________________________________________ FreeBSD Release Engineering Team URL: http://www.freebsd.org/releases/8.4R/errata.html URL: http://www.freebsd.org/releases/9.2R/schedule.html Contact: FreeBSD Release Engineering Team The FreeBSD 8.4-RELEASE cycle completed on June 7, 2013, approximately two months behind the original schedule. Please be sure to read the Errata Notices for any post-release issues discovered after 8.4-RELEASE. The FreeBSD 9.2-RELEASE process will begin July 6, 2013. Unless any critical issues arise, FreeBSD 9.2-RELEASE is expected to be available late August or early September. Users tracking the FreeBSD 9.X branch are encouraged to test the -BETA and -RC builds whenever possible, and provide feedback and report issues to the freebsd-stable mailing list. __________________________________________________________________ FreeBSD Security Team Contact: FreeBSD Security Team On April 15th Dag-Erling Sm=C3=B8rgrav and Xin Li took over as security officers for the FreeBSD Project, and the team welcomed Qing Li back to the team in June. This report briefly summarizes the work of the Security Team from April until the end of June. The Security Team has released the following advisories: * FreeBSD-SA-13:05.nfsserver: Insufficient input validation in the NFS server (nfsd(8)), reported by Adam Nowacki. * FreeBSD-SA-13:06.mmap: Privilege escalation via mmap(), reported by Konstantin Belousov. The Security Team has contributed to the following errata notices: * FreeBSD-EN-13:02.vtnet: Frames are not properly forwarded to vtnet(4) when two or more MAC addresses are configured on QEMU 1.4.0 and later in 8.4-RELEASE, reported by Julian Stecklina. * FreeBSD-EN-13:01.fxp: Initialization of fxp(4) network interfaces results in an infinite loop with dhclient(8) in 8.4-RELEASE, reported by Michael L. Squires. Per the request of Baptiste Daroussin, the Security Team has also reviewed the source code of Poudriere, the port build and test system which is planned to be used for producing pkg(8) ("new-style") packages on the FreeBSD cluster. __________________________________________________________________ GNOME/FreeBSD URL: http://www.FreeBSD.org/gnome/ Contact: FreeBSD GNOME Team The GNOME 3.6 work is moving along slowly but steadily. Almost all the GNOME 3 desktop ports were updated to their corresponding 3.6 versions. A big challenge was taken by getting the webkit-gtk3 port updated to 2.0.3. Currently programs using webkit-gtk3 crash on launch. It is hard to find the causes as the debug build of webkit-gtk either runs out of memory or disk space on the developement system used. Open tasks: 1. Update the FreeBSD GNOME website with recent changes in the ports tree, add new items in preparation for GNOME 3 and Mate, etc. 2. Merge Glib 2.36, GTK+ 3.8 and related ports back to the Ports Collection. 3. Continue work on GNOME 3.6, fix bugs and write code for missing features. 4. Complete the port of MATE. __________________________________________________________________ Improved TCP SYN Cookies URL: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D28838+0+current/free= bsd-net URL: http://people.freebsd.org/~andre/syncookie-20130708.diff Contact: Andre Oppermann We have had a SYN cookie implementation for quite some time now but it has some limitations with current realities for window scaling and SACK encoding the in the few available bits. This patch updates and improves SYN cookies mainly by: 1. Encoding of MSS, WSCALE (window scaling) and SACK into the ISN (initial sequence number) without the use of timestamp bits. 2. Switching to the very fast and cryptographically strong SipHash-2-4 hash MAC algorithm to protect the SYN cookie against forgery. The common parameters used on TCP sessions have changed quite a bit since SYN cookies were invented some 17 years ago. Today we have a lot more bandwidth which makes use of window scaling almost mandatory. Also SACK has become standard as it makes recovering from packet loss much more efficient. The original SYN cookies method only stored an indexed MSS value in the cookie. This obviously is not sufficient any more and breaks in the presence of WSCALE. WSCALE information is only exchanged during SYN and SYN-ACK. If we cannot keep track of it then we severely underestimate the available send or receive window, compounded with the fact that with large window scaling the window size information on the TCP segment header would be even lower numerically. A number of years back, SYN cookies were extended to store the additional state in the TCP timestamp fields, if available on a connection. It has been adopted by Linux as well. While timestamps are common among the BSD, Linux and other Unix systems, Windows never enabled them by default, thus they are not present for the vast majority of clients seen on the Internet. The new improvement in this patch moves all necessary information into the ISN again, removing the need for timestamps. Both the MSS and send WSCALE are stored in 3 bit indexed form together with a single bit for SACK. While we cannot represent all possible MSS and WSCALE values in only 3 bits each (both are 16-bit fields in the TCP header), it turns out that is not actually necessary. These improvements allow one to run with SYN cookies only on Internet-facing servers. However while SYN cookies are calculated and sent all the time, they are only used when the syn cache overflows due to attacks or overload. In that case though, you can rest assured that no significant degradation in TCP connection setup happens any more and that even Windows clients can make use of window scaling and SACK. Open tasks: 1. Additional testing on busy servers. __________________________________________________________________ Intel IOMMU (VT-d, DMAR) Support URL: http://www.intel.com/content/www/us/en/intelligent-systems/intel-te= chnology/vt-directed-io-spec.html URL: http://lists.freebsd.org/pipermail/freebsd-arch/2013-May/014368.htm= l URL: http://people.freebsd.org/~kib/misc/dmar.1.patch Contact: Konstantin Belousov Intel VT-d is a set of extensions that were originally designed to allow virtualizing devices. It allows safe access to physical devices from virtual machines and can also be used for better isolation and performance increases. A VT-d driver was developed that implements the busdma(9) interface using the DMA Remap units (DMARs) found in current Intel chipsets. The driver provides reliability and security improvements for the system by facilitating restricted access to main memory from busmastering devices. It also eliminates bounce buffering (copying) by allocating remapped regions that satisfy a device's access limitations. With additional work to define a suitable interface the VT-d driver will also provide PCI pass-through functionality for hypervisors. This project is sponsored by The FreeBSD Foundation. Open tasks: 1. Implement workarounds for chipset errata. 2. Commit to HEAD after additional testing. 3. Rebalance MSI/MSI-X using interrupt remapping unit, also required for x2APIC use on big machines. 4. Integrate with the Intel GPU MMU and handle Ironlake and SandyBridge errata for the GFXVTd unit. 5. Provide an interface for VMM (hypervisors). 6. Consider implementing a driver for AMD's IOMMU. __________________________________________________________________ KDE/FreeBSD URL: http://FreeBSD.kde.org URL: http://FreeBSD.kde.org/area51.php Contact: KDE FreeBSD The KDE/FreeBSD Team has continued to improve the experience of KDE software and Qt under FreeBSD. During this quarter, the team has kept most of the KDE and Qt ports up-to-date, working on the following releases: * KDE SC: 4.10.2, 4.10.3, 4.10.4 * Qt: 5.0.2 (area51) * PyQt: 4.10.2; QScintilla 2.7.2; SIP: 4.14.7 * KDevelop: 4.5.1 * Calligra: 2.6.2 * CMake: 2.8.11.1 * Digikam (and KIPI-plugins): 3.1.0, 3.2.0 * KDE Telepathy: 0.6.0, 0.6.1 As a result -- according to PortScout -- kde@ has 473 ports (up from 431), of which 98.73% are up-to-date (up from 93.5%). iXsystems Inc. continues to provided a machine for the team to build packages and to test updates. iXsystems Inc. has been providing the KDE/FreeBSD Team with support for quite a long time and we are very grateful for that. This quarter, we would also like to thank Steve Wills (swills@) for providing access to another machine so that we can do our work even faster. While a great deal of the team's efforts are focused towards packaging released code, we also take a proactive stand in making sure future versions of the software we port is also going to work well on FreeBSD. This involves being in close contact with upstream, raising awareness of FreeBSD as an active project and also sending actual patches that most of the time benefit many other operating systems besides FreeBSD itself. In this regard, we have been dedicating a lot of time making sure both clang and libc++ are fully supported in KDE and Qt. Not only has this resulted in many patches being sent to these projects, but the exposure to these large code bases have been beneficial to the Clang-on-FreeBSD project as well. Dimitry Andric (dim@) has been of great help as a point of contact for all the issues we have faced. As usual, the team is always looking for more testers and porters so please contact us and visit our home page. It would be especially useful to have more helping hands on tasks such as getting rid of the dependency on the defunct HAL project and providing integration with KDE's Bluedevil Bluetooth interface. Open tasks: 1. Update out-of-date ports, see PortScout for a list. 2. Work on KDE 4.11 and Qt 5. 3. Make sure the whole KDE stack (including Qt) builds and works correctly with clang and libc++. 4. Remove the dependency on HAL. __________________________________________________________________ LLDB Debugger Port URL: https://wiki.freebsd.org/lldb Contact: Ed Maste LLDB is the the debugger project in the LLVM family. It supports the Mac OS X, Linux, and FreeBSD platforms, but the latter has recently suffered under a lack of maintenance. After cleaning bit rot in LLDB's FreeBSD support, it again builds and can be used for basic debugging of single-threaded applications. The test suite also runs to completion, although it experiences a large number of failures. Ed Maste has been granted an LLDB commit bit, and is now committing ongoing bug fixes and development directly to the upstream repository. There is a significant amount of work still to be done, with one goal being the incorporation of lldb into the base system. This project is sponsored by DARPA/AFRL in collaboration with SRI International and the University of Cambridge. Open tasks: 1. Add support for multithreaded processes. 2. Fix watchpoints. 3. Add support for remote debuging (gdbserver / debugserver). 4. Add support for core files. 5. Add support for kernel debugging. 6. Verify i386 and ARM architectures. 7. Implement MIPS target support. 8. Verify cross-debugging. 9. Investigate and fix test suite failures. 10. Prepare lldb for incorporation into the base system. __________________________________________________________________ Multi-threaded Pagedaemon URL: http://people.freebsd.org/~kib/misc/pagedaemon-numa.1.patch Contact: Konstantin Belousov This project aims to improve scalability of the virtual memory subsystem. Based on a prototype change from Jeff Roberson, per-domain page queues and per-domain pagedaemon working threads have been implemented to enable this. At the moment, the domains coincide with the NUMA proximity domains, but this is not neccessary and could be improved with further separation to allow more parallelism in the pagedaemon. The patch is relatively simple, with the most delicate parts being the page laundry and OOM logic, which requires coordination between all pagedaemon threads to prevent false triggering. Testing on diverse workloads and on real multi-socket machines is required. This project is sponsored by The FreeBSD Foundation. Open tasks: 1. Debug on multi-domain NUMA machine. 2. Test, get review and commit. __________________________________________________________________ Native iSCSI Stack URL: https://wiki.freebsd.org/Native%20iSCSI%20target Contact: Edward Tomasz Napiera=C5=82a The native kernel iSCSI target and initiator project progressed well over the April to June period. The primary focus was to introduce support for iSER (iSCSI over RDMA) in both the initiator and the target. Prerequisite for this was merging some common parts together and implementing a workaround for the lack of iSER support in userspace. Apart from that, there were a myriad of smaller improvements. Such as creating more user-friendly administration utilities, for example iscsictl(8) which displays SCSI device nodes for each iSCSI session. This frees the user from getting the same information through camcontrol(8). There are also improvements in logging and manual pages. Once the iSER support becomes stable, the work will focus on performance optimizations. The plan is to commit both the new initiator and target in August to allow shipping them in 10.0. The project will continue with implementing support for software iWARP stack (useful mostly for testing and development), SCSI passthrough and various other improvements. This project is being sponsored by The FreeBSD Foundation. Open tasks: 1. Performance optimization. 2. Merge to FreeBSD head. __________________________________________________________________ New Capsicum Features URL: https://wiki.freebsd.org/SummerOfCode2013/CapsicumFeatures Contact: Mariusz Zaborski Contact: Pawel Jakub Dawidek Capsicum is a lightweight OS capability and sandboxing framework implemented in FreeBSD. This is still a new technology, so there is a lot of space for improvements. Thanks to the Google Summer of Code program and Pawel Jakub Dawidek for volunteering as mentor, Mariusz will have the chance to work on this project in the summer. The work on sandboxing the rwho(1) and rwhod(8) utilities was completed recently. There is also a plan to implement two new modules for Casper. Casper is a daemon to provide services for applications using Capsicum's capability mode. Some experimentation with implementing two new capability rights is in progress, so is porting one more program to use the existing features of the Capsicum framework. Open tasks: 1. system.unix -- a Casper module provides connect and listen on Unix domain socket. 2. system.udp -- a Casper module enabling connect, listen, send, and receive of UDP packets. 3. Implementing sandboxing for fetch(1). 4. Introduce new capability rights: CAP_SEND_RIGHTS and CAP_RECV_RIGHTS. __________________________________________________________________ Newcons Reboot Contact: Aleksandr Rybalko The purpose of the Newcons project is to provide a new interface for console and video output to graphic devices. This will allow simple drivers access the console and terminal mode early, and framebuffer access for xorg. Drivers will not need embedded font bitmaps, color maps, or mouse cursor bitmaps, as the whole infrastructure will be provided by the vt(4) Newcons driver. As the project includes Kernel Mode Setting (KMS) integration, one of the goals is support for modern Xorg releases, allowing the kernel to switch back to virtual terminal mode after graphics mode or resolution used with xorg changes. There are a lot of changes involved in the project. Main tasks include: * Core functionality (almost done). * Mouse support. * KMS (kernel mode setting) support. * USB keyboard support. * Splash screen support (partially working). * Driver support. * vidcontrol(1) support. The first deliverables of the project, including moused(8), ukbd(4), and KMS support are expected to arrive around the middle or end of August 2013. The whole project is expected to complete in November 2013. This project is being sponsored by The FreeBSD Foundation. Many thanks to Ed Schouten who started Newcons project and did most of the work. Open tasks: 1. Provide different flavors of hardware for testing the implementation. Do not hesitate to volunteer when a call for testing is announced. __________________________________________________________________ PC-BSD URL: http://www.pcbsd.org Contact: Kris Moore Progress on moving PC-BSD & TrueOS to a "rolling release" is happening quickly. We have implemented our own package repository, fully based on pkg(8), which is updated twice monthly, and are now hosting dedicated freebsd-update(8) systems. In addition to the 9.1-RELEASE ISO images, we have begun to create a 9-STABLE branch as well, using freebsd-update(8) to push out the latest world and kernel binaries on a monthly basis. We are currently working on an implementation of ZFS Boot Environments for desktops and servers. These users to install updates or experimental versions in separate ZFS clones and select the one to run at boot time, providing an easy way of testing upgrades before deployment. __________________________________________________________________ Qt and GTK+ Frontends for pkg(8) URL: https://wiki.freebsd.org/SummerOfCode2013/pkgQtGtk Contact: Justin Muniz Contact: Eitan Adler This project is part of Google Summer of Code. Work has only just begun, and the code is in its infancy. The Subversion repository holds experimental code that is actively being developed. Development should be concluded before the end of September, and the project will enter the maintenance phase of its life cycle. Open tasks: 1. Work with Matt Windsor to create a pkg(8) backend for PackageKit. 2. Extend PackageKit's Qt frontend to offer more functionality through pkg(8). 3. Extend PackageKit's GKT+ frontend to offer more functionality through pkg(8). __________________________________________________________________ Realtek RTL8188CU/RTL8192CU USB Wireless Driver Contact: Rui Paulo Contact: Kevin Lo The urtwn(4) driver was imported from OpenBSD. This is a driver for very small Realtek USB WiFi cards which are pretty inexpensive and can do 802.11n at the maximum theoretical speed of 150 Mbps. They make a good addition to embedded systems such as the Raspberry Pi and the BeagleBone. The driver requires firmware that is available in the FreeBSD Ports Collection (net/urtwn-firmware-kmod). Note that 802.11n is not yet supported. __________________________________________________________________ SDIO Driver URL: https://wiki.freebsd.org/SDIO URL: https://github.com/kibab/freebsd/tree/kibab-dplug Contact: Ilya Bakulin SDIO is an interface designed as an extension for the existing SD card standard, to allow connecting different peripherals to the host with the standard SD controller. Peripherals currently sold at the general market include WLAN/BT modules, cameras, fingerprint readers, barcode scanners. The driver is implemented as an extension to the existing MMC bus, adding a lot of new SDIO-specific bus methods. Getting information about the card works, including querying all the supported I/O functions. Simple byte transfers and multi-byte reads work. A prototype of the driver for Marvell SDIO WLAN/BT module is also being developed, using the existing Linux driver as a reference. Open tasks: 1. Extend MMC bus interface with more SDIO-specific bus methods to allow child drivers to perform multi-byte in/out transfers. 2. Write firmware loading code for the prototype of the WLAN driver. Further work on the WLAN driver should probably be done as a separate project. 3. Implement detach path. It has not been tested yet because the DreamPlug hardware available does not have an external SDIO-capable slot. __________________________________________________________________ Superpages for ARMv7 URL: http://static.usenix.org/events/osdi02/tech/full_papers/navarro/nav= arro.pdf URL: https://wiki.freebsd.org/ARMSuperpages URL: https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.g= it Contact: Zbigniew Bodek Contact: Grzegorz Bernacki Contact: Rafa=C5=82 Jaworowski The ARM architecture is becoming more and more prevalent, with increasing usage beyond the mobile and embedded space. Among the more interesting industry trends emerging in the recent months, there has been the concept of "ARM server". Some top-tier companies, e.g. Dell and HP, have already started to develop such systems. Key to success of FreeBSD in these new areas is dealing with the sophisticated features of the platform, for example adding support for superpages. The objective of this project is to enable FreeBSD/arm to utilize superpages which would allow efficient use of TLB translations (by enlarging TLB coverage), leading to improved performance in many applications and scalability. This is intended to work on ARMv7-based processors, however compatibility with ARMv6 will be preserved. The following steps have been made since the last status report: * Implement pmap_copy() to support fork() system calls. * Support for multiple page sizes. * Implement superpage creation, promotion, demotion, and eviction mechanisms. * Implement PV entry management for superpages. * Partially integrate code to the head branch. Next steps: * Test and benchmark. * Complete integration into FreeBSD head. This project is jointly sponsored by The FreeBSD Foundation and Semihalf. Open tasks: 1. Start utilizing superpages on ARMv6/v7. 2. Find bugs and debug. __________________________________________________________________ The FreeBSD Foundation URL: http://www.FreeBSDFoundation.org/ Contact: Deb Goodkin We started the quarter with our "Raise a Million -- Spend a Million" Spring Fundraiser. This was the first of three major fundraisers scheduled for the year. We were pleased to have raised $365,291 by the end of the campaign -- May 31. Last year, by the same time, we had raised only $56,196. We have started this year off with a much better fundraising strategy. We want to send a big thank you to everyone out there that has made a donation in 2013. Your early donations have made a significant impact on our fundraising endeavors so far this year. Some things we accomplished this last quarter are: * Attended BSDCan in Ottawa, Texas LinuxFest in Austin, SouthEast LinuxFest in Charlotte, and ICANN 46 meeting in Beijing. * We were a Gold Sponsor for BSDCan 2013 and sponsored 7 developers to attend the conference. * We signed up to be a Platinum Sponsor for EuroBSDCon 2013. * We sponsored 1 developer to attend OpenHelp. * Recognized Mark Linimon, Simon L. B. Nielsen, Bjoern A. Zeeb, and Ken Smith, at BSDCan, for their significant contributions to FreeBSD. We also recognized Dan Langille for his tireless effort of putting on BSDCan for 10 years. * We sponsored the developer and vendor summits at BSDCan, with 100 and 30 attendees respectively. * We sponsored BSD-Day 2013 that was held in Naples, Italy on April 6. * We held our annual board meeting in Ottawa. * We sponsored the following projects: Capsicum, ARM Superpages, iSCSI, Page Queue Locking, Input/Output Memory Management Unit, Documentation project infrastructure, and writing white papers. * We hired Edward Tomasz Napieral/a as the second member of our technical staff to work on FreeBSD projects full-time. * We hired Ed Maste as Director of Project Development. * With our continued support of building out the FreeBSD infrastructure, we purchased high-end servers for the Sentex Lab to be used with the latest 40 Gbps Ethernet cards from Chelsio to do performance testing and analysis, smaller servers for firewalls for NYI and ISC, and cables to connect our Juniper switches together into a bigger Juniper switch we purchased for NYI. __________________________________________________________________ Upgrading the Documentation Set to DocBook 5.0 Contact: G=C3=A1bor K=C3=B6vesd=C3=A1n The Documentation Project has been using old versions of markup standards until recently when we switched to a real XML toolchain and DocBook 4.5. However, we still depend on obsolete technologies -- DSSSL and Jade. DocBook 5.0 provides cleaner markup and some nice new features. The objective of this project is to upgrade the documentation set to DocBook 5.0 and to find a way to properly render our sources without using DSSSL, since the DSSSL stylesheets are discontinued and cannot render DocBook 5.0. The documentation sources have already been successfully transformed to DocBook 5.0 and updates to the rendering process are under development. The common opinion among FreeBSD developers is that Java is a heavy dependency that should be avoided. This has suggested the transformation of DocBook sources to TeX and use TeX as a rendering backend. There are two ways to do this; the sources can be transformed either directly or through the XSL FO output generated by the stylesheets provided for the DocBook Project. The latter approach has been chosen as a preferred way since it better fits the existing documentation infrastructure and provides easier customization. This project is generously funded by The FreeBSD Foundation. Open tasks: 1. Finish the implementation of the rendering process. 2. Integrate the rendering solution into the infrastructure. 3. Merge back changes to head. __________________________________________________________________ V4L2 Update in the Linuxulator Contact: Alexander Leidinger The V4L2 support in the linuxulator was updated in FreeBSD head. This lets Skype v4 display video. Open tasks: 1. Find out why audio in Skype v4 stops working after some calls. __________________________________________________________________ Virtual Private Systems URL: http://www.7he.at/freebsd/vps/ URL: http://svnweb.freebsd.org/base/projects/vps/ Contact: Klaus Ohrhallinger VPS for FreeBSD is an OS-level based virtualization implementation that supports advanced features like live migration. It has been recently imported into the Project's Subversion repository as a project branch. The code is currently of alpha quality. Open tasks: 1. Test with many different guest setups/applications. All feedback is highly appreciated. __________________________________________________________________ Wireless Networking Improvements Contact: Adrian Chadd Recently the FreeBSD wireless networking stack has received updates in the following areas: * Improved transmit locking in net80211(4) to eliminate a whole class of subtle race conditions leading to out-of-order packets being handed to the driver. * Spectral scan (FFT) information is now available for the AR9280, AR9285, AR9287 series NICs. * Added support for AR93xx, AR94xx, AR95xx NICs -- hostap, adhoc and station modes have been tested, including 3x3 stream support for the those NICs where appropriate. * Implemented ps-poll handling in hostap mode. This was required for correct behaviour with stations that implement aggressive power save. * Added AR933x SoC support -- including all on-board peripherals -- the 8devices.com Carambola-2 board is now fully supported and will run FreeBSD from NOR flash. __________________________________________________________________ Xen Support Improvements URL: http://xenbits.xen.org/gitweb/?p=3Dpeople/royger/freebsd.git;a=3Dsu= mmary Contact: Justin T. Gibbs Contact: Will Andrews Contact: Andre Oppermann Contact: Roger Pau Monn=C3=A9 FreeBSD Xen HVM can be further improved by using more PV interfaces inside a HVM guest. So far the following items have been completed: * Update Xen interface files. (Merged into head) * Add support for the vector callback injection mechanism. This replaces the PCI interrupt and provides a per-cpu callback, which was not possible when using the PCI interrupt. * Rework event channel implementation and use the same code paths for both PV and PVHVM. * Implement PV one-shot event timers and timecounters. * Implement PV IPIs. * Live migration support for PV timers and PV IPIs. With this changes, FreeBSD will have a complete PVHVM port, this will also set the ground for a future PVH port (when PVH support is merged into Xen). PVHVM allows a virtual machine that boots as a native guest to be able to take full advantage of paravirtualized drivers, giving a performance improvement in most I/O related tasks. PVH allows a guest to take advantage of hardware assistance for memory management, but uses fully paravirtualized events and boot procedure, which brings two significant advantages beyond performance. The first is that domain 0 does not have to run a QEMU instance for emulated boot for PVH guests, which is a common reason for hosting providers to charge more for Windows and other HVM guests. The second is that PVH domains can be used as domain 0, without requiring different pmap (memory management) code from the conventional kernel. This will allow us to ship a single kernel binary supporting bare metal hardware, running as a Xen unprivileged guest, and eventually as Xen domain 0. Further improvements on blkfront and netfront have also been commited: * Fix netfront crash when detaching an interface. * Enable netfront to specify a maximum TSO length limiting the segment chain to what the Xen host side can handle after defragmentation. * Add barriers and flush support to blkfront. Netfront changes have been merged to stable branches, blkfront changes are only in head. Open tasks: 1. Merge remaining changes into head. __________________________________________________________________ Xfce/FreeBSD URL: https://wiki.freebsd.org/Xfce Contact: FreeBSD Xfce Team The FreeBSD Xfce Team has updated its ports to the latest stable releases, especially: * Core (mostly bugfixes and translation updates): * deskutils/xfce4-tumbler (0.1.29) * x11-wm/xfce4-panel (4.10.1) * sysutils/xfce4-settings (4.10.1) * x11-wm/xfce4-session (4.10.1) * sysutils/garcon (0.2.1) * x11/libxfce4util (4.10.1) * x11-wm/xfce4-wm (4.10.1) Applications: * multimedia/xfce4-parole (0.5.1) * www/midori (0.5.2) * deskutils/xfce4-notifyd (0.2.4) * misc/xfce4-appfinder (4.10.1) * x11/xfce4-terminal (0.6.2) * x11-fm/thunar (1.6.3) Panel plugins: * deskutils/xfce4-xkb-plugin (0.5.6) * textproc/xfce4-dict-plugin (0.7.0) * x11-clocks/xfce4-timer-plugin (1.5.0) * x11/xfce4-embed-plugin (new) Thunar plugins: * audio/thunar-media-tags-plugin (0.2.1) * archivers/thunar-archive-plugin (0.3.1) x11/xfce4-embed-plugin can integrate any application window into the Xfce panel. A new plugin is also available which monitors and displays earthquakes, it is called xfce4-equake-plugin. Open tasks: 1. Fix CPU issue with textproc/xfce4-dict-plugin (bug #10103). 2. Investigate why midori-gtk3 crashes too often. (The port is finished, but some libraries are not present by default in ports tree). 3. Fix x11-themes/gtk-xfce-engine with Gtk+ >=3D3.6. __________________________________________________________________ xorg on FreeBSD URL: http://wiki.freebsd.org/Xorg URL: http://trillian.chruetertee.ch/ports/browser/trunk Contact: Contact: Niclas Zeising Contact: Koop Mast During the beginning of this quarter, work focused on making the xorg update as robust and stable as possible in preparation for the merge to ports. As a part of this, ports exp-runs were performed to find and resolve regressions and other issues. Once this was completed, xorg was updated to version 7.7 on May 25, after more than a year of hard work. After the update, work immediately shifted to focus on updating and patching xorg client libraries, since numerous security issues had been identified in those. Unfortunately, this took a little longer than anticipated, but all fixes were comitted eventually. There has also been work on making the new xorg distribution the default for FreeBSD 9.1 and later. A patch was sent out and tested with good results, but this is currently postponed because switching virtual terminals is not working with the KMS driver. Currently, work is focusing on keeping xorg drivers and libraries up to date. Instead of making big updates every year or less, minor updates to some libraries, applications and drivers happen fairly regularly. Focus is also starting to shift towards newer versions of MESA and xorg-server, but this is still very experimental. Open tasks: 1. Continue the porting effort of recent versions of MESA. This is ongoing work, but integrating this into the development repo is hard work. Once this is completed, and KMS support for ATI is more mature, more testing can be done. 2. Port Wayland. The future of graphical environments in open source operating system seems to be Wayland. This needs to be ported to FreeBSD so that a wider audience can test it, and so that it eventually can be integrated into the ports tree, perhaps as a replacement for the current xorg. 3. Look into replacements for HAL. HAL is used for hot-plugging of devices, but it has been long abandoned by Linux. A replacement, perhaps built on top of devd(8), would be nice to have. This work should be coordinated with the FreeBSD GNOME and KDE teams. __________________________________________________________________ ZFS TRIM and Enhanced BIO_DELETE Support Contact: Pawel Jakub Dawidek Contact: Steven Hartland As of the end of June, FreeBSD's ZFS implementation now includes TRIM support in head, stable/9, and stable/8 branches. This allows ZFS to help maintain high performance on flash-based devices such as SSD's even under high-load conditions. When creating new pools and adding new devices to existing pools it first performs a full-device level TRIM to help ensure optimum starting performance. This behaviour can be overridden by setting the vfs.zfs.vdev.trim_on_init sysctl variable to 0 if for example the disks are new or have already been secure erased, which can also now be done using camcontrol(8) security actions. In order to support TRIM, the kernel requires the underlying device driver supports BIO_DELETE. This is currently mapped through to hardware methods such as ATA TRIM and SCSI UNMAP, which are commonly supported by SSDs via CAM. In order to increase the supported hardware base, CAM's SCSI layer was also enhanced to allow ATA TRIM via SATL ATA Passthrough to be used in addition to the existing UNMAP and WS methods. This allows SATA disks attached to SCSI controllers with CAM based drivers such as mps(4) and mpt(4) to provide delete support. Stats for ZFS TRIM can be monitored by looking at the sysctl variables under kstat.zfs.misc.zio_trim in addition to live GEOM delete stats via the gstat -d command. This project was sponsored by Multiplay and implemented by Pawel Jakub Dawidek. __________________________________________________________________ From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 02:28:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4515B627 for ; Tue, 16 Jul 2013 02:28:42 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) by mx1.freebsd.org (Postfix) with ESMTP id E5A378BB for ; Tue, 16 Jul 2013 02:28:41 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6G2SeFg053676; Mon, 15 Jul 2013 22:28:40 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Mon, 15 Jul 2013 22:28:40 -0400 (EDT) Date: Mon, 15 Jul 2013 22:28:40 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Jan Bramkamp Subject: Re: LDAP authentication confusion In-Reply-To: <51E480C3.50008@rlwinm.de> Message-ID: References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> <20130715224748.GA45649@anubis.morrow.me.uk> <51E480C3.50008@rlwinm.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 02:28:42 -0000 On Tue, 16 Jul 2013, Jan Bramkamp wrote: > On 16.07.2013 00:47, Ben Morrow wrote: >> Quoth Jan Bramkamp : >>> On 15.07.2013 21:51, Daniel Eischen wrote: >>>> >>>> Wouldn't it be easier just to edit /etc/nsswitch.conf >>>> anyway? >>> PAM and NSS switch are two different subsystems. NSS is just for >>> resource lookups (users, groups, hosts, ...). PAM is for access control. >>> >>> With ldap in nsswitch.conf for users and groups you can lookup a LDAP >>> user but the user can't log into $service through PAM. This requires >>> pam_ldap.so in pam.d/$service. >> >> The default pam_unix.so calls getpwent, so if nss_ldap returns cryptable >> passwords in its result I think pam_unix can authenticate against those. >> >> This is not the same as authenticating by LDAP bind, but may end up >> accepting the same passwords. > > If you want every process to read your hashed passwords and you use > non-portable crypt hashes it could work. The correct solution would be > authenticate users by LDAP binds without allowing anyone to read the > password or to use the {SASL} password style and authenticate users > against Kerberos with saslauthd. Just don't let you users play with > passwords. Either your password policy allows dumb users to pick trivial > password or it forces complex password structures on them resulting in > post-it notes with passwords around every second desk. I think something is lost on me here. getpwent/getpwuid do not return the password hashes in the returned struct passwd unless the calling process is root. So you have to be root in order to see the hashes anyway. Not all users are going to have access to the hashes, unless your machine's compromised or otherwise allows root privileges to others. -- DE From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 02:33:30 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8A9CA798 for ; Tue, 16 Jul 2013 02:33:30 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:140:72e1::ac16:e45e]) by mx1.freebsd.org (Postfix) with ESMTP id 4F2B58F4 for ; Tue, 16 Jul 2013 02:33:30 +0000 (UTC) Received: from hexe.rlwinm.de (p4FE67BC6.dip0.t-ipconnect.de [79.230.123.198]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id 47355117A0 for ; Tue, 16 Jul 2013 02:33:28 +0000 (UTC) Message-ID: <51E4B0F9.5050200@rlwinm.de> Date: Tue, 16 Jul 2013 04:33:29 +0200 From: Jan Bramkamp User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130707 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: LDAP authentication confusion References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> <20130715224748.GA45649@anubis.morrow.me.uk> <51E480C3.50008@rlwinm.de> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 02:33:30 -0000 On 16.07.2013 04:28, Daniel Eischen wrote: > On Tue, 16 Jul 2013, Jan Bramkamp wrote: > >> On 16.07.2013 00:47, Ben Morrow wrote: >>> Quoth Jan Bramkamp : >>>> On 15.07.2013 21:51, Daniel Eischen wrote: >>>>> >>>>> Wouldn't it be easier just to edit /etc/nsswitch.conf >>>>> anyway? >>>> PAM and NSS switch are two different subsystems. NSS is just for >>>> resource lookups (users, groups, hosts, ...). PAM is for access >>>> control. >>>> >>>> With ldap in nsswitch.conf for users and groups you can lookup a LDAP >>>> user but the user can't log into $service through PAM. This requires >>>> pam_ldap.so in pam.d/$service. >>> >>> The default pam_unix.so calls getpwent, so if nss_ldap returns cryptable >>> passwords in its result I think pam_unix can authenticate against those. >>> >>> This is not the same as authenticating by LDAP bind, but may end up >>> accepting the same passwords. >> >> If you want every process to read your hashed passwords and you use >> non-portable crypt hashes it could work. The correct solution would be >> authenticate users by LDAP binds without allowing anyone to read the >> password or to use the {SASL} password style and authenticate users >> against Kerberos with saslauthd. Just don't let you users play with >> passwords. Either your password policy allows dumb users to pick trivial >> password or it forces complex password structures on them resulting in >> post-it notes with passwords around every second desk. > > I think something is lost on me here. getpwent/getpwuid do > not return the password hashes in the returned struct passwd > unless the calling process is root. So you have to be root in > order to see the hashes anyway. Not all users are going to > have access to the hashes, unless your machine's compromised > or otherwise allows root privileges to others. > If the crypted password can be read by an LDAP client with the information available to every process in (nss_)ldap.conf you're crypted passwords are easily accessible for offline attacks. Their is no reason for an attacker to go through the getpwent/getpwuid API. From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 02:37:34 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5968C8BC; Tue, 16 Jul 2013 02:37:34 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from sarah.protected-networks.net (sarah.protected-networks.net [IPv6:2001:470:1f07:4e1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2696A915; Tue, 16 Jul 2013 02:37:34 +0000 (UTC) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "Iain Michael Butler", Issuer "Protected Networks Certificate Authority" (verified OK)) (Authenticated sender: imb@protected-networks.net) by sarah.protected-networks.net (Postfix) with ESMTPSA id 227106148; Mon, 15 Jul 2013 22:37:33 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=faZ7U1X+ZU/3A+Rhf6xqzS1rNvJPvzHHL9C2u8qyXucYxya2gUjHPKz64juPNM0fY 5J/qmOqCxY57I33GMVaMQ9bg9pRuGaFQB70bAw9NtN4kk+T2SF2Y2N+5Dg9ir3f Message-ID: <51E4B1EB.2000800@protected-networks.net> Date: Mon, 15 Jul 2013 22:37:31 -0400 From: Michael Butler User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130710 Thunderbird/17.0.7 MIME-Version: 1.0 To: Daniel Eischen Subject: Re: LDAP authentication confusion References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> <20130715224748.GA45649@anubis.morrow.me.uk> <51E480C3.50008@rlwinm.de> In-Reply-To: X-Enigmail-Version: 1.5.1 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 02:37:34 -0000 On 07/15/13 22:28, Daniel Eischen wrote: > I think something is lost on me here. getpwent/getpwuid do > not return the password hashes in the returned struct passwd > unless the calling process is root. So you have to be root in > order to see the hashes anyway. Not all users are going to > have access to the hashes, unless your machine's compromised > or otherwise allows root privileges to others. My personal preference is to configure the LDAP server with this fragment in slapd.conf .. # lock down passwords access to attrs=userPassword by self write by anonymous auth by * none .. which achieves everything needed without exposing anything superfluously, imb From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 02:45:01 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 86735AFE for ; Tue, 16 Jul 2013 02:45:01 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) by mx1.freebsd.org (Postfix) with ESMTP id 32C03952 for ; Tue, 16 Jul 2013 02:45:00 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6G2j0Xr063415; Mon, 15 Jul 2013 22:45:00 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Mon, 15 Jul 2013 22:45:00 -0400 (EDT) Date: Mon, 15 Jul 2013 22:45:00 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Jan Bramkamp Subject: Re: LDAP authentication confusion In-Reply-To: <51E4B0F9.5050200@rlwinm.de> Message-ID: References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> <20130715224748.GA45649@anubis.morrow.me.uk> <51E480C3.50008@rlwinm.de> <51E4B0F9.5050200@rlwinm.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 02:45:01 -0000 On Tue, 16 Jul 2013, Jan Bramkamp wrote: > On 16.07.2013 04:28, Daniel Eischen wrote: >> On Tue, 16 Jul 2013, Jan Bramkamp wrote: >> >>> On 16.07.2013 00:47, Ben Morrow wrote: >>>> Quoth Jan Bramkamp : >>>>> On 15.07.2013 21:51, Daniel Eischen wrote: >>>>>> >>>>>> Wouldn't it be easier just to edit /etc/nsswitch.conf >>>>>> anyway? >>>>> PAM and NSS switch are two different subsystems. NSS is just for >>>>> resource lookups (users, groups, hosts, ...). PAM is for access >>>>> control. >>>>> >>>>> With ldap in nsswitch.conf for users and groups you can lookup a LDAP >>>>> user but the user can't log into $service through PAM. This requires >>>>> pam_ldap.so in pam.d/$service. >>>> >>>> The default pam_unix.so calls getpwent, so if nss_ldap returns cryptable >>>> passwords in its result I think pam_unix can authenticate against those. >>>> >>>> This is not the same as authenticating by LDAP bind, but may end up >>>> accepting the same passwords. >>> >>> If you want every process to read your hashed passwords and you use >>> non-portable crypt hashes it could work. The correct solution would be >>> authenticate users by LDAP binds without allowing anyone to read the >>> password or to use the {SASL} password style and authenticate users >>> against Kerberos with saslauthd. Just don't let you users play with >>> passwords. Either your password policy allows dumb users to pick trivial >>> password or it forces complex password structures on them resulting in >>> post-it notes with passwords around every second desk. >> >> I think something is lost on me here. getpwent/getpwuid do >> not return the password hashes in the returned struct passwd >> unless the calling process is root. So you have to be root in >> order to see the hashes anyway. Not all users are going to >> have access to the hashes, unless your machine's compromised >> or otherwise allows root privileges to others. >> > If the crypted password can be read by an LDAP client with the > information available to every process in (nss_)ldap.conf you're crypted > passwords are easily accessible for offline attacks. Their is no reason > for an attacker to go through the getpwent/getpwuid API. The root bind password is kept in a separate file that only root has read rights to. I don't think the password hashes are available when binding anonymously or through the proxy agent. -- DE From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 03:45:11 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8460C551 for ; Tue, 16 Jul 2013 03:45:11 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) by mx1.freebsd.org (Postfix) with ESMTP id 4A003C23 for ; Tue, 16 Jul 2013 03:45:10 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r6G3j9kh035164; Mon, 15 Jul 2013 23:45:09 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.9]); Mon, 15 Jul 2013 23:45:09 -0400 (EDT) Date: Mon, 15 Jul 2013 23:45:09 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Jan Bramkamp Subject: Re: LDAP authentication confusion In-Reply-To: Message-ID: References: <1373915752.13754.140661255962197.3CA2BD96@webmail.messagingengine.com> <20130715224748.GA45649@anubis.morrow.me.uk> <51E480C3.50008@rlwinm.de> <51E4B0F9.5050200@rlwinm.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Daniel Eischen List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 03:45:11 -0000 On Mon, 15 Jul 2013, Daniel Eischen wrote: > On Tue, 16 Jul 2013, Jan Bramkamp wrote: > >> On 16.07.2013 04:28, Daniel Eischen wrote: [ ... ] >>> >>> I think something is lost on me here. getpwent/getpwuid do >>> not return the password hashes in the returned struct passwd >>> unless the calling process is root. So you have to be root in >>> order to see the hashes anyway. Not all users are going to >>> have access to the hashes, unless your machine's compromised >>> or otherwise allows root privileges to others. >>> >> If the crypted password can be read by an LDAP client with the >> information available to every process in (nss_)ldap.conf you're crypted >> passwords are easily accessible for offline attacks. Their is no reason >> for an attacker to go through the getpwent/getpwuid API. > > The root bind password is kept in a separate file that only > root has read rights to. I don't think the password hashes > are available when binding anonymously or through the proxy > agent. I guess I was wrong - it seems the proxy agent by default (at least with Oracle DSEE7) has read access to the userPassword attribute. I'll have to try adding an ACI, as suggested by Michael Butler, to restrict that. -- DE From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 06:06:02 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E1935EFD for ; Tue, 16 Jul 2013 06:06:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 54245FCC for ; Tue, 16 Jul 2013 06:06:01 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r6G65txM095651; Tue, 16 Jul 2013 09:05:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r6G65txM095651 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r6G65tv0095648; Tue, 16 Jul 2013 09:05:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 16 Jul 2013 09:05:55 +0300 From: Konstantin Belousov To: Patrick Lamaiziere Subject: Re: (9.2) panic under disk load (gam_server / knlist_remove_kq) Message-ID: <20130716060555.GF91021@kib.kiev.ua> References: <20130714115953.1afd6e90@davenulle.org> <20130714163353.2367a6a4@davenulle.org> <20130715142647.GA9293@dft-labs.eu> <20130715185009.052d7614@davenulle.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vcGfevjIs3IRswOr" Content-Disposition: inline In-Reply-To: <20130715185009.052d7614@davenulle.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: Mateusz Guzik , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 06:06:02 -0000 --vcGfevjIs3IRswOr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 15, 2013 at 06:50:09PM +0200, Patrick Lamaiziere wrote: > Le Mon, 15 Jul 2013 16:26:47 +0200, > Mateusz Guzik a ?crit : >=20 > Hello, >=20 > > > > I'm seeing a panic while trying to build a poudriere repository. > > > >=20 > > > > As far I can see it always happens when gam_server is started (ie > > > > xfce is running) and under disk load (poudriere bulk build) : > > > > (That is something new, the box was pretty stable) > > > >=20 > > > > the complete crash dump (core.0.txt) is here: > > > > http://user.lamaiziere.net/patrick/panic_gam_server.txt > > >=20 > > > With WITNESS and ASSERTION on, I see a warning that looks related : > > >=20 > > > Jul 14 16:23:29 roxette kernel: WARNING: destroying knlist w/ > > > knotes on it! > > >=20 > > > and the box panics just after this. > > >=20 > >=20 > > can you switch that printf to a panic and paste backtrace? >=20 > Yes the full core.txt : > http://user.lamaiziere.net/patrick/panic_knlist_wknotes.txt=20 >=20 > panic: WARNING: destroying knlist w/ knotes on it! >=20 > Unread portion of the kernel message buffer: > lock order reversal: > 1st 0xfffffe00b678c098 ufs (ufs) @ /usr/src/sys/modules/nullfs/../../fs/= nullfs/null_vnops.c:620 > 2nd 0xffffffff813ebda0 allproc (allproc) @ /usr/src/sys/kern/kern_descri= p.c:2822 > KDB: stack backtrace: > #0 0xffffffff8094bc26 at kdb_backtrace+0x66 > #1 0xffffffff809603ae at _witness_debugger+0x2e > #2 0xffffffff80961a85 at witness_checkorder+0x865 > #3 0xffffffff8091b1ea at _sx_slock+0x5a > #4 0xffffffff808d30ff at mountcheckdirs+0x3f > #5 0xffffffff809a890f at dounmount+0x2df > #6 0xffffffff809a913e at sys_unmount+0x3ce > #7 0xffffffff80cec429 at amd64_syscall+0x2f9 > #8 0xffffffff80cd6d47 at Xfast_syscall+0xf7 > panic: WARNING: destroying knlist w/ knotes on it! >=20 > cpuid =3D 3 > KDB: stack backtrace: > #0 0xffffffff8094bc26 at kdb_backtrace+0x66 > #1 0xffffffff80912da8 at panic+0x1d8 > #2 0xffffffff808db269 at knlist_destroy+0x39 > #3 0xffffffff809afd7e at destroy_vpollinfo+0x1e > #4 0xffffffff809b13ef at vdropl+0x18f > #5 0xffffffff809b404c at vputx+0xac > #6 0xffffffff8299ce13 at null_reclaim+0x103 > #7 0xffffffff80d912eb at VOP_RECLAIM_APV+0xdb > #8 0xffffffff809b20a2 at vgonel+0x112 > #9 0xffffffff809b4cd9 at vflush+0x2b9 > #10 0xffffffff8299bbb3 at nullfs_unmount+0x43 > #11 0xffffffff809a8982 at dounmount+0x352 > #12 0xffffffff809a913e at sys_unmount+0x3ce > #13 0xffffffff80cec429 at amd64_syscall+0x2f9 > #14 0xffffffff80cd6d47 at Xfast_syscall+0xf7 > Uptime: 4m47s > Dumping 915 out of 3544 MB:..2%..11%..21%..32%..41%..51%..62%..72%..81%..= 91% >=20 > #0 doadump (textdump=3D) at pcpu.h:234 > 234 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) #0 doadump (textdump=3D) at pcpu.h:234 > #1 0xffffffff80913354 in kern_reboot (howto=3D260) > at /usr/src/sys/kern/kern_shutdown.c:449 > #2 0xffffffff80912d79 in panic (fmt=3D0x1
) > at /usr/src/sys/kern/kern_shutdown.c:637 > #3 0xffffffff808db269 in knlist_destroy (knl=3D) > at /usr/src/sys/kern/kern_event.c:1961 > #4 0xffffffff809afd7e in destroy_vpollinfo (vi=3D0xfffffe007ffec690) > at /usr/src/sys/kern/vfs_subr.c:3583 > #5 0xffffffff809b13ef in vdropl (vp=3D0xfffffe00b678c000) > at /usr/src/sys/kern/vfs_subr.c:2530 > #6 0xffffffff809b404c in vputx (vp=3D0xfffffe00b678c000, func=3D2) > at /usr/src/sys/kern/vfs_subr.c:2358 > #7 0xffffffff8299ce13 in ?? () > #8 0xffffffff8299d510 in ?? () > #9 0xfffffe00000002ec in ?? () > #10 0xffffff81090b8750 in ?? () > #11 0x0000000000000246 in ?? () > #12 0xfffffe002af55000 in ?? () > #13 0xffffffff81576950 in w_locklistdata () > #14 0xffffffff81322ce0 in pmc___lock_failed () > #15 0xffffffff8299d8a0 in ?? () > #16 0xffffff81090b87b0 in ?? () > #17 0x0000000000000000 in ?? () > (kgdb)=20 Hm, try this (mostly naive) patch. If kernel does not panic for you anymore, check that gam_server is still operational. If not, I have some other thing to try. diff --git a/sys/kern/vfs_subr.c b/sys/kern/vfs_subr.c index e64f379..e2c2813 100644 --- a/sys/kern/vfs_subr.c +++ b/sys/kern/vfs_subr.c @@ -3455,6 +3455,8 @@ vfs_msync(struct mount *mp, int flags) static void destroy_vpollinfo(struct vpollinfo *vi) { + + knlist_clear(&vi->vpi_selinfo.si_note, 1); seldrain(&vi->vpi_selinfo); knlist_destroy(&vi->vpi_selinfo.si_note); mtx_destroy(&vi->vpi_lock); --vcGfevjIs3IRswOr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJR5OLCAAoJEJDCuSvBvK1Bl0QP/0EXr40qDouPlMVX/hpAYe6+ xDGpEWxpNJl1wBiNUqz4SjjM+oqRT4KXi+gMh2M7Fk4KwlIgOxdb/YrfUA5IjK5C 9mfm4+xQv3p/wmeiwTrBKRfs6SZkMx+NulUtW/VEYz0xv4rTSXWXWrQ3zmaCdmJG 0fiQbN+MXf8NByhQIbzaUnPOgfglkUFP27k2twzCWZoFXw45tfRG6/Tuy+HRpOoC ysrm3zqlsFln8NBZIIRcgWknW9ak03yjMOFEDClaD2IOMySI1M19/SBtm1rWvxcH pCQB/Rh9Vry/dqFNG/UQT6CdeDcduA1RzGTj/Rm33SZPptc6ltbmS3GhhLaVZWBJ 63kmdya58ltXdOaNhVGRPoqgWUdZtl0AOc3xmrkcM2kcfWNeiv7q2D2xop5kPiWF JD9jPmwC4hBdh86wEQZqb4VBaz/laAOVrsBNz26uD4a0LluByrxQ1Kpt8cTJtant 642xK40PK7CH8YOKFPLkpAaiKAPdfvCGdq+TKLnMTess0Igx0H9AghtqkPMTv55l woxOxHkVo14AY9y2b3373KqGLP9XFVuVxLUdaCtdh5Yp9P3fb+hsfVIDoZEgxnu3 Tm+31XAwMFCIa0yArdm4wGYS3fHArnzgkSt9wVrmlabPrQex3n6NrQa2BDrr9PLy L2vbEcpqtuo/xkCYZHOd =tGvp -----END PGP SIGNATURE----- --vcGfevjIs3IRswOr-- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 09:16:52 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 98682F25; Tue, 16 Jul 2013 09:16:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by mx1.freebsd.org (Postfix) with ESMTP id DE5F092C; Tue, 16 Jul 2013 09:16:51 +0000 (UTC) Received: by mail-wg0-f45.google.com with SMTP id j13so380726wgh.24 for ; Tue, 16 Jul 2013 02:16:51 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=0O2BeIWZBBtbAdMs4oVt3gUtAiQkbHX4FFpp49ztVq4=; b=NLnhH28xt7/vYLeO/4MNwCZfNZXoYJ3tCumq7OA6Li67HtPUPP/BteRKa7m5C+Lt44 BWp5HS7e526WpSQPq7wSfwEZS/0jecKn8Gw82SPz8Vkenjf+IfIigPu57YcmHHaNtVA5 ccox4ugrzt7c28Q24/j/L5XVrYwSObLLINNrF32A0rfgMQQ/kn+VHNJz5n+arVtei1Ye fjuIvTErCHnvCYF+YMCnWKy5xkJyrs/b87MqffQksR3xIzqV1oiKcOFNyrcF1aNIV+fK Rnk5QSPJ8uJcuYHIQgnzCR7rax9xyVCZA3m7rO8mENjYvnFVp5yxwlRIZO2H50wuJQHQ absA== MIME-Version: 1.0 X-Received: by 10.180.39.212 with SMTP id r20mr420986wik.30.1373966210968; Tue, 16 Jul 2013 02:16:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Tue, 16 Jul 2013 02:16:50 -0700 (PDT) In-Reply-To: <20130716063512.d48fcc385a64619952a52a66@tackymt.homeip.net> References: <20130621220013.X55167@sola.nimnet.asn.au> <20130626152833.M78748@sola.nimnet.asn.au> <20130626195154.GK88288@e-new.0x20.net> <20130627213331.W26984@sola.nimnet.asn.au> <20130630233640.Y23789@sola.nimnet.asn.au> <20130707204957.GD88288@e-new.0x20.net> <20130708140804.R26496@sola.nimnet.asn.au> <20130716063512.d48fcc385a64619952a52a66@tackymt.homeip.net> Date: Tue, 16 Jul 2013 02:16:50 -0700 X-Google-Sender-Auth: INxP5vDictfWGR0QVyIsAo1PoIU Message-ID: Subject: Re: USB ports on Lenovo T400 do not work after a suspend/resume From: Adrian Chadd To: Taku YAMAMOTO Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org, Ian Smith , freebsd-usb@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 09:16:52 -0000 I'll try it out soon, thanks! -adrian On 15 July 2013 14:35, Taku YAMAMOTO wrote: > This reminds me of my local patch which I wrote and forgot about deep in > the git :) > > This hack was required to have working USB ports on X61 after resume, > but I'm not sure whether it's still required because I don't have X61 han= dy > anymore... > > > On Mon, 8 Jul 2013 11:09:20 -0700 > Adrian Chadd wrote: > >> On 7 July 2013 22:00, Ian Smith wrote: >> >> > Checking one more point .. do the USB ports come up ok if you original= ly >> > boot with nothing plugged in? If so (or if not), does that local APIC >> >> Yes. >> >> > error message appear the same then too? >> >> > >> >> No >> >> >> -adrian >> _______________________________________________ >> freebsd-acpi@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > > > -- > -|-__ =E5=B1=B1=E6=9C=AC=E3=80=80=E6=8B=93 / YAMAMOTO, Taku > | __ < > > - A chicken is an egg's way of producing more eggs. - From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 10:14:40 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 89666E54; Tue, 16 Jul 2013 10:14:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by mx1.freebsd.org (Postfix) with ESMTP id CF051BF0; Tue, 16 Jul 2013 10:14:39 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id y10so3474611wgg.4 for ; Tue, 16 Jul 2013 03:14:39 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=jxMgEGD3jpjEh3dF5u3HQohdXIgP+2VpYW6izXmXgdY=; b=z2JJ2X9uYeq/6jgB7lKDbkAMIrjDtHWn1ZA/ln7DGRU9U8SBB3D3zquaqaK23325+j vnBZt1ZPf3PMXTPtx3CZUhCrjCZXwVnGk5lcpuLaMh84FSzLB7rVTqGzeOl9PrvdnyVc rdejkRCZ/4OVyeQ274UUMDRbU9WA3AgsvZerYDAfdru4w3UFNvJWHMYPD0O/xSbcFENY Xr4hb1/+Pl3BaWsPQ+wHY7HeMkVHYmUEeiGE4xb3pnhMhFok6W22dN4hhlc0xqZ0sRJ9 Qx93dXGEZsMETRAZriUZZF+Kh+gb/HAP5EC3pzmrcmV/eJWHKIDA0p1T+HgkZq7jx+Ta ILcw== MIME-Version: 1.0 X-Received: by 10.180.39.212 with SMTP id r20mr587578wik.30.1373969679048; Tue, 16 Jul 2013 03:14:39 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Tue, 16 Jul 2013 03:14:38 -0700 (PDT) In-Reply-To: References: <20130621220013.X55167@sola.nimnet.asn.au> <20130626152833.M78748@sola.nimnet.asn.au> <20130626195154.GK88288@e-new.0x20.net> <20130627213331.W26984@sola.nimnet.asn.au> <20130630233640.Y23789@sola.nimnet.asn.au> <20130707204957.GD88288@e-new.0x20.net> <20130708140804.R26496@sola.nimnet.asn.au> <20130716063512.d48fcc385a64619952a52a66@tackymt.homeip.net> Date: Tue, 16 Jul 2013 03:14:38 -0700 X-Google-Sender-Auth: pPk_Q1s0OsWw-kuZe_31CIRx5wU Message-ID: Subject: Re: USB ports on Lenovo T400 do not work after a suspend/resume From: Adrian Chadd To: Taku YAMAMOTO Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org, Ian Smith , freebsd-usb@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 10:14:40 -0000 Nope, no such joy. What else can I try? -adrian On 16 July 2013 02:16, Adrian Chadd wrote: > I'll try it out soon, thanks! > > > > -adrian > > On 15 July 2013 14:35, Taku YAMAMOTO wrote: >> This reminds me of my local patch which I wrote and forgot about deep in >> the git :) >> >> This hack was required to have working USB ports on X61 after resume, >> but I'm not sure whether it's still required because I don't have X61 ha= ndy >> anymore... >> >> >> On Mon, 8 Jul 2013 11:09:20 -0700 >> Adrian Chadd wrote: >> >>> On 7 July 2013 22:00, Ian Smith wrote: >>> >>> > Checking one more point .. do the USB ports come up ok if you origina= lly >>> > boot with nothing plugged in? If so (or if not), does that local API= C >>> >>> Yes. >>> >>> > error message appear the same then too? >>> >>> > >>> >>> No >>> >>> >>> -adrian >>> _______________________________________________ >>> freebsd-acpi@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >>> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" >> >> >> -- >> -|-__ =E5=B1=B1=E6=9C=AC=E3=80=80=E6=8B=93 / YAMAMOTO, Taku >> | __ < >> >> - A chicken is an egg's way of producing more eggs. - From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 11:12:45 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7FB498C8; Tue, 16 Jul 2013 11:12:45 +0000 (UTC) (envelope-from lukasz@wasikowski.net) Received: from mail.wasikowski.net (mail.wasikowski.net [IPv6:2001:6a0:1cb::b]) by mx1.freebsd.org (Postfix) with ESMTP id 3EB35E14; Tue, 16 Jul 2013 11:12:45 +0000 (UTC) Received: from mail.wasikowski.net (mail.wasikowski.net [IPv6:2001:6a0:1cb::b]) by mail.wasikowski.net (Postfix) with ESMTP id AFCC52C64; Tue, 16 Jul 2013 13:12:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at wasikowski.net Received: from mail.wasikowski.net ([91.204.91.44]) by mail.wasikowski.net (scan.wasikowski.net [91.204.91.44]) (amavisd-new, port 10026) with ESMTP id C7B2mxyDmsUI; Tue, 16 Jul 2013 13:12:41 +0200 (CEST) Received: from [192.168.138.150] (83-144-115-210.static.chello.pl [83.144.115.210]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.wasikowski.net (Postfix) with ESMTPSA id 4700F2C61; Tue, 16 Jul 2013 13:12:41 +0200 (CEST) Message-ID: <51E52AA8.3010109@wasikowski.net> Date: Tue, 16 Jul 2013 13:12:40 +0200 From: =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Hiroki Sato Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) References: <20130712.135621.1408565802386368060.hrs@allbsd.org> <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> In-Reply-To: <20130712.160358.1330135778606339435.hrs@allbsd.org> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org, trashcan@odo.in-berlin.de X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 11:12:45 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 W dniu 2013-07-12 09:03, Hiroki Sato pisze: > Please let me know if the existing configurations and/or the new > formats do not work. The following is a summary of the supported > rc.conf variables, FYI: > > Hiroki Sato wrote in > <201306200229.r5K2TnfR085621@svn.freebsd.org>: > [...] What is the current, non deprecated way, to configure IP addresses in rc.conf? Let's say for a dual stack, multi IP box I need to set: 10.0.0.66/28 and 10.0.0.67-78 as aliases and fdda:5cc1:23:4::1/48 and fdda:5cc1:23:4::2-f as aliases What is the best way to accomplish it? - -- best regards, Lukasz Wasikowski -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHlKqQACgkQXlaUxx+udUUtnwCfc74UJLDPnCjec+v8TP0d8ceV Pz4AnA6Nd5rwO5HL/LYdaJiPmBC1ENxC =bzG8 -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 11:29:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BD1EBED3 for ; Tue, 16 Jul 2013 11:29:23 +0000 (UTC) (envelope-from feld@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 95892EF3 for ; Tue, 16 Jul 2013 11:29:23 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1DA0120B38 for ; Tue, 16 Jul 2013 07:29:21 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Tue, 16 Jul 2013 07:29:22 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=KzLFXMjI9aVgL/1RGU0eDf91z/M=; b=UKWC4 yCKWp1x00FAIF7P9yngPU7mh4nqRaX0UDXCDg3Gs424I6XGx5TOMrujBiMSl7Elf ddTuDem22uVpHPPRBgf0s4NKfyH2ZbyZpXG3OtUmdgxPugzEx2tIAhPMV47kxvYJ C7hKAcbD89Camqud5lwMzUSm07oc3yLIvWljfA= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id BDF4BB00003; Tue, 16 Jul 2013 07:29:21 -0400 (EDT) Message-Id: <1373974161.29269.140661256227369.575EA8E4@webmail.messagingengine.com> X-Sasl-Enc: DzCh4U7UeHJGMqDsyuRdoJA5OYt/N618JHvXE5UStVgT 1373974161 From: Mark Felder To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-bdcdd1cb Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) Date: Tue, 16 Jul 2013 06:29:21 -0500 In-Reply-To: <51E52AA8.3010109@wasikowski.net> References: <20130712.135621.1408565802386368060.hrs@allbsd.org> <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <51E52AA8.3010109@wasikowski.net> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 11:29:23 -0000 On Tue, Jul 16, 2013, at 6:12, =C5=81ukasz W=C4=85sikowski wrote: > > What is the current, non deprecated way, to configure IP addresses in > rc.conf? Let's say for a dual stack, multi IP box I need to set: >=20 > 10.0.0.66/28 and 10.0.0.67-78 as aliases and > fdda:5cc1:23:4::1/48 and fdda:5cc1:23:4::2-f as aliases >=20 > What is the best way to accomplish it? > ipv4_addrs_em0=3D"10.0.0.66-78/28" ipv6 syntax depends on if you're using 8.x or 9.1-RELEASE, but you're going to have to do all the aliases manually. From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 12:21:35 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CA418F4B; Tue, 16 Jul 2013 12:21:35 +0000 (UTC) (envelope-from lukasz@wasikowski.net) Received: from mail.wasikowski.net (mail.wasikowski.net [91.204.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 85CBC231; Tue, 16 Jul 2013 12:21:35 +0000 (UTC) Received: from mail.wasikowski.net (mail.wasikowski.net [IPv6:2001:6a0:1cb::b]) by mail.wasikowski.net (Postfix) with ESMTP id C405D2CF8; Tue, 16 Jul 2013 14:21:27 +0200 (CEST) X-Virus-Scanned: amavisd-new at wasikowski.net Received: from mail.wasikowski.net ([91.204.91.44]) by mail.wasikowski.net (scan.wasikowski.net [91.204.91.44]) (amavisd-new, port 10026) with ESMTP id KdNsAiNrDwfk; Tue, 16 Jul 2013 14:21:27 +0200 (CEST) Received: from [192.168.138.150] (83-144-115-210.static.chello.pl [83.144.115.210]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.wasikowski.net (Postfix) with ESMTPSA id 713B62CF5; Tue, 16 Jul 2013 14:21:27 +0200 (CEST) Message-ID: <51E53AC7.1040307@wasikowski.net> Date: Tue, 16 Jul 2013 14:21:27 +0200 From: =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Mark Felder Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) References: <20130712.135621.1408565802386368060.hrs@allbsd.org> <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <51E52AA8.3010109@wasikowski.net> <1373974161.29269.140661256227369.575EA8E4@webmail.messagingengine.com> In-Reply-To: <1373974161.29269.140661256227369.575EA8E4@webmail.messagingengine.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 12:21:35 -0000 W dniu 2013-07-16 13:29, Mark Felder pisze: > On Tue, Jul 16, 2013, at 6:12, Åukasz WÄ…sikowski wrote: >> >> What is the current, non deprecated way, to configure IP addresses in >> rc.conf? Let's say for a dual stack, multi IP box I need to set: >> >> 10.0.0.66/28 and 10.0.0.67-78 as aliases and >> fdda:5cc1:23:4::1/48 and fdda:5cc1:23:4::2-f as aliases >> >> What is the best way to accomplish it? >> > > > ipv4_addrs_em0="10.0.0.66-78/28" > > ipv6 syntax depends on if you're using 8.x or 9.1-RELEASE, but you're > going to have to do all the aliases manually. I'm using ipv4_addrs_em0 now (and ipv6_addrs_em0 with Kimmo Paasiala's patch), but Hiroki Sato wrote: hr> # IPv4 address range spec. Now deprecated. hr> ipv4_addr_em0="10.2.1.1-10" So I'm a little confused now :) If I'd use post r252015 system then would this be better way? ifconfig_em0_aliases="inet 10.0.0.66/28 inet 10.0.0.67-78 inet6 fdda:5cc1:23:4::1/48 inet6 fdda:5cc1:23:4::2-f" -- best regards, Lukasz Wasikowski From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 12:25:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4E62824D for ; Tue, 16 Jul 2013 12:25:42 +0000 (UTC) (envelope-from feld@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 24CEE26B for ; Tue, 16 Jul 2013 12:25:41 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 31EA321714; Tue, 16 Jul 2013 08:25:40 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute2.internal (MEProxy); Tue, 16 Jul 2013 08:25:41 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=pWBEqd8dYJ/z1Es7KSKEatAxFLw=; b=QhK 2h6f3/C0M0kzJtFNySfHDjmkJw/kZkODIVXnoP+7nMACh8dcPf+YBjFt69Wk++XN C5aoy26n7a33RwxWToy+JV6I7xqoettKP4XOdMkRA2gYgWIyHxMo9lQvTP6ayobi 8S+NaR5H1+wmO+CQCYU0vk5lnyRfeuZ8YybXUqD8= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 8B66DB00003; Tue, 16 Jul 2013 08:25:40 -0400 (EDT) Message-Id: <1373977540.14057.140661256246869.614AF7F5@webmail.messagingengine.com> X-Sasl-Enc: 4nfPdNCZbYGd05jjM97sJ1sdZAiHB+Tqgs/HG/vd9ClI 1373977540 From: Mark Felder To: =?utf-8?Q?=C5=81ukasz=20W=C4=85sikowski?= MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-bdcdd1cb In-Reply-To: <51E53AC7.1040307@wasikowski.net> References: <20130712.135621.1408565802386368060.hrs@allbsd.org> <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <51E52AA8.3010109@wasikowski.net> <1373974161.29269.140661256227369.575EA8E4@webmail.messagingengine.com> <51E53AC7.1040307@wasikowski.net> Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) Date: Tue, 16 Jul 2013 07:25:40 -0500 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 12:25:42 -0000 On Tue, Jul 16, 2013, at 7:21, =C5=81ukasz W=C4=85sikowski wrote: >=20 > I'm using ipv4_addrs_em0 now (and ipv6_addrs_em0 with Kimmo Paasiala's > patch), but Hiroki Sato wrote: >=20 > hr> # IPv4 address range spec. Now deprecated. > hr> ipv4_addr_em0=3D"10.2.1.1-10" >=20 > So I'm a little confused now :) As am I... when did ipv4_addr get deprecated? From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 15:47:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1A2E25D1 for ; Tue, 16 Jul 2013 15:47:49 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id D21EFF65 for ; Tue, 16 Jul 2013 15:47:48 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1Uz7Tb-000AO7-9r; Tue, 16 Jul 2013 17:47:43 +0200 Date: Tue, 16 Jul 2013 17:47:43 +0200 From: Kurt Jaeger To: freebsd@jdc.parodius.com Subject: Re: Interpreting MCA error output Message-ID: <20130716154743.GR2947@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 15:47:49 -0000 Hi! Approx. two years ago there was a thread on -stable about MCA output. See http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064083.html for a post from Jeremy Chadwick with a link to a AMD paper on that topic ? http://www.amd.com/us/Documents/47644A_ecc_embedded.pdf which is no longer available 8-( Anyone has a copy ? There's new mcelog source (1.0pre3), but the MASTER_SITES look deserted 8-( And I'm not sure the CPU is really supported by that mcelog version, due to the error: mcelog: Unsupported new Family 6 Model 2d CPU: only decoding architectural errors We have a HP360 gen8 running FreeBSD 9.1 and try to get support from HP on that topic. -- pi@opsec.eu +49 171 3101372 7 years to go ! From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 16:01:09 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CC035973; Tue, 16 Jul 2013 16:01:09 +0000 (UTC) (envelope-from taku@tackymt.homeip.net) Received: from basalt.tackymt.homeip.net (basalt.tackymt.homeip.net [IPv6:2001:470:fd92:0:20d:61ff:fecc:2253]) by mx1.freebsd.org (Postfix) with ESMTP id 8D19494; Tue, 16 Jul 2013 16:01:09 +0000 (UTC) Received: from basalt.tackymt.homeip.net (localhost [127.0.0.1]) by basalt.tackymt.homeip.net (Postfix) with ESMTP id 0E28583C5; Wed, 17 Jul 2013 01:01:09 +0900 (JST) X-Virus-Scanned: amavisd-new at tackymt.homeip.net Received: from localhost by basalt.tackymt.homeip.net (amavisd-new, unix socket) with ESMTP id 4lWkOTRRYL2v; Wed, 17 Jul 2013 01:01:07 +0900 (JST) Received: from basalt.tackymt.homeip.net (basalt.tackymt.homeip.net [IPv6:2001:470:fd92:0:20d:61ff:fecc:2253]) by basalt.tackymt.homeip.net (Postfix) with ESMTPSA; Wed, 17 Jul 2013 01:01:07 +0900 (JST) Date: Wed, 17 Jul 2013 01:01:06 +0900 From: Taku YAMAMOTO To: Adrian Chadd Subject: Re: USB ports on Lenovo T400 do not work after a suspend/resume Message-Id: <20130717010106.2f174c2b0dc1b50b95a9dde3@tackymt.homeip.net> In-Reply-To: References: <20130621220013.X55167@sola.nimnet.asn.au> <20130626152833.M78748@sola.nimnet.asn.au> <20130626195154.GK88288@e-new.0x20.net> <20130627213331.W26984@sola.nimnet.asn.au> <20130630233640.Y23789@sola.nimnet.asn.au> <20130707204957.GD88288@e-new.0x20.net> <20130708140804.R26496@sola.nimnet.asn.au> <20130716063512.d48fcc385a64619952a52a66@tackymt.homeip.net> X-Mailer: Sylpheed 3.3.0 (GTK+ 2.24.6; i386-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org, Ian Smith , freebsd-usb@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 16:01:10 -0000 On Tue, 16 Jul 2013 03:14:38 -0700 Adrian Chadd wrote: > Nope, no such joy. > > What else can I try? Maybe sysctl dev.[uoex]hci.*.wake=1 works. Other than that I have out of my ideas :(... > -adrian > > On 16 July 2013 02:16, Adrian Chadd wrote: > > I'll try it out soon, thanks! > > > > > > > > -adrian > > > > On 15 July 2013 14:35, Taku YAMAMOTO wrote: > >> This reminds me of my local patch which I wrote and forgot about deep in > >> the git :) > >> > >> This hack was required to have working USB ports on X61 after resume, > >> but I'm not sure whether it's still required because I don't have X61 handy > >> anymore... > >> > >> > >> On Mon, 8 Jul 2013 11:09:20 -0700 > >> Adrian Chadd wrote: > >> > >>> On 7 July 2013 22:00, Ian Smith wrote: > >>> > >>> > Checking one more point .. do the USB ports come up ok if you originally > >>> > boot with nothing plugged in? If so (or if not), does that local APIC > >>> > >>> Yes. > >>> > >>> > error message appear the same then too? > >>> > >>> > > >>> > >>> No > >>> > >>> > >>> -adrian > >>> _______________________________________________ > >>> freebsd-acpi@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > >>> To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > >> > >> > >> -- > >> -|-__ $B;3K\!!Bs(B / YAMAMOTO, Taku > >> | __ < > >> > >> - A chicken is an egg's way of producing more eggs. - -- -|-__ $B;3K\!!Bs(B / YAMAMOTO, Taku | __ < - A chicken is an egg's way of producing more eggs. - From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 17:19:32 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8F8F761E; Tue, 16 Jul 2013 17:19:32 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by mx1.freebsd.org (Postfix) with ESMTP id 4E5F163D; Tue, 16 Jul 2013 17:19:32 +0000 (UTC) Received: by mail-ob0-f169.google.com with SMTP id up14so1094874obb.0 for ; Tue, 16 Jul 2013 10:19:31 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=F2U9ZaCz0LvmCc8E3rrD3TL3dmMUR3AL3lRMDRm8Vws=; b=ANyvRtQtXm/ftav40sr2FK0mjEDXEAs0F1cLH+9MUsqWCnXgq8KfFr+AUFJFK5AxLG mnH1y9u8MoIOn45qz6TQ1ki8UptUhP6WHaHmufnh6rRxSQZpSJgjmwiWY/VUo6D+GX6k HEZ3Hw86CUYucuPA3hw3l3oOPGYYbLSU3CMGlLZnvO0vqblTEsJsb6FEQhtACrFSHA3B vHsXt/paCm2ha+KChWpmT63EkLRJrEgc3oov475D2wS3aZTLPdlgStbCWSOdqci5Pi4N 8EX9bwGQaG+Ui+GjMuF668Ur9rV2svLMwJcwZUafflRv057mur6v1wHqD5EbyngTscCt MkJw== MIME-Version: 1.0 X-Received: by 10.182.79.165 with SMTP id k5mr668418obx.31.1373995171842; Tue, 16 Jul 2013 10:19:31 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.76.112.212 with HTTP; Tue, 16 Jul 2013 10:19:31 -0700 (PDT) In-Reply-To: <1373977540.14057.140661256246869.614AF7F5@webmail.messagingengine.com> References: <20130712.135621.1408565802386368060.hrs@allbsd.org> <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <51E52AA8.3010109@wasikowski.net> <1373974161.29269.140661256227369.575EA8E4@webmail.messagingengine.com> <51E53AC7.1040307@wasikowski.net> <1373977540.14057.140661256246869.614AF7F5@webmail.messagingengine.com> Date: Tue, 16 Jul 2013 10:19:31 -0700 X-Google-Sender-Auth: jFSpJzwyuSNZf7p7yNOiN9Xknyc Message-ID: Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) From: Kevin Oberman To: Mark Felder Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-stable@freebsd.org Stable" , =?UTF-8?Q?=C5=81ukasz_W=C4=85sikowski?= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 17:19:32 -0000 On Tue, Jul 16, 2013 at 5:25 AM, Mark Felder wrote: > On Tue, Jul 16, 2013, at 7:21, =C5=81ukasz W=C4=85sikowski wrote: > > > > I'm using ipv4_addrs_em0 now (and ipv6_addrs_em0 with Kimmo Paasiala's > > patch), but Hiroki Sato wrote: > > > > hr> # IPv4 address range spec. Now deprecated. > > hr> ipv4_addr_em0=3D"10.2.1.1-10" > > > > So I'm a little confused now :) > > As am I... when did ipv4_addr get deprecated? > It didn't. 10.2.1.1-10 syntax did. --=20 R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 17:38:18 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CBB84B41 for ; Tue, 16 Jul 2013 17:38:18 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 8F485784 for ; Tue, 16 Jul 2013 17:38:18 +0000 (UTC) Received: by mail-vc0-f180.google.com with SMTP id gf11so655580vcb.25 for ; Tue, 16 Jul 2013 10:38:18 -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=/y8gNKuGR2eHZ8Ou/K1LK/i1/yYwIVQmx19qnffx3xQ=; b=iWZSPNmCmhQvGpwGQGvYDo24ZyhVkg6ri6uSWlr6CqwbIdsSuw3DXJWvSjXWGO8vrV 5SjMFv9C5avJFeBg6ofL8cWCtLIAYlCdox4LEkVviNskuXV9k739kyArqTEAiXwRNVly CVrYk/D3KxPX4qNM2oSHVJqt2I6C+8Q3zAPGR9H/U3/yoQqIfWNJE8RbUGVeUMOq6Sd2 fCRV9AvsWO0gOjy3JB8yAnJbhhNWPSO6JUeFY+mEStrFbVsEzKJQoH6NoRAFodcLrAgR xDRZBqXMksI5/54u4zw8/ckl0hZHIW/kZH3Rn9ImA6nxL0WYteDvzV8dLKjBeSsts04T 5QwA== MIME-Version: 1.0 X-Received: by 10.52.16.77 with SMTP id e13mr654197vdd.49.1373996297948; Tue, 16 Jul 2013 10:38:17 -0700 (PDT) Received: by 10.58.249.1 with HTTP; Tue, 16 Jul 2013 10:38:17 -0700 (PDT) In-Reply-To: <51E41419.3040503@ixsystems.com> References: <51D90B9B.9080209@ixsystems.com> <51D92826.1070707@freebsd.org> <51E1061F.3050804@ixsystems.com> <51E398F3.40008@freebsd.org> <51E3EEAA.3040106@freebsd.org> <51E3EFA8.1050606@ixsystems.com> <20130715141300.GA1986@glenbarber.us> <51E41419.3040503@ixsystems.com> Date: Tue, 16 Jul 2013 19:38:17 +0200 Message-ID: Subject: Re: status of autotuning freebsd for 9.2 From: Johan Hendriks To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 17:38:19 -0000 Op maandag 15 juli 2013 schreef Alfred Perlstein (alfred@ixsystems.com) het volgende: > On 7/15/13 7:13 AM, Glen Barber wrote: > >> On Mon, Jul 15, 2013 at 05:48:40AM -0700, Alfred Perlstein wrote: >> >>> On 7/15/13 5:44 AM, Andre Oppermann wrote: >>> >>>> On 15.07.2013 08:38, Andre Oppermann wrote: >>>> >>>>> On 13.07.2013 09:47, Alfred Perlstein wrote: >>>>> >>>>>> Andre, we have a number of people running this patch in the >>>>>> following configurations: >>>>>> >>>>>> 6-8GB ram + 10gigE ethernet using iozone over NFS. >>>>>> >>>>> As you haven't seen any problems yet I've asked RE to green light >>>>> the MFC. >>>>> >>>> RE has rejected the MFC out of fears for unexpected regressions. >>>> >>>> That is unfortunate. I guess re@ doesn't understand that FreeBSD >>> 9.2 will be unusable out of the box for doing 10gigE for more than a >>> few microseconds. >>> >>> Can we not just do my original patch that has the check for 64bit >>> pointers before unscaling maxusers? That would be dirt simple and >>> just work with minimal risk. >>> >>> IMHO, this is considered a new feature, and not a critical bug fix. re@ >> asked from the start of the code slush to avoid new features, and at >> this point, it is too late. It is not worth introducing possible >> regressions, which will only delay the 9.2-RELEASE. >> >> Glen >> >> OK, then we need a release notes telling people a sane value for > nmbclusters and friends so that they know how to make 10gigE work. > > I'll poll my team for a value if someone else has one, that would be even > better. > > -- > Alfred Perlstein > VP Software Engineering, iXsystems Is there a possibility that a separate unofficial patch set could be released for people who want the autotuning but do not want to run 9 stable after 9.2 is released. I would like the autotuning, but i am a little reluctent to use other stable stuff i will get when tracking stable. Regards Johan > ______________________________**_________________ > 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 Tue Jul 16 17:54:22 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 38AFF34A for ; Tue, 16 Jul 2013 17:54:22 +0000 (UTC) (envelope-from feld@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 0BD50870 for ; Tue, 16 Jul 2013 17:54:21 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id EED1E21214; Tue, 16 Jul 2013 13:54:20 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Tue, 16 Jul 2013 13:54:20 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=FEKAOOoqlIdw+3lGQTriXXDZ5NU=; b=COQ lmMK+kRfsr/PBaMwsDdGtOaWUSCQByg/iqFBAa+ZehEX3/evX+mCIxJVZErixq6s Kgdtkui/1sK59MyRREuYaqiQ6EoWqoZBk/HtZhg1cV9ZpMWNAYHGbDbxKuRrIetk VpNsKYneugy4TCAlwgfX760l2D8is5qYZSKi8MhU= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id C7802B00003; Tue, 16 Jul 2013 13:54:20 -0400 (EDT) Message-Id: <1373997260.28225.140661256374549.2C39287C@webmail.messagingengine.com> X-Sasl-Enc: LHMrdH6YucjVlZJ2fe47Rj6+DsKx7jSiMX1X6G/oD9jk 1373997260 From: Mark Felder To: Kevin Oberman MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-bdcdd1cb In-Reply-To: References: <20130712.135621.1408565802386368060.hrs@allbsd.org> <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <51E52AA8.3010109@wasikowski.net> <1373974161.29269.140661256227369.575EA8E4@webmail.messagingengine.com> <51E53AC7.1040307@wasikowski.net> <1373977540.14057.140661256246869.614AF7F5@webmail.messagingengine.com> Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) Date: Tue, 16 Jul 2013 12:54:20 -0500 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-stable@freebsd.org Stable" , =?utf-8?Q?=C5=81ukasz=20W=C4=85sikowski?= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 17:54:22 -0000 On Tue, 16 Jul 2013 12:19:31 -0500, Kevin Oberman <[1]rkoberman@gmail.com> wrote: > It didn't. 10.2.1.1-10 syntax did. I'm not totally clear on this yet -- the entire concept of being able to do *ranges* is deprecated? Or is it deprecated because it's missing the CIDR? Thanks References 1. mailto:rkoberman@gmail.com From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 19:42:55 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 010E9117 for ; Tue, 16 Jul 2013 19:42:54 +0000 (UTC) (envelope-from e31@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by mx1.freebsd.org (Postfix) with ESMTP id A2112D90 for ; Tue, 16 Jul 2013 19:42:54 +0000 (UTC) Received: from 3capp-gmx-bs30.server.lan ([172.19.170.82]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MaXIN-1UjaEe2LGb-00K7bd for ; Tue, 16 Jul 2013 21:42:53 +0200 Received: from [31.18.128.230] by 3capp-gmx-bs30.server.lan with HTTP; Tue Jul 16 21:42:53 CEST 2013 Message-ID: From: "Pascal Drecker" To: "Johan Hendriks" Subject: Aw: Re: status of autotuning freebsd for 9.2 Date: Tue, 16 Jul 2013 21:42:53 +0200 (CEST) Importance: normal Sensitivity: Normal In-Reply-To: References: <51D90B9B.9080209@ixsystems.com> <51D92826.1070707@freebsd.org> <51E1061F.3050804@ixsystems.com> <51E398F3.40008@freebsd.org> <51E3EEAA.3040106@freebsd.org> <51E3EFA8.1050606@ixsystems.com> <20130715141300.GA1986@glenbarber.us> <51E41419.3040503@ixsystems.com>, X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K0:QPxEB+JsFc3DRNthPaN7BVC4yodc3cCvrDgSDstHFN5 KauH/+m4KLXeOqxITcVezldR9Rqwzs/mnB4BYRqdbc8OCCZe6W 4fNDcMtpkDyfXQZzjuUs0J4iiS19Fq3u2NYrgwDLr0h10B8VJy zhiUrszWZPNQCfcUmiPJIhUiENDlxmEJRTOVNg+ZRSOw6NNniE zE9C/6Bbf5GEwuctIZDBmv5rnpHxIlSSl9RSKmbKyc0dL4K/jW TQGKi/0tFwSm/Mwypkr8mL2mqF7HOKNlpksD4lQfA8/LvXMnBJ neJW68= MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-stable , Alfred Perlstein X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 19:42:55 -0000 > Op maandag 15 juli 2013 schreef Alfred Perlstein (alfred@ixsystems.com) het > volgende: > >> On 7/15/13 7:13 AM, Glen Barber wrote: >>> >>> On Mon, Jul 15, 2013 at 05:48:40AM -0700, Alfred Perlstein wrote: >>> >>>> On 7/15/13 5:44 AM, Andre Oppermann wrote: >>>> >>>>> On 15.07.2013 08:38, Andre Oppermann wrote: >>>>> >>>>>> On 13.07.2013 09:47, Alfred Perlstein wrote: >>>>>> >>>>>>> Andre, we have a number of people running this patch in the >>>>>>> following configurations: >>>>>>> >>>>>>> 6-8GB ram + 10gigE ethernet using iozone over NFS. >>>>>>> >>>>>> As you haven't seen any problems yet I've asked RE to green light >>>>>> the MFC. >>>>>> >>>>> RE has rejected the MFC out of fears for unexpected regressions. >>>>> >>>>> That is unfortunate. I guess re@ doesn't understand that FreeBSD >>>> 9.2 will be unusable out of the box for doing 10gigE for more than a >>>> few microseconds. >>>> >>>> Can we not just do my original patch that has the check for 64bit >>>> pointers before unscaling maxusers? That would be dirt simple and >>>> just work with minimal risk. >>>> >>>> IMHO, this is considered a new feature, and not a critical bug fix. re@ >>> asked from the start of the code slush to avoid new features, and at >>> this point, it is too late. It is not worth introducing possible >>> regressions, which will only delay the 9.2-RELEASE. >>> >>> Glen >>> >>> OK, then we need a release notes telling people a sane value for >> nmbclusters and friends so that they know how to make 10gigE work. >> >> I'll poll my team for a value if someone else has one, that would be even >> better. >> >> -- >> Alfred Perlstein >> VP Software Engineering, iXsystems > > >Is there a possibility that a separate unofficial patch set could be >released for people who want the autotuning but do not want to run 9 >stable after 9.2 is released. >I would like the autotuning, but i am a little reluctent to use other >stable stuff i will get when tracking stable. > >Regards >Johan Hi, I think that's a good point. In our company, it´s not allowed to use the stable tree for any production system. Little and useful patches are still allowed. Having a central point with a description of each patch it would be much easier to update the release version with the needed patches. Perhaps, each patch could also have a comment section and a state (experimental, almost stable, stable ...) or a counter for successfully and unsuccessfully deployments. Any objections? Regards, Pascal From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 20:14:50 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9875795D for ; Tue, 16 Jul 2013 20:14:50 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [94.23.254.147]) by mx1.freebsd.org (Postfix) with ESMTP id 63B86EE4 for ; Tue, 16 Jul 2013 20:14:49 +0000 (UTC) Received: from roxette.lamaiziere.net (232.176.97.84.rev.sfr.net [84.97.176.232]) by smtp.lamaiziere.net (Postfix) with ESMTPA id 694AC528F; Tue, 16 Jul 2013 22:14:43 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by roxette.lamaiziere.net (Postfix) with ESMTP id C24F9B2FC; Tue, 16 Jul 2013 22:14:40 +0200 (CEST) Date: Tue, 16 Jul 2013 22:14:36 +0200 From: Patrick Lamaiziere To: Konstantin Belousov Subject: Re: (9.2) panic under disk load (gam_server / knlist_remove_kq) Message-ID: <20130716221436.672d0fba@davenulle.org> In-Reply-To: <20130716060555.GF91021@kib.kiev.ua> References: <20130714115953.1afd6e90@davenulle.org> <20130714163353.2367a6a4@davenulle.org> <20130715142647.GA9293@dft-labs.eu> <20130715185009.052d7614@davenulle.org> <20130716060555.GF91021@kib.kiev.ua> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Mateusz Guzik , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 20:14:50 -0000 Le Tue, 16 Jul 2013 09:05:55 +0300, Konstantin Belousov a écrit : Hello, Thanks Konstantin. I'm trying your patch and that looks better. poudriere runs since 3 hours now (before the box paniced few minutes after I start a poudriere bulk) (I've removed the previous change to panic on the warning "WARNING: destroying knlist w/ knotes on it!" / I guess it is ok ?) As far I can see gamin still works (xfce sees changes and the "testgam" tool works fine : https://people.gnome.org/~veillard/gamin/debug.html) I will run few "poudriere bulk" tomorrow and report the result here. I've tried on my workstation at work which uses the same configuration as at home, but I was not able to reproduce this problem. The only big change is that it has 8 GB RAM versus 4 GB here. I don't know what can trigger this panic. If you have patch to test or idea, please let me know. Thanks, regards. From owner-freebsd-stable@FreeBSD.ORG Tue Jul 16 21:37:53 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B2E34E78; Tue, 16 Jul 2013 21:37:53 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from nskntmtas01p.mx.bigpond.com (nskntmtas01p.mx.bigpond.com [61.9.168.137]) by mx1.freebsd.org (Postfix) with ESMTP id 2BC052E3; Tue, 16 Jul 2013 21:37:52 +0000 (UTC) Received: from nskntcmgw07p ([61.9.169.167]) by nskntmtas01p.mx.bigpond.com with ESMTP id <20130716213745.RGUQ21423.nskntmtas01p.mx.bigpond.com@nskntcmgw07p>; Tue, 16 Jul 2013 21:37:45 +0000 Received: from hermes.heuristicsystems.com.au ([58.172.113.247]) by nskntcmgw07p with BigPond Outbound id 19dl1m0075LKYmq019dl9C; Tue, 16 Jul 2013 21:37:45 +0000 X-Authority-Analysis: v=2.0 cv=IccFqBWa c=1 sm=1 a=YibVxx38Z+cwdCKSMcELyg==:17 a=UllZXCvykFMA:10 a=twTT4oUKOlYA:10 a=kj9zAlcOel0A:10 a=GHIR_BbyAAAA:8 a=-n0au9XHs5EA:10 a=naDOvgkJbzev1vbrOXkA:9 a=CjuIK1q_8ugA:10 a=-F5lUHHfTgUA:10 a=wzpLH4MSTj8A:10 a=YibVxx38Z+cwdCKSMcELyg==:117 Received: from white (white.hs [10.0.5.2]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.14.5/8.13.6) with ESMTP id r6GLaPG1001715; Wed, 17 Jul 2013 07:36:25 +1000 (EST) (envelope-from dewayne.geraghty@heuristicsystems.com.au) From: "Dewayne Geraghty" To: "'Hiroki Sato'" References: <20130712.135621.1408565802386368060.hrs@allbsd.org> <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> Subject: RE: ipv6_addrs_IF aliases in rc.conf(5) Date: Wed, 17 Jul 2013 07:36:25 +1000 Message-ID: <14677223DB6D4CD48E880520725B3552@white> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20130712.160358.1330135778606339435.hrs@allbsd.org> Thread-Index: Ac5+zhTwMbG675pcT2ajI58xFRqiKADnXwiw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 16 Jul 2013 21:37:53 -0000 Sato-san, You have provided a very useful summary of ifconfig parameters for rc.conf. However, you are missing one example that would provide clearer understanding. Would you please advise if ipv4_addr_em0="10.2.1.1-10/32" is deprecated, backward compatible or remains valid into the future? I particularly appreciate the succinctness of: ifconfig_em0_aliases="inet 10.3.3.201-204/24 inet6 2001:db8:210-213::1/64 inet 10.1.1.1/24" Kind regards, Dewayne. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 05:37:24 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 497F5348 for ; Wed, 17 Jul 2013 05:37:24 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id E11546B4 for ; Wed, 17 Jul 2013 05:37:23 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r6H5bJKl098281; Wed, 17 Jul 2013 08:37:19 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r6H5bJKl098281 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r6H5bIAf098280; Wed, 17 Jul 2013 08:37:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 17 Jul 2013 08:37:18 +0300 From: Konstantin Belousov To: Patrick Lamaiziere Subject: Re: (9.2) panic under disk load (gam_server / knlist_remove_kq) Message-ID: <20130717053718.GO5991@kib.kiev.ua> References: <20130714115953.1afd6e90@davenulle.org> <20130714163353.2367a6a4@davenulle.org> <20130715142647.GA9293@dft-labs.eu> <20130715185009.052d7614@davenulle.org> <20130716060555.GF91021@kib.kiev.ua> <20130716221436.672d0fba@davenulle.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4oF+6Ged69J0+4/e" Content-Disposition: inline In-Reply-To: <20130716221436.672d0fba@davenulle.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: Mateusz Guzik , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 05:37:24 -0000 --4oF+6Ged69J0+4/e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 16, 2013 at 10:14:36PM +0200, Patrick Lamaiziere wrote: > Le Tue, 16 Jul 2013 09:05:55 +0300, > Konstantin Belousov a ?crit : >=20 > Hello, >=20 > Thanks Konstantin. I'm trying your patch and that looks better. > poudriere runs since 3 hours now (before the box paniced few minutes > after I start a poudriere bulk) >=20 > (I've removed the previous change to panic on the warning "WARNING: > destroying knlist w/ knotes on it!" / I guess it is ok ?) >=20 > As far I can see gamin still works (xfce sees changes and the "testgam" > tool works fine : https://people.gnome.org/~veillard/gamin/debug.html) Does stopping the gamin server work as well ? >=20 > I will run few "poudriere bulk" tomorrow and report the result here. =20 >=20 > I've tried on my workstation at work which uses the same configuration > as at home, but I was not able to reproduce this problem. The only big > change is that it has 8 GB RAM versus 4 GB here. I don't know what can > trigger this panic. This is something very specific. E.g., you would not be able to reproduce the problem easily with tail -F and forced unmount of the volume. Anyway, if gamin works and stops normally with the patch, I will just commit it. >=20 > If you have patch to test or idea, please let me know. > Thanks, regards. --4oF+6Ged69J0+4/e Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJR5i2OAAoJEJDCuSvBvK1BJRQP/A7OSD9JpllGL+95ON5+PZkx dpYjiqqmoNB+TWYUPvpwJLHjulNXltIuTcpgY2HUhE5k9lCl0dq2M3uahDGOPI/M m2Mayz2LTjL214uwlPdGzfaYPGE71pkbRlN7hZhacyge3dVw/BN18TYeVJAGxi6u LoacuehADDtsGIj5nxnIAv64vk1MDIcY3o3RrAt4WKiSlNCmGn2JQJ0h3ecQulK7 lI4ljSRsL8pUQa+5YKEak+ZkrHQLC1QtaG4x+fC99vOfoHQn8cH3xCJan8RUF8wr f75wnyWz7sVwP8r/+q8Rtnpr/SItkq7MkoZ6ROMhr1SuMiTBtrYY2cjkzlrYUw+c kv1Uc3oXPqZnvz5peDiNrRtuurW9Uw0P4W546GbJxkZdOPqtnOCAOWINCBQLSjn5 f6ud5FDVmVO9mNKsqOwtcVWn3oN001+mPNQ3u/p3jq8vWJxXi5uapAsHHi4o3RRM yTmjH0mIsxxTpW56r6emWJ8MFJfek6CSXKhLmYa/AjItgrrpueUno/x1Hta+ma5h dD3ZJd+SdC8tFrc6T1JUiKoYX6TyJlfvaU27REyILlJJr7D9gpneT3STzZdkssEr JUJGaKPGp1a2BRDjs5PpDTk3Kaf0/Wmsq2WyyumHZD+vbms99wv+QYMo5LQYVcTp EDRpkv5+ltQeyMVg1Kgd =5zZP -----END PGP SIGNATURE----- --4oF+6Ged69J0+4/e-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 08:28:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4BF463BA for ; Wed, 17 Jul 2013 08:28:23 +0000 (UTC) (envelope-from maurizio.vairani@cloverinformatica.it) Received: from smtpdg2.aruba.it (smtpdg220.aruba.it [62.149.158.220]) by mx1.freebsd.org (Postfix) with ESMTP id 862BEC95 for ; Wed, 17 Jul 2013 08:28:21 +0000 (UTC) Received: from cloverinformatica.it ([188.10.129.202]) by smtpcmd01.ad.aruba.it with bizsmtp id 1LT91m00h4N8xN401LT9JH; Wed, 17 Jul 2013 10:27:10 +0200 Received: from [192.168.0.81] (ASUS-TERMINATOR [192.168.0.81]) by cloverinformatica.it (Postfix) with ESMTP id B66FBF5E6; Wed, 17 Jul 2013 10:27:09 +0200 (CEST) Message-ID: <51E6555D.2080803@cloverinformatica.it> Date: Wed, 17 Jul 2013 10:27:09 +0200 From: Maurizio Vairani User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org, freebsd-fs@freebsd.org Subject: Shutdown problem with an USB memory stick as ZFS cache device Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 08:28:23 -0000 Hi all, on a Compaq Presario laptop I have just installed the latest stable #uname -a FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 For speed up the compilation I have added to the pool, tank0, a SanDisk memory stick as cache device with the command: # zpool add tank0 cache /dev/da0 But when I shutdown the laptop the process will halt with this screen shot: http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html and I need to press the power button for more than 4 seconds to switch off the laptop. The problem is always reproducible. Regards Maurizio From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 09:37:21 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E44CD304; Wed, 17 Jul 2013 09:37:20 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 4C9E0F57; Wed, 17 Jul 2013 09:37:20 +0000 (UTC) Received: from alph.d.allbsd.org (p2049-ipbf1102funabasi.chiba.ocn.ne.jp [122.26.101.49]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r6H9b2qu044940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jul 2013 18:37:12 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.5/8.14.5) with ESMTP id r6H9axKh001752; Wed, 17 Jul 2013 18:37:01 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Wed, 17 Jul 2013 18:36:28 +0900 (JST) Message-Id: <20130717.183628.1254490649724740016.hrs@allbsd.org> To: dewayne.geraghty@heuristicsystems.com.au, lukasz@wasikowski.net Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) From: Hiroki Sato In-Reply-To: <14677223DB6D4CD48E880520725B3552@white> <51E53AC7.1040307@wasikowski.net> References: <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <14677223DB6D4CD48E880520725B3552@white> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Wed_Jul_17_18_36_28_2013_430)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Wed, 17 Jul 2013 18:37:13 +0900 (JST) X-Spam-Status: No, score=-89.1 required=13.0 tests=CONTENT_TYPE_PRESENT, DIRECTOCNDYN,DYN_PBL,QENCPTR1,RCVD_IN_PBL,RCVD_IN_RP_RNBL,SPF_SOFTFAIL, USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: rkoberman@gmail.com, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 09:37:21 -0000 ----Security_Multipart(Wed_Jul_17_18_36_28_2013_430)-- Content-Type: Text/Plain; charset=utf-8 Content-Transfer-Encoding: base64 xYF1a2FzeiBXxIVzaWtvd3NraSA8bHVrYXN6QHdhc2lrb3dza2kubmV0PiB3cm90ZQ0KICBpbiA8 NTFFNTNBQzcuMTA0MDMwN0B3YXNpa293c2tpLm5ldD46DQoNCmx1PiBocj4gICAgIyBJUHY0IGFk ZHJlc3MgcmFuZ2Ugc3BlYy4gIE5vdyBkZXByZWNhdGVkLg0KbHU+IGhyPiAgICBpcHY0X2FkZHJf ZW0wPSIxMC4yLjEuMS0xMCINCmx1PiANCmx1PiBTbyBJJ20gYSBsaXR0bGUgY29uZnVzZWQgbm93 IDopIElmIEknZCB1c2UgcG9zdCByMjUyMDE1IHN5c3RlbSB0aGVuDQpsdT4gd291bGQgdGhpcyBi ZSBiZXR0ZXIgd2F5Pw0KbHU+IA0KbHU+IGlmY29uZmlnX2VtMF9hbGlhc2VzPSJpbmV0IDEwLjAu MC42Ni8yOCBpbmV0IDEwLjAuMC42Ny03OCBpbmV0Ng0KbHU+IGZkZGE6NWNjMToyMzo0OjoxLzQ4 IGluZXQ2IGZkZGE6NWNjMToyMzo0OjoyLWYiDQoNCiJEZXdheW5lIEdlcmFnaHR5IiA8ZGV3YXlu ZS5nZXJhZ2h0eUBoZXVyaXN0aWNzeXN0ZW1zLmNvbS5hdT4gd3JvdGUNCiAgaW4gPDE0Njc3MjIz REI2RDRDRDQ4RTg4MDUyMDcyNUIzNTUyQHdoaXRlPjoNCg0KZGU+IFNhdG8tc2FuLA0KZGU+IA0K ZGU+IFlvdSBoYXZlIHByb3ZpZGVkIGEgdmVyeSB1c2VmdWwgc3VtbWFyeSBvZiBpZmNvbmZpZyBw YXJhbWV0ZXJzIGZvcg0KZGU+IHJjLmNvbmYuIEhvd2V2ZXIsIHlvdSBhcmUgbWlzc2luZyBvbmUg ZXhhbXBsZSB0aGF0IHdvdWxkIHByb3ZpZGUNCmRlPiBjbGVhcmVyIHVuZGVyc3RhbmRpbmcuICBX b3VsZCB5b3UgcGxlYXNlIGFkdmlzZSBpZiANCmRlPiAgDQpkZT4gaXB2NF9hZGRyX2VtMD0iMTAu Mi4xLjEtMTAvMzIiDQpkZT4gDQpkZT4gaXMgZGVwcmVjYXRlZCwgYmFja3dhcmQgY29tcGF0aWJs ZSBvciByZW1haW5zIHZhbGlkIGludG8gdGhlIGZ1dHVyZT8NCmRlPiANCmRlPiBJIHBhcnRpY3Vs YXJseSBhcHByZWNpYXRlIHRoZSBzdWNjaW5jdG5lc3Mgb2Y6DQpkZT4gaWZjb25maWdfZW0wX2Fs aWFzZXM9ImluZXQgMTAuMy4zLjIwMS0yMDQvMjQgaW5ldDYNCmRlPiAyMDAxOmRiODoyMTAtMjEz OjoxLzY0IGluZXQgMTAuMS4xLjEvMjQiDQoNCiBUaGUgcmVjb21tZW5kZWQgd2F5IGlzIGlmY29u ZmlnX0lGX2FsaWFzTiBvciBpZmNvbmZpZ19JRl9hbGlhc2VzLg0KIGlwdjRfYWRkcl9JRiB3aWxs IG5vdCBiZSByZW1vdmVkIGluIHRoZSBuZWFyIGZ1dHVyZSwgYnV0IHBsZWFzZSB1c2UNCiBpZmNv bmZpZ19JRl9hbGlhc3tOLGVzfSBmb3IgbmV3bHktY29uZmlndXJlZCBzeXN0ZW1zLiAgQmFja3dh cmQNCiBjb21wYXRpYmlsaXR5IGZvciBub3QgYnJlYWtpbmcgdGhlIGV4aXN0aW5nIGNvbmZpZ3Vy YXRpb25zIHdpbGwgYmUNCiBtYWludGFpbmVkIGFzIG11Y2ggYXMgcG9zc2libGUgKGV2ZW4gb24g dGhlIHVwY29taW5nIDEwLjBSIGFuZA0KIGxhdGVyKS4NCg0KIFRoaXMgaXMgYmVjYXVzZSB3ZSBo YXZlIGEgbG90IG9mIHZhcmlhYmxlcyB3aGljaCBoYXZlIChhbG1vc3QpIHRoZQ0KIHNhbWUgZnVu Y3Rpb25hbGl0eSBpbiByYy5jb25mIGFuZCBJIHdhbnQgdG8gc2ltcGxpZnkgdGhlbSBieSBtZXJn aW5nDQogdGhlbSB3aXRoIGVhY2ggb3RoZXIsIG5vdCBiZWNhdXNlIHRoZXNlIGFyZSBiZXR0ZXIg dGhhbiB0aGUgb3RoZXJzLg0KIFZhcmlhYmxlcyB3aXRoIG92ZXJsYXBwZWQgZnVuY3Rpb25hbGl0 eSBoYXZlIG1hZGUgZGlmZmljdWx0IHRvDQogbWFpbnRhaW4vaW1wcm92ZSB0aGUgcmMuZCBzY3Jp cHRzLg0KDQotLSBIaXJva2kNCg== ----Security_Multipart(Wed_Jul_17_18_36_28_2013_430)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlHmZZwACgkQTyzT2CeTzy1R3wCfW4VxMSSZ9funqp+VZy4t95XX EMsAniJFRTp3L72P140GoW6oaofjPrG3 =35FF -----END PGP SIGNATURE----- ----Security_Multipart(Wed_Jul_17_18_36_28_2013_430)---- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 09:40:18 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E8D45449; Wed, 17 Jul 2013 09:40:18 +0000 (UTC) (envelope-from Ivailo.Tanusheff@skrill.com) Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0253.outbound.messaging.microsoft.com [213.199.154.253]) by mx1.freebsd.org (Postfix) with ESMTP id 4BD67F8C; Wed, 17 Jul 2013 09:40:17 +0000 (UTC) Received: from mail9-db9-R.bigfish.com (10.174.16.230) by DB9EHSOBE017.bigfish.com (10.174.14.80) with Microsoft SMTP Server id 14.1.225.22; Wed, 17 Jul 2013 09:25:05 +0000 Received: from mail9-db9 (localhost [127.0.0.1]) by mail9-db9-R.bigfish.com (Postfix) with ESMTP id 97B8DC80216; Wed, 17 Jul 2013 09:25:05 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI X-SpamScore: -1 X-BigFish: PS-1(zz9371I542I14ffIzz1f42h1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz17326ah8275dhz2fh2a8h668h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh9a9j1155h) Received-SPF: pass (mail9-db9: domain of skrill.com designates 157.56.249.213 as permitted sender) client-ip=157.56.249.213; envelope-from=Ivailo.Tanusheff@skrill.com; helo=AM2PRD0710HT004.eurprd07.prod.outlook.com ; .outlook.com ; X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(377454003)(13464003)(199002)(189002)(53754006)(4396001)(69226001)(63696002)(79102001)(54356001)(33646001)(83072001)(74876001)(74366001)(59766001)(77982001)(65816001)(47446002)(46102001)(76786001)(16406001)(77096001)(74502001)(50986001)(76576001)(54316002)(81342001)(31966008)(49866001)(81542001)(47976001)(47736001)(74316001)(56816003)(66066001)(76796001)(56776001)(51856001)(74662001)(15202345003)(80022001)(53806001)(76482001)(74706001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:DB3PR07MB059; H:DB3PR07MB059.eurprd07.prod.outlook.com; CLIP:217.18.249.148; RD:InfoNoRecords; A:1; MX:1; LANG:en; Received: from mail9-db9 (localhost.localdomain [127.0.0.1]) by mail9-db9 (MessageSwitch) id 1374053102822740_658; Wed, 17 Jul 2013 09:25:02 +0000 (UTC) Received: from DB9EHSMHS009.bigfish.com (unknown [10.174.16.231]) by mail9-db9.bigfish.com (Postfix) with ESMTP id B9673920046; Wed, 17 Jul 2013 09:25:02 +0000 (UTC) Received: from AM2PRD0710HT004.eurprd07.prod.outlook.com (157.56.249.213) by DB9EHSMHS009.bigfish.com (10.174.14.19) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 17 Jul 2013 09:25:02 +0000 Received: from DB3PR07MB059.eurprd07.prod.outlook.com (10.242.137.149) by AM2PRD0710HT004.eurprd07.prod.outlook.com (10.255.165.39) with Microsoft SMTP Server (TLS) id 14.16.329.3; Wed, 17 Jul 2013 09:25:02 +0000 Received: from DB3PR07MB059.eurprd07.prod.outlook.com (10.242.137.149) by DB3PR07MB059.eurprd07.prod.outlook.com (10.242.137.149) with Microsoft SMTP Server (TLS) id 15.0.731.16; Wed, 17 Jul 2013 09:25:00 +0000 Received: from DB3PR07MB059.eurprd07.prod.outlook.com ([169.254.2.117]) by DB3PR07MB059.eurprd07.prod.outlook.com ([169.254.2.117]) with mapi id 15.00.0731.000; Wed, 17 Jul 2013 09:25:00 +0000 From: Ivailo Tanusheff To: Maurizio Vairani , "freebsd-stable@FreeBSD.org" , "freebsd-fs@freebsd.org" Subject: RE: Shutdown problem with an USB memory stick as ZFS cache device Thread-Topic: Shutdown problem with an USB memory stick as ZFS cache device Thread-Index: AQHOgseq21n5ubkB006RuCOsHZ/zxplomN5Q Date: Wed, 17 Jul 2013 09:25:00 +0000 Message-ID: <0243b7c6538240c69770fdd0aaa4e8e0@DB3PR07MB059.eurprd07.prod.outlook.com> References: <51E6555D.2080803@cloverinformatica.it> In-Reply-To: <51E6555D.2080803@cloverinformatica.it> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [217.18.249.148] x-forefront-prvs: 0910AAF391 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: skrill.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 09:40:19 -0000 I think this is expected as your screenshot shows the USB has being disconn= ected, so you actually lost the cache device on the shutdown. Maybe you should implement a shutdown script that removes the USB cache fro= m the pool before the shutdown command is issued :) Best regards, Ivailo Tanusheff -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd= .org] On Behalf Of Maurizio Vairani Sent: Wednesday, July 17, 2013 11:27 AM To: freebsd-stable@FreeBSD.org; freebsd-fs@freebsd.org Subject: Shutdown problem with an USB memory stick as ZFS cache device Hi all, on a Compaq Presario laptop I have just installed the latest stable #uname -a FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16=20 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 For speed up the compilation I have added to the pool, tank0, a SanDisk me= mory stick as cache device with the command: # zpool add tank0 cache /dev/da0 But when I shutdown the laptop the process will halt with this screen shot: http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.= jpg.html and I need to press the power button for more than 4 seconds to switch=20 off the laptop. The problem is always reproducible. Regards Maurizio _______________________________________________ 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 Wed Jul 17 09:50:32 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BAD18703; Wed, 17 Jul 2013 09:50:32 +0000 (UTC) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) by mx1.freebsd.org (Postfix) with ESMTP id 7F0D4A3; Wed, 17 Jul 2013 09:50:32 +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.69) (envelope-from ) id 1UzONM-0002DW-CT; Wed, 17 Jul 2013 11:50:25 +0200 Received: from [81.21.138.17] (helo=ronaldradial.versatec.local) by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1UzONM-0002DC-8P; Wed, 17 Jul 2013 11:50:24 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-stable@freebsd.org, freebsd-fs@freebsd.org, "Maurizio Vairani" Subject: Re: Shutdown problem with an USB memory stick as ZFS cache device References: <51E6555D.2080803@cloverinformatica.it> Date: Wed, 17 Jul 2013 11:50:22 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Ronald Klop" Message-ID: In-Reply-To: <51E6555D.2080803@cloverinformatica.it> User-Agent: Opera Mail/12.16 (Win32) X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: - X-Spam-Score: -1.9 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=disabled version=3.3.1 X-Scan-Signature: dfea3049d3b923820beb462d65569822 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 09:50:32 -0000 On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani wrote: > Hi all, > > > on a Compaq Presario laptop I have just installed the latest stable > > > #uname -a > > FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 > 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 > > > For speed up the compilation I have added to the pool, tank0, a SanDisk > memory stick as cache device with the command: > > > # zpool add tank0 cache /dev/da0 > > > But when I shutdown the laptop the process will halt with this screen > shot: > > > http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html > > > and I need to press the power button for more than 4 seconds to switch > off the laptop. > > The problem is always reproducible. Does sysctl hw.usb.no_shutdown_wait=1 help? Ronald. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 09:56:52 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3B56BA6E for ; Wed, 17 Jul 2013 09:56:52 +0000 (UTC) (envelope-from sowmya@cloudbyte.co) Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) by mx1.freebsd.org (Postfix) with ESMTP id BA44219C for ; Wed, 17 Jul 2013 09:56:51 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id x10so1412571lbi.19 for ; Wed, 17 Jul 2013 02:56:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=dL2l1B65ZwAkmMVkhCvwmwgKQmt2nUUvaneSJj43p9o=; b=XzJAtGSt1lR4j5iZ3IzmpzL4t46LILRp1z/DpUkdEeYjymtRcVDMpbTqu0GwsH11oM 9RJrJ5gqms+HyFdCX9G+kxAx42pBDbirtC60i15YA8m/Tf1u2FDSYXZrU2jC7RZ3j5hg ppD+Q05QnR3uetEntBYBQjkslesyWSZ2qvJh61JETa+z78xGXJ3lJN+ISAUaDQoMDKO+ 7B6cC4/TMpwQ+9KITE/CVIU3FUk9VMT+XNgYUJ2R+OOyqGaH2sdPWP2o6QGcMS7LEd44 RenzGiGKqDjsOP3xnjUL0NT+wl2+B/KGB1G2ZHFPSdrXXUazamETd2oJ674W7eUX0DYX uwLQ== MIME-Version: 1.0 X-Received: by 10.112.28.7 with SMTP id x7mr3011713lbg.7.1374055010148; Wed, 17 Jul 2013 02:56:50 -0700 (PDT) Received: by 10.114.13.138 with HTTP; Wed, 17 Jul 2013 02:56:50 -0700 (PDT) In-Reply-To: References: Date: Wed, 17 Jul 2013 15:26:50 +0530 Message-ID: Subject: Fwd: I/O errors on the pool created using geom_multipath device. From: Sowmya L To: freebsd-stable@freebsd.org X-Gm-Message-State: ALoCoQk702bz78gcANA1WerX6/nmMKJKmLhKuunAlCwA3kYkCso6cxICh+mtV7hK0ojsz/ux3pKk Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 09:56:52 -0000 Hi , Read/Write errors are recorded when an active path of the geom_multipath device is pulled while running the i/o on dataset created for the pool. Running I/o on dataset using dd. *Freebsd version :* 9.0 *Patch imported from stable 9 : *r229303, r234916 *zpool status:* * * pool: poola state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM poola ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 multipath/newdisk4 ONLINE 0 0 0 multipath/newdisk2 ONLINE 0 0 0 errors: No known data errors * * * * *gmultipath status:* * * Name Status Components multipath/newdisk2 OPTIMAL da7 (ACTIVE) da2 (PASSIVE) multipath/newdisk1 OPTIMAL da6 (ACTIVE) da1 (PASSIVE) multipath/newdisk4 OPTIMAL da3 (ACTIVE) da4 (PASSIVE) multipath/newdisk OPTIMAL da0 (ACTIVE) da5 (PASSIVE) multipath/newdisk3 OPTIMAL da8 (ACTIVE) da9 (PASSIVE) * * *zpool status after pulling the active path g_multipath device*: pool: mypool1 state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scan: resilvered 27.2M in 0h0m with 0 errors on Thu Jul 4 19:47:44 2013 config: NAME STATE READ WRITE CKSUM mypool1 ONLINE 0 0 0 mirror-0 ONLINE 0 12 0 multipath/newdisk4 ONLINE 0 27 0 multipath/newdisk2 ONLINE 0 12 0 spares multipath/newdisk AVAIL errors: No known data errors Are there any dependencies for the patch that is picked from stable 9 as mentioned above?? -- Thanks & Regards, Sowmya L -- Thanks & Regards, Sowmya L From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 09:56:58 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E12D6AB8 for ; Wed, 17 Jul 2013 09:56:58 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [94.23.254.147]) by mx1.freebsd.org (Postfix) with ESMTP id AC0C81C4 for ; Wed, 17 Jul 2013 09:56:58 +0000 (UTC) Received: from mr129166.localdomain (mr129166.cri.univ-rennes1.fr [129.20.129.166]) by smtp.lamaiziere.net (Postfix) with ESMTPA id BE75A536B; Wed, 17 Jul 2013 11:56:56 +0200 (CEST) Received: from mr129166 (localhost [127.0.0.1]) by mr129166.localdomain (Postfix) with ESMTP id 05C69397; Wed, 17 Jul 2013 11:56:56 +0200 (CEST) Date: Wed, 17 Jul 2013 11:56:53 +0200 From: Patrick Lamaiziere To: Konstantin Belousov Subject: Re: (9.2) panic under disk load (gam_server / knlist_remove_kq) Message-ID: <20130717115653.00768608@mr129166> In-Reply-To: <20130717053718.GO5991@kib.kiev.ua> References: <20130714115953.1afd6e90@davenulle.org> <20130714163353.2367a6a4@davenulle.org> <20130715142647.GA9293@dft-labs.eu> <20130715185009.052d7614@davenulle.org> <20130716060555.GF91021@kib.kiev.ua> <20130716221436.672d0fba@davenulle.org> <20130717053718.GO5991@kib.kiev.ua> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Mateusz Guzik , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 09:56:59 -0000 Le Wed, 17 Jul 2013 08:37:18 +0300, Konstantin Belousov a écrit : Hello, > > Thanks Konstantin. I'm trying your patch and that looks better. > > poudriere runs since 3 hours now (before the box paniced few minutes > > after I start a poudriere bulk) > > > > (I've removed the previous change to panic on the warning "WARNING: > > destroying knlist w/ knotes on it!" / I guess it is ok ?) > > > > As far I can see gamin still works (xfce sees changes and the > > "testgam" tool works fine : > > https://people.gnome.org/~veillard/gamin/debug.html) > Does stopping the gamin server work as well ? Yes. $ export GAMIN_DEBUG_SERVER="/usr/pkg/usr/ports/devel/gamin/work/gamin-0.1.10/server/gam_server" $ export GAM_CLIENT_ID=test $ export GAM_DEBUG= $ /usr/pkg/usr/ports/devel/gamin/work/gamin-0.1.10/tests/testgam - > connect test FAMOpen() Reusing socket directory /tmp/fam-patrick Asking to launch /usr/pkg/usr/ports/devel/gamin/work/gamin-0.1.10/server/gam_server with client id test /// (ps shows this process) > mondir /poudriere_data/build/9amd64-default ... (some events) ^C $ Then after the end of the client testgam, the gam_server disappears so that looks good. Thanks Konstantin and Mateusz. Regards. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 09:58:51 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8D3F4F20; Wed, 17 Jul 2013 09:58:51 +0000 (UTC) (envelope-from prvs=1910bf16bb=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 0243A286; Wed, 17 Jul 2013 09:58:49 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50005028799.msg; Wed, 17 Jul 2013 10:58:40 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Wed, 17 Jul 2013 10:58:40 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1910bf16bb=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <6ACFDC285CB64C148915BC0FD8357B11@multiplay.co.uk> From: "Steven Hartland" To: , , "Maurizio Vairani" , "Ronald Klop" References: <51E6555D.2080803@cloverinformatica.it> Subject: Re: Shutdown problem with an USB memory stick as ZFS cache device Date: Wed, 17 Jul 2013 10:59:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response 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.14 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, 17 Jul 2013 09:58:51 -0000 ----- Original Message ----- From: "Ronald Klop" > > Does sysctl hw.usb.no_shutdown_wait=1 help? That will just prevent the wait it won't stop the shutdown from happening. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 10:28:33 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 909AFB15 for ; Wed, 17 Jul 2013 10:28:33 +0000 (UTC) (envelope-from maurizio.vairani@cloverinformatica.it) Received: from smtpdg9.aruba.it (smtpdg8.aruba.it [62.149.158.238]) by mx1.freebsd.org (Postfix) with ESMTP id ECA8E7E2 for ; Wed, 17 Jul 2013 10:28:32 +0000 (UTC) Received: from cloverinformatica.it ([188.10.129.202]) by smtpcmd03.ad.aruba.it with bizsmtp id 1NUN1m01L4N8xN401NUPLB; Wed, 17 Jul 2013 12:28:24 +0200 Received: from [192.168.0.100] (MAURIZIO-PC [192.168.0.100]) by cloverinformatica.it (Postfix) with ESMTP id 8571BF651; Wed, 17 Jul 2013 12:28:23 +0200 (CEST) Message-ID: <51E671C7.50409@cloverinformatica.it> Date: Wed, 17 Jul 2013 12:28:23 +0200 From: Maurizio Vairani User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Ronald Klop Subject: [SOLVED] Re: Shutdown problem with an USB memory stick as ZFS cache device References: <51E6555D.2080803@cloverinformatica.it> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 10:28:33 -0000 On 17/07/2013 11:50, Ronald Klop wrote: > On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani > wrote: > >> Hi all, >> >> >> on a Compaq Presario laptop I have just installed the latest stable >> >> >> #uname -a >> >> FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 >> 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 >> >> >> For speed up the compilation I have added to the pool, tank0, a >> SanDisk memory stick as cache device with the command: >> >> >> # zpool add tank0 cache /dev/da0 >> >> >> But when I shutdown the laptop the process will halt with this screen >> shot: >> >> >> http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html >> >> >> >> and I need to press the power button for more than 4 seconds to >> switch off the laptop. >> >> The problem is always reproducible. > > Does sysctl hw.usb.no_shutdown_wait=1 help? > > Ronald. Thank you Ronald it works ! In /boot/loader.conf added the line hw.usb.no_shutdown_wait=1 Maurizio From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 10:38:41 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 862C4EF7; Wed, 17 Jul 2013 10:38:41 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 842F6857; Wed, 17 Jul 2013 10:38:40 +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 NAA01409; Wed, 17 Jul 2013 13:38:38 +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 1UzP81-00002p-NS; Wed, 17 Jul 2013 13:38:37 +0300 Message-ID: <51E67409.3010901@FreeBSD.org> Date: Wed, 17 Jul 2013 13:38:01 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130708 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org, freebsd-fs@FreeBSD.org Subject: Re: Shutdown problem with an USB memory stick as ZFS cache device References: <51E6555D.2080803@cloverinformatica.it> In-Reply-To: X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 10:38:41 -0000 on 17/07/2013 12:50 Ronald Klop said the following: > Does sysctl hw.usb.no_shutdown_wait=1 help? I believe that the root cause of the issue is that ZFS does not perform full clean up on shutdown and thus does not release its devices. But perhaps I am mistaken. In any case, I think that doing the same kind of clean up as done on zfs module unload would be advantageous. -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 11:09:30 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3ADAA808 for ; Wed, 17 Jul 2013 11:09:30 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from mail.tyknet.dk (mail.tyknet.dk [176.9.9.186]) by mx1.freebsd.org (Postfix) with ESMTP id EF8109A9 for ; Wed, 17 Jul 2013 11:09:29 +0000 (UTC) Received: from [10.10.1.214] (217.71.4.82.static.router4.bolignet.dk [217.71.4.82]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.tyknet.dk (Postfix) with ESMTPSA id 01580160E67 for ; Wed, 17 Jul 2013 13:09:21 +0200 (CEST) X-DKIM: OpenDKIM Filter v2.5.2 mail.tyknet.dk 01580160E67 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gibfest.dk; s=default; t=1374059362; bh=kxj5j+fAcQx135d8HoyFdRyqeoYxaHJnFzXUtkU+n0E=; h=Date:From:To:Subject:References:In-Reply-To; b=tTfRhawvfKtpYH1ORqXipsxcwwxaLAO/EfNZBCl9bjNkNVQAU8ksoFbsXAaQ038+o 23sPzoQESOgK8acqIVtwxCPSijUWgS29Q9OSehdp9krvL51qYVKhsCu4Pw03LU4A2n 17msvm+NSFk8s+WqpMZQU3l2+5Ww65vxgX2wi4X4= Message-ID: <51E67B5B.5020603@gibfest.dk> Date: Wed, 17 Jul 2013 13:09:15 +0200 From: Thomas Steen Rasmussen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) References: <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <14677223DB6D4CD48E880520725B3552@white> <20130717.183628.1254490649724740016.hrs@allbsd.org> In-Reply-To: <20130717.183628.1254490649724740016.hrs@allbsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 11:09:30 -0000 On 17-07-2013 11:36, Hiroki Sato wrote: > The recommended way is ifconfig_IF_aliasN or ifconfig_IF_aliases. > ipv4_addr_IF will not be removed in the near future, but please use > ifconfig_IF_alias{N,es} for newly-configured systems. Hello, Does this work on stable/9 or only on current ? If not, are there any plans to MFC ? I ask because I don't see the ifconfig_IF_aliases syntax in /etc/defaults/rc.conf on a newly built stable/9 box. Thanks for this by the way - it _greatly_ simplifies rc.conf on my jail hosts, very nice. Best regards, Thomas Steen Rasmussen From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 11:41:34 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 787D2CD3 for ; Wed, 17 Jul 2013 11:41:34 +0000 (UTC) (envelope-from feld@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5108CAB5 for ; Wed, 17 Jul 2013 11:41:34 +0000 (UTC) Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 46EB320F1C; Wed, 17 Jul 2013 07:41:33 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute4.internal (MEProxy); Wed, 17 Jul 2013 07:41:33 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=ySUdwuL/IphP37XYm8qYS4oMK2g=; b=C5x JwU9WbWRvmcgZsRPXEP/YY1iMhvonz6ibDA5FdIuS0kkE+JK9yDjiRLW7KPZ9UPc JwPiNZar27eUYufJkZJUi83F7C7dSMdTuKJk2yKj5ji3c+7hIZ145qiGdznLiM/l 4MarogkkRAFMN4OMvlKaBWzHMk9ymwwKm6Ua0li0= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 1AE03B00005; Wed, 17 Jul 2013 07:41:33 -0400 (EDT) Message-Id: <1374061293.32153.140661256672461.5D4916ED@webmail.messagingengine.com> X-Sasl-Enc: aAxXOksQ2wrM912NpPY0+zoTqbcFx8XrVz+B3zttLxtR 1374061293 From: Mark Felder To: Thomas Steen Rasmussen , freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-5a449c7a In-Reply-To: <51E67B5B.5020603@gibfest.dk> References: <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <14677223DB6D4CD48E880520725B3552@white> <20130717.183628.1254490649724740016.hrs@allbsd.org> <51E67B5B.5020603@gibfest.dk> Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) Date: Wed, 17 Jul 2013 06:41:33 -0500 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 11:41:34 -0000 On Wed, Jul 17, 2013, at 6:09, Thomas Steen Rasmussen wrote: > Hello, > > Does this work on stable/9 or only on current ? If not, are there > any plans to MFC ? I ask because I don't see the > ifconfig_IF_aliases syntax in /etc/defaults/rc.conf on a newly > built stable/9 box. > It's there in /etc/defaults/rc.conf, but maybe not very obvious: #ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample alias entry. It is also in the Handbook: http://www.freebsd.org/doc/en/books/handbook/configtuning-virtual-hosts.html From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 11:48:49 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3164F7C; Wed, 17 Jul 2013 11:48:49 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from mail.tyknet.dk (mail.tyknet.dk [176.9.9.186]) by mx1.freebsd.org (Postfix) with ESMTP id E3C7AB04; Wed, 17 Jul 2013 11:48:48 +0000 (UTC) Received: from [10.10.1.214] (217.71.4.82.static.router4.bolignet.dk [217.71.4.82]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.tyknet.dk (Postfix) with ESMTPSA id C0859160EDA; Wed, 17 Jul 2013 13:48:47 +0200 (CEST) X-DKIM: OpenDKIM Filter v2.5.2 mail.tyknet.dk C0859160EDA DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gibfest.dk; s=default; t=1374061727; bh=A5E+e0+ao9I7hH9EiyfT1DrPX5h+6A+57SPRXGt9wB0=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=egQkSqkeEPCIigG4SdarfSiZtScdZien3pkz/Gu/EQLm0oa7gSID1K8liA5WXphyS jNedeARh4FApQCJU+lEXcMiVOW3X0sUAmFKaZ74dkyLfstdCqN50ncWPlNONz55WPo w85GMuaWOfMBa5a2UMtVUxb9MXAHmIkL06C0i+2k= Message-ID: <51E68498.8090801@gibfest.dk> Date: Wed, 17 Jul 2013 13:48:40 +0200 From: Thomas Steen Rasmussen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Mark Felder Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) References: <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <14677223DB6D4CD48E880520725B3552@white> <20130717.183628.1254490649724740016.hrs@allbsd.org> <51E67B5B.5020603@gibfest.dk> <1374061293.32153.140661256672461.5D4916ED@webmail.messagingengine.com> In-Reply-To: <1374061293.32153.140661256672461.5D4916ED@webmail.messagingengine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 11:48:49 -0000 On 17-07-2013 13:41, Mark Felder wrote: > On Wed, Jul 17, 2013, at 6:09, Thomas Steen Rasmussen wrote: >> Hello, >> >> Does this work on stable/9 or only on current ? If not, are there >> any plans to MFC ? I ask because I don't see the >> ifconfig_IF_aliases syntax in /etc/defaults/rc.conf on a newly >> built stable/9 box. >> > It's there in /etc/defaults/rc.conf, but maybe not very obvious: > > #ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample > alias entry. > > It is also in the Handbook: > > http://www.freebsd.org/doc/en/books/handbook/configtuning-virtual-hosts.html Hello, There is a big difference between ifconfig_IF_aliasN which is v4 only and requires a line for each IP, and must be continous, meaning that _alias1, _alias2, _alias4 wont work - and the new fancy ifconfig_IF_aliases which accepts both address families and also ranges and stuff. I was asking about the new _aliases form. Thanks! /Thomas Steen Rasmussen From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 11:55:21 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 900E9343; Wed, 17 Jul 2013 11:55:21 +0000 (UTC) (envelope-from feld@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 657EBB4D; Wed, 17 Jul 2013 11:55:21 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C2C4D218E5; Wed, 17 Jul 2013 07:55:20 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute2.internal (MEProxy); Wed, 17 Jul 2013 07:55:20 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=gYLEasA0ladY2ALXrpTZcBHKchc=; b=JCn+q VOE3epLWDOrmBF+LEs92e6H1ppKYLawxUF9wkqi04rjAp2bFNbZbnHIgV7sftO8O nd4khgOHLFZQy92oszJqbUpV+qsa2XlyqKnREyLRXhjDJ6VfsQUeyxFwTW6mV0tS uMRReeRxvKX70l3Pd+4N1HYNRjAF8rr89SRFCU= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 8EF54B00003; Wed, 17 Jul 2013 07:55:20 -0400 (EDT) Message-Id: <1374062120.4532.140661256673649.36ED5B44@webmail.messagingengine.com> X-Sasl-Enc: JB1mJyAVB42XOS2LqpWjwaWFdPdlHFiV3gfN3ZDiPnk3 1374062120 From: Mark Felder To: Hiroki Sato , dewayne.geraghty@heuristicsystems.com.au, lukasz@wasikowski.net MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-5a449c7a Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) Date: Wed, 17 Jul 2013 06:55:20 -0500 In-Reply-To: <20130717.183628.1254490649724740016.hrs@allbsd.org> References: <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> <14677223DB6D4CD48E880520725B3552@white> <20130717.183628.1254490649724740016.hrs@allbsd.org> Cc: rkoberman@gmail.com, freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 11:55:21 -0000 On Wed, Jul 17, 2013, at 4:36, Hiroki Sato wrote: > > The recommended way is ifconfig_IF_aliasN or ifconfig_IF_aliases. > ipv4_addr_IF will not be removed in the near future, but please use > ifconfig_IF_alias{N,es} for newly-configured systems. Backward > compatibility for not breaking the existing configurations will be > maintained as much as possible (even on the upcoming 10.0R and > later). > Almost everyone is familiar with ifconfig_IF_aliasN, but can you provide example syntax for ifconfig_IF_aliases ? I've never seen that before and can't find it documented. > > This is because we have a lot of variables which have (almost) the > same functionality in rc.conf and I want to simplify them by merging > them with each other, not because these are better than the others. > Variables with overlapped functionality have made difficult to > maintain/improve the rc.d scripts. > I would actually prefer to see the ifconfig_IF_aliasN syntax go away entirely as it simply cannot scale without becoming tedious. I know we can't cover every edge case, but after discussing with people on this list about the desire for ipv6_addrs_IF, now committed, it seems I'm not the only example of this use case. The best scenario I can describe is a situation where you have a shared webhosting environment on FreeBSD. I may very well have 200 IPs on one server. Being able to use ranges and CIDR syntax is invaluable. The idea of ifconfig_IF_aliasN is not so bad as long as you never have to make any changes. However, it's not uncommon to receive a work order from sales where a customer needs to be moved from the shared webhosting environment to their own private VM. We need to move the IP they were using as we probably do not control DNS and it might be difficult for the customer to get that changed. Removing an IP from the middle of 200 ifconfig_IF_aliasN entries requires you to renumber them all. This is simply cruel and error-prone. Being able to adjust the ranges of ipv4_addrs_IF is much cleaner and reliable. This thread isn't exactly the proper forum to debate the future of network configuration on FreeBSD, but please take this into consideration. And thank you for your work on the rc.d scripts -- they're the #1 reason many of us prefer working with FreeBSD. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 13:19:27 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1D3CF8B6; Wed, 17 Jul 2013 13:19:27 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 89ADEEFA; Wed, 17 Jul 2013 13:19:26 +0000 (UTC) Received: from alph.d.allbsd.org (p2049-ipbf1102funabasi.chiba.ocn.ne.jp [122.26.101.49]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r6HDJ86u067464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jul 2013 22:19:19 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.5/8.14.5) with ESMTP id r6HDJ8MF003847; Wed, 17 Jul 2013 22:19:08 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Wed, 17 Jul 2013 22:18:57 +0900 (JST) Message-Id: <20130717.221857.228051450632054039.hrs@allbsd.org> To: feld@FreeBSD.org Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) From: Hiroki Sato In-Reply-To: <1374062120.4532.140661256673649.36ED5B44@webmail.messagingengine.com> References: <14677223DB6D4CD48E880520725B3552@white> <20130717.183628.1254490649724740016.hrs@allbsd.org> <1374062120.4532.140661256673649.36ED5B44@webmail.messagingengine.com> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Wed_Jul_17_22_18_57_2013_471)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Wed, 17 Jul 2013 22:19:20 +0900 (JST) X-Spam-Status: No, score=-88.7 required=13.0 tests=CONTENT_TYPE_PRESENT, DIRECTOCNDYN, DYN_PBL, FAKEDWORD_ZERO, RCVD_IN_PBL, RCVD_IN_RP_RNBL, SPF_SOFTFAIL, USER_IN_WHITELIST,X_CHINESE_RELAY autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: freebsd-stable@FreeBSD.org, rkoberman@gmail.com, lukasz@wasikowski.net, dewayne.geraghty@heuristicsystems.com.au X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 13:19:27 -0000 ----Security_Multipart(Wed_Jul_17_22_18_57_2013_471)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mark Felder wrote in <1374062120.4532.140661256673649.36ED5B44@webmail.messagingengine.com>: fe> On Wed, Jul 17, 2013, at 4:36, Hiroki Sato wrote: fe> > fe> > The recommended way is ifconfig_IF_aliasN or ifconfig_IF_aliases. fe> > ipv4_addr_IF will not be removed in the near future, but please use fe> > ifconfig_IF_alias{N,es} for newly-configured systems. Backward fe> > compatibility for not breaking the existing configurations will be fe> > maintained as much as possible (even on the upcoming 10.0R and fe> > later). fe> > fe> fe> Almost everyone is familiar with ifconfig_IF_aliasN, but can you provide fe> example syntax for ifconfig_IF_aliases ? I've never seen that before and fe> can't find it documented. I committed some descriptions about it to rc.conf(5) at the same time. It is basically the same as ifconfig_IF_aliasN, but can have multiple address specification. Both of ifconfig_IF_alias{N,es} now supports range specification, so there is no difference in the functionality. The following two examples give the same result: ifconfig_ed0_alias0="inet 127.0.0.251 netmask 0xffffffff" ifconfig_ed0_alias1="inet 127.0.0.252 netmask 0xffffffff" ifconfig_ed0_alias2="inet 127.0.0.253 netmask 0xffffffff" ifconfig_ed0_alias3="inet 127.0.0.254 netmask 0xffffffff" ifconfig_ed0_aliases="\ inet 127.0.0.251 netmask 0xffffffff \ inet 127.0.0.252 netmask 0xffffffff \ inet 127.0.0.253 netmask 0xffffffff \ inet 127.0.0.254 netmask 0xffffffff \ " The implementation actually converts values in the variables in ifconfig_IF_aliasN, ipv6_ifconfig_IF_aliasN, and ipv4_addrs_IF into a list of them in a consistent format (AF-keyword + address spec + options) used in ifconfig_IF_aliases, and then it processes ifconfig_IF_aliases and them. ifconfig_IF_aliasN accepts address spec without address family keyword for backward compatibility, but ifconfig_IF_aliases does not. This is the difference between the two. fe> This thread isn't exactly the proper forum to debate the future of fe> network configuration on FreeBSD, but please take this into fe> consideration. And thank you for your work on the rc.d scripts -- fe> they're the #1 reason many of us prefer working with FreeBSD. Fair enough. Please do not hesitate to speak up on freebsd-rc@ for this kind of topics. -- Hiroki ----Security_Multipart(Wed_Jul_17_22_18_57_2013_471)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlHmmcEACgkQTyzT2CeTzy0yfACfccDdqLfKM7LKHlTHujotPnNF LHoAmQGBihWAWdUnZOmbyc7zR+/L48ZO =AJd5 -----END PGP SIGNATURE----- ----Security_Multipart(Wed_Jul_17_22_18_57_2013_471)---- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 14:18:00 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 85EC5FE5; Wed, 17 Jul 2013 14:18:00 +0000 (UTC) (envelope-from feld@freebsd.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5DD40240; Wed, 17 Jul 2013 14:18:00 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 41571212DF; Wed, 17 Jul 2013 10:17:59 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Wed, 17 Jul 2013 10:17:59 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=iQSoIYfHYAqRiOeZpz8fbKIcX5U=; b=F/8 64w3hYpFdOwx8bc4VrndgFdPumMJC1hG+rzBpBX6E1it2IsxAU17L80ubybUWKby jUZzZ0whNR5ac+babvbiZghNLop7+ArGNfoM4o/iUhAM9rbxSTVYuZqwhZ/l24ZS dZ2ZAv/TRfVZUVkOaYvqzLmVrzSczdcWnlSY2Xuw= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 18E92B00003; Wed, 17 Jul 2013 10:17:58 -0400 (EDT) Message-Id: <1374070678.20685.140661256728705.40B5AA9C@webmail.messagingengine.com> X-Sasl-Enc: 9yr7oOJjiY6JePKksFOrFi1bXsIxvbH4h75s+IxxbbB4 1374070678 From: Mark Felder To: Hiroki Sato MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-5a449c7a In-Reply-To: <20130717.221857.228051450632054039.hrs@allbsd.org> References: <14677223DB6D4CD48E880520725B3552@white> <20130717.183628.1254490649724740016.hrs@allbsd.org> <1374062120.4532.140661256673649.36ED5B44@webmail.messagingengine.com> <20130717.221857.228051450632054039.hrs@allbsd.org> Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) Date: Wed, 17 Jul 2013 09:17:58 -0500 Cc: freebsd-stable@FreeBSD.org, rkoberman@gmail.com, lukasz@wasikowski.net, dewayne.geraghty@heuristicsystems.com.au X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 14:18:00 -0000 Thanks for that info, Hiroki. I'm running CURRENT on my main server and do see this now. Could you also make a note to add it to /etc/default/rc.conf as well? Thanks! From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 15:30:02 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7DAC37B9; Wed, 17 Jul 2013 15:30:02 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from land.berklix.org (land.berklix.org [144.76.10.75]) by mx1.freebsd.org (Postfix) with ESMTP id EC7FC8D1; Wed, 17 Jul 2013 15:30:01 +0000 (UTC) Received: from park.js.berklix.net (pD9FBEF06.dip0.t-ipconnect.de [217.251.239.6]) (authenticated bits=128) by land.berklix.org (8.14.5/8.14.5) with ESMTP id r6HFTwND089577; Wed, 17 Jul 2013 15:29:59 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.14.3/8.14.3) with ESMTP id r6HFTpWF004069; Wed, 17 Jul 2013 17:29:51 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id r6HFT4EK063849; Wed, 17 Jul 2013 17:29:10 +0200 (CEST) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201307171529.r6HFT4EK063849@fire.js.berklix.net> To: Maurizio Vairani Subject: Re: [SOLVED] Re: Shutdown problem with an USB memory stick as ZFS cache device From: "Julian H. Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 17 Jul 2013 12:28:23 +0200." <51E671C7.50409@cloverinformatica.it> Date: Wed, 17 Jul 2013 17:29:04 +0200 Sender: jhs@berklix.com Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Ronald Klop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 15:30:02 -0000 Maurizio Vairani wrote: > On 17/07/2013 11:50, Ronald Klop wrote: > > On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani > > wrote: > > > >> Hi all, > >> > >> > >> on a Compaq Presario laptop I have just installed the latest stable > >> > >> > >> #uname -a > >> > >> FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 > >> 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 > >> > >> > >> For speed up the compilation I have added to the pool, tank0, a > >> SanDisk memory stick as cache device with the command: > >> > >> > >> # zpool add tank0 cache /dev/da0 > >> > >> > >> But when I shutdown the laptop the process will halt with this screen > >> shot: > >> > >> > >> http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html > >> > >> > >> > >> and I need to press the power button for more than 4 seconds to > >> switch off the laptop. > >> > >> The problem is always reproducible. > > > > Does sysctl hw.usb.no_shutdown_wait=1 help? > > > > Ronald. > Thank you Ronald it works ! > > In /boot/loader.conf added the line > hw.usb.no_shutdown_wait=1 > > Maurizio I wonder (from ignorance as I dont use ZFS yet), if that merely masks the symptom or cures the fault ? Presumably one should use a ZFS command to disassociate whatever might have the cache open ? (in case something might need to be written out from cache, if it was a writeable cache ?) I too had a USB shutdown problem (non ZFS, now solved) & several people made useful comments on shutdown scripts etc, so I'm cross referencing: http://lists.freebsd.org/pipermail/freebsd-mobile/2013-July/012803.html Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. No quoted-printable, HTML, base64, multipart/alternative. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 16:02:13 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DF55FF8F for ; Wed, 17 Jul 2013 16:02:13 +0000 (UTC) (envelope-from lab@gta.com) Received: from mailgate.gta.com (mailgate.gta.com [199.120.225.20]) by mx1.freebsd.org (Postfix) with ESMTP id A90DAA82 for ; Wed, 17 Jul 2013 16:02:12 +0000 (UTC) Received: (qmail 56293 invoked by uid 1000); 17 Jul 2013 11:55:31 -0400 Date: Wed, 17 Jul 2013 11:55:31 -0400 From: Larry Baird To: freebsd-stable@freebsd.org Subject: bce and "Warning: bootcode thinks driver is absent." Message-ID: <20130717155531.GA52015@gta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: yongari@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 16:02:13 -0000 Recently under amd64 and 9.1-STABLE I am seeing issues with the bce driver. Message is "Warning: bootcode thinks driver is absent". After this message, the box appears to be wedged. After rebooting, it got the same message during fsck. So we installed 9.2 pre-release using a snapshot iso from 7/13/13. Shortly after boot we got the same message. We are now in the process of installing 9.1 release to verify this is a driver issue and not hardware flaking out. Anybody else seen this issue? Thank you for your time, Larry -- ------------------------------------------------------------------------ Larry Baird Global Technology Associates, Inc. 1992-2012 | http://www.gta.com Celebrating Twenty Years of Software Innovation | Orlando, FL Email: lab@gta.com | TEL 407-380-0220 From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 18:07:10 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C7B543BB for ; Wed, 17 Jul 2013 18:07:10 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id 9CEA715A for ; Wed, 17 Jul 2013 18:07:10 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so4835826iec.27 for ; Wed, 17 Jul 2013 11:07:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; bh=z125jsncMZtP0Zj2Z+lCvIdzUU5voF0nU+YHHXc/s/I=; b=iKXq1fJKhMsIGVuooniHApd4b3otF8KJkPrT3znllDFJcdkWA8YioHKL4hfaoNhlvW RtWh/QtDoInYe3JpNX33lK+S4lxtRyjIXvXQwO7QyV6ULlmgZXYbLhuRmQoAbUd9OXRB uO8yQuM9kkqqy4CfNgm7koR4UYJkILEqwAeKN8GvuNP1pV2qO1MBUpAmuygZHasklT6I jdKQzMNpJtYQJvb/Cam4rH53rxVos/omumQ/H/LD0BKlNf18bAAQuz4+BZmVIK0qJ89u LOp2Bx4UG5reWsHb1txZ3Ak/yZY/mxpp0M1+oeSpVGzyU3FAiJMKy/+BCtHezug9wq5D 4ANA== X-Received: by 10.50.225.66 with SMTP id ri2mr1681949igc.55.1374084430392; Wed, 17 Jul 2013 11:07:10 -0700 (PDT) Received: from charmander (mail1.sandvine.com. [64.7.137.162]) by mx.google.com with ESMTPSA id nm17sm30284167igb.5.2013.07.17.11.07.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Jul 2013 11:07:09 -0700 (PDT) Sender: Mark Johnston Date: Wed, 17 Jul 2013 14:07:55 -0400 From: Mark Johnston To: freebsd-stable@freebsd.org Subject: syncer causing latency spikes Message-ID: <20130717180720.GA8289@charmander> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 18:07:10 -0000 Hello, I'm trying to investigate and solve some postgres latency spikes that I'm seeing as a result of some behaviour in the syncer. This is with FreeBSD 8.2 (with some local modifications and backports, r231160 in particular). The system has an LSI 9261-8i RAID controller (backed by mfi(4)) and the database and WALs are on separate volumes, a RAID 6 and a RAID 1 respectively. It has about 96GB of RAM installed. What's happening is that the syncer tries to fsync a large database file and goes to sleep in getpbuf() with the corresponding vnode lock held and the following stack: #3 0xffffffff805fceb5 in _sleep (ident=0xffffffff80ca8e20, lock=0xffffffff80d6bc20, priority=-2134554464, wmesg=0xffffffff80a4fe43 "wswbuf0", timo=0) at /d2/usr/src/sys/kern/kern_synch.c:234 #4 0xffffffff808780d5 in getpbuf (pfreecnt=0xffffffff80ca8e20) at /d2/usr/src/sys/vm/vm_pager.c:339 #5 0xffffffff80677a00 in cluster_wbuild (vp=0xffffff02ea3d7ce8, size=16384, start_lbn=20869, len=2) at /d2/usr/src/sys/kern/vfs_cluster.c:801 #6 0xffffffff808477ed in ffs_syncvnode (vp=0xffffff02ea3d7ce8, waitfor=Variable "waitfor" is not available.) at /d2/usr/src/sys/ufs/ffs/ffs_vnops.c:306 #7 0xffffffff808488cf in ffs_fsync (ap=0xffffff9b0cd27b00) at /d2/usr/src/sys/ufs/ffs/ffs_vnops.c:190 #8 0xffffffff8096798a in VOP_FSYNC_APV (vop=0xffffffff80ca5300, a=0xffffff9b0cd27b00) at vnode_if.c:1267 #9 0xffffffff8068bade in sync_vnode (slp=0xffffff002ab8e758, bo=0xffffff9b0cd27bc0, td=0xffffff002ac89460) at vnode_if.h:549 #10 0xffffffff8068bdcd in sched_sync () at /d2/usr/src/sys/kern/vfs_subr.c:1841 (kgdb) frame 6 #6 0xffffffff808477ed in ffs_syncvnode (vp=0xffffff02ea3d7ce8, waitfor=Variable "waitfor" is not available.) at /d2/usr/src/sys/ufs/ffs/ffs_vnops.c:306 306 vfs_bio_awrite(bp); (kgdb) vpath vp 0xffffff02ea3d7ce8: 18381 0xffffff02eab1dce8: 16384 0xffffff02eaaf0588: base 0xffffff01616d8b10: data 0xffffff01616d8ce8: pgsql 0xffffff002af9f588: 0xffffff002af853b0: d3 0xffffff002abd6b10: / (kgdb) During such an fsync, DTrace shows me that syncer sleeps of 50-200ms are happening up to 8 or 10 times a second. When this happens, a bunch of postgres threads become blocked in vn_write() waiting for the vnode lock to become free. It looks like the write-clustering code is limited to using (nswbuf / 2) pbufs, and FreeBSD prevents one from setting nswbuf to anything greater than 256. Since the sleeps are happening in the write-clustering code, I tried disabling write clustering on the mountpoint (with the noclusterw mount option) and found that this replaces my problem with another one: the syncer periodically generates large bursts of writes that create a backlog in the mfi(4) bioq. Then postgres' reads take a few seconds to return, causing more or less the same end result. Does anyone have any suggestions on what I can do to help reduce the impact of the syncer on my systems? I can't just move to a newer version of FreeBSD, but I'm willing to backport changes if anyone can point me to something that might help. Thanks, -Mark From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 18:33:55 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F0E81940; Wed, 17 Jul 2013 18:33:55 +0000 (UTC) (envelope-from trashcan@odo.in-berlin.de) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [91.121.60.26]) by mx1.freebsd.org (Postfix) with ESMTP id BC90D286; Wed, 17 Jul 2013 18:33:55 +0000 (UTC) Received: from sulu.fritz.box (p5DDC1812.dip0.t-ipconnect.de [93.220.24.18]) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 3bwRvQ6h23zRKP; Wed, 17 Jul 2013 20:33:54 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) From: Michael Grimm In-Reply-To: <20130712.160358.1330135778606339435.hrs@allbsd.org> Date: Wed, 17 Jul 2013 20:33:54 +0200 Content-Transfer-Encoding: 7bit Message-Id: References: <20130712.135621.1408565802386368060.hrs@allbsd.org> <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> To: X-Mailer: Apple Mail (2.1508) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 18:33:56 -0000 On 12.07.2013, at 09:03, Hiroki Sato wrote: > Please let me know if the existing configurations and/or the new > formats do not work. First of all: great work! It is that much easier to deal with aliases, now. There is only one minor issue, if at all: rc.conf: | ifconfig_em0_ipv6="inet6 dead:beef:1111:2222::1 prefixlen 56" | ifconfig_em0_aliases="\ | inet6 dead:beef:1111:2222::2-3 prefixlen 56 \ | inet6 dead:beef:1111:2222::4 prefixlen 56 \ | inet6 dead:beef:1111:2222::5-6/56" ifconfig: | inet6 dead:beef:1111:2222::1 prefixlen 56 | inet6 dead:beef:1111:2222::2 prefixlen 64 | inet6 dead:beef:1111:2222::3 prefixlen 64 | inet6 dead:beef:1111:2222::4 prefixlen 56 | inet6 dead:beef:1111:2222::5 prefixlen 56 | inet6 dead:beef:1111:2222::6 prefixlen 56 Any combination of a range definition (2-3) *and* "prefixlen 56" is ignored whereas a range definition (5-6) *and* "/56" is interpreted as wanted. Well, that combination of a range and "prefix" isn't documented, thus I am not sure if that's an issue or a feature? With kind regards, Michael From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 19:19:03 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 01E3D453; Wed, 17 Jul 2013 19:19:03 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4CE25642; Wed, 17 Jul 2013 19:19:02 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r6HJIqmC089035; Wed, 17 Jul 2013 22:18:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r6HJIqmC089035 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r6HJIqDD089034; Wed, 17 Jul 2013 22:18:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 17 Jul 2013 22:18:52 +0300 From: Konstantin Belousov To: Mark Johnston Subject: Re: syncer causing latency spikes Message-ID: <20130717191852.GS5991@kib.kiev.ua> References: <20130717180720.GA8289@charmander> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lx6+J6gHrzwEpYNy" Content-Disposition: inline In-Reply-To: <20130717180720.GA8289@charmander> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 19:19:03 -0000 --lx6+J6gHrzwEpYNy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 17, 2013 at 02:07:55PM -0400, Mark Johnston wrote: > Hello, >=20 > I'm trying to investigate and solve some postgres latency spikes that > I'm seeing as a result of some behaviour in the syncer. This is with > FreeBSD 8.2 (with some local modifications and backports, r231160 in > particular). The system has an LSI 9261-8i RAID controller (backed by > mfi(4)) and the database and WALs are on separate volumes, a RAID 6 and > a RAID 1 respectively. It has about 96GB of RAM installed. >=20 > What's happening is that the syncer tries to fsync a large database file > and goes to sleep in getpbuf() with the corresponding vnode lock held > and the following stack: >=20 > #3 0xffffffff805fceb5 in _sleep (ident=3D0xffffffff80ca8e20, lock=3D0xff= ffffff80d6bc20, priority=3D-2134554464, wmesg=3D0xffffffff80a4fe43 "wswbuf0= ", timo=3D0) at /d2/usr/src/sys/kern/kern_synch.c:234 > #4 0xffffffff808780d5 in getpbuf (pfreecnt=3D0xffffffff80ca8e20) at /d2/= usr/src/sys/vm/vm_pager.c:339 > #5 0xffffffff80677a00 in cluster_wbuild (vp=3D0xffffff02ea3d7ce8, size= =3D16384, start_lbn=3D20869, len=3D2) at /d2/usr/src/sys/kern/vfs_cluster.c= :801 > #6 0xffffffff808477ed in ffs_syncvnode (vp=3D0xffffff02ea3d7ce8, waitfor= =3DVariable "waitfor" is not available.) at /d2/usr/src/sys/ufs/ffs/ffs_vno= ps.c:306 > #7 0xffffffff808488cf in ffs_fsync (ap=3D0xffffff9b0cd27b00) at /d2/usr/= src/sys/ufs/ffs/ffs_vnops.c:190 > #8 0xffffffff8096798a in VOP_FSYNC_APV (vop=3D0xffffffff80ca5300, a=3D0x= ffffff9b0cd27b00) at vnode_if.c:1267 > #9 0xffffffff8068bade in sync_vnode (slp=3D0xffffff002ab8e758, bo=3D0xff= ffff9b0cd27bc0, td=3D0xffffff002ac89460) at vnode_if.h:549 > #10 0xffffffff8068bdcd in sched_sync () at /d2/usr/src/sys/kern/vfs_subr.= c:1841 >=20 > (kgdb) frame 6 > #6 0xffffffff808477ed in ffs_syncvnode (vp=3D0xffffff02ea3d7ce8, waitfor= =3DVariable "waitfor" is not available.) at /d2/usr/src/sys/ufs/ffs/ffs_vno= ps.c:306 > 306 vfs_bio_awrite(bp); > (kgdb) vpath vp > 0xffffff02ea3d7ce8: 18381 > 0xffffff02eab1dce8: 16384 > 0xffffff02eaaf0588: base > 0xffffff01616d8b10: data > 0xffffff01616d8ce8: pgsql > 0xffffff002af9f588: > 0xffffff002af853b0: d3 > 0xffffff002abd6b10: / > (kgdb) >=20 > During such an fsync, DTrace shows me that syncer sleeps of 50-200ms are > happening up to 8 or 10 times a second. When this happens, a bunch of > postgres threads become blocked in vn_write() waiting for the vnode lock > to become free. It looks like the write-clustering code is limited to > using (nswbuf / 2) pbufs, and FreeBSD prevents one from setting nswbuf > to anything greater than 256. Syncer is probably just a victim of profiling. Would postgres called fsync(2), you then blame the fsync code for the pauses. Just add a tunable to allow the user to manually-tune the nswbuf, regardless of the buffer cache sizing. And yes, nswbuf default max probably should be bumped to something like 1024, at least on 64bit architectures which do not starve for kernel memory. >=20 > Since the sleeps are happening in the write-clustering code, I tried > disabling write clustering on the mountpoint (with the noclusterw mount > option) and found that this replaces my problem with another one: the > syncer periodically generates large bursts of writes that create a > backlog in the mfi(4) bioq. Then postgres' reads take a few seconds to > return, causing more or less the same end result. Well, this is exactly what clustering code is for, merge a lot of short i/o requests into the bigger i/o ? >=20 > Does anyone have any suggestions on what I can do to help reduce the > impact of the syncer on my systems? I can't just move to a newer version > of FreeBSD, but I'm willing to backport changes if anyone can point me > to something that might help. As a side note, syncer code for UFS was redone in HEAD and 9 to only iterate over the active vnodes. This is mostly irrelevant to your problems which happen when syncer does perform the i/o, but still it saves a lot of CPU. --lx6+J6gHrzwEpYNy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJR5u4bAAoJEJDCuSvBvK1BIicQAIX9KpI4uwHfTpcdzry0pBjO g5jl7r23MH2Y/34snX1oNfW0TWIP9dSypMZnmioswLLEVa3G/CFL+dr+A1tCaznc 4WctmktebGlyhjN1qZus/xLhNA1xeiXvSjiPccFTBnd53ce79+FrKvpsQICLXJwh hzPfHFG4x3VCkbRP/tKj/F000MlYaZm2QUXsp7uSJahd/L0E1UfdRuw/oxUG9dG8 KqtUuq8i2uBZMCR8b/AsRZ9LNOymjc6DKcDEeuQi4xTp51GvMMqy/mspkb0LJDBj YjsbdhV9fGOArq1TehknwTps0ApdK10++mv0r2QKj5IDOsYhOKDJMg9giYa81bbb jD3qdMMPVeLqjQxqeGOx1jbKwV0NXvHonOU2b41Bo3xJL8WkdtT3RxeyPNYeLhUZ 2UYTr1k+zCDUnSckK1RH1ezLLiFxfOczpODoWecQI1pq3LNHI3LoH3zblsqzugiJ nO/eMes2P4szPXTYy8pFI6q8m+XFeOsdJi6j+C+GC56O95Gfzp3I8gaPIKSaidoS hXuCAXzqZRW1A6ByaMMl5eZIJdXwDWCT+OEWZh0jfwyB2IXO/FmAgqfLTnCRvdJK uiV1Uvofm325EXldTHT5HeAZW6SHrJHZj6m9It1Tjw13JuuZkgT2w+/n9O3kVYD3 Fv8y4JZIk4/cne0TQo6Z =8U9c -----END PGP SIGNATURE----- --lx6+J6gHrzwEpYNy-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 20:15:51 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 96197480; Wed, 17 Jul 2013 20:15:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) by mx1.freebsd.org (Postfix) with ESMTP id 7045E904; Wed, 17 Jul 2013 20:15:51 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D1765B922; Wed, 17 Jul 2013 16:15:49 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: syncer causing latency spikes Date: Wed, 17 Jul 2013 16:15:35 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <20130717180720.GA8289@charmander> <20130717191852.GS5991@kib.kiev.ua> In-Reply-To: <20130717191852.GS5991@kib.kiev.ua> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201307171615.35484.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 17 Jul 2013 16:15:49 -0400 (EDT) Cc: Konstantin Belousov , smh@freebsd.org, Mark Johnston X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 20:15:51 -0000 On Wednesday, July 17, 2013 3:18:52 pm Konstantin Belousov wrote: > On Wed, Jul 17, 2013 at 02:07:55PM -0400, Mark Johnston wrote: > > During such an fsync, DTrace shows me that syncer sleeps of 50-200ms are > > happening up to 8 or 10 times a second. When this happens, a bunch of > > postgres threads become blocked in vn_write() waiting for the vnode lock > > to become free. It looks like the write-clustering code is limited to > > using (nswbuf / 2) pbufs, and FreeBSD prevents one from setting nswbuf > > to anything greater than 256. > Syncer is probably just a victim of profiling. Would postgres called > fsync(2), you then blame the fsync code for the pauses. > > Just add a tunable to allow the user to manually-tune the nswbuf, > regardless of the buffer cache sizing. And yes, nswbuf default max > probably should be bumped to something like 1024, at least on 64bit > architectures which do not starve for kernel memory. Also, if you are seeing I/O stalls with mfi(4), then you might need a firmware update for your mfi(4) controller. cc'ing smh@ who knows more about that particular issue (IIRC). -- John Baldwin From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 20:47:58 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D61F0DA2 for ; Wed, 17 Jul 2013 20:47:58 +0000 (UTC) (envelope-from hartzell@alacrity.alerce.com) Received: from griffon.alerce.com (griffon.alerce.com [206.125.171.162]) by mx1.freebsd.org (Postfix) with ESMTP id B40D9AB3 for ; Wed, 17 Jul 2013 20:47:58 +0000 (UTC) Received: from griffon.alerce.com (localhost [127.0.0.1]) by griffon.alerce.com (Postfix) with ESMTP id B2E0E2842A for ; Wed, 17 Jul 2013 13:47:55 -0700 (PDT) Received: from alacrity.alerce.com (75-149-38-78-SFBA.hfc.comcastbusiness.net [75.149.38.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by griffon.alerce.com (Postfix) with ESMTPSA id 652C228424 for ; Wed, 17 Jul 2013 13:47:55 -0700 (PDT) Received: by alacrity.alerce.com (Postfix, from userid 503) id 2874C150594E; Wed, 17 Jul 2013 13:47:52 -0700 (PDT) From: George Hartzell Message-ID: <20967.760.95825.310085@gargle.gargle.HOWL> Date: Wed, 17 Jul 2013 13:47:52 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-stable@freebsd.org Subject: Help with filing a [maybe] ZFS/mmap bug. X-Mailer: VM 8.2.0b under 24.2.1 (x86_64-apple-darwin) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 20:47:59 -0000 Hi All, I have what I think is a ZFS related bug. Unfortunately my simplest test case is a bit cumbersome and I haven't definitively proven that the problem is ZFS related. I'm hoping for some feedback on how to move forward. Quick background: I rip my CD's using grip and produce flac files. I tag the music using Musicbrainz' Picard and transcode it to mp3's within Picard using a plugin that I wrote. Picard is a python based app and uses the Mutagen library to tag files. I'm working on a MacPro with 10GB ram and using Seagate ST31000340AS drives updated to the latest firmware (SD1A). The system is running 9-STABLE from late June. It is ZFS only and boots from a mirrored pool that provides a bunch of zfs filesystems, including my home directory. I recently realized that some of the flacs were corrupt and have been chasing down the problem. I've blamed Picard, my disks (there was newer, "important" firmware, which they're now running), my RAM, etc... After blaming each of the moving parts in turn I offer up the following experiment as evidence that I have found a ZFS problem. - start with a bunch of untagged flac files that pass validation with "flac -t". - load them into Picard, tag them and save them (this also transcodes them to mp3's using my plugin and runs a plugin which runs flac -t on the tagged file). - run flac -t on all of the tag flac files and collect the result as pre-exit-validation. - exit Picard "politely" (using the menu options, not killing it from the command line...). - run flac -t on all of the tag flac files and collect the result post-exit-validation. - reboot the machine - run flac -t on all of the tag flac files and collect the result post-reboot-validation. On multiple runs through this routine I'll sometimes see errors in the {pre,post}-exit-validations, but they'll often all validate perfectly. On all of the runs through the validation I'll see many invalid files in the post-reboot-validation output. I've even scp'd the directories to an unrelated machine (Mac OS X 10.8) at the various points to do the "flac -t" validation, with the same results. Looking carefully at a couple of instances shows that they differ in a few bytes. E.g. one file differs by a few bytes starting at 139253 to 139264 (I might have an off by one counting issue, using emacs' buffer positions here). 2^17 + 2^13 = 139264, which is an interesting coincidence. In another file I see a difference ending at 2^17+2^12 (again, I might be off by one or so in my counting). Patching the different hunk from a good file into a bad file (again via emacs) results in a file that passes validation. At one point I was blaming RAM and was pulling/swapping sims. Running with less memory increased the likelihood of files being invalid. I built up a similar system running 9-STABLE as of yesterday (7/16) that uses UFS and have been unable to recreate the problem. Given that the files are valid after exiting Picard, I do not think that there is anything in my tagging pipeline that is causing the problem. The fact that the files "become" invalid after a reboot suggests something in the ZFS buffering and/or interactions with the VM system. The observation that running with less memory causes more/earlier problems reinforces this. The fact that the garbage in the file happens near a power-of-two boundry also reinforces this. My current test case involves my local version of Picard and my plugins, and 165 flac files (some of which Picard can discover automatically based on grip's freedb based metadata, some of which need a helping hand). Not particularly minimal but I'm not sure that I can ever get it trimmed down to something trivial that a ZFS developer might be able to run locally. Thanks for making it this far! How should I move forward with this? g. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 21:13:40 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CD722544 for ; Wed, 17 Jul 2013 21:13:40 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [94.23.254.147]) by mx1.freebsd.org (Postfix) with ESMTP id 98EE0BF0 for ; Wed, 17 Jul 2013 21:13:40 +0000 (UTC) Received: from roxette.lamaiziere.net (232.176.97.84.rev.sfr.net [84.97.176.232]) by smtp.lamaiziere.net (Postfix) with ESMTPA id BD8F25467; Wed, 17 Jul 2013 23:13:32 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by roxette.lamaiziere.net (Postfix) with ESMTP id E56C5640; Wed, 17 Jul 2013 23:13:31 +0200 (CEST) Date: Wed, 17 Jul 2013 23:13:30 +0200 From: Patrick Lamaiziere To: freebsd-stable@freebsd.org Subject: Re: (9.2) panic under disk load (gam_server / knlist_remove_kq) Message-ID: <20130717231330.45bfa778@davenulle.org> In-Reply-To: <20130716221436.672d0fba@davenulle.org> References: <20130714115953.1afd6e90@davenulle.org> <20130714163353.2367a6a4@davenulle.org> <20130715142647.GA9293@dft-labs.eu> <20130715185009.052d7614@davenulle.org> <20130716060555.GF91021@kib.kiev.ua> <20130716221436.672d0fba@davenulle.org> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: Konstantin Belousov , Mateusz Guzik X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 21:13:40 -0000 Le Tue, 16 Jul 2013 22:14:36 +0200, Patrick Lamaiziere a écrit : Hello, > Thanks Konstantin. I'm trying your patch and that looks better. > poudriere runs since 3 hours now (before the box paniced few minutes > after I start a poudriere bulk) > > (I've removed the previous change to panic on the warning "WARNING: > destroying knlist w/ knotes on it!" / I guess it is ok ?) > > As far I can see gamin still works (xfce sees changes and the > "testgam" tool works fine : > https://people.gnome.org/~veillard/gamin/debug.html) > > I will run few "poudriere bulk" tomorrow and report the result here. looks good :) Many thanks! Regards. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 21:42:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 65785EA7 for ; Wed, 17 Jul 2013 21:42:38 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by mx1.freebsd.org (Postfix) with ESMTP id 39FA2D1E for ; Wed, 17 Jul 2013 21:42:38 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id c10so5312786ieb.38 for ; Wed, 17 Jul 2013 14:42:37 -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=8Dzfn/bm1SGYFt3bBT7Egz12sFMqLs97852EpBKBP8I=; b=WaleYh5yS018aTFG2e1N5VR078S7LTuOejZSgvFrlC4UJL1LmrU5jFcD9EVD0V8nfD Gfw9sGbCi1tgF4pIbv8PtxVSsmg8D1aHF6me4Z9JV9voUayAO/Jx5bTJ3JmYbf3ZHvRv rUNb6sj68TA65S+9zngCLpDBMItsr3rdqrA1CvoXzYgFDJD2I1OLn1A0/yf5pxWr/EtK jkPcvAevTCKeA00cg5Cj138/sEw68jAlWsllSswMSa685YtWd+oUtHsIxJKpK6lU+yR1 68uFXpGaIVm48Hv6/bGzqNfHveEczu7yLboktz4sO4cuSPSoPajmujVldr2w7mZT5a5R 6KBQ== X-Received: by 10.43.73.7 with SMTP id yq7mr5406335icb.76.1374097357850; Wed, 17 Jul 2013 14:42:37 -0700 (PDT) Received: from charmander (mail1.sandvine.com. [64.7.137.162]) by mx.google.com with ESMTPSA id n8sm31057913igk.7.2013.07.17.14.42.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Jul 2013 14:42:37 -0700 (PDT) Sender: Mark Johnston Date: Wed, 17 Jul 2013 17:43:25 -0400 From: Mark Johnston To: Konstantin Belousov Subject: Re: syncer causing latency spikes Message-ID: <20130717214325.GB8289@charmander> References: <20130717180720.GA8289@charmander> <20130717191852.GS5991@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130717191852.GS5991@kib.kiev.ua> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 21:42:38 -0000 On Wed, Jul 17, 2013 at 10:18:52PM +0300, Konstantin Belousov wrote: > On Wed, Jul 17, 2013 at 02:07:55PM -0400, Mark Johnston wrote: > > Hello, > > > > I'm trying to investigate and solve some postgres latency spikes that > > I'm seeing as a result of some behaviour in the syncer. This is with > > FreeBSD 8.2 (with some local modifications and backports, r231160 in > > particular). The system has an LSI 9261-8i RAID controller (backed by > > mfi(4)) and the database and WALs are on separate volumes, a RAID 6 and > > a RAID 1 respectively. It has about 96GB of RAM installed. > > > > What's happening is that the syncer tries to fsync a large database file > > and goes to sleep in getpbuf() with the corresponding vnode lock held > > and the following stack: > > > > #3 0xffffffff805fceb5 in _sleep (ident=0xffffffff80ca8e20, lock=0xffffffff80d6bc20, priority=-2134554464, wmesg=0xffffffff80a4fe43 "wswbuf0", timo=0) at /d2/usr/src/sys/kern/kern_synch.c:234 > > #4 0xffffffff808780d5 in getpbuf (pfreecnt=0xffffffff80ca8e20) at /d2/usr/src/sys/vm/vm_pager.c:339 > > #5 0xffffffff80677a00 in cluster_wbuild (vp=0xffffff02ea3d7ce8, size=16384, start_lbn=20869, len=2) at /d2/usr/src/sys/kern/vfs_cluster.c:801 > > #6 0xffffffff808477ed in ffs_syncvnode (vp=0xffffff02ea3d7ce8, waitfor=Variable "waitfor" is not available.) at /d2/usr/src/sys/ufs/ffs/ffs_vnops.c:306 > > #7 0xffffffff808488cf in ffs_fsync (ap=0xffffff9b0cd27b00) at /d2/usr/src/sys/ufs/ffs/ffs_vnops.c:190 > > #8 0xffffffff8096798a in VOP_FSYNC_APV (vop=0xffffffff80ca5300, a=0xffffff9b0cd27b00) at vnode_if.c:1267 > > #9 0xffffffff8068bade in sync_vnode (slp=0xffffff002ab8e758, bo=0xffffff9b0cd27bc0, td=0xffffff002ac89460) at vnode_if.h:549 > > #10 0xffffffff8068bdcd in sched_sync () at /d2/usr/src/sys/kern/vfs_subr.c:1841 > > > > (kgdb) frame 6 > > #6 0xffffffff808477ed in ffs_syncvnode (vp=0xffffff02ea3d7ce8, waitfor=Variable "waitfor" is not available.) at /d2/usr/src/sys/ufs/ffs/ffs_vnops.c:306 > > 306 vfs_bio_awrite(bp); > > (kgdb) vpath vp > > 0xffffff02ea3d7ce8: 18381 > > 0xffffff02eab1dce8: 16384 > > 0xffffff02eaaf0588: base > > 0xffffff01616d8b10: data > > 0xffffff01616d8ce8: pgsql > > 0xffffff002af9f588: > > 0xffffff002af853b0: d3 > > 0xffffff002abd6b10: / > > (kgdb) > > > > During such an fsync, DTrace shows me that syncer sleeps of 50-200ms are > > happening up to 8 or 10 times a second. When this happens, a bunch of > > postgres threads become blocked in vn_write() waiting for the vnode lock > > to become free. It looks like the write-clustering code is limited to > > using (nswbuf / 2) pbufs, and FreeBSD prevents one from setting nswbuf > > to anything greater than 256. > Syncer is probably just a victim of profiling. Would postgres called > fsync(2), you then blame the fsync code for the pauses. True, and postgres does frequently fsync(2) its own database files as part its checkpointing operations. However, every time I take a look at what's happening during an I/O spike, it's the syncer that's holding the lock. I'm digging into the postgres internals right now, but I think that it mangages to avoid having a backend writing to a database file at the same time that the bg writer is fsync(2)ing it. postgres takes care to checkpoint its files when it wants to ensure that data has been written out, so it seems to me that the syncer's behaviour is at least somewhat redundant here. > > Just add a tunable to allow the user to manually-tune the nswbuf, > regardless of the buffer cache sizing. And yes, nswbuf default max > probably should be bumped to something like 1024, at least on 64bit > architectures which do not starve for kernel memory. I ended trying that right after I wrote the first email. I goosed up nswbuf to 8192 and found that it just exacerbated the problem - the syncer still ends up going to sleep waiting for pbufs, but it generates a lot more I/O than before and mfi(4)'s bioq becomes huge; I saw it go up to 20000 regularly, which takes a while to drain. > > > > > Since the sleeps are happening in the write-clustering code, I tried > > disabling write clustering on the mountpoint (with the noclusterw mount > > option) and found that this replaces my problem with another one: the > > syncer periodically generates large bursts of writes that create a > > backlog in the mfi(4) bioq. Then postgres' reads take a few seconds to > > return, causing more or less the same end result. > Well, this is exactly what clustering code is for, merge a lot of > short i/o requests into the bigger i/o ? Right - it's what I expected. I just wanted to preemptively answer the question of "what happens if you disable clustering?" > > > > > Does anyone have any suggestions on what I can do to help reduce the > > impact of the syncer on my systems? I can't just move to a newer version > > of FreeBSD, but I'm willing to backport changes if anyone can point me > > to something that might help. > > As a side note, syncer code for UFS was redone in HEAD and 9 to only > iterate over the active vnodes. This is mostly irrelevant to your > problems which happen when syncer does perform the i/o, but still it > saves a lot of CPU. I noticed that change yesterday when I was going through some commit logs. I'd like to bring it in at some point, but as you point out, it probably doesn't really help with this particular problem since the CPUs are mostly idle in my test setup. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 21:45:40 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id ADB52FEE; Wed, 17 Jul 2013 21:45:40 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id 6ECB9D50; Wed, 17 Jul 2013 21:45:40 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id u16so5251026iet.23 for ; Wed, 17 Jul 2013 14:45:40 -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=qpp8FxmuVpYsr4L6WK85wQFxBnwIjxtiMI9z6PGXr5k=; b=OTJloyLZINqp8j/BRcympa+iOCuuJ4VLMTBd2zXumP5CAEJE9WFf1KeVK9IGy3JieQ a36FOU47xWkQhOqgTnWXb17T09luP391ZCwApTm6DnI7RU4aCDNpUzxhDjCv4TEorWLi gfId4mo/xZ/HbomaibFYmyiAOSiXErBTe5NUbGSzt+YKRhlcK8epvGkBNGFGhcKIYm7Y hgCFdkKBozlo5XRf5v6nGGmpf6D+GenMcwt3ZE+ZVyNfuMRxMHGAEXQy4cxIIx1PxXmC nIZU8FFnpG/Bl6/8QMKSxAHrtyLVJT/BKSDAJEpwjR8TqnreNN/TeQsq/LGBIaZZ3s5k kN4A== X-Received: by 10.50.16.8 with SMTP id b8mr11399351igd.1.1374097540054; Wed, 17 Jul 2013 14:45:40 -0700 (PDT) Received: from charmander (mail1.sandvine.com. [64.7.137.162]) by mx.google.com with ESMTPSA id o14sm31083363igw.2.2013.07.17.14.45.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Jul 2013 14:45:39 -0700 (PDT) Sender: Mark Johnston Date: Wed, 17 Jul 2013 17:46:27 -0400 From: Mark Johnston To: John Baldwin Subject: Re: syncer causing latency spikes Message-ID: <20130717214627.GC8289@charmander> References: <20130717180720.GA8289@charmander> <20130717191852.GS5991@kib.kiev.ua> <201307171615.35484.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201307171615.35484.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Konstantin Belousov , smh@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 21:45:40 -0000 On Wed, Jul 17, 2013 at 04:15:35PM -0400, John Baldwin wrote: > On Wednesday, July 17, 2013 3:18:52 pm Konstantin Belousov wrote: > > On Wed, Jul 17, 2013 at 02:07:55PM -0400, Mark Johnston wrote: > > > During such an fsync, DTrace shows me that syncer sleeps of 50-200ms are > > > happening up to 8 or 10 times a second. When this happens, a bunch of > > > postgres threads become blocked in vn_write() waiting for the vnode lock > > > to become free. It looks like the write-clustering code is limited to > > > using (nswbuf / 2) pbufs, and FreeBSD prevents one from setting nswbuf > > > to anything greater than 256. > > Syncer is probably just a victim of profiling. Would postgres called > > fsync(2), you then blame the fsync code for the pauses. > > > > Just add a tunable to allow the user to manually-tune the nswbuf, > > regardless of the buffer cache sizing. And yes, nswbuf default max > > probably should be bumped to something like 1024, at least on 64bit > > architectures which do not starve for kernel memory. > > Also, if you are seeing I/O stalls with mfi(4), then you might need a > firmware update for your mfi(4) controller. cc'ing smh@ who knows more about > that particular issue (IIRC). I tried upgrading the firmware to the latest available image (I believe it was from March), but that didn't help. I wouldn't call my problem a stall in the sense of commands timing out (which I've seen before), it's just that we manage to generate a large enough backlog that the driver/controller take at least several seconds to clear it, during which all I/O is stalled in the kernel. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 22:06:06 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B1F36D9E for ; Wed, 17 Jul 2013 22:06:06 +0000 (UTC) (envelope-from oemc2017@bol.com.br) Received: from a2-sato3.bol.com.br (a2-sato3.bol.com.br [200.147.32.242]) by mx1.freebsd.org (Postfix) with ESMTP id 39B46E9D for ; Wed, 17 Jul 2013 22:06:06 +0000 (UTC) Received: from smtps.bol.com.br (a4-smart2.host.intranet [10.131.129.51]) by a2-sato3.bol.com.br (Postfix) with ESMTP id D201980065C9 for ; Wed, 17 Jul 2013 19:00:43 -0300 (BRT) Received: from localhost (localhost.localdomain [127.0.0.1]) by a4-smart2.bol.com.br (Postfix) with ESMTP id 6BA40E0000AA for ; Wed, 17 Jul 2013 19:00:37 -0300 (BRT) X-UOL-SMTP: SMTPS465 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bol.com.br; s=afl; t=1374098437; bh=GDO1T5tZLVZgg6m657/7ASedvw35fvd5OvHiF00t4lI=; h=From:To:Cc:Subject:Date; b=Hee8oEA8pyGXi26Uwf6Kjb/YatS1uFZDsXrZLVGKfUfhOTI4Ah98eABB/wRGcfMOp Z1i+7A+T543e4ioZUEyaR6lEVahq7O7LCCqQk0XhT9nY5pow1qNHSYc9KKd6iQTgH9 kjQgAkewyFb13UbdupeuFHK4PvnSuh7aH47MhK1Y= Received: from UserPC (201-41-175-179.fozit701.dsl.brasiltelecom.net.br [201.41.175.179]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by a4-smart2.bol.com.br (Postfix) with ESMTPSA id E1990E000090 for ; Wed, 17 Jul 2013 19:00:35 -0300 (BRT) thread-index: Ac6DORPECP+GyuqHRZqMXuzXuVqrpg== Thread-Topic: =?iso-8859-1?Q?RAUL_GIL_ACABOU_DE_LAN=C7AR_UM_MMN_-_CADASTRO_GR=C1TIS__-_?= =?iso-8859-1?Q?_________________________________=28yhejv=29?= From: To: Cc: Subject: =?iso-8859-1?Q?RAUL_GIL_ACABOU_DE_LAN=C7AR_UM_MMN_-_CADASTRO_GR=C1TIS__-_?= =?iso-8859-1?Q?_________________________________=28yhejv=29?= Date: Wed, 17 Jul 2013 19:00:40 -0300 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft CDO for Windows 2000 Content-Class: urn:content-classes:message Importance: normal Priority: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7600.16385 X-SpikeMilter3: MISS X-SIG5: 1347938911ae6c5dfc37c4a107e8b889 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 22:06:06 -0000 (yhejv) RAUL GIL ACABOU DE LAN=C7AR UM MMN O RAUL GIL ACABOU DE LAN=C7AR UM MMN E J=C1 ADERIRAM MAIS DE 50 MIL PESSOAS. O CADASTRO =C9 GR=C1TIS. ENTRE VC TB. PARA ENTRAR, BASTA = CLICAR: http://dumba.com.br/jairfoz VEJA O VIDEO DO RAUL GIL NO YOUTUBE: http://www.youtube.com/watch?v=3DmeQfKK5Yqzo OBRIGADO, JAIR ROJAS DA SILVA (yhejv) From owner-freebsd-stable@FreeBSD.ORG Wed Jul 17 22:58:47 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 30159187; Wed, 17 Jul 2013 22:58:47 +0000 (UTC) (envelope-from smh@freebsd.org) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id EC409196; Wed, 17 Jul 2013 22:58:46 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id 3D58D20E7088C; Wed, 17 Jul 2013 22:58:45 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-2.2 required=8.0 tests=ALL_TRUSTED,AWL,BAYES_00, 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 ESMTPA id B339920E70847; Wed, 17 Jul 2013 22:58:43 +0000 (UTC) Message-ID: From: "Steven Hartland" To: "John Baldwin" , References: <20130717180720.GA8289@charmander> <20130717191852.GS5991@kib.kiev.ua> <201307171615.35484.jhb@freebsd.org> Subject: Re: syncer causing latency spikes Date: Wed, 17 Jul 2013 23:59:10 +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 Cc: Konstantin Belousov , Mark Johnston X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 17 Jul 2013 22:58:47 -0000 ----- Original Message ----- From: "John Baldwin" > On Wednesday, July 17, 2013 3:18:52 pm Konstantin Belousov wrote: >> On Wed, Jul 17, 2013 at 02:07:55PM -0400, Mark Johnston wrote: >> > During such an fsync, DTrace shows me that syncer sleeps of 50-200ms are >> > happening up to 8 or 10 times a second. When this happens, a bunch of >> > postgres threads become blocked in vn_write() waiting for the vnode lock >> > to become free. It looks like the write-clustering code is limited to >> > using (nswbuf / 2) pbufs, and FreeBSD prevents one from setting nswbuf >> > to anything greater than 256. >> Syncer is probably just a victim of profiling. Would postgres called >> fsync(2), you then blame the fsync code for the pauses. >> >> Just add a tunable to allow the user to manually-tune the nswbuf, >> regardless of the buffer cache sizing. And yes, nswbuf default max >> probably should be bumped to something like 1024, at least on 64bit >> architectures which do not starve for kernel memory. > > Also, if you are seeing I/O stalls with mfi(4), then you might need a > firmware update for your mfi(4) controller. cc'ing smh@ who knows more about > that particular issue (IIRC). Indeed if your seeing any IO timeouts in /var/log/messages or the console there is a know issue in older mfi(4) firmware which can cause extended IO stalls. We believe that fixed firmware packages include "APP" version > *.130.* For Dell branded HW that corrisponds with FW package version 21.2.1-0000 Regards Steve From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 00:41:24 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 30D53FD3 for ; Thu, 18 Jul 2013 00:41:24 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo103.cox.net (fed1rmfepo103.cox.net [68.230.241.145]) by mx1.freebsd.org (Postfix) with ESMTP id 1176E7F1 for ; Thu, 18 Jul 2013 00:41:23 +0000 (UTC) Received: from fed1rmimpo306 ([68.230.241.174]) by fed1rmfepo103.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130718004123.XIZV3894.fed1rmfepo103.cox.net@fed1rmimpo306> for ; Wed, 17 Jul 2013 20:41:23 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo306 with cox id 1chN1m00d2oShb201chNN4; Wed, 17 Jul 2013 20:41:23 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020204.51E739B3.0027,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=XPTuv3dE c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=ktNfuVtv0skA:10 a=8nJEP1OIZ-IA:10 a=05pWP5ZVAAAA:8 a=wdeVDi26gDEA:10 a=1AP1W6Bq7vjQAHV62EUA:9 a=wPNLvfGTeEIA:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r6HHUkME074980 for ; Wed, 17 Jul 2013 17:30:47 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51E73AA9.5030004@reynoldsnet.org> Date: Wed, 17 Jul 2013 17:45:29 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: stable@freebsd.org Subject: experience with 9.2-PRERELEASE 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.14 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, 18 Jul 2013 00:41:24 -0000 Hello all, I have some feedback for the recently prepared snapshot of 9.2-RELEASE. I've been trying like crazy to get the 9x series code installed on a brand new workstation I'm building. It consists of a brand new ASRock motherboard and haswell i7-4770k processor, Z87 chipset. I tried at first to install 9.1-RELEASE. it worked (after I learned a bit about the new installer--I have used FreeBSD "forever" but have been "out of it" in terms of this list and other going's on for about a year due to workload), but upon booting I was getting "timeout" errors ahcich0: Timeout on slot xx port 0 ahcich0: is 000000000 cs 00000000 ss e0000000 rs e0000000 tfd 40 serr 00000000 cmd 0004df17 to the SSD that I used as the primary hard drive. So, then I figured I would try a more recent snapshot hoping that something had been spotted and fixed already. I got the 9.2-PRERELEASE amd64 snapshot and tried to install it. However, I couldn't even get past the first screen of the install because of these messages: ugen0.2: (Unknown) at usbus0 (disconnected) uhub_reattach_port: could not allocate new device and the keyboard was non-functional. It just sat there spewing these errors about 1 per second. So, even though I'm having some sort of ahci "timeout" issue with this hardware and 9.1-RELEASE, it certainly appears that something has zig-zagged in the usb stack in this 9.2-PRELEASE snapshot because I can't even get through the install program. :(. Same hardware, same everything. I also tried the 9.2-PRELEASE i386 snapshot for giggles. Same result. The final blow to my sanity was when I rolled back and tried to install 8.4-RELEASE and sysinstall couldn't make the disk devices after I hit 'W' in the disk label editor to commit my changes. So, I'm wondering generically are people having problems with SSD's in FreeBSD? In this hardware I have not tried using a traditional SATA disk yet. But just thought I would report that 9.2-PRERELEASE can't even get through install on this H/W where 9.1 could......... -Jr From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 00:48:58 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F1C6327A; Thu, 18 Jul 2013 00:48:57 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) by mx1.freebsd.org (Postfix) with ESMTP id B0647849; Thu, 18 Jul 2013 00:48:57 +0000 (UTC) Received: from glenbarber.us (nucleus.glenbarber.us [IPv6:2001:470:8:1205:2:2:ff:29]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 9F25B9A37; Thu, 18 Jul 2013 00:48:56 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 9F25B9A37 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Wed, 17 Jul 2013 20:48:54 -0400 From: Glen Barber To: John Reynolds Subject: Re: experience with 9.2-PRERELEASE Message-ID: <20130718004854.GC2264@glenbarber.us> References: <51E73AA9.5030004@reynoldsnet.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="uxuisgdDHaNETlh8" Content-Disposition: inline In-Reply-To: <51E73AA9.5030004@reynoldsnet.org> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 00:48:58 -0000 --uxuisgdDHaNETlh8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi John, On Wed, Jul 17, 2013 at 05:45:29PM -0700, John Reynolds wrote: > Hello all, I have some feedback for the recently prepared snapshot > of 9.2-RELEASE. >=20 > I've been trying like crazy to get the 9x series code installed on a > brand new workstation I'm building. It consists of a brand new > ASRock motherboard and haswell i7-4770k processor, Z87 chipset. I > tried at first to install 9.1-RELEASE. it worked (after I learned a > bit about the new installer--I have used FreeBSD "forever" but have > been "out of it" in terms of this list and other going's on for > about a year due to workload), but upon booting I was getting > "timeout" errors >=20 > ahcich0: Timeout on slot xx port 0 > ahcich0: is 000000000 cs 00000000 ss e0000000 rs e0000000 tfd 40 > serr 00000000 cmd 0004df17 >=20 > to the SSD that I used as the primary hard drive. So, then I figured > I would try a more recent snapshot hoping that something had been > spotted and fixed already. I got the 9.2-PRERELEASE amd64 snapshot > and tried to install it. However, I couldn't even get past the first > screen of the install because of these messages: >=20 > ugen0.2: (Unknown) at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device >=20 > and the keyboard was non-functional. It just sat there spewing these > errors about 1 per second. >=20 > So, even though I'm having some sort of ahci "timeout" issue with > this hardware and 9.1-RELEASE, it certainly appears that something > has zig-zagged in the usb stack in this 9.2-PRELEASE snapshot > because I can't even get through the install program. :(. Same > hardware, same everything. >=20 > I also tried the 9.2-PRELEASE i386 snapshot for giggles. Same result. >=20 > The final blow to my sanity was when I rolled back and tried to > install 8.4-RELEASE and sysinstall couldn't make the disk devices > after I hit 'W' in the disk label editor to commit my changes. So, > I'm wondering generically are people having problems with SSD's in > FreeBSD? In this hardware I have not tried using a traditional SATA > disk yet. >=20 > But just thought I would report that 9.2-PRERELEASE can't even get > through install on this H/W where 9.1 could......... >=20 Do you have a SATA drive you can try with this hardware? It would be useful to know if that works, or same errors, etc. Glen --uxuisgdDHaNETlh8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJR5zt2AAoJEFJPDDeguUajr2cIAJDda4QGRX7tyDo5ekpwE5E+ AvIvCXx5KKIUPCr7qC/GvaUU40r8fVA3qpLgmVBdrNJvjG/dOGU7Vy2ibd0ifkgI amqyH9zhZJ13m+vULIpNEkLZmwpQE7V6g1kqWkzStMn2QJzDv3Y2fOefAKsUUiB8 5uLmkJy1nEhe5JNJQ9dG1jb0VwsR7txiSE6B+MFxCO3vh3tMb2fpwIRhD7yw6TQ8 t0UXdZq2k8BQm/hRHFcX1Ib8UtwKaUVQNKKPsuur45Fjeejf0FW5PlKHw7K7Act3 mj+P9vn/pdSyHFhtAH3N0H6H6A6djVLv7AiFQHLLzr52EYbdfci6zSL8CASac8s= =2dp+ -----END PGP SIGNATURE----- --uxuisgdDHaNETlh8-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 01:14:59 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3ED62B26 for ; Thu, 18 Jul 2013 01:14:59 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 037BE941 for ; Thu, 18 Jul 2013 01:14:58 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6I1EvLp005803; Wed, 17 Jul 2013 19:14:57 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6I1EvSc005800; Wed, 17 Jul 2013 19:14:57 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 17 Jul 2013 19:14:57 -0600 (MDT) From: Warren Block To: John Reynolds Subject: Re: experience with 9.2-PRERELEASE In-Reply-To: <51E73AA9.5030004@reynoldsnet.org> Message-ID: References: <51E73AA9.5030004@reynoldsnet.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Wed, 17 Jul 2013 19:14:57 -0600 (MDT) Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 01:14:59 -0000 On Wed, 17 Jul 2013, John Reynolds wrote: > The final blow to my sanity was when I rolled back and tried to install > 8.4-RELEASE and sysinstall couldn't make the disk devices after I hit 'W' in > the disk label editor to commit my changes. Somewhere, there is a FAQ or note that you should not press "W" in the installer. But a quick check did not find where that was. > So, I'm wondering generically are people having problems with SSD's in > FreeBSD? In this hardware I have not tried using a traditional SATA > disk yet. I use SSDs without problems on 9.2-STABLE amd64, but all on motherboard controllers. The problems you're seeing sound like a controller problem. For reference: http://www.wonkity.com/~wblock/docs/html/ssd.html From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 02:30:43 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C821EF8C for ; Thu, 18 Jul 2013 02:30:43 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by mx1.freebsd.org (Postfix) with ESMTP id A7EF5C88 for ; Thu, 18 Jul 2013 02:30:43 +0000 (UTC) Received: by mail-pb0-f48.google.com with SMTP id ma3so2574439pbc.21 for ; Wed, 17 Jul 2013 19:30:43 -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=pE/B7V+raJj7/BmLseFa4Z5EnhRP8tMFfCovMxDUyeI=; b=erBoOqt3UbMy9I94mvzeVlAt9rmIdwkjDVjWmIv1j0z7TtNtyeK75Pe0CrtP+RjBJY 6/hSN3wjgu6St4wq6FtjlArn6jGuizvGpfMeNcKWCDupg5CAfMmWU9f+ranv+A7aCA6H wAMjQ6xrJRW+NomfonMYth1YqPgBz40Fmyeh33xue3NufTjc+VwcSDunZxFRUeAnEc/y aBX+B1mu9VXLQoXwwNIrs87R0c8ingpy1+qFzHjbuZO9Q2hXUIsk+yDlYl7MWxbPSiy8 nx3OKXRqD0EeVln9XC1+gc7JUns5RFTJKIPpGXQoGkbarCJiQ3SIMMzes3htU9MOQBQK Laaw== MIME-Version: 1.0 X-Received: by 10.66.252.234 with SMTP id zv10mr10771517pac.186.1374114643416; Wed, 17 Jul 2013 19:30:43 -0700 (PDT) Received: by 10.70.88.74 with HTTP; Wed, 17 Jul 2013 19:30:43 -0700 (PDT) In-Reply-To: <51E73AA9.5030004@reynoldsnet.org> References: <51E73AA9.5030004@reynoldsnet.org> Date: Wed, 17 Jul 2013 21:30:43 -0500 Message-ID: Subject: Re: experience with 9.2-PRERELEASE From: Adam Vande More To: John Reynolds Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 02:30:43 -0000 On Wed, Jul 17, 2013 at 7:45 PM, John Reynolds wrote: > to the SSD that I used as the primary hard drive. So, then I figured I > would try a more recent snapshot hoping that something had been spotted and > fixed already. I got the 9.2-PRERELEASE amd64 snapshot and tried to install > it. However, I couldn't even get past the first screen of the install > because of these messages: > > ugen0.2: (Unknown) at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > > and the keyboard was non-functional. It just sat there spewing these > errors about 1 per second. > Try toggling usb compatibility mode in the bios. -- Adam Vande More From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 03:33:44 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6E5F5EB2 for ; Thu, 18 Jul 2013 03:33:44 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 63F7A150 for ; Thu, 18 Jul 2013 03:33:43 +0000 (UTC) Received: from alph.d.allbsd.org (p2049-ipbf1102funabasi.chiba.ocn.ne.jp [122.26.101.49]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r6I3XQND055159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Jul 2013 12:33:36 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.5/8.14.5) with ESMTP id r6I3XPOK011680; Thu, 18 Jul 2013 12:33:26 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Thu, 18 Jul 2013 12:33:23 +0900 (JST) Message-Id: <20130718.123323.1730389945845032580.hrs@allbsd.org> To: trashcan@odo.in-berlin.de Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) From: Hiroki Sato In-Reply-To: References: <4c07217dc9200841dfd065a6d52849eb@mx1.enfer-du-nord.net> <20130712.160358.1330135778606339435.hrs@allbsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Thu_Jul_18_12_33_23_2013_929)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Thu, 18 Jul 2013 12:33:37 +0900 (JST) X-Spam-Status: No, score=-89.3 required=13.0 tests=CONTENT_TYPE_PRESENT, DIRECTOCNDYN,DYN_PBL,RCVD_IN_PBL,RCVD_IN_RP_RNBL,SPF_SOFTFAIL, USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 03:33:44 -0000 ----Security_Multipart(Thu_Jul_18_12_33_23_2013_929)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Michael Grimm wrote in : tr> On 12.07.2013, at 09:03, Hiroki Sato wrote: tr> tr> > Please let me know if the existing configurations and/or the new tr> > formats do not work. tr> tr> First of all: great work! It is that much easier to deal with aliases, now. tr> tr> There is only one minor issue, if at all: tr> tr> rc.conf: tr> | ifconfig_em0_ipv6="inet6 dead:beef:1111:2222::1 prefixlen 56" tr> | ifconfig_em0_aliases="\ tr> | inet6 dead:beef:1111:2222::2-3 prefixlen 56 \ tr> | inet6 dead:beef:1111:2222::4 prefixlen 56 \ tr> | inet6 dead:beef:1111:2222::5-6/56" tr> tr> ifconfig: tr> | inet6 dead:beef:1111:2222::1 prefixlen 56 tr> | inet6 dead:beef:1111:2222::2 prefixlen 64 tr> | inet6 dead:beef:1111:2222::3 prefixlen 64 tr> | inet6 dead:beef:1111:2222::4 prefixlen 56 tr> | inet6 dead:beef:1111:2222::5 prefixlen 56 tr> | inet6 dead:beef:1111:2222::6 prefixlen 56 tr> tr> Any combination of a range definition (2-3) *and* "prefixlen 56" is ignored tr> whereas a range definition (5-6) *and* "/56" is interpreted as wanted. tr> tr> Well, that combination of a range and "prefix" isn't documented, thus I am tr> not sure if that's an issue or a feature? It seems a bug. Thank you for your report. I am investigating it now. -- Hiroki ----Security_Multipart(Thu_Jul_18_12_33_23_2013_929)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlHnYgMACgkQTyzT2CeTzy3hMwCgvZMdS7y/kaM/T1mRJsj7zH30 I48An2wnr9zuKlZju5U5p1BuZz662a5I =SEP7 -----END PGP SIGNATURE----- ----Security_Multipart(Thu_Jul_18_12_33_23_2013_929)---- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 03:45:35 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BE92D297 for ; Thu, 18 Jul 2013 03:45:35 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo203.cox.net (fed1rmfepo203.cox.net [68.230.241.148]) by mx1.freebsd.org (Postfix) with ESMTP id 96FCD1E6 for ; Thu, 18 Jul 2013 03:45:35 +0000 (UTC) Received: from fed1rmimpo305 ([68.230.241.173]) by fed1rmfepo203.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130718034534.BZFM3846.fed1rmfepo203.cox.net@fed1rmimpo305> for ; Wed, 17 Jul 2013 23:45:34 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo305 with cox id 1flZ1m00k2oShb201flabj; Wed, 17 Jul 2013 23:45:34 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020206.51E764DE.0030,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=R/Dd76tX c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=ktNfuVtv0skA:10 a=8nJEP1OIZ-IA:10 a=05pWP5ZVAAAA:8 a=fW0g_zRN6pgA:10 a=ZFYZBgU_vsG1MUvYJ8YA:9 a=wPNLvfGTeEIA:10 a=lmzjfRu-FekA:10 a=BX9vNuiFPD8A:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r6HKYvYp076182; Wed, 17 Jul 2013 20:34:58 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51E765D3.8090801@reynoldsnet.org> Date: Wed, 17 Jul 2013 20:49:39 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Glen Barber Subject: Re: experience with 9.2-PRERELEASE References: <51E73AA9.5030004@reynoldsnet.org> <20130718004854.GC2264@glenbarber.us> In-Reply-To: <20130718004854.GC2264@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 03:45:35 -0000 On 7/17/2013 5:48 PM, Glen Barber wrote: > Hi John, > > > Do you have a SATA drive you can try with this hardware? It would be > useful to know if that works, or same errors, etc. > > Glen > I do, and that was my plan for tomorrow. A bit under the weather today. I will most definitely report back any findings. Thanks for your reply! -Jr From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 05:17:54 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1A8B5E26 for ; Thu, 18 Jul 2013 05:17:54 +0000 (UTC) (envelope-from chko@mx011.cosites1.pw) Received: from mx011.cosites1.pw (mx011.cosites1.pw [23.81.49.11]) by mx1.freebsd.org (Postfix) with ESMTP id E539969F for ; Thu, 18 Jul 2013 05:17:49 +0000 (UTC) Received: from qvybeil ([127.0.0.1]) by mx002.cosites1.pw (IceWarp 10.4.5) with SMTP id 201307172317280255 for ; Wed, 17 Jul 2013 23:17:28 -0600 From: "FILP" To: freebsd-stable@freebsd.org Subject: Re:freebsd-stable@freebsd.org Date: Wed, 17 Jul 2013 23:17:28 -0600 X-Mailer: Hpsvzceh 01 MIME-Version: 1.0 X-Priority: 3 Message-ID: Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: 2383882121@qq.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 05:17:54 -0000 From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 05:18:00 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A248EE27 for ; Thu, 18 Jul 2013 05:18:00 +0000 (UTC) (envelope-from rmtodd@servalan.servalan.com) Received: from ln.servalan.com (unknown [IPv6:2600:3c00::f03c:91ff:fe96:62f5]) by mx1.freebsd.org (Postfix) with ESMTP id 7DC126A0 for ; Thu, 18 Jul 2013 05:18:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=servalan.com; s=rsadkim; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:From:References:Subject:To; bh=Lx7oVFmn5o7gbfUyrvgcZa8JJNkyJm3YtKTwO8o1yKk=; b=oV0m9uc7sbqlOnXRkIcq2XtbxBWFIL+F05/Quvr9vixr3D+ZlMzHxjgthnrrWWg7nAwkiLYlQbGFpLAkSgUaBNh1N1h59LeKqNnOI7RWrwfmIDpZ+qbOB3+nTZCQ4NRDJac6AOCuSdK6xuIuqcKXT3JsBajnLkWvelr7905YTvA=; Received: from uucp by ln.servalan.com with local-rmail (Exim 4.71) (envelope-from ) id 1UzgbH-0007pF-SW for freebsd-stable@freebsd.org; Thu, 18 Jul 2013 00:17:59 -0500 Received: from rmtodd by servalan.servalan.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UzgXG-000HZw-5c; Thu, 18 Jul 2013 00:13:50 -0500 To: hartzell@alerce.com, freebsd-stable@freebsd.org Subject: Re: Help with filing a [maybe] ZFS/mmap bug. References: <20967.760.95825.310085@gargle.gargle.HOWL> From: Richard Todd Date: Thu, 18 Jul 2013 00:13:49 -0500 In-Reply-To: <20967.760.95825.310085@gargle.gargle.HOWL> (George Hartzell's message of "Wed, 17 Jul 2013 13:47:52 -0700") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.5-b28 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 05:18:00 -0000 George Hartzell writes: > Hi All, > > I have what I think is a ZFS related bug. Unfortunately my simplest > test case is a bit cumbersome and I haven't definitively proven that > the problem is ZFS related. > I'm hoping for some feedback on how to move forward. > > Quick background: I rip my CD's using grip and produce flac files. I > tag the music using Musicbrainz' Picard and transcode it to mp3's > within Picard using a plugin that I wrote. Picard is a python based > app and uses the Mutagen library to tag files. [summary: Picard seems to trigger an mmap consistency bug in ZFS]. Aw, crud. I ran into what may be this same issue a few years ago, under almost identical circumstances (picard with Ogg files instead of flac), but never got around to writing up a proper mailinglist post on it. I *thought* it had been fixed some time back, though I'm not entirely sure because I've been running with my local patch to py-mutagen to disable its mmap() usage. Anyway, here's what I recall from when I was trying to track this down way back when: 1) Your suspicions are right, it's definitely a ZFS/mmap interaction bug. UFS filesystems didn't show the bug. 2) It's triggered by the insert_bytes or delete_bytes function in py-mutagen. 3) As long as the in-memory version of that chunk of the file stuck around in memory, the file read OK, but the data on disk was corrupt, so if that data got evicted from cache and had to be reread, or if you forced the cache data to be disposed of by unmounting and remounting the FS, you would see a corrupt file. (Rebooting, of course, would also allow the corrupted file data to become visible again.) I'll attach my patch to disable py-mutagen's mmap usage in insert/delete_bytes below. Try it and see if it makes the corruption problems go away. If so, that narrows your search down to those two routines in py-mutagen and what they're doing. I *had* what at the time I recall was a simple C++ test program that managed to trigger the bug more-or-less reliably. Unfortunately, it doesn't look like my test case still works, i.e., the test program doesn't seem to trigger the bug either on the 10-CURRENT box or RELENG-9 VM I'm trying them on now. As I recall, the bug's presence was dependent on fairly picky details on what exact offsets were used on the mmap()s and the write()s, so it may be that different offsets from what I tried will still show the bug. Anyway, what I'd suggest is the following: see if my patch for py-mutagen disabling the mmap() in those two functions lets you run picard reliably. If so, then the issue is triggered by one or both of those two routines; hack them to print out the exact offsets used on each call and use that to try and code up a simple C++ test case. Here's the py-mutagen patch: --- mutagen/_util.py.orig 2008-06-01 01:33:00.000000000 -0500 +++ mutagen/_util.py 2009-04-11 18:16:53.363758128 -0500 @@ -213,12 +213,6 @@ fobj.write('\x00' * size) fobj.flush() try: - try: - import mmap - map = mmap.mmap(fobj.fileno(), filesize + size) - try: map.move(offset + size, offset, movesize) - finally: map.close() - except (ValueError, EnvironmentError, ImportError): # handle broken mmap scenarios locked = lock(fobj) fobj.truncate(filesize) @@ -272,17 +266,11 @@ try: if movesize > 0: fobj.flush() - try: - import mmap - map = mmap.mmap(fobj.fileno(), filesize) - try: map.move(offset, offset + size, movesize) - finally: map.close() - except (ValueError, EnvironmentError, ImportError): - # handle broken mmap scenarios - locked = lock(fobj) - fobj.seek(offset + size) - buf = fobj.read(BUFFER_SIZE) - while buf: + # handle broken mmap scenarios + locked = lock(fobj) + fobj.seek(offset + size) + buf = fobj.read(BUFFER_SIZE) + while buf: fobj.seek(offset) fobj.write(buf) offset += len(buf) and here's my test case: # This is a shell archive. Save it in a file, remove anything before # this line, and then unpack it by entering "sh file". Note, it may # create directories; files and directories will be owned by you and # have default permissions. # # This archive contains: # # gen4.cpp # test4.sh # echo x - gen4.cpp sed 's/^X//' >gen4.cpp << 'END-of-gen4.cpp' X/* X** Program to create a file of data and do some mmap()ing writes to it. X*/ X X#include X#include X#include X#include X#include X#include X#include X#include X X/* Insert size bytes (zeros) into file at offset */ Xvoid Xinsert_bytes(int fd, unsigned int size, unsigned int offset) X{ X unsigned int filesize = lseek(fd, (off_t)0, SEEK_END); X unsigned int movesize = filesize - offset; X X char *buf = new char[size]; X for (unsigned int i = 0 ; i < size ; ++i) { X buf[i] = '\0'; X } X write(fd, buf, size); X X char *addr = (char *) mmap((void *)NULL, filesize+size, PROT_READ|PROT_WRITE, MAP_SHARED, fd, offset); X memmove(addr+size, addr, movesize); X if (munmap(addr, filesize+size)) { X perror("munmap"); X } X} X X/* Delete size bytes (zeros) from file at offset */ Xvoid Xdelete_bytes(int fd, unsigned int size, unsigned int offset) X{ X unsigned int filesize = lseek(fd, (off_t)0, SEEK_END); X unsigned int movesize = filesize - offset - size; X X char *addr = (char *) mmap((void *)NULL, filesize, PROT_READ|PROT_WRITE, MAP_SHARED, fd, offset); X memmove(addr, addr+size, movesize); X if (munmap(addr, filesize)) { X perror("munmap"); X } X ftruncate(fd, filesize - size); X} X X X X/* Usage: gen1 filename number-of-seconds */ Xint Xmain(int argc, char **argv) X{ X char *fname = argv[1]; X FILE *f = fopen(fname, "w"); X X unsigned int size = 1024; X X for (unsigned int i = 0 ; i < size ; ++i) { X char c = i & 0xff; X fwrite((void *)&c, 1, 1, f); X } X X fclose(f); X X int fd = open(fname, O_RDWR); X X unsigned int S1 = atoi(argv[2]); X#define O1 0 X insert_bytes(fd, S1, O1); X X (void) lseek(fd, (off_t) O1, SEEK_SET); X X#define S2 1 X#define O2 (O1+S1) X X delete_bytes(fd, S2, O2); X X exit(0); X} END-of-gen4.cpp echo x - test4.sh sed 's/^X//' >test4.sh << 'END-of-test4.sh' X#!/bin/sh X# Set the following variables appropriately X# ZFSFS name of your ZFS filesystem to test X# ZFSMP mount point of your ZFS filesystem to test X# ZFSDIR a writable dir somewhere under ZFSMP X# UFSDIR a writable dir somewhere on a UFS filesystem X# Script takes one argument, S1, a number of bytes. X XZFSFS=u1 XZFSMP=/u1 XZFSDIR=/u1/tmp XUFSDIR=/var/tmp X XNAME=$ZFSDIR/foo1 XS1=$1 Xrm $NAME X./gen4 $NAME $S1 Xmd5 $NAME Xcp $NAME $UFSDIR/before Xls -l $NAME Xsudo umount $ZFSMP Xsudo mount -t zfs $ZFSFS $ZFSMP Xmd5 $NAME Xls -l $NAME Xcp $NAME $UFSDIR/after Xcmp -l $UFSDIR/before $UFSDIR/after END-of-test4.sh exit From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 07:29:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DF647735; Thu, 18 Jul 2013 07:29:23 +0000 (UTC) (envelope-from joe@karthauser.co.uk) Received: from babel.karthauser.co.uk (212-13-197-151.karthauser.co.uk [212.13.197.151]) by mx1.freebsd.org (Postfix) with ESMTP id 3C0EBBC7; Thu, 18 Jul 2013 07:29:22 +0000 (UTC) Received: from [192.168.10.240] (unknown [81.144.225.214]) (Authenticated sender: joemail@tao.org.uk) by babel.karthauser.co.uk (Postfix) with ESMTPSA id B4FFC290E; Thu, 18 Jul 2013 07:29:13 +0000 (UTC) Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? From: Dr Josef Karthauser Date: Thu, 18 Jul 2013 08:29:14 +0100 Message-Id: <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> References: <20130716225013.1C63B23A@babel.karthauser.co.uk> To: "freebsd-fs@freebsd.org" X-Mailer: Apple Mail (2.1508) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 07:29:23 -0000 Hi there, I'm scratching my head. I've just migrated to a super micro chassis and = at the same time gone from FreeBSD 9.0 to 9.1-RELEASE. The machine in question is running a ZFS mirror configuration on two ada = devices (with a 8gb gmirror carved out for swap). Since doing so I've been having strange drop outs on the drives; the = just disappear from the bus like so: (ada2:ahcich2:0:0:0): removing device entry (aprobe0:ahcich2:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error (aprobe0:ahcich2:0:0:0): ATA status: d1 (BSY DRDY SERV ERR), error: 04 = (ABRT ) (aprobe0:ahcich2:0:0:0): RES: d1 04 ff ff ff ff ff ff ff ff ff (aprobe0:ahcich2:0:0:0): Error 5, Retries exhausted (aprobe0:ahcich2:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error (aprobe0:ahcich2:0:0:0): ATA status: d1 (BSY DRDY SERV ERR), error: 04 = (ABRT ) (aprobe0:ahcich2:0:0:0): RES: d1 04 ff ff ff ff ff ff ff ff ff (aprobe0:ahcich2:0:0:0): Error 5, Retries exhausted At first I though it was a failing drive - one of the drives did this, = and I limped on a single drive for a week until I could get someone up = to the rack to plug a third drive in. We resilvered the zpool onto the = new device and ran with the failed drive still plugged in (but not = responding to a reset on the ada bus with camcontrol) for a week or so. Then, the new drive dropped out in exactly the same way, followed in = short order by the remaining original drive!!! After rebooting the machine, and observing all three drives probing and = available, I resilvered the gmirror and zpool again on the two devices = expected that I thought were reliable, but before the resilvering was = completed the new drive dropped out again. I'm scratching my head now. I can't imagine that it's a wiring problem, = as they are all on individual SATA buses and individually cabled. Smart isn't reporting an drive issues either=85. :/ So, I'm wondering, is it a driver issuer with 9.1-RELEASE, if I upgrade = to 9-RELENG would I expect that to resolve the problem? (Have there = been any reported ada bus issuer reported since last December?) The hardware in question is: ahci0: port = 0xf050-0xf057,0xf040-0xf043,0xf030-0xf037,0xf020-0xf023,0xf000-0xf01f = mem 0xdfb02000-0xdfb027ff irq 19 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad6 ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 ada2: ATA-8 SATA 2.x device ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad8 Any ideas would be greatly welcomed. Thanks, Joe From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 07:33:14 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 822B993A; Thu, 18 Jul 2013 07:33:14 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 02AF4C0C; Thu, 18 Jul 2013 07:33:13 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50005041117.msg; Thu, 18 Jul 2013 08:33:10 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 18 Jul 2013 08:33:10 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1911771df7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <33EF2240EDC1446D8E45F8C51974136B@multiplay.co.uk> From: "Steven Hartland" To: "Dr Josef Karthauser" , References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? Date: Thu, 18 Jul 2013 08:33:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=original Content-Transfer-Encoding: 8bit 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 Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 07:33:14 -0000 What chassis is this? ----- Original Message ----- From: "Dr Josef Karthauser" To: Cc: Sent: Thursday, July 18, 2013 8:29 AM Subject: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? Hi there, I'm scratching my head. I've just migrated to a super micro chassis and at the same time gone from FreeBSD 9.0 to 9.1-RELEASE. The machine in question is running a ZFS mirror configuration on two ada devices (with a 8gb gmirror carved out for swap). Since doing so I've been having strange drop outs on the drives; the just disappear from the bus like so: (ada2:ahcich2:0:0:0): removing device entry (aprobe0:ahcich2:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error (aprobe0:ahcich2:0:0:0): ATA status: d1 (BSY DRDY SERV ERR), error: 04 (ABRT ) (aprobe0:ahcich2:0:0:0): RES: d1 04 ff ff ff ff ff ff ff ff ff (aprobe0:ahcich2:0:0:0): Error 5, Retries exhausted (aprobe0:ahcich2:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error (aprobe0:ahcich2:0:0:0): ATA status: d1 (BSY DRDY SERV ERR), error: 04 (ABRT ) (aprobe0:ahcich2:0:0:0): RES: d1 04 ff ff ff ff ff ff ff ff ff (aprobe0:ahcich2:0:0:0): Error 5, Retries exhausted At first I though it was a failing drive - one of the drives did this, and I limped on a single drive for a week until I could get someone up to the rack to plug a third drive in. We resilvered the zpool onto the new device and ran with the failed drive still plugged in (but not responding to a reset on the ada bus with camcontrol) for a week or so. Then, the new drive dropped out in exactly the same way, followed in short order by the remaining original drive!!! After rebooting the machine, and observing all three drives probing and available, I resilvered the gmirror and zpool again on the two devices expected that I thought were reliable, but before the resilvering was completed the new drive dropped out again. I'm scratching my head now. I can't imagine that it's a wiring problem, as they are all on individual SATA buses and individually cabled. Smart isn't reporting an drive issues either…. :/ So, I'm wondering, is it a driver issuer with 9.1-RELEASE, if I upgrade to 9-RELENG would I expect that to resolve the problem? (Have there been any reported ada bus issuer reported since last December?) The hardware in question is: ahci0: port 0xf050-0xf057,0xf040-0xf043,0xf030-0xf037,0xf020-0xf023,0xf000-0xf01f mem 0xdfb02000-0xdfb027ff irq 19 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad6 ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 ada2: ATA-8 SATA 2.x device ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad8 Any ideas would be greatly welcomed. Thanks, Joe _______________________________________________ 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" ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 07:36:24 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 45D3AC17 for ; Thu, 18 Jul 2013 07:36:24 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id CB7E4C43 for ; Thu, 18 Jul 2013 07:36:23 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50005041136.msg for ; Thu, 18 Jul 2013 08:36:22 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 18 Jul 2013 08:36:22 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1911771df7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: stable@freebsd.org Message-ID: <268355E08D804BFDAC8C9883FA13AD93@multiplay.co.uk> From: "Steven Hartland" To: "John Reynolds" , References: <51E73AA9.5030004@reynoldsnet.org> Subject: Re: experience with 9.2-PRERELEASE Date: Thu, 18 Jul 2013 08:36:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response 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.14 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, 18 Jul 2013 07:36:24 -0000 Is the SSD running at 6Gbps? If so have you tried limiting the speed to 3Gbps? Regards Steve ----- Original Message ----- From: "John Reynolds" To: Sent: Thursday, July 18, 2013 1:45 AM Subject: experience with 9.2-PRERELEASE > Hello all, I have some feedback for the recently prepared snapshot of > 9.2-RELEASE. > > I've been trying like crazy to get the 9x series code installed on a > brand new workstation I'm building. It consists of a brand new ASRock > motherboard and haswell i7-4770k processor, Z87 chipset. I tried at > first to install 9.1-RELEASE. it worked (after I learned a bit about the > new installer--I have used FreeBSD "forever" but have been "out of it" > in terms of this list and other going's on for about a year due to > workload), but upon booting I was getting "timeout" errors > > ahcich0: Timeout on slot xx port 0 > ahcich0: is 000000000 cs 00000000 ss e0000000 rs e0000000 tfd 40 serr > 00000000 cmd 0004df17 > > to the SSD that I used as the primary hard drive. So, then I figured I > would try a more recent snapshot hoping that something had been spotted > and fixed already. I got the 9.2-PRERELEASE amd64 snapshot and tried to > install it. However, I couldn't even get past the first screen of the > install because of these messages: > > ugen0.2: (Unknown) at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > > and the keyboard was non-functional. It just sat there spewing these > errors about 1 per second. > > So, even though I'm having some sort of ahci "timeout" issue with this > hardware and 9.1-RELEASE, it certainly appears that something has > zig-zagged in the usb stack in this 9.2-PRELEASE snapshot because I > can't even get through the install program. :(. Same hardware, same > everything. > > I also tried the 9.2-PRELEASE i386 snapshot for giggles. Same result. > > The final blow to my sanity was when I rolled back and tried to install > 8.4-RELEASE and sysinstall couldn't make the disk devices after I hit > 'W' in the disk label editor to commit my changes. So, I'm wondering > generically are people having problems with SSD's in FreeBSD? In this > hardware I have not tried using a traditional SATA disk yet. > > But just thought I would report that 9.2-PRERELEASE can't even get > through install on this H/W where 9.1 could......... > > -Jr > > _______________________________________________ > 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" > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 07:53:36 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 95649F68 for ; Thu, 18 Jul 2013 07:53:36 +0000 (UTC) (envelope-from maurizio.vairani@cloverinformatica.it) Received: from smtpdg10.aruba.it (smtpdg4.aruba.it [62.149.158.234]) by mx1.freebsd.org (Postfix) with ESMTP id 3CE0ECFF for ; Thu, 18 Jul 2013 07:53:33 +0000 (UTC) Received: from cloverinformatica.it ([188.10.129.202]) by smtpcmd04.ad.aruba.it with bizsmtp id 1jsB1m0114N8xN401jsCrs; Thu, 18 Jul 2013 09:52:15 +0200 Received: from [192.168.0.100] (MAURIZIO-PC [192.168.0.100]) by cloverinformatica.it (Postfix) with ESMTP id 3FDB9FCB3; Thu, 18 Jul 2013 09:52:12 +0200 (CEST) Message-ID: <51E79EAD.5040602@cloverinformatica.it> Date: Thu, 18 Jul 2013 09:52:13 +0200 From: Maurizio Vairani User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: "Julian H. Stacey" Subject: Re: [SOLVED] Re: Shutdown problem with an USB memory stick as ZFS cache device References: <201307171529.r6HFT4EK063849@fire.js.berklix.net> In-Reply-To: <201307171529.r6HFT4EK063849@fire.js.berklix.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Ronald Klop X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 07:53:36 -0000 On 17/07/2013 17:29, Julian H. Stacey wrote: > Maurizio Vairani wrote: >> On 17/07/2013 11:50, Ronald Klop wrote: >>> On Wed, 17 Jul 2013 10:27:09 +0200, Maurizio Vairani >>> wrote: >>> >>>> Hi all, >>>> >>>> >>>> on a Compaq Presario laptop I have just installed the latest stable >>>> >>>> >>>> #uname -a >>>> >>>> FreeBSD presario 9.2-PRERELEASE FreeBSD 9.2-PRERELEASE #0: Tue Jul 16 >>>> 16:32:39 CEST 2013 root@presario:/usr/obj/usr/src/sys/GENERIC amd64 >>>> >>>> >>>> For speed up the compilation I have added to the pool, tank0, a >>>> SanDisk memory stick as cache device with the command: >>>> >>>> >>>> # zpool add tank0 cache /dev/da0 >>>> >>>> >>>> But when I shutdown the laptop the process will halt with this screen >>>> shot: >>>> >>>> >>>> http://www.dump-it.fr/freebsd-screen-shot/2f9169f18c7c77e52e873580f9c2d4bf.jpg.html >>>> >>>> >>>> >>>> and I need to press the power button for more than 4 seconds to >>>> switch off the laptop. >>>> >>>> The problem is always reproducible. >>> Does sysctl hw.usb.no_shutdown_wait=1 help? >>> >>> Ronald. >> Thank you Ronald it works ! >> >> In /boot/loader.conf added the line >> hw.usb.no_shutdown_wait=1 >> >> Maurizio > I wonder (from ignorance as I dont use ZFS yet), > if that merely masks the symptom or cures the fault ? > > Presumably one should use a ZFS command to disassociate whatever > might have the cache open ? (in case something might need to be > written out from cache, if it was a writeable cache ?) > > I too had a USB shutdown problem (non ZFS, now solved)& several people > made useful comments on shutdown scripts etc, so I'm cross referencing: > > http://lists.freebsd.org/pipermail/freebsd-mobile/2013-July/012803.html > > Cheers, > Julian Probably it masks the symptom. Andriy Gapon hypothesizes a bug in the ZFS clean up code: http://lists.freebsd.org/pipermail/freebsd-fs/2013-July/017857.html Surely one can use a startup script with the command: zpool add tank0 cache /dev/da0 and a shutdown script with: zpool remove tank0 /dev/da0 but this mask the symptom too. I prefer the Ronald solution because: - is simpler: it adds only one line (hw.usb.no_shutdown_wait=1) to one file (/boot/loader.conf). - is fastest: the zpool add/remove commands take time and “hw.usb.no_shutdown_wait=1” in /boot/loader.conf speeds up the shutdown process. - is cleaner: the zpool add/remove commands pair will fill up the tank0 pool history. Regards Maurizio From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 08:25:27 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 147B58BF; Thu, 18 Jul 2013 08:25:27 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) by mx1.freebsd.org (Postfix) with ESMTP id C0550E7B; Thu, 18 Jul 2013 08:25:26 +0000 (UTC) Received: from [194.32.164.26] (80-46-130-69.static.dsl.as9105.com [80.46.130.69]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id r6I8POHj066332; Thu, 18 Jul 2013 09:25:25 +0100 (BST) (envelope-from rb@gid.co.uk) Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Bob Bishop In-Reply-To: <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> Date: Thu, 18 Jul 2013 09:25:19 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <281DBD06-81D5-4DDD-9464-B96C80C22C3F@gid.co.uk> References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> To: Dr Josef Karthauser X-Mailer: Apple Mail (2.1283) Cc: "freebsd-fs@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 08:25:27 -0000 Hi, On 18 Jul 2013, at 08:29, Dr Josef Karthauser wrote: > Hi there, >=20 > I'm scratching my head. I've just migrated to a super micro chassis = and at the same time gone from FreeBSD 9.0 to 9.1-RELEASE. >=20 > The machine in question is running a ZFS mirror configuration on two = ada devices (with a 8gb gmirror carved out for swap). >=20 > Since doing so I've been having strange drop outs on the drives; the = just disappear from the bus like so: >=20 > (ada2:ahcich2:0:0:0): removing device entry > (aprobe0:ahcich2:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 > (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error > (aprobe0:ahcich2:0:0:0): ATA status: d1 (BSY DRDY SERV ERR), error: 04 = (ABRT ) > (aprobe0:ahcich2:0:0:0): RES: d1 04 ff ff ff ff ff ff ff ff ff > (aprobe0:ahcich2:0:0:0): Error 5, Retries exhausted > (aprobe0:ahcich2:0:0:0): NOP. ACB: 00 00 00 00 00 00 00 00 00 00 00 00 > (aprobe0:ahcich2:0:0:0): CAM status: ATA Status Error > (aprobe0:ahcich2:0:0:0): ATA status: d1 (BSY DRDY SERV ERR), error: 04 = (ABRT ) > (aprobe0:ahcich2:0:0:0): RES: d1 04 ff ff ff ff ff ff ff ff ff > (aprobe0:ahcich2:0:0:0): Error 5, Retries exhausted >=20 >=20 > At first I though it was a failing drive - one of the drives did this, = and I limped on a single drive for a week until I could get someone up = to the rack to plug a third drive in. We resilvered the zpool onto the = new device and ran with the failed drive still plugged in (but not = responding to a reset on the ada bus with camcontrol) for a week or so. >=20 > Then, the new drive dropped out in exactly the same way, followed in = short order by the remaining original drive!!! >=20 > After rebooting the machine, and observing all three drives probing = and available, I resilvered the gmirror and zpool again on the two = devices expected that I thought were reliable, but before the = resilvering was completed the new drive dropped out again. >=20 > I'm scratching my head now. I can't imagine that it's a wiring = problem, as they are all on individual SATA buses and individually = cabled. >=20 > Smart isn't reporting an drive issues either=85. :/ >=20 > So, I'm wondering, is it a driver issuer with 9.1-RELEASE, if I = upgrade to 9-RELENG would I expect that to resolve the problem? (Have = there been any reported ada bus issuer reported since last December?) >=20 > The hardware in question is: >=20 > ahci0: port = 0xf050-0xf057,0xf040-0xf043,0xf030-0xf037,0xf020-0xf023,0xf000-0xf01f = mem 0xdfb02000-0xdfb027ff irq 19 at device 31.2 on pci0 > ahci0: AHCI v1.30 with 6 3Gbps ports, Port Multiplier not supported > ahcich0: at channel 0 on ahci0 > ahcich1: at channel 1 on ahci0 > ahcich2: at channel 2 on ahci0 > ahcich3: at channel 3 on ahci0 > ahcich4: at channel 4 on ahci0 > ahcich5: at channel 5 on ahci0 > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: ATA-8 SATA 2.x device > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) > ada0: Previously was known as ad4 > ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 > ada1: ATA-8 SATA 2.x device > ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada1: Command Queueing enabled > ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) > ada1: Previously was known as ad6 > ada2 at ahcich2 bus 0 scbus2 target 0 lun 0 > ada2: ATA-8 SATA 2.x device > ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada2: Command Queueing enabled > ada2: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) > ada2: Previously was known as ad8 >=20 >=20 > Any ideas would be greatly welcomed. >=20 > Thanks, > Joe Me too (over a long period, with various hardware). There is a general problem with energy-saving drives that controllers = don't understand them. Typically the drive decides to go into some = power-saving mode, the controller wants to do some operation, the drive = takes too long to come ready, the controller decides the drive has gone = away. You have to persuade the controller to wait longer for the drive to come = ready, and/or persuade the drive to stay awake. This isn't necessarily = easy, eg the controller's ready wait may not be programmable. (Or avoid such drives like the plague, life's too short). -- Bob Bishop rb@gid.co.uk From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 09:45:32 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 41D68842 for ; Thu, 18 Jul 2013 09:45:32 +0000 (UTC) (envelope-from sowmya@cloudbyte.co) Received: from mail-lb0-f177.google.com (mail-lb0-f177.google.com [209.85.217.177]) by mx1.freebsd.org (Postfix) with ESMTP id C32B21FB for ; Thu, 18 Jul 2013 09:45:31 +0000 (UTC) Received: by mail-lb0-f177.google.com with SMTP id 10so2303350lbf.22 for ; Thu, 18 Jul 2013 02:45:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=s81wwHMJI6m4JdcNUvO0LFmbp4QmLLrUVq0EC5Fu2wI=; b=av9mIb78A1spMQQ122mUN4nb7iNvyiRWG5Dz3n5MIe3Cw+KnrfA4dgLv0QTw1TH00R Q4/3ZfF0rketu80Ic5z0NedkdhX+XVch7/pBHMhsb34DwLTxi30fZ1WsRcAkTTmMaN8G LQNvCwCMQnMc4Svxq4h8YBuNtXdW/QOnxoTRe/IFOLKi494EgiT0LgZ8XG6CKj7+iU00 mjfWqHQAyreZ3OcknGBrPsA/SmCSyOynlNP1O5l+c0zbuiJn78I22D3AFAiHOqkGc1LY MIstk+9LvPmK0RKP/A+PXz6umj/iryFNQ32q1e8S41aCE1gb0OnAAyuGrv9vj1hm4wtF TacA== MIME-Version: 1.0 X-Received: by 10.112.88.169 with SMTP id bh9mr5023061lbb.12.1374140724658; Thu, 18 Jul 2013 02:45:24 -0700 (PDT) Received: by 10.114.13.138 with HTTP; Thu, 18 Jul 2013 02:45:24 -0700 (PDT) Date: Thu, 18 Jul 2013 15:15:24 +0530 Message-ID: Subject: Seeing data corruption with g_multipath utility From: Sowmya L To: killing@multiplay.co.uk, freebsd-stable@freebsd.org X-Gm-Message-State: ALoCoQmnNgUmNACl8kw54lJHfIO6OmWxE8HSObBOeQzDm0+qv2SnFj6QAutZbIwtwvzkCo9oZiO6 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 09:45:32 -0000 Hi Steven, Read/Write errors are recorded when an active path of the geom_multipath device is pulled while running the i/o on dataset created for the pool. Running I/o on dataset using dd. *Freebsd version :* 9.0 *Patch imported from stable 9 : *r229303, r234916 *zpool status:* * * pool: poola state: ONLINE scan: none requested config: NAME STATE READ WRITE CKSUM poola ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 multipath/newdisk4 ONLINE 0 0 0 multipath/newdisk2 ONLINE 0 0 0 errors: No known data errors * * * * *gmultipath status:* * * Name Status Components multipath/newdisk2 OPTIMAL da7 (ACTIVE) da2 (PASSIVE) multipath/newdisk1 OPTIMAL da6 (ACTIVE) da1 (PASSIVE) multipath/newdisk4 OPTIMAL da3 (ACTIVE) da4 (PASSIVE) multipath/newdisk OPTIMAL da0 (ACTIVE) da5 (PASSIVE) multipath/newdisk3 OPTIMAL da8 (ACTIVE) da9 (PASSIVE) * * *zpool status after pulling the active path g_multipath device*: pool: mypool1 state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scan: resilvered 27.2M in 0h0m with 0 errors on Thu Jul 4 19:47:44 2013 config: NAME STATE READ WRITE CKSUM mypool1 ONLINE 0 0 0 mirror-0 ONLINE 0 12 0 multipath/newdisk4 ONLINE 0 27 0 multipath/newdisk2 ONLINE 0 12 0 spares multipath/newdisk AVAIL errors: No known data errors Are there any dependencies for the patch that is picked from stable 9 as mentioned above?? sorry for posting it in many areas of the forum its just to find the rite fit. -- Thanks & Regards, Sowmya L From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 12:07:43 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4B7DE861 for ; Thu, 18 Jul 2013 12:07:43 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp.eutelia.it (mp1-smtp-6.eutelia.it [62.94.10.166]) by mx1.freebsd.org (Postfix) with ESMTP id 04D97A07 for ; Thu, 18 Jul 2013 12:07:42 +0000 (UTC) Received: from ns2.biolchim.it (ip-188-188.sn2.eutelia.it [83.211.188.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.eutelia.it (Eutelia) with ESMTP id 9BB10661DFA for ; Thu, 18 Jul 2013 14:07:41 +0200 (CEST) Received: from soth.ventu (adsl-ull-163-156.41-151.net24.it [151.41.156.163]) (authenticated bits=0) by ns2.biolchim.it (8.14.7/8.14.7) with ESMTP id r6IC7Zru042567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 18 Jul 2013 14:07:38 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: ns2.biolchim.it: Host adsl-ull-163-156.41-151.net24.it [151.41.156.163] claimed to be soth.ventu Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.7/8.14.5) with ESMTP id r6IC7OHg084898; Thu, 18 Jul 2013 14:07:24 +0200 (CEST) (envelope-from ml@netfence.it) Message-ID: <51E7DA7C.8060105@netfence.it> Date: Thu, 18 Jul 2013 14:07:24 +0200 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130626 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org, joe@karthauser.co.uk Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> <281DBD06-81D5-4DDD-9464-B96C80C22C3F@gid.co.uk> In-Reply-To: <281DBD06-81D5-4DDD-9464-B96C80C22C3F@gid.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 X-Scanned-By: MIMEDefang 2.73 on 10.1.2.13 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ns2.biolchim.it [192.168.2.203]); Thu, 18 Jul 2013 14:07:38 +0200 (CEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 12:07:43 -0000 On 07/18/13 10:25, Bob Bishop wrote: > Me too (over a long period, with various hardware). > > There is a general problem with energy-saving drives that controllers don't understand them. Typically the drive decides to go into some power-saving mode, the controller wants to do some operation, the drive takes too long to come ready, the controller decides the drive has gone away. > > You have to persuade the controller to wait longer for the drive to come ready, and/or persuade the drive to stay awake. This isn't necessarily easy, eg the controller's ready wait may not be programmable. > > (Or avoid such drives like the plague, life's too short). Perhaps they are WD Green drives? In that case, other than quoting Bob's suggestion about avoiding them, there's something you can do: a) turn off the drives' power-saving features (this is done through a DOS utility you can download); b) try different controllers and/or different OS releases. You'll find a lot on this problem if you search the web. There's also a report of mine you can search on this ML, regarding FreeBSD specifically. HTH. bye av. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 15:36:24 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BF4DFD0E for ; Thu, 18 Jul 2013 15:36:24 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id F2708680 for ; Thu, 18 Jul 2013 15:36:23 +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 SAA24331; Thu, 18 Jul 2013 18:36:09 +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 1UzqFU-0005H6-D7; Thu, 18 Jul 2013 18:36:08 +0300 Message-ID: <51E80B30.1090004@FreeBSD.org> Date: Thu, 18 Jul 2013 18:35:12 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130708 Thunderbird/17.0.7 MIME-Version: 1.0 To: hartzell@alerce.com Subject: Re: Help with filing a [maybe] ZFS/mmap bug. References: <20967.760.95825.310085@gargle.gargle.HOWL> In-Reply-To: <20967.760.95825.310085@gargle.gargle.HOWL> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 15:36:24 -0000 on 17/07/2013 23:47 George Hartzell said the following: > How should I move forward with this? Could you please try to reproduce this problem using a kernel built with INVARIANTS options? -- Andriy Gapon From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 15:44:30 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B94871D3 for ; Thu, 18 Jul 2013 15:44:30 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo101.cox.net (fed1rmfepo101.cox.net [68.230.241.143]) by mx1.freebsd.org (Postfix) with ESMTP id 92B46751 for ; Thu, 18 Jul 2013 15:44:30 +0000 (UTC) Received: from fed1rmimpo110 ([68.230.241.159]) by fed1rmfepo101.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130718154424.YZSF3892.fed1rmfepo101.cox.net@fed1rmimpo110> for ; Thu, 18 Jul 2013 11:44:24 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo110 with cox id 1rkP1m00g2oShb201rkP5F; Thu, 18 Jul 2013 11:44:24 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020202.51E80D58.0065,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=KYMMR3kD c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=ktNfuVtv0skA:10 a=8nJEP1OIZ-IA:10 a=05pWP5ZVAAAA:8 a=fW0g_zRN6pgA:10 a=_FPKKZXn1eEX6rsb_0oA:9 a=wPNLvfGTeEIA:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r6I8XkYB084924; Thu, 18 Jul 2013 08:33:46 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51E80E4C.1010603@reynoldsnet.org> Date: Thu, 18 Jul 2013 08:48:28 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Steven Hartland Subject: Re: experience with 9.2-PRERELEASE References: <51E73AA9.5030004@reynoldsnet.org> <268355E08D804BFDAC8C9883FA13AD93@multiplay.co.uk> In-Reply-To: <268355E08D804BFDAC8C9883FA13AD93@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 15:44:30 -0000 On 7/18/2013 12:36 AM, Steven Hartland wrote: > Is the SSD running at 6Gbps? If so have you tried limiting the speed > to 3Gbps? I would imagine so. It has a 6Gbps interface and the Z87 board does also--so I can only imagine it's trying to go as fast as possible by default. I will fiddle with the BIOS and see if I can limit it and see if that prevents the "timeout" problems I was having after the 9.1-R install. Somebody else suggested changing the USB settings in the BIOS to try and overcome the problem when using the snap of 9.2-PRERELEASE as well so I will try that too. Ultimately if nothing likes the SSD I will try a regular SATA drive as last resort. The drive is an Intel 520 Series 240Gb model, FWIW. Thanks! -Jr From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 15:49:11 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F13A537C; Thu, 18 Jul 2013 15:49:11 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) by mx1.freebsd.org (Postfix) with ESMTP id CB93978B; Thu, 18 Jul 2013 15:49:11 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:120e:1:1:c57c:729]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 0B1C830DF; Thu, 18 Jul 2013 15:49:09 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 0B1C830DF Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 18 Jul 2013 11:49:08 -0400 From: Glen Barber To: John Reynolds Subject: Re: experience with 9.2-PRERELEASE Message-ID: <20130718154908.GD1945@glenbarber.us> References: <51E73AA9.5030004@reynoldsnet.org> <20130718004854.GC2264@glenbarber.us> <51E765D3.8090801@reynoldsnet.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nHwqXXcoX0o6fKCv" Content-Disposition: inline In-Reply-To: <51E765D3.8090801@reynoldsnet.org> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 15:49:12 -0000 --nHwqXXcoX0o6fKCv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 17, 2013 at 08:49:39PM -0700, John Reynolds wrote: > On 7/17/2013 5:48 PM, Glen Barber wrote: > >Hi John, > > > > > >Do you have a SATA drive you can try with this hardware? It would be > >useful to know if that works, or same errors, etc. > > > >Glen > > > I do, and that was my plan for tomorrow. A bit under the weather > today. I will most definitely report back any findings. Thanks for > your reply! >=20 John, in addition to suggestions/replies from others, can you also try the 10.0-CURRENT snapshot? In particular, if your problem continues with a SATA drive, I am curious if the problem still exists in head/. http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/ Thanks. Glen --nHwqXXcoX0o6fKCv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJR6A50AAoJEFJPDDeguUajh5MH/3lzFM6kfT64rMqFDCoeJR2L 1hp3f6Q9+ls8NEtDVzidH59s6ahvEsirM/ezNpGoJnXNJSeP1veQS/eKnEIFxBe0 oKwPxDXZB1yQthbigWycld/np+MY0LegI8fT6sjTaL+7uvGa/YcRwdaCHa8vzi/E QJ3rV9uvdHd/fM3dqGANhsH/zozHVb44e4Cx9Lc7doFsPgMBc50m52JhVflmjP6j U3amqLAnd8IJ14Bi8bwP/RE/pnNxwyxxST18ZOgQPKdZOSxc6rWUMW+R7X28T5M3 pSmo9Bd2k/GkZW/T/1Ea5eCcrqjeyT7INBj08PS+McvpbjlC3en+qY4b4QchwGQ= =rrih -----END PGP SIGNATURE----- --nHwqXXcoX0o6fKCv-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 16:02:31 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 718D571E for ; Thu, 18 Jul 2013 16:02:31 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 1731E826 for ; Thu, 18 Jul 2013 16:02:30 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50005046661.msg for ; Thu, 18 Jul 2013 17:02:21 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 18 Jul 2013 17:02:21 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1911771df7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: stable@freebsd.org Message-ID: From: "Steven Hartland" To: "John Reynolds" References: <51E73AA9.5030004@reynoldsnet.org> <268355E08D804BFDAC8C9883FA13AD93@multiplay.co.uk> <51E80E4C.1010603@reynoldsnet.org> Subject: Re: experience with 9.2-PRERELEASE Date: Thu, 18 Jul 2013 17:02:45 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response 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 Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 16:02:31 -0000 You can use: hint.ahcich.X.sata_rev to limit the speed See man for ahci(4) for more details. ----- Original Message ----- From: "John Reynolds" To: "Steven Hartland" Cc: Sent: Thursday, July 18, 2013 4:48 PM Subject: Re: experience with 9.2-PRERELEASE > On 7/18/2013 12:36 AM, Steven Hartland wrote: >> Is the SSD running at 6Gbps? If so have you tried limiting the speed >> to 3Gbps? > I would imagine so. It has a 6Gbps interface and the Z87 board does > also--so I can only imagine it's trying to go as fast as possible by > default. I will fiddle with the BIOS and see if I can limit it and see > if that prevents the "timeout" problems I was having after the 9.1-R > install. Somebody else suggested changing the USB settings in the BIOS > to try and overcome the problem when using the snap of 9.2-PRERELEASE as > well so I will try that too. Ultimately if nothing likes the SSD I will > try a regular SATA drive as last resort. > > The drive is an Intel 520 Series 240Gb model, FWIW. > > Thanks! > > -Jr > > ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 16:35:41 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B10A554A for ; Thu, 18 Jul 2013 16:35:41 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo201.cox.net (fed1rmfepo201.cox.net [68.230.241.146]) by mx1.freebsd.org (Postfix) with ESMTP id 89CA7A4D for ; Thu, 18 Jul 2013 16:35:41 +0000 (UTC) Received: from fed1rmimpo306 ([68.230.241.174]) by fed1rmfepo201.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130718163535.EXVN3849.fed1rmfepo201.cox.net@fed1rmimpo306> for ; Thu, 18 Jul 2013 12:35:35 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo306 with cox id 1sbb1m00B2oShb201sbb5Q; Thu, 18 Jul 2013 12:35:35 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020205.51E81957.01AA,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=XPTuv3dE c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=ktNfuVtv0skA:10 a=8nJEP1OIZ-IA:10 a=05pWP5ZVAAAA:8 a=fW0g_zRN6pgA:10 a=6I5d2MoRAAAA:8 a=JsMUEArgoxbth2vio3AA:9 a=wPNLvfGTeEIA:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r6I9Owpu085315; Thu, 18 Jul 2013 09:24:58 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51E81A4C.8000702@reynoldsnet.org> Date: Thu, 18 Jul 2013 09:39:40 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Glen Barber Subject: Re: experience with 9.2-PRERELEASE References: <51E73AA9.5030004@reynoldsnet.org> <20130718004854.GC2264@glenbarber.us> <51E765D3.8090801@reynoldsnet.org> <20130718154908.GD1945@glenbarber.us> In-Reply-To: <20130718154908.GD1945@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 16:35:41 -0000 > John, in addition to suggestions/replies from others, can you also try > the 10.0-CURRENT snapshot? In particular, if your problem continues > with a SATA drive, I am curious if the problem still exists in head/. > > http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/ > > Thanks. > Yes, I can try that. I will try a basic install with -current and see if a) the USB problem exists b) if I am getting the "timeout" errors with the SSD before I go off and tweak speed settings / USB settings. -jr From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 17:12:29 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4C035D9B; Thu, 18 Jul 2013 17:12:29 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) by mx1.freebsd.org (Postfix) with ESMTP id 273ADBE6; Thu, 18 Jul 2013 17:12:28 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:120e:1:1:c57c:729]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 7D0993A25; Thu, 18 Jul 2013 17:12:27 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 7D0993A25 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 18 Jul 2013 13:12:25 -0400 From: Glen Barber To: John Reynolds Subject: Re: experience with 9.2-PRERELEASE Message-ID: <20130718171225.GE1945@glenbarber.us> References: <51E73AA9.5030004@reynoldsnet.org> <268355E08D804BFDAC8C9883FA13AD93@multiplay.co.uk> <51E80E4C.1010603@reynoldsnet.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qftxBdZWiueWNAVY" Content-Disposition: inline In-Reply-To: <51E80E4C.1010603@reynoldsnet.org> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@freebsd.org, Steven Hartland X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 17:12:29 -0000 --qftxBdZWiueWNAVY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 18, 2013 at 08:48:28AM -0700, John Reynolds wrote: > On 7/18/2013 12:36 AM, Steven Hartland wrote: > >Is the SSD running at 6Gbps? If so have you tried limiting the speed > >to 3Gbps? > I would imagine so. It has a 6Gbps interface and the Z87 board does > also--so I can only imagine it's trying to go as fast as possible by > default. I will fiddle with the BIOS and see if I can limit it and > see if that prevents the "timeout" problems I was having after the > 9.1-R install. Somebody else suggested changing the USB settings in > the BIOS to try and overcome the problem when using the snap of > 9.2-PRERELEASE as well so I will try that too. Ultimately if nothing > likes the SSD I will try a regular SATA drive as last resort. >=20 > The drive is an Intel 520 Series 240Gb model, FWIW. >=20 FWIW, I had one of these in my laptop for about a year, and can confirm that it should work fine, at least on 10.0-CURRENT. Glen --qftxBdZWiueWNAVY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJR6CH5AAoJEFJPDDeguUajLQ0IAJ7C3/Zd/DNGiAO6PcPZibDO 6FHfApjTQbQky620w5XLyf6M/TnyRId6MdYu0bNsLtnLWXVtbZHCM5Cl9N7vN9yv Y+1Khzhi1xzGBnV65OismXDackW8jbEM2beva3vHGHrysUDVhGC2+eq9NYU1KXxu DiSEbmhF/a6oDVAMlPuJg/ETWX73TW6STY4tvwG3Zdmn6UcG80dSA58rdk2s8Ar7 hCUYTFj0eGvbSSM0lpyLsdDQkIyH1GPmVqUHft4/V6YvefCf9vlCQfEHF04uzolv UFTqBy2TDyxi5vLAHp2A2jQ0Nm7FyUZ8H/zZOKsTgnX4rLeyHi0i1v5d6BQEpos= =krId -----END PGP SIGNATURE----- --qftxBdZWiueWNAVY-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 17:44:59 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 516776D1; Thu, 18 Jul 2013 17:44:59 +0000 (UTC) (envelope-from hartzell@alacrity.alerce.com) Received: from griffon.alerce.com (griffon.alerce.com [206.125.171.162]) by mx1.freebsd.org (Postfix) with ESMTP id 3D5D0D1B; Thu, 18 Jul 2013 17:44:58 +0000 (UTC) Received: from griffon.alerce.com (localhost [127.0.0.1]) by griffon.alerce.com (Postfix) with ESMTP id 17C092842A; Thu, 18 Jul 2013 10:44:58 -0700 (PDT) Received: from alacrity.alerce.com (75-149-38-78-SFBA.hfc.comcastbusiness.net [75.149.38.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by griffon.alerce.com (Postfix) with ESMTPSA id D5E5E28424; Thu, 18 Jul 2013 10:44:57 -0700 (PDT) Received: by alacrity.alerce.com (Postfix, from userid 503) id E6866150C3C2; Thu, 18 Jul 2013 10:44:53 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20968.10645.880772.30501@gargle.gargle.HOWL> Date: Thu, 18 Jul 2013 10:44:53 -0700 To: Andriy Gapon Subject: Re: Help with filing a [maybe] ZFS/mmap bug. In-Reply-To: <51E80B30.1090004@FreeBSD.org> References: <20967.760.95825.310085@gargle.gargle.HOWL> <51E80B30.1090004@FreeBSD.org> X-Mailer: VM 8.2.0b under 24.2.1 (x86_64-apple-darwin) X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@FreeBSD.org, hartzell@alerce.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 17:44:59 -0000 Andriy Gapon writes: > on 17/07/2013 23:47 George Hartzell said the following: > > How should I move forward with this? > > Could you please try to reproduce this problem using a kernel built with > INVARIANTS options? I added INVARIANT_SUPPORT and INVARIANTS options to the GENERIC kernel, rebuilt it, installed it and running through my "test case" generated a lot of invalid flac files. I"m not sure what the options are/were supposed to do though, it looks like they generally lead to KASSERTS, which lead to abort()'s. Nothing in /var/log/messages or on the console. g. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 18:40:53 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C46E0B19 for ; Thu, 18 Jul 2013 18:40:53 +0000 (UTC) (envelope-from hartzell@alacrity.alerce.com) Received: from griffon.alerce.com (griffon.alerce.com [206.125.171.162]) by mx1.freebsd.org (Postfix) with ESMTP id B0161F4F for ; Thu, 18 Jul 2013 18:40:53 +0000 (UTC) Received: from griffon.alerce.com (localhost [127.0.0.1]) by griffon.alerce.com (Postfix) with ESMTP id 2AD212842A; Thu, 18 Jul 2013 11:40:53 -0700 (PDT) Received: from alacrity.alerce.com (75-149-38-78-SFBA.hfc.comcastbusiness.net [75.149.38.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by griffon.alerce.com (Postfix) with ESMTPSA id E4C4228424; Thu, 18 Jul 2013 11:40:52 -0700 (PDT) Received: by alacrity.alerce.com (Postfix, from userid 503) id E3D2E150C749; Thu, 18 Jul 2013 11:40:51 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20968.14003.813473.517439@gargle.gargle.HOWL> Date: Thu, 18 Jul 2013 11:40:51 -0700 To: Richard Todd Subject: Re: Help with filing a [maybe] ZFS/mmap bug. In-Reply-To: References: <20967.760.95825.310085@gargle.gargle.HOWL> X-Mailer: VM 8.2.0b under 24.2.1 (x86_64-apple-darwin) X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, hartzell@alerce.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 18:40:53 -0000 Richard Todd writes: > George Hartzell writes: > > > Hi All, > > > > I have what I think is a ZFS related bug. > > [...] > > [summary: Picard seems to trigger an mmap consistency bug in ZFS]. > > [...] > Anyway, what I'd suggest is the following: see if my patch for py-mutagen > disabling the mmap() in those two functions lets you run picard reliably. Removing the mmap support from those two routines seems to avoid the issue. > If so, then the issue is triggered by one or both of those two routines; > hack them to print out the exact offsets used on each call and use that to > try and code up a simple C++ test case. > [...] Your test case doesn't use mmap, I assume that you've offered it up as a hint, not as something that's nearly done. The shell script in particular seems useful. In my case I'd want to find a particular set of file size, offset, and insertion size that triggers the problem and code up a c/c++ equiv. of the mmap calls that py-mutagen does. Right? I'm hesistant about that. I believe (and will try to prove) that the problem does not occur deterministically for a particular track between different test runs. I'm worried that it's not as simple as "using mmap to insert 27 bytes into a 1024 bytes file at pos 42 causes corruption" but rather that it depends on a more complex set of interactions. My next step will be to see if a track that has trouble in one run has trouble in another. If not, then I'm not sure that a simple test will be successful. g. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:10:23 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8080C366 for ; Thu, 18 Jul 2013 19:10:23 +0000 (UTC) (envelope-from yerenkow@gmail.com) Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 4449A112 for ; Thu, 18 Jul 2013 19:10:23 +0000 (UTC) Received: by mail-vc0-f170.google.com with SMTP id hf12so2638925vcb.15 for ; Thu, 18 Jul 2013 12:10:22 -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=cRnrsrkPiqu/Pb8CqFOxnj8u2ET3YBm8XPh1sbYw8Sg=; b=YTYfN+Tpbdy1YEZU1WCy+i80BDGcFSsb+2NhjyGfgVnKhzBMpJmIzTQcEUZF/veocr NEsU97q1241gS2VYBynHL+NMsP1Pb+u5SZerxMc+rOUq9Y60c+T+HvbOLEW4hVGZ2qHt 4i4QE7OUw0+pnhurVklf9oZdALKHt7sAs915F5uXjX/XHS9WSKlxlVoRRIlFIq8ubojm iz750oKJTsFAcNPFbZQTh6x4wWBlWlW2IKcVPspNSUogfT+J0CzVepruXgUJr0mRB5YN jk4rU509KWW3FCBoShGuyoA/tp9ckhBnwEFWr8OPJA8FhrdbDNoWdSu7PXjYwrNZAKpU 6pSw== MIME-Version: 1.0 X-Received: by 10.52.249.66 with SMTP id ys2mr3857373vdc.55.1374174622749; Thu, 18 Jul 2013 12:10:22 -0700 (PDT) Received: by 10.52.190.200 with HTTP; Thu, 18 Jul 2013 12:10:22 -0700 (PDT) In-Reply-To: <20968.14003.813473.517439@gargle.gargle.HOWL> References: <20967.760.95825.310085@gargle.gargle.HOWL> <20968.14003.813473.517439@gargle.gargle.HOWL> Date: Thu, 18 Jul 2013 22:10:22 +0300 Message-ID: Subject: Re: Help with filing a [maybe] ZFS/mmap bug. From: Alexander Yerenkow To: hartzell@alerce.com Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Richard Todd , FreeBSD Stable Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:10:23 -0000 I know how all not loving "me-too" emails, but I'll try :) There's a rtorrent, which uses mmap. And I had cases (related to reboot), where big files (or average files in many-files torrents) appears with broken checksum without any good reason. Author of rtorrent not very politely always assume that really broken other filesystems, while rtorrent have simple logic (with mmap using)... This post is pretty interesting: http://libtorrent.rakshasa.no/ticket/483 In the end I just switched to transmission. Anyway, there could be really some weird/rare bugs with ZFS and mmap. Or just ZFS. I hope this will help at least to narrow direction for potential bugbusting. 2013/7/18 George Hartzell > Richard Todd writes: > > George Hartzell writes: > > > > > Hi All, > > > > > > I have what I think is a ZFS related bug. > > > [...] > > > > [summary: Picard seems to trigger an mmap consistency bug in ZFS]. > > > > [...] > > Anyway, what I'd suggest is the following: see if my patch for > py-mutagen > > disabling the mmap() in those two functions lets you run picard > reliably. > > Removing the mmap support from those two routines seems to avoid the > issue. > > > If so, then the issue is triggered by one or both of those two routines; > > hack them to print out the exact offsets used on each call and use that > to > > try and code up a simple C++ test case. > > [...] > > Your test case doesn't use mmap, I assume that you've offered it up as > a hint, not as something that's nearly done. The shell script in > particular seems useful. > > In my case I'd want to find a particular set of file size, offset, and > insertion size that triggers the problem and code up a c/c++ equiv. of > the mmap calls that py-mutagen does. Right? > > I'm hesistant about that. I believe (and will try to prove) that the > problem does not occur deterministically for a particular track > between different test runs. I'm worried that it's not as simple as > "using mmap to insert 27 bytes into a 1024 bytes file at pos 42 causes > corruption" but rather that it depends on a more complex set of > interactions. > > My next step will be to see if a track that has trouble in one run has > trouble in another. If not, then I'm not sure that a simple test will > be successful. > > g. > _______________________________________________ > 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" > -- Regards, Alexander Yerenkow From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:13:27 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 661F8478 for ; Thu, 18 Jul 2013 19:13:27 +0000 (UTC) (envelope-from joe@karthauser.co.uk) Received: from babel.karthauser.co.uk (212-13-197-151.karthauser.co.uk [212.13.197.151]) by mx1.freebsd.org (Postfix) with ESMTP id 32A17130 for ; Thu, 18 Jul 2013 19:13:26 +0000 (UTC) Received: from phoenix.fritz.box (unknown [81.187.183.70]) (Authenticated sender: joemail@tao.org.uk) by babel.karthauser.co.uk (Postfix) with ESMTPSA id 677C12AD6; Thu, 18 Jul 2013 19:13:25 +0000 (UTC) Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <51E7DA7C.8060105@netfence.it> Date: Thu, 18 Jul 2013 20:13:24 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5B6FB80D-609D-4336-B3F8-C09AA7CACB44@karthauser.co.uk> References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> <281DBD06-81D5-4DDD-9464-B96C80C22C3F@gid.co.uk> <51E7DA7C.8060105@netfence.it> To: Andrea Venturoli X-Mailer: Apple Mail (2.1508) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:13:27 -0000 On 18 Jul 2013, at 13:07, Andrea Venturoli wrote: > Perhaps they are WD Green drives? They're WD RE2-GP 1 TB drives (model WD1000FYPS) , not sure if that's = green or not. > In that case, other than quoting Bob's suggestion about avoiding them, = there's something you can do: > a) turn off the drives' power-saving features (this is done through a = DOS utility you can download); > b) try different controllers and/or different OS releases. I'm committed to FreeBSD, as the machine is already rolled out and in a = data centre ;). > You'll find a lot on this problem if you search the web. > There's also a report of mine you can search on this ML, regarding = FreeBSD specifically. I'll see if I can find it. Thanks. Joe From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:18:22 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 54DB782D; Thu, 18 Jul 2013 19:18:22 +0000 (UTC) (envelope-from joe@karthauser.co.uk) Received: from babel.karthauser.co.uk (212-13-197-151.karthauser.co.uk [212.13.197.151]) by mx1.freebsd.org (Postfix) with ESMTP id 24191188; Thu, 18 Jul 2013 19:18:21 +0000 (UTC) Received: from phoenix.fritz.box (unknown [81.187.183.70]) (Authenticated sender: joemail@tao.org.uk) by babel.karthauser.co.uk (Postfix) with ESMTPSA id 2C0A12AF5; Thu, 18 Jul 2013 19:18:21 +0000 (UTC) Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=windows-1252 From: Dr Josef Karthauser X-Priority: 3 In-Reply-To: <33EF2240EDC1446D8E45F8C51974136B@multiplay.co.uk> Date: Thu, 18 Jul 2013 20:18:20 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> <33EF2240EDC1446D8E45F8C51974136B@multiplay.co.uk> To: "Steven Hartland" X-Mailer: Apple Mail (2.1508) Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:18:22 -0000 On 18 Jul 2013, at 08:33, "Steven Hartland" wrote: > What chassis is this? Hey Steven, It's a Supermicro CSE-813MTQ-350CB. Cheers, Joe From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:30:10 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D7E34EE8 for ; Thu, 18 Jul 2013 19:30:10 +0000 (UTC) (envelope-from rmtodd@servalan.servalan.com) Received: from ln.servalan.com (unknown [IPv6:2600:3c00::f03c:91ff:fe96:62f5]) by mx1.freebsd.org (Postfix) with ESMTP id B746423A for ; Thu, 18 Jul 2013 19:30:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=servalan.com; s=rsadkim; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=vRGN6la7EJioumjnlEeLjjyq9CNb2uKxPG00t+GvTNI=; b=P4meuLOTAX6J4IHTyAPjDrSo9a/I+dsGfb/Tb3IVGEFmETD3I+MIPCOK8eGRdcgCkf40QBiN5yIwukTSTvHeVe4Kd/vrt4iwOrOEC15dK8NjrWVqYrPrmNhcoJs4h24EHEMxa2dpEaFeB4nvbbFJ9YYd/njH1QdRQZ/hA1ptkRk=; Received: from uucp by ln.servalan.com with local-rmail (Exim 4.71) (envelope-from ) id 1Uzttx-00011G-JD for freebsd-stable@freebsd.org; Thu, 18 Jul 2013 14:30:09 -0500 Received: from rmtodd by servalan.servalan.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UztqK-000CCU-Ha; Thu, 18 Jul 2013 14:26:24 -0500 Date: Thu, 18 Jul 2013 14:26:24 -0500 From: Richard Todd To: George Hartzell Subject: Re: Help with filing a [maybe] ZFS/mmap bug. Message-ID: <20130718192624.GA45917@ichotolot.servalan.com> References: <20967.760.95825.310085@gargle.gargle.HOWL> <20968.14003.813473.517439@gargle.gargle.HOWL> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20968.14003.813473.517439@gargle.gargle.HOWL> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Richard Todd , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:30:10 -0000 On Thu, Jul 18, 2013 at 11:40:51AM -0700, George Hartzell wrote: > Removing the mmap support from those two routines seems to avoid the > issue. Aha. > > If so, then the issue is triggered by one or both of those two routines; > > hack them to print out the exact offsets used on each call and use that to > > try and code up a simple C++ test case. > > [...] > > Your test case doesn't use mmap, I assume that you've offered it up as > a hint, not as something that's nearly done. The shell script in > particular seems useful. Um, go look at gen4.cpp again. It uses mmap(). The insert_bytes and delete_bytes functions should work the same way as the (mmap-using path of) the functions of the same name in py-mutagen. > In my case I'd want to find a particular set of file size, offset, and > insertion size that triggers the problem and code up a c/c++ equiv. of > the mmap calls that py-mutagen does. Right? Yeah. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:31:16 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 71532FE9 for ; Thu, 18 Jul 2013 19:31:16 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from st11p05mm-asmtp001.mac.com (st11p05mm-asmtpout004.mac.com [17.172.108.249]) by mx1.freebsd.org (Postfix) with ESMTP id 4A6B224C for ; Thu, 18 Jul 2013 19:31:16 +0000 (UTC) Received: from cswiger1.apple.com (unknown [17.209.8.53]) by st11p05mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MQ5001NDCVV6270@st11p05mm-asmtp001.mac.com> for freebsd-stable@freebsd.org; Thu, 18 Jul 2013 19:31:08 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8794,1.0.431,0.0.0000 definitions=2013-07-18_08:2013-07-18,2013-07-18,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1305010000 definitions=main-1307180156 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? From: Charles Swiger In-reply-to: <5B6FB80D-609D-4336-B3F8-C09AA7CACB44@karthauser.co.uk> Date: Thu, 18 Jul 2013 12:31:06 -0700 Content-transfer-encoding: quoted-printable Message-id: <8AB7617E-791C-45D8-9FA1-A927057EE048@mac.com> References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> <281DBD06-81D5-4DDD-9464-B96C80C22C3F@gid.co.uk> <51E7DA7C.8060105@netfence.it> <5B6FB80D-609D-4336-B3F8-C09AA7CACB44@karthauser.co.uk> To: Dr Josef Karthauser X-Mailer: Apple Mail (2.1508) Cc: freebsd-stable@freebsd.org, Andrea Venturoli X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:31:16 -0000 Hi-- On Jul 18, 2013, at 12:13 PM, Dr Josef Karthauser = wrote: > On 18 Jul 2013, at 13:07, Andrea Venturoli wrote: >=20 >> Perhaps they are WD Green drives? >=20 > They're WD RE2-GP 1 TB drives (model WD1000FYPS) , not sure if that's = green or not. Yes, those are WDC's Green drives, although they are also the higher = grade version as compared to standard desktop drives which are supposed = to have firmware which plays nice with RAID (TLER, time-limited error = recovery). Updating the firmware and increasing the timeout before these spin down = automagically is likely to help, but as Andrea noted, such drives do = have quite a history of timeout problems due to excessive head parking = and their power conservation attempts. Regards, --=20 -Chuck From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:33:22 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4619A1AD for ; Thu, 18 Jul 2013 19:33:22 +0000 (UTC) (envelope-from joe@karthauser.co.uk) Received: from babel.karthauser.co.uk (212-13-197-151.karthauser.co.uk [212.13.197.151]) by mx1.freebsd.org (Postfix) with ESMTP id 13747270 for ; Thu, 18 Jul 2013 19:33:21 +0000 (UTC) Received: from phoenix.fritz.box (unknown [81.187.183.70]) (Authenticated sender: joemail@tao.org.uk) by babel.karthauser.co.uk (Postfix) with ESMTPSA id 087C52E82; Thu, 18 Jul 2013 19:33:20 +0000 (UTC) Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <8AB7617E-791C-45D8-9FA1-A927057EE048@mac.com> Date: Thu, 18 Jul 2013 20:33:20 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <46338EA7-6195-478C-9999-17810530A6AC@karthauser.co.uk> References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> <281DBD06-81D5-4DDD-9464-B96C80C22C3F@gid.co.uk> <51E7DA7C.8060105@netfence.it> <5B6FB80D-609D-4336-B3F8-C09AA7CACB44@karthauser.co.uk> <8AB7617E-791C-45D8-9FA1-A927057EE048@mac.com> To: Charles Swiger X-Mailer: Apple Mail (2.1508) Cc: freebsd-stable@freebsd.org, Andrea Venturoli X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:33:22 -0000 On 18 Jul 2013, at 20:31, Charles Swiger wrote: > Hi-- >=20 > On Jul 18, 2013, at 12:13 PM, Dr Josef Karthauser = wrote: >> On 18 Jul 2013, at 13:07, Andrea Venturoli wrote: >>=20 >>> Perhaps they are WD Green drives? >>=20 >> They're WD RE2-GP 1 TB drives (model WD1000FYPS) , not sure if that's = green or not. >=20 > Yes, those are WDC's Green drives, although they are also the higher = grade version as compared to standard desktop drives which are supposed = to have firmware which plays nice with RAID (TLER, time-limited error = recovery). >=20 > Updating the firmware and increasing the timeout before these spin = down automagically is likely to help, but as Andrea noted, such drives = do have quite a history of timeout problems due to excessive head = parking and their power conservation attempts. We also wondered whether it was the motherboard, and so we've replaced = it! Hope that that works! But, from what's being said here, it looks like that might not be the = case. :/ Although, we've been up for 5 days now with no recurrences of = the previous issue. Joe= From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:35:15 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7B0BD39D for ; Thu, 18 Jul 2013 19:35:15 +0000 (UTC) (envelope-from joe@karthauser.co.uk) Received: from babel.karthauser.co.uk (212-13-197-151.karthauser.co.uk [212.13.197.151]) by mx1.freebsd.org (Postfix) with ESMTP id 4902B2A8 for ; Thu, 18 Jul 2013 19:35:14 +0000 (UTC) Received: from phoenix.fritz.box (unknown [81.187.183.70]) (Authenticated sender: joemail@tao.org.uk) by babel.karthauser.co.uk (Postfix) with ESMTPSA id D96272E94; Thu, 18 Jul 2013 19:35:13 +0000 (UTC) Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=us-ascii From: Dr Josef Karthauser In-Reply-To: <8AB7617E-791C-45D8-9FA1-A927057EE048@mac.com> Date: Thu, 18 Jul 2013 20:35:13 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <646F215B-95F3-4C3B-9174-4DD2E3F9D72A@karthauser.co.uk> References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> <281DBD06-81D5-4DDD-9464-B96C80C22C3F@gid.co.uk> <51E7DA7C.8060105@netfence.it> <5B6FB80D-609D-4336-B3F8-C09AA7CACB44@karthauser.co.uk> <8AB7617E-791C-45D8-9FA1-A927057EE048@mac.com> To: Charles Swiger X-Mailer: Apple Mail (2.1508) Cc: Andrea Venturoli , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:35:15 -0000 On 18 Jul 2013, at 20:31, Charles Swiger wrote: > On Jul 18, 2013, at 12:13 PM, Dr Josef Karthauser = wrote: >> On 18 Jul 2013, at 13:07, Andrea Venturoli wrote: >>=20 >>> Perhaps they are WD Green drives? >>=20 >> They're WD RE2-GP 1 TB drives (model WD1000FYPS) , not sure if that's = green or not. >=20 > Yes, those are WDC's Green drives, although they are also the higher = grade version as compared to standard desktop drives which are supposed = to have firmware which plays nice with RAID (TLER, time-limited error = recovery). >=20 > Updating the firmware and increasing the timeout before these spin = down automagically is likely to help, but as Andrea noted, such drives = do have quite a history of timeout problems due to excessive head = parking and their power conservation attempts. They're currently on firmware 02.01B01, btw. Not sure if that's the = latest or not. Joe From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:35:45 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 12B244A2; Thu, 18 Jul 2013 19:35:45 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 8719A2BC; Thu, 18 Jul 2013 19:35:44 +0000 (UTC) Received: from r2d2 ([82.69.141.170]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50005048668.msg; Thu, 18 Jul 2013 20:35:41 +0100 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 18 Jul 2013 20:35:41 +0100 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 82.69.141.170 X-Return-Path: prvs=1911771df7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk Message-ID: <964B87D56B7C4B529E995E7A660E9AAD@multiplay.co.uk> From: "Steven Hartland" To: "Dr Josef Karthauser" References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> <33EF2240EDC1446D8E45F8C51974136B@multiplay.co.uk> Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? Date: Thu, 18 Jul 2013 20:36:03 +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 Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:35:45 -0000 ----- Original Message ----- From: "Dr Josef Karthauser" > On 18 Jul 2013, at 08:33, "Steven Hartland" wrote: > >> What chassis is this? > > Hey Steven, > > It's a Supermicro CSE-813MTQ-350CB. We've seen issues on supermicro chassis before which cause timeouts and in extreme cases device drops so if you can try wiring the disks up directly to the MB via sata cables bypassing the hotswap midplane and see if that helps. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:53:53 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3FB89A32 for ; Thu, 18 Jul 2013 19:53:53 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp.eutelia.it (mp1-smtp-6.eutelia.it [62.94.10.166]) by mx1.freebsd.org (Postfix) with ESMTP id EC4ED3DC for ; Thu, 18 Jul 2013 19:53:52 +0000 (UTC) Received: from ns2.biolchim.it (ip-188-188.sn2.eutelia.it [83.211.188.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.eutelia.it (Eutelia) with ESMTP id A6CA66618CB for ; Thu, 18 Jul 2013 21:53:50 +0200 (CEST) Received: from soth.ventu (adsl-ull-104-180.41-151.net24.it [151.41.180.104]) (authenticated bits=0) by ns2.biolchim.it (8.14.7/8.14.7) with ESMTP id r6IJrgPs065781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 18 Jul 2013 21:53:46 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: ns2.biolchim.it: Host adsl-ull-104-180.41-151.net24.it [151.41.180.104] claimed to be soth.ventu Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.7/8.14.5) with ESMTP id r6IJrRSk062843; Thu, 18 Jul 2013 21:53:27 +0200 (CEST) (envelope-from ml@netfence.it) Message-ID: <51E847B7.5000508@netfence.it> Date: Thu, 18 Jul 2013 21:53:27 +0200 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130626 Thunderbird/17.0.7 MIME-Version: 1.0 To: Dr Josef Karthauser Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> <281DBD06-81D5-4DDD-9464-B96C80C22C3F@gid.co.uk> <51E7DA7C.8060105@netfence.it> <5B6FB80D-609D-4336-B3F8-C09AA7CACB44@karthauser.co.uk> In-Reply-To: <5B6FB80D-609D-4336-B3F8-C09AA7CACB44@karthauser.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 X-Scanned-By: MIMEDefang 2.73 on 10.1.2.13 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ns2.biolchim.it [192.168.2.203]); Thu, 18 Jul 2013 21:53:47 +0200 (CEST) Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:53:53 -0000 On 07/18/13 21:13, Dr Josef Karthauser wrote: >> b) try different controllers and/or different OS releases. > > I'm committed to FreeBSD, as the machine is already rolled out and in a data centre ;). I said different "OS releases", not different "OS"! I wouln't say such a blasphemy :) bye av. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 19:57:08 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 46554CB7 for ; Thu, 18 Jul 2013 19:57:08 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp.eutelia.it (mp1-smtp-6.eutelia.it [62.94.10.166]) by mx1.freebsd.org (Postfix) with ESMTP id F24685F1 for ; Thu, 18 Jul 2013 19:57:07 +0000 (UTC) Received: from ns2.biolchim.it (ip-188-188.sn2.eutelia.it [83.211.188.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.eutelia.it (Eutelia) with ESMTP id BC6D16618F0 for ; Thu, 18 Jul 2013 21:57:06 +0200 (CEST) Received: from soth.ventu (adsl-ull-104-180.41-151.net24.it [151.41.180.104]) (authenticated bits=0) by ns2.biolchim.it (8.14.7/8.14.7) with ESMTP id r6IJv2s6065942 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 18 Jul 2013 21:57:03 +0200 (CEST) (envelope-from ml@netfence.it) X-Authentication-Warning: ns2.biolchim.it: Host adsl-ull-104-180.41-151.net24.it [151.41.180.104] claimed to be soth.ventu Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.7/8.14.5) with ESMTP id r6IJurHr063135; Thu, 18 Jul 2013 21:56:54 +0200 (CEST) (envelope-from ml@netfence.it) Message-ID: <51E84885.9070500@netfence.it> Date: Thu, 18 Jul 2013 21:56:53 +0200 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130626 Thunderbird/17.0.7 MIME-Version: 1.0 To: Charles Swiger Subject: Re: Drive failures with ada on FreeBSD-9.1, driver bug or wiring issue? References: <20130716225013.1C63B23A@babel.karthauser.co.uk> <60F7BE75-5E2F-471E-A9CE-AF4CD17D96E2@karthauser.co.uk> <281DBD06-81D5-4DDD-9464-B96C80C22C3F@gid.co.uk> <51E7DA7C.8060105@netfence.it> <5B6FB80D-609D-4336-B3F8-C09AA7CACB44@karthauser.co.uk> <8AB7617E-791C-45D8-9FA1-A927057EE048@mac.com> In-Reply-To: <8AB7617E-791C-45D8-9FA1-A927057EE048@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 X-Scanned-By: MIMEDefang 2.73 on 10.1.2.13 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ns2.biolchim.it [192.168.2.203]); Thu, 18 Jul 2013 21:57:03 +0200 (CEST) Cc: Dr Josef Karthauser , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 19:57:08 -0000 On 07/18/13 21:31, Charles Swiger wrote: > Updating the firmware and increasing the timeout before these spin down > automagically is likely to help, but as Andrea noted, such drives do > have quite a history of timeout problems due to excessive head parking > and their power conservation attempts. Just for the record, I've been using them for several months without a hitch; it's just a matter of finding the correct settings/firmware/OS version/controller. This is to say you should be able to get them to work, altough you might require some luck (or some sort of divination). bye av. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 20:24:12 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A04BB491 for ; Thu, 18 Jul 2013 20:24:12 +0000 (UTC) (envelope-from johnjen@reynoldsnet.org) Received: from fed1rmfepo202.cox.net (fed1rmfepo202.cox.net [68.230.241.147]) by mx1.freebsd.org (Postfix) with ESMTP id 78ADF794 for ; Thu, 18 Jul 2013 20:24:12 +0000 (UTC) Received: from fed1rmimpo210 ([68.230.241.161]) by fed1rmfepo202.cox.net (InterMail vM.8.01.05.09 201-2260-151-124-20120717) with ESMTP id <20130718202406.KGVC3842.fed1rmfepo202.cox.net@fed1rmimpo210> for ; Thu, 18 Jul 2013 16:24:06 -0400 Received: from ip70-162-30-130.ph.ph.cox.net ([70.162.30.130]) by fed1rmimpo210 with cox id 1wQ51m00Y2oShb201wQ6TC; Thu, 18 Jul 2013 16:24:06 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020204.51E84EE6.008E,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=drIF/Sc4 c=1 sm=1 a=niybPLZ33vM10MUkQ8CgDg==:17 a=WIJ4OnAGe2cA:10 a=ktNfuVtv0skA:10 a=8nJEP1OIZ-IA:10 a=05pWP5ZVAAAA:8 a=fW0g_zRN6pgA:10 a=6I5d2MoRAAAA:8 a=Y6j2amh57tHYvc_ipJYA:9 a=wPNLvfGTeEIA:10 a=niybPLZ33vM10MUkQ8CgDg==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from [192.168.1.16] (mussel.home-net [192.168.1.16]) by ip70-162-30-130.ph.ph.cox.net (8.14.6/8.14.6) with ESMTP id r6IDDSgZ087074; Thu, 18 Jul 2013 13:13:28 GMT (envelope-from johnjen@reynoldsnet.org) Message-ID: <51E84FDA.3010607@reynoldsnet.org> Date: Thu, 18 Jul 2013 13:28:10 -0700 From: John Reynolds User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Glen Barber Subject: Re: experience with 9.2-PRERELEASE References: <51E73AA9.5030004@reynoldsnet.org> <20130718004854.GC2264@glenbarber.us> <51E765D3.8090801@reynoldsnet.org> <20130718154908.GD1945@glenbarber.us> In-Reply-To: <20130718154908.GD1945@glenbarber.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 20:24:12 -0000 On 7/18/2013 8:49 AM, Glen Barber wrote: > On Wed, Jul 17, 2013 at 08:49:39PM -0700, John Reynolds wrote: >> today. I will most definitely report back any findings. Thanks for >> your reply! >> > John, in addition to suggestions/replies from others, can you also try > the 10.0-CURRENT snapshot? In particular, if your problem continues > with a SATA drive, I am curious if the problem still exists in head/. > > http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/ > > Thanks. Thanks to Glen and Steve and all those who replied to my initial posting. I am quite pleased after having been "figuratively gone" from (but still running) FreeBSD for coming up on 2 years (hey--when it's so rock solid, it's easy when you don't have to ask questions :) that i can come back to these lists and still find lots of people willing to help! You guys (and gals) are awesome! Anyway, it seems I have solved my problems with this new hardware. There was really two issues I bumped into. After installing 9.1-R I saw this "timeout" problem to ahcich1 device and it would "hang" for about 5 minutes then continue to boot. Then I tried 9.2-PRE but there the keyboard was not recognized and I kept getting infinite "ugen0.2: ..... (disconnected)" errors at the install screen. One person said to fiddle in the BIOS with the USB settings. I went into the BIOS and disabled "Intel USB 3.0 Mode" support (this is a very new motherboard with USB 3.0). That fixed the issue! For those curious about -current, I also tried to install that and it experienced the same USB problems until I disabled this 3.0 mode. Once I got past that and installed 9.2-PRE again, I let it timeout again during boot. Then I looked at the dmesg output much more closely than I could have during the boot from DVD. It turns out that I only THOUGHT it was a timeout to the SSD. The Intel Series 520 SSD was NOT the issue. I was getting a timeout on ahcich1 which from the dmesg output was my DVD burner! The SSD was on ahcich5. The only difference here is that by sheer happenstance, I connected the SSD to the SATA port owned by the Intel Z87 (Lynx Point) controller. The DVD burner (which is probably 5 years old) was hooked to ASRock's own "ASMedia ASM1061" controller. Apparently this controller doesn't play well with my older DVD burner. I switched ports and put both on the Intel controller and BOOM! Success! No timeouts, no funny business. Nothing. At this point i don't mind at all turning off the USB 3.0 mode because I have yet to actually see a 3.0 device in the wild and I certainly won't own one anytime soon. :) .... so it's kind of a moot point. I'm sure the USB developers will see this problem and tackle it in time. I'm just thrilled to be booting on this new H/W! Thanks again to all on the list that replied! -Jr From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 20:31:24 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CBFC66AE; Thu, 18 Jul 2013 20:31:24 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) by mx1.freebsd.org (Postfix) with ESMTP id 6DA1D7EE; Thu, 18 Jul 2013 20:31:24 +0000 (UTC) Received: from glenbarber.us (nucleus.glenbarber.us [IPv6:2001:470:8:1205:2:2:ff:29]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 66AA2AC50; Thu, 18 Jul 2013 20:31:23 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 66AA2AC50 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Thu, 18 Jul 2013 16:31:21 -0400 From: Glen Barber To: John Reynolds Subject: Re: experience with 9.2-PRERELEASE Message-ID: <20130718203121.GA2135@glenbarber.us> References: <51E73AA9.5030004@reynoldsnet.org> <20130718004854.GC2264@glenbarber.us> <51E765D3.8090801@reynoldsnet.org> <20130718154908.GD1945@glenbarber.us> <51E84FDA.3010607@reynoldsnet.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: <51E84FDA.3010607@reynoldsnet.org> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 20:31:25 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 18, 2013 at 01:28:10PM -0700, John Reynolds wrote: > On 7/18/2013 8:49 AM, Glen Barber wrote: > >On Wed, Jul 17, 2013 at 08:49:39PM -0700, John Reynolds wrote: > >>today. I will most definitely report back any findings. Thanks for > >>your reply! > >> > >John, in addition to suggestions/replies from others, can you also try > >the 10.0-CURRENT snapshot? In particular, if your problem continues > >with a SATA drive, I am curious if the problem still exists in head/. > > > > http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/ > > > >Thanks. >=20 > Thanks to Glen and Steve and all those who replied to my initial > posting. I am quite pleased after having been "figuratively gone" > from (but still running) FreeBSD for coming up on 2 years (hey--when > it's so rock solid, it's easy when you don't have to ask questions > :) that i can come back to these lists and still find lots of people > willing to help! You guys (and gals) are awesome! >=20 > Anyway, it seems I have solved my problems with this new hardware. > There was really two issues I bumped into. After installing 9.1-R I > saw this "timeout" problem to ahcich1 device and it would "hang" for > about 5 minutes then continue to boot. Then I tried 9.2-PRE but > there the keyboard was not recognized and I kept getting infinite > "ugen0.2: ..... (disconnected)" errors at the install > screen. One person said to fiddle in the BIOS with the USB settings. > I went into the BIOS and disabled "Intel USB 3.0 Mode" support (this > is a very new motherboard with USB 3.0). That fixed the issue! For > those curious about -current, I also tried to install that and it > experienced the same USB problems until I disabled this 3.0 mode. >=20 > Once I got past that and installed 9.2-PRE again, I let it timeout > again during boot. Then I looked at the dmesg output much more > closely than I could have during the boot from DVD. It turns out > that I only THOUGHT it was a timeout to the SSD. The Intel Series > 520 SSD was NOT the issue. I was getting a timeout on ahcich1 which > from the dmesg output was my DVD burner! The SSD was on ahcich5. The > only difference here is that by sheer happenstance, I connected the > SSD to the SATA port owned by the Intel Z87 (Lynx Point) controller. > The DVD burner (which is probably 5 years old) was hooked to > ASRock's own "ASMedia ASM1061" controller. Apparently this > controller doesn't play well with my older DVD burner. I switched > ports and put both on the Intel controller and BOOM! Success! No > timeouts, no funny business. Nothing. At this point i don't mind at > all turning off the USB 3.0 mode because I have yet to actually see > a 3.0 device in the wild and I certainly won't own one anytime soon. > :) .... so it's kind of a moot point. I'm sure the USB developers > will see this problem and tackle it in time. I'm just thrilled to be > booting on this new H/W! >=20 > Thanks again to all on the list that replied! >=20 Great to hear. Thank you for trying different suggestions, and reporting back the results. I'm glad things worked out (though, I'm still a bit worried about the xhci(4) in your case...). Glen --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBCAAGBQJR6FCZAAoJEFJPDDeguUajJwcH/Av0lHF2ZHnr8BSEMTHdw7EF VH71tp0gVVZmQKSD3odeMu/AXyOQ1ApzicPvUQDaMaFyB5Cf3B8n9JfmcmsgAzb0 QiQTv9vATogem+v0TR73M/OjxqZ4+FdHHUHLX2f0TdBWrfIin85m4rQJooP4BW8i hC8JStgbhZyTUSqcKEFwiVuaDCt3sHK9k7ZIRixfxx47In4aWI6QOxvA3Q/tMpSw uy0lJIfRmME1/2M5aZSMpHK3bCT/jd9z8aH1ymw3fndhIudZ2QgmpuMoysWyhhC1 kX61WVrNpfDy1KD0t2SNugH3i8tWSh7g8mWS4c1kPYwiMwiWcuDQ5EWiLe+9lyQ= =sAC4 -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 18 22:10:29 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 91AB848B; Thu, 18 Jul 2013 22:10:29 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by mx1.freebsd.org (Postfix) with ESMTP id 046B2BDF; Thu, 18 Jul 2013 22:10:28 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id n11so3314070wgh.21 for ; Thu, 18 Jul 2013 15:10:28 -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=jiqqlo0OLWcMtbeeOEyrCDyBfjb2mHfsienPs7ytUPY=; b=pQznU2rzaIxesmNIMrCWYo5oQLNM1ipNWA8NMCW+S4pdOiL6IEy0R29wYVY0pG9rd8 TVLyMy9xdxVYHvQdu1l5W16+bmRdGO8HWrRVBic955iwpYjf/WgsZdzPRAR89VsBydLV c4XrRFaVdMdZ/fOvJPoDHNFl8YV/VFZVygsK9V4fiV8LNSunMiq3XbpkSAc+jkjcujaA eycmfKbcxqn5IFlnWtx9qTfy4dSulexW6fPnsRnLSTtCm2XLUGdWFVyITdQ4ccUY3QgG byjacfI9vrP2EP8Yu8yrzxUF6hsrcBr8UgQMmTXYXZY2GaIr4oJ0DdTMSxCRAS8p7enS npiw== MIME-Version: 1.0 X-Received: by 10.194.249.129 with SMTP id yu1mr10166085wjc.10.1374185428221; Thu, 18 Jul 2013 15:10:28 -0700 (PDT) Received: by 10.194.103.41 with HTTP; Thu, 18 Jul 2013 15:10:28 -0700 (PDT) In-Reply-To: <51E84FDA.3010607@reynoldsnet.org> References: <51E73AA9.5030004@reynoldsnet.org> <20130718004854.GC2264@glenbarber.us> <51E765D3.8090801@reynoldsnet.org> <20130718154908.GD1945@glenbarber.us> <51E84FDA.3010607@reynoldsnet.org> Date: Thu, 18 Jul 2013 17:10:28 -0500 Message-ID: Subject: Re: experience with 9.2-PRERELEASE From: Adam Vande More To: John Reynolds Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Glen Barber , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 18 Jul 2013 22:10:29 -0000 On Thu, Jul 18, 2013 at 3:28 PM, John Reynolds wrote: > One person said to fiddle in the BIOS with the USB settings. I went into > the BIOS and disabled "Intel USB 3.0 Mode" support (this is a very new > motherboard with USB 3.0). That fixed the issue! For those curious about > -current, I also tried to install that and it experienced the same USB > problems until I disabled this 3.0 mode. > This is worth pursuing on freebsdf-usb@ or by filing a PR. Only way it gets fixed is if the right people know about it. -- Adam Vande More From owner-freebsd-stable@FreeBSD.ORG Fri Jul 19 04:04:50 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BB00BF3; Fri, 19 Jul 2013 04:04:50 +0000 (UTC) (envelope-from olivier777a7@gmail.com) Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by mx1.freebsd.org (Postfix) with ESMTP id 73D16D4A; Fri, 19 Jul 2013 04:04:50 +0000 (UTC) Received: by mail-qc0-f174.google.com with SMTP id m15so2109913qcq.5 for ; Thu, 18 Jul 2013 21:04:49 -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=/VwWr052W/qjaNDzVlBXPIalwkJVETCK6q/NvH8p57o=; b=mXnFjTZ6k/sNdijpQV+vVpTfYysMyXnZuZvYq8mGEQs43UIX0AML6M7q7K3pCWmci/ mzhJEideaLIpnZwXMh2fSMZnZhU3EJxkyUtTEPLS4Ad/gZX9RQsXvTuCnbVlBUbDalke usQkxMJPk4x9CiXoiZ868EaXZz0mGKJEH/8EonyrsQ6qAVxVvqBcvtIruwy2INcJvqVs jR9UKtwpEf24ykKVQWI9+2Q6pYlOJwKgI3e24J8Uxu+b6Dn1k7G2zq5gxBrUDTOQGqLW iO4vDPSng3ryzs84SM8MsYtjIcLYW12BGCqCZPgDrZYxvZ5gjfGi6HipWIWnlKWVJVVX JEtg== MIME-Version: 1.0 X-Received: by 10.224.65.202 with SMTP id k10mr16754534qai.69.1374206689864; Thu, 18 Jul 2013 21:04:49 -0700 (PDT) Received: by 10.49.97.5 with HTTP; Thu, 18 Jul 2013 21:04:49 -0700 (PDT) Date: Thu, 18 Jul 2013 21:04:49 -0700 Message-ID: Subject: 9.2PRERELEASE ZFS panic in lzjb_compress From: olivier To: "freebsd-stable@freebsd.org" , zfs-devel@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jul 2013 04:04:50 -0000 Hi, Running 9.2-PRERELEASE #19 r253313 I got the following panic Fatal trap 12: page fault while in kernel mode cpuid = 22; apic id = 46 fault virtual address = 0xffffff827ebca30c fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff81983055 stack pointer = 0x28:0xffffffcf75bd60a0 frame pointer = 0x28:0xffffffcf75bd68f0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (zio_write_issue_hig) trap number = 12 panic: page fault cpuid = 22 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a/frame 0xffffffcf75bd5b30 kdb_backtrace() at kdb_backtrace+0x37/frame 0xffffffcf75bd5bf0 panic() at panic+0x1ce/frame 0xffffffcf75bd5cf0 trap_fatal() at trap_fatal+0x290/frame 0xffffffcf75bd5d50 trap_pfault() at trap_pfault+0x211/frame 0xffffffcf75bd5de0 trap() at trap+0x344/frame 0xffffffcf75bd5fe0 calltrap() at calltrap+0x8/frame 0xffffffcf75bd5fe0 --- trap 0xc, rip = 0xffffffff81983055, rsp = 0xffffffcf75bd60a0, rbp = 0xffffffcf75bd68f0 --- lzjb_compress() at lzjb_compress+0x185/frame 0xffffffcf75bd68f0 zio_compress_data() at zio_compress_data+0x92/frame 0xffffffcf75bd6920 zio_write_bp_init() at zio_write_bp_init+0x24b/frame 0xffffffcf75bd6970 zio_execute() at zio_execute+0xc3/frame 0xffffffcf75bd69b0 taskqueue_run_locked() at taskqueue_run_locked+0x74/frame 0xffffffcf75bd6a00 taskqueue_thread_loop() at taskqueue_thread_loop+0x46/frame 0xffffffcf75bd6a20 fork_exit() at fork_exit+0x11f/frame 0xffffffcf75bd6a70 fork_trampoline() at fork_trampoline+0xe/frame 0xffffffcf75bd6a70 --- trap 0, rip = 0, rsp = 0xffffffcf75bd6b30, rbp = 0 --- lzjb_compress+0x185 corresponds to line 85 in 80 cpy = src - offset; 81 if (cpy >= (uchar_t *)s_start && cpy != src && 82 src[0] == cpy[0] && src[1] == cpy[1] && src[2] == cpy[2]) { 83 *copymap |= copymask; 84 for (mlen = MATCH_MIN; mlen < MATCH_MAX; mlen++) 85 if (src[mlen] != cpy[mlen]) 86 break; 87 *dst++ = ((mlen - MATCH_MIN) << (NBBY - MATCH_BITS)) | 88 (offset >> NBBY); 89 *dst++ = (uchar_t)offset; I think it's the first time I've seen this panic. It happened while doing a send/receive. I have two pools with lzjb compression; I don't know which of these pools caused the problem, but one of them was the source of the send/receive. I only have a textdump but I'm happy to try to provide more information that could help anyone look into this. Thanks Olivier From owner-freebsd-stable@FreeBSD.ORG Fri Jul 19 05:32:55 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 27D174C7; Fri, 19 Jul 2013 05:32:55 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.freebsd.org (Postfix) with ESMTP id B44661000; Fri, 19 Jul 2013 05:32:54 +0000 (UTC) Received: from mail3.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.13.6/8.13.6) with ESMTP id r6J5WlEg026951; Fri, 19 Jul 2013 07:32:47 +0200 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail3.siemens.de (8.13.6/8.13.6) with ESMTP id r6J5WlRC001757; Fri, 19 Jul 2013 07:32:47 +0200 Received: (from localhost) by curry.mchp.siemens.de (8.14.7/8.14.7) id r6J5Wlpk009970; Date: Fri, 19 Jul 2013 07:32:47 +0200 From: Andre Albsmeier To: Konstantin Belousov Subject: Re: FreeBSD-9.1: machine reboots during snapshot creation, LORs found Message-ID: <20130719053247.GA72555@bali> References: <20130531122611.GA6607@bali> <201305311051.03157.jhb@freebsd.org> <20130616063942.GA72803@bali> <201306171530.31208.jhb@freebsd.org> <20130704051409.GA22021@bali> <20130704052440.GG91021@kib.kiev.ua> <20130704052659.GA23398@bali> <20130704061550.GI91021@kib.kiev.ua> <20130704142919.GA1798@bali> <20130704172528.GL91021@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130704172528.GL91021@kib.kiev.ua> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.21 (2010-09-15) Cc: "freebsd-stable@freebsd.org" , John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jul 2013 05:32:55 -0000 On Thu, 04-Jul-2013 at 19:25:28 +0200, Konstantin Belousov wrote: > On Thu, Jul 04, 2013 at 04:29:19PM +0200, Andre Albsmeier wrote: > > OK, patch is applied. I will reboot the machine later > > and see what happens tomorrow in the morning. However, > > it might take a few days since the last 2 weeks all was > > fine. > > > > BTW, should this patch be used in general or is it just > > for debugging? My understanding is that it is something > > which could stay in the code... > > Patch is to improve debugging. > > I probably commit it after the issue is closed. Arguments against > the commit is that the change imposes small performance penalty > due to save and restore of the %ebp (I doubt that this is measureable > by any means). Also, arguably, such change should be done for all > functions in support.s, but bcopy() is the hot spot. Thanks to this patch, we (you ;-) were able to track down the problem. So how are we going to deal with this debugging patch itself? My suggestion would be to #ifdef it somehow so on one hand it will be availabe in future (and with bcopy being used a lot probability is high it might help in other places), on the other hand it won't steal cycles during normal use. -Andre From owner-freebsd-stable@FreeBSD.ORG Fri Jul 19 07:05:47 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BCF1BC9C; Fri, 19 Jul 2013 07:05:47 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4C9213EA; Fri, 19 Jul 2013 07:05:47 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r6J75gk4080907; Fri, 19 Jul 2013 10:05:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r6J75gk4080907 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r6J75f62080898; Fri, 19 Jul 2013 10:05:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 19 Jul 2013 10:05:41 +0300 From: Konstantin Belousov To: Andre Albsmeier Subject: Re: FreeBSD-9.1: machine reboots during snapshot creation, LORs found Message-ID: <20130719070541.GH5991@kib.kiev.ua> References: <201305311051.03157.jhb@freebsd.org> <20130616063942.GA72803@bali> <201306171530.31208.jhb@freebsd.org> <20130704051409.GA22021@bali> <20130704052440.GG91021@kib.kiev.ua> <20130704052659.GA23398@bali> <20130704061550.GI91021@kib.kiev.ua> <20130704142919.GA1798@bali> <20130704172528.GL91021@kib.kiev.ua> <20130719053247.GA72555@bali> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jxJZfy9MYHgKPwT/" Content-Disposition: inline In-Reply-To: <20130719053247.GA72555@bali> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: "freebsd-stable@freebsd.org" , John Baldwin X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jul 2013 07:05:47 -0000 --jxJZfy9MYHgKPwT/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 19, 2013 at 07:32:47AM +0200, Andre Albsmeier wrote: > On Thu, 04-Jul-2013 at 19:25:28 +0200, Konstantin Belousov wrote: > > Patch is to improve debugging. > >=20 > > I probably commit it after the issue is closed. Arguments against > > the commit is that the change imposes small performance penalty > > due to save and restore of the %ebp (I doubt that this is measureable > > by any means). Also, arguably, such change should be done for all > > functions in support.s, but bcopy() is the hot spot. >=20 > Thanks to this patch, we (you ;-) were able to track down the problem. > So how are we going to deal with this debugging patch itself? > My suggestion would be to #ifdef it somehow so on one hand it will > be availabe in future (and with bcopy being used a lot probability > is high it might help in other places), on the other hand it won't > steal cycles during normal use. This was already committed as r253328 in HEAD. I dislike the #ifdef, since the stack access is interwinned through all text, making the function forked. --jxJZfy9MYHgKPwT/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJR6OVEAAoJEJDCuSvBvK1BuZkQAIg0+1fbmoREh3A0xE3Ax/oH KbbUA8w5QJf9bRfGOQbe6YP2Ux6E8aO5F9LPgyYpfEnvAO/bmmo94+HK7u5SFoK8 rW4cHASBD78IqsCne8FroNqjjpea/osAsD7HL8dbs8q0bDhYui1JsO0rvDuO59YH ZTuT+jcKu+rvDh2W/hddtL6yMK8HrcJMOpNsMCs2aMKoxTcqpdfSJ9NdlYLdNweA lVW5wT8x5gJ0MHn+oaL6epxMHVhxVLkxwjqT7LKR2acWzdvJ/n6fiMlUUixDWc9N IG12yBjQCaLTKYCtGfJzrmeiPdPKdLulF88lrawTN4W+nCUw1mj9NasoimuMhAmb kuktCcryJ72f0wVIpR8B0+C6FIUl3OSvnviSjbl4QIILPFbICjYfTWni1fty+0n2 hiQ0Vtmtb8fpsMSF4MWflRJ3FN7iz1TV6h+kkk9GaXnn7/O2H0sxnZuVk9S07OK9 u/i9Icoy8z18LYKSRJwS1C8GrXd0EYS5ECS3eggC3wxBg2t2kbGvxFcraT8PWszY m5wci5HZreEIagAl73mEk6ZZ21W8ERAVPY0RKOaje94NU4viDEBMiLlV1A0GsZNp SLzskxHdhOk7FS/3p6OKOfzKUu15Xjcio8+1MXPcbXsLSsMQr21uyXbNJ3oVTD7l AhYkM61rsiSVSOgI5Dxa =FM3Q -----END PGP SIGNATURE----- --jxJZfy9MYHgKPwT/-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 19 08:09:21 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 42B5EB93; Fri, 19 Jul 2013 08:09:21 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id BDEEF8A9; Fri, 19 Jul 2013 08:09:20 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1V05bF-000InB-3t; Fri, 19 Jul 2013 10:59:37 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3 To: Jeremy Chadwick Subject: Re: make buildworld is now 50% slower In-reply-to: <20130707101714.GA51445@icarus.home.lan> References: <20130705145839.GB5449@icarus.home.lan> <20130707101714.GA51445@icarus.home.lan> Comments: In-reply-to Jeremy Chadwick message dated "Sun, 07 Jul 2013 03:17:14 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Jul 2013 10:59:37 +0300 From: Daniel Braniss Message-ID: Cc: "freebsd-stable@freebsd.org Stable" , Dimitry Andric X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jul 2013 08:09:21 -0000 > On Sun, Jul 07, 2013 at 11:50:29AM +0300, Daniel Braniss wrote: > > > On Fri, Jul 05, 2013 at 02:39:00PM +0200, Dimitry Andric wrote: > > > > [redirecting to the correct mailing list, freebsd-stable@ ...] > > > > > > > > On Jul 5, 2013, at 10:53, Daniel Braniss wrote: > > > > > after today's update of 9.1-STABLE I noticed that make build[world|kernel] are > > > > > taking conciderable more time, is it because the upgrade of clang? > > > > > and if so, is the code produced any better? > > > > > > > > > > before: > > > > > buildwordl: 26m4.52s real 2h28m32.12s user 36m6.27s sys > > > > > buildkernel: 7m29.42s real 23m22.22s user 4m26.26s sys > > > > > > > > > > today: > > > > > buildwordl: 34m29.80s real 2h38m9.37s user 37m7.61s sys > > > > > buildkernel: 15m31.52s real 22m59.40s user 4m33.06s sys > > > > > > > > Ehm, your user and sys times are not that much different at all, they > > > > add up to about 5% slower for buildworld, and 1% faster for build kernel. > > > > Are you sure nothing else is running on that machine, eating up CPU time > > > > while you are building? :) > > > > > > > > But yes, clang 3.3 is of course somewhat larger than 3.2. You might > > > > especially notice that, if you are using gcc, which is very slow at > > > > compiling C++. > > > > > > > > In any case, if you do not care about clang, just set WITHOUT_CLANG= in > > > > your /etc/src.conf, and you can shave off some build time. > > > > > > I just built world/kernel (stable/9 r252769) 5 hours ago. Results: > > > > > > time make -j4 buildworld = roughly 21 minutes on my hardware > > > time make -j4 buildkernel = roughly 8 minutes on my hardware > > > > > > > It's been a long time since I saw such numbers, maybe it's time > > to see where time is being spent, I will run it without clang to compare with > > your numbers. > > > > > These numbers are about the norm for me, meaning I do not see a > > > substantial increase in build times. > > > > > > Key point: I do not use/build/grok clang, i.e. WITHOUT_CLANG=true is in > > > my src.conf. But I am aware of the big clang change in r252723. > > > > > > If hardware details are wanted, ask, but I don't think it's relevant to > > > what the root cause is. > > > > > > > from what you are saying, I guess clang is not responsible. > > looking for my Sherlock Holmes hat. > > Some points to those numbers I stated above: > > - System is an Intel Q9550 with 8GB of RAM > > - Single SSD (UFS2+SU+TRIM) is used for root, /usr, /var, /tmp, and swap > > - /usr/src is on ZFS (raidz1 + 3 disks) -- however I got equally small > numbers when it was on the SSD > > - /usr/src is using compression=lz4 (to folks from -fs: yeah, I'm > trying it out to see how much of an impact it has on interactivity. I > can still tell when it kicks in, but it's way, way better than lzjb. > Rather not get into that here) > > - Contents of /etc/src.conf (to give you some idea of what I disable): > > WITHOUT_ATM=true > WITHOUT_BLUETOOTH=true > WITHOUT_CLANG=true > WITHOUT_FLOPPY=true > WITHOUT_FREEBSD_UPDATE=true > WITHOUT_INET6=true > WITHOUT_IPFILTER=true > WITHOUT_IPX=true > WITHOUT_KERBEROS=true > WITHOUT_LIB32=true > WITHOUT_LPR=true > WITHOUT_NDIS=true > WITHOUT_NETGRAPH=true > WITHOUT_PAM_SUPPORT=true > WITHOUT_PPP=true > WITHOUT_SENDMAIL=true > WITHOUT_WIRELESS=true > WITH_OPENSSH_NONE_CIPHER=true > > It's WITHOUT_CLANG that cuts down the buildworld time by a *huge* amount > (I remember when it got introduced, my buildworld jumped up to something > like 40 minutes); the rest probably save a minute or two at most. > > - /etc/make.conf doesn't contain much that's relevant, other than: > > CPUTYPE?=core2 > > # For DTrace; also affects ports > STRIP= > CFLAGS+= -fno-omit-frame-pointer > > - I do some tweaks in /etc/sysctl.conf (mainly vfs.read_min and > vfs.read_max), but I will admit I am not completely sure what those > do quite yet (I just saw the commit from scottl@ a while back talking > about how an increased vfs.read_min helps them at Netflix quite a > lot). I also adjust kern.maxvnodes. > > - Some ZFS ARC settings are adjusted in /boot/loader.conf (I'm playing > with some stuff I read in Andriy Gapon's ZFS PDF), but they definitely > do not have a major impact on the numbers I listed off. > > - I do increase kern.maxdsiz, kern.dfldsiz, and kern.maxssiz in > /boot/loader.conf to 2560M/2560M/256M respectively, but that was mainly > from the days when I ran MySQL and needed a huge userland processes. > > All in all my numbers are low/small because of two things: the SSD, and > WITHOUT_CLANG. > > Hope this gives you somewhere to start/stuff to ponder. > indeed! on my pretty much standard dev machine, PowerEdge R710, X5550 @ 2.67GHz, 16384 MB, root on ufs, the rest is via ZFS, this is what I'm getting for buildworld: with clang 27m32.91s real 2h42m52.82s user 36m20.69s sys without clang 13m24.19s real 1h23m26.52s user 29m5.18s sys on a similar machine but with root via NFS, and /var on ZFS, the numbers are similar: with clang 23m30.92s real 2h9m8.85s user 29m27.84s sys without clang 12m7.53s real 1h7m54.24s user 23m9.78s sys (this host is newer, PowerEdge C6220, E5-2643 0 @ 3.30GHz, 32768 MB) it's still not clear what happened last week, but probably my machine had some runaway process. cheers, danny From owner-freebsd-stable@FreeBSD.ORG Fri Jul 19 13:52:52 2013 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 06D9CBF8; Fri, 19 Jul 2013 13:52:52 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 5F81BB51; Fri, 19 Jul 2013 13:52:51 +0000 (UTC) Received: by mail-lb0-f172.google.com with SMTP id v20so3493511lbc.3 for ; Fri, 19 Jul 2013 06:52:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=bgM3m8esa5/XraltbhB5pSqLrutuTLAVM8S3aIkkBfg=; b=KlZVpCBoP95A/aIPcuUO1JZLZ/2cGbbxpOF25d6Rh1VcVSOMCm1yuqxTu2M1/AMDoQ RehASXurcEUlEyljT67n/Tfv3vzfaEVWEqR9oK1pCtPjwmWpS6ZEhbtADLjvwhesyA31 vhBWIpywJHLKqEmd1MWqI4QEA1w9PFOf1BYW+dGG8q/Vtx88M5POXVhSgH0/I26/1ta6 /3pHrOV3nFUnLUpPlmaEzXrQAcwahHTg46D3hzcIejfN+Nutfxy1zNsRAswbQCGgNAfz Vzq9JjKaAUNezbtogxdb8v9xjeBr1Xyh6klpn6KUN/52IQjq0jlat/EI/0A66WyIjkJW uNKg== X-Received: by 10.112.143.162 with SMTP id sf2mr7072684lbb.1.1374241970326; Fri, 19 Jul 2013 06:52:50 -0700 (PDT) Received: from [192.168.1.139] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPSA id p7sm6145025lbi.15.2013.07.19.06.52.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Jul 2013 06:52:49 -0700 (PDT) Message-ID: <51E944B0.5080409@gmail.com> Date: Fri, 19 Jul 2013 16:52:48 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130710 Thunderbird/17.0.7 MIME-Version: 1.0 To: olivier Subject: Re: 9.2PRERELEASE ZFS panic in lzjb_compress References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org" , zfs-devel@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jul 2013 13:52:52 -0000 19.07.2013 07:04, olivier wrote: > Hi, > Running 9.2-PRERELEASE #19 r253313 I got the following panic > > Fatal trap 12: page fault while in kernel mode > cpuid = 22; apic id = 46 > fault virtual address = 0xffffff827ebca30c > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff81983055 > stack pointer = 0x28:0xffffffcf75bd60a0 > frame pointer = 0x28:0xffffffcf75bd68f0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (zio_write_issue_hig) > trap number = 12 > panic: page fault > cpuid = 22 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a/frame > 0xffffffcf75bd5b30 > kdb_backtrace() at kdb_backtrace+0x37/frame 0xffffffcf75bd5bf0 > panic() at panic+0x1ce/frame 0xffffffcf75bd5cf0 > trap_fatal() at trap_fatal+0x290/frame 0xffffffcf75bd5d50 > trap_pfault() at trap_pfault+0x211/frame 0xffffffcf75bd5de0 > trap() at trap+0x344/frame 0xffffffcf75bd5fe0 > calltrap() at calltrap+0x8/frame 0xffffffcf75bd5fe0 > --- trap 0xc, rip = 0xffffffff81983055, rsp = 0xffffffcf75bd60a0, rbp = > 0xffffffcf75bd68f0 --- > lzjb_compress() at lzjb_compress+0x185/frame 0xffffffcf75bd68f0 > zio_compress_data() at zio_compress_data+0x92/frame 0xffffffcf75bd6920 > zio_write_bp_init() at zio_write_bp_init+0x24b/frame 0xffffffcf75bd6970 > zio_execute() at zio_execute+0xc3/frame 0xffffffcf75bd69b0 > taskqueue_run_locked() at taskqueue_run_locked+0x74/frame 0xffffffcf75bd6a00 > taskqueue_thread_loop() at taskqueue_thread_loop+0x46/frame > 0xffffffcf75bd6a20 > fork_exit() at fork_exit+0x11f/frame 0xffffffcf75bd6a70 > fork_trampoline() at fork_trampoline+0xe/frame 0xffffffcf75bd6a70 > --- trap 0, rip = 0, rsp = 0xffffffcf75bd6b30, rbp = 0 --- > > lzjb_compress+0x185 corresponds to line 85 in > 80 cpy = src - offset; > 81 if (cpy >= (uchar_t *)s_start && cpy != src && > 82 src[0] == cpy[0] && src[1] == cpy[1] && src[2] == cpy[2]) { > 83 *copymap |= copymask; > 84 for (mlen = MATCH_MIN; mlen < MATCH_MAX; mlen++) > 85 if (src[mlen] != cpy[mlen]) > 86 break; > 87 *dst++ = ((mlen - MATCH_MIN) << (NBBY - MATCH_BITS)) | > 88 (offset >> NBBY); > 89 *dst++ = (uchar_t)offset; > > I think it's the first time I've seen this panic. It happened while doing a > send/receive. I have two pools with lzjb compression; I don't know which of > these pools caused the problem, but one of them was the source of the > send/receive. > > I only have a textdump but I'm happy to try to provide more information > that could help anyone look into this. > Thanks > Olivier Oh, I can add to this one. I have a full core dump of the same problem caused by copying large set of files from lzjb compressed pool to lz4 compressed pool. vfs.zfs.recover was set. #1 0xffffffff8039d954 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 #2 0xffffffff8039ddce in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:637 #3 0xffffffff80620a6a in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:879 #4 0xffffffff80620d25 in trap_pfault (frame=0x0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:700 #5 0xffffffff806204f6 in trap (frame=0xffffff821ca43600) at /usr/src/sys/amd64/amd64/trap.c:463 #6 0xffffffff8060a032 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:232 #7 0xffffffff805a9367 in vm_page_alloc (object=0xffffffff80a34030, pindex=16633, req=97) at /usr/src/sys/vm/vm_page.c:1445 #8 0xffffffff8059c42e in kmem_back (map=0xfffffe00010000e8, addr=18446743524021862400, size=16384, flags=) at /usr/src/sys/vm/vm_kern.c:362 #9 0xffffffff8059c2ac in kmem_malloc (map=0xfffffe00010000e8, size=16384, flags=257) at /usr/src/sys/vm/vm_kern.c:313 #10 0xffffffff80595104 in uma_large_malloc (size=, wait=257) at /usr/src/sys/vm/uma_core.c:994 #11 0xffffffff80386b80 in malloc (size=16384, mtp=0xffffffff80ea7c40, flags=0) at /usr/src/sys/kern/kern_malloc.c:492 #12 0xffffffff80c9e13c in lz4_compress (s_start=0xffffff80d0b19000, d_start=0xffffff8159445000, s_len=131072, d_len=114688, n=-2) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/lz4.c:843 #13 0xffffffff80cdde25 in zio_compress_data (c=, src=, dst=0xffffff8159445000, s_len=131072) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio_compress.c:109 #14 0xffffffff80cda012 in zio_write_bp_init (zio=0xfffffe0143a12000) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1107 #15 0xffffffff80cd8ec6 in zio_execute (zio=0xfffffe0143a12000) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1305 #16 0xffffffff803e25e6 in taskqueue_run_locked (queue=0xfffffe00060ca300) at /usr/src/sys/kern/subr_taskqueue.c:312 #17 0xffffffff803e2e38 in taskqueue_thread_loop (arg=) at /usr/src/sys/kern/subr_taskqueue.c:501 #18 0xffffffff8036f40a in fork_exit ( callout=0xffffffff803e2da0 , arg=0xfffffe00060cc3d0, frame=0xffffff821ca43a80) at /usr/src/sys/kern/kern_fork.c:988 #19 0xffffffff8060a56e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:606 I have a full crash dump in case someone wants to look at it. -- Sphinx of black quartz, judge my vow. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 19 15:37:28 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D2BF0274 for ; Fri, 19 Jul 2013 15:37:28 +0000 (UTC) (envelope-from nicolas.roosen@gmail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) by mx1.freebsd.org (Postfix) with ESMTP id 6D6B2E8 for ; Fri, 19 Jul 2013 15:37:28 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id ey16so4554689wid.4 for ; Fri, 19 Jul 2013 08:37:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; bh=enm8yBFpNH5Ve51mludtfE/t7AhY9CsXyinEznyoXtI=; b=TEa5QfdT+AABAIdqVru8I9cdhwvgAJLjFywEZ3xnM8VFd9a50VL0Kbo3fjsnKqPoKt YMaEwqDe5fiXNVN5kuiHremIMVbrSHdMi0qv5nzveEImE0rGRTGN1hSVHm17xwQpHTTp pYC9M2iKZXmSty08Ap/2k2KtEKHuvpEjvDmNOTC7QdgDUU/KoTJ0LJPopwdc7xog19Wk n8J5UkbR0fm9EpFVE/5/SPMtitXI0+7hz78pd3KKtCKDe8lilGFzrqkRNC37prupe5sJ kYdAyZkbXB8k3fbkBgNx6UNnLSz03rT09WgafbQKo4KV2MxrSZsgrKqRXrvUU595vkjn b3CQ== X-Received: by 10.194.121.132 with SMTP id lk4mr12643625wjb.25.1374248246953; Fri, 19 Jul 2013 08:37:26 -0700 (PDT) Received: from [192.168.100.105] (24.172.80.79.rev.sfr.net. [79.80.172.24]) by mx.google.com with ESMTPSA id u7sm43439206wiw.9.2013.07.19.08.37.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Jul 2013 08:37:25 -0700 (PDT) Message-ID: <51E95D31.3060103@gmail.com> Date: Fri, 19 Jul 2013 17:37:21 +0200 From: Nicolas Roosen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Virtio drivers and FreeBSD 9.1 X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 19 Jul 2013 15:37:28 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I have some trouble with the following configuration: - - a Samsung SSD 840 Pro drive of 128 GB - - a Debian Wheezy (7.1) as a KVM host - - multiple Debian 7.1 and FreeBSD 9.1 guests on top of it I have installed the virtio drivers (from http://people.freebsd.org/~kuriyama/virtio/) on all guests, and configured the KVM domain.xml files accordingly. Then I ran some I/O tests using iozone. And as you can see on the results below, there is a big difference between the Debian guest and the FreeBSD guest. Is there any option I could have forgotten to set up in FreeBSD that could explain this difference? On the host server: iozone -s 64M -r 4k -i 0 -i 1 -i 2 random random KB reclen write rewrite read reread read write 65536 4 258532 553602 922146 969225 1523242 530324 On the FreeBSD guest: random random KB reclen write rewrite read reread read write 65536 4 61687 128261 574681 580237 537510 20690 On the Debian guest: random random KB reclen write rewrite read reread read write 65536 4 119604 481670 878853 935172 1328093 473255 Thank you. - -- Vos conversations sont privées, sécurisez-les. Your conversations are private, secure them. https://gpgtools.org or http://gpg4win.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJR6V0qAAoJEIylYwQV0UQcGAgIAJB6PCo6Bc5ewpBPVFf1ZaoU aePblYD2YNgkIRA074WHMFgdudoIzc+U/0IpVSM+N+OvpRwyFXrAW8PuY46Hrdxp Qnh+d9uYFaN8tZqKbpbWvmSziwepHBfozrsIugoP+7fohNAro0/ycpC8EYvuqJI6 JuOqVAOK87fuTXKV0GbwSuhxVvrvaxOTY083QxGoiS0isieEE2DCwFa5y/blmQPe yJTMn45ykbkkskDUWrdNne3lsmM1PFktfyFkslxSuaaNN1Nm+tWKgRDQm4lusRup 3IRy/ZNVI2Gu0/fnqs3Z6nY+LSke1qsKL9WveQEZCZLt/BhkyHCQVlclwGKhZjA= =Kl+S -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 19 17:27:41 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 859C256B for ; Fri, 19 Jul 2013 17:27:41 +0000 (UTC) (envelope-from hartzell@alacrity.alerce.com) Received: from griffon.alerce.com (griffon.alerce.com [206.125.171.162]) by mx1.freebsd.org (Postfix) with ESMTP id 6FAE57F6 for ; Fri, 19 Jul 2013 17:27:41 +0000 (UTC) Received: from griffon.alerce.com (localhost [127.0.0.1]) by griffon.alerce.com (Postfix) with ESMTP id 167A12842A; Fri, 19 Jul 2013 10:27:35 -0700 (PDT) Received: from alacrity.alerce.com (75-149-38-78-SFBA.hfc.comcastbusiness.net [75.149.38.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by griffon.alerce.com (Postfix) with ESMTPSA id D888328424; Fri, 19 Jul 2013 10:27:34 -0700 (PDT) Received: by alacrity.alerce.com (Postfix, from userid 503) id 9F2BB15191B4; Fri, 19 Jul 2013 10:27:31 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20969.30467.601461.313726@gargle.gargle.HOWL> Date: Fri, 19 Jul 2013 10:27:31 -0700 To: Richard Todd Subject: Re: Help with filing a [maybe] ZFS/mmap bug. In-Reply-To: <20130718192624.GA45917@ichotolot.servalan.com> References: <20967.760.95825.310085@gargle.gargle.HOWL> <20968.14003.813473.517439@gargle.gargle.HOWL> <20130718192624.GA45917@ichotolot.servalan.com> X-Mailer: VM 8.2.0b under 24.2.1 (x86_64-apple-darwin) X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org, George Hartzell X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 17:27:41 -0000 Richard Todd writes: > On Thu, Jul 18, 2013 at 11:40:51AM -0700, George Hartzell wrote: > [...] > > [...] > > In my case I'd want to find a particular set of file size, offset, and > > insertion size that triggers the problem and code up a c/c++ equiv. of > > the mmap calls that py-mutagen does. Right? > > Yeah. I'm stuck. Or I've discovered something relevant. Or both. I've identified a slightly simpler test case. I load my handful of test albums, look up single, particular album, and save a particular track. The tagged flac file appears to be valid. Then I reboot. Now the flac file is invalid. It's repeatable, which is useful. Following the lead of your test script I created a new zfs filesystem, mounted it, and had picard save the tagged files there. After exiting picard the files appears to be valid. After unmounting and remounting the filesystem the file *still* appears to be valid. After rebooting, the file *still* appears to be valid. So, it would seem that there's something about the filesystem in which my home directory resides that contributes to the problem. The only obvious thing I saw is that my homedir filesystem has a quota and is 80% full. I tried creating a new, small, zfs filesystem and running the test there. The tagged flac file validates successfully, I do not see the problem (the single file makes the filesystem 88% full). All of the filesystems have automagically created snapshots, so I tried creating a snapshot of the new zfs filesystem before running through the test case. I was still unable to replicate the problem. My spin on your gen4.cpp test case (modified to use the filesize and offset that picard uses) does not generate a difference when run in my home directory followed by a reboot (picard calls insert_bytes twice, using either set of values does not cause a problem). The only difference I see in "zfs get all" output (excluding obvious sizes, etc...) is that the new filesystem has xattr on via the "default", whereas my home directory has it off via "temporary". I'm not sure why it's off. So, I currently have a repeatable, not-too-efficient test case using my home directory. I am unable to repeat the test case using a newly created zfs filesystem (even a very small one) nor am I able to make any headway with Richard's test case. As I described in another thread with Andriy, add INVARIANTS and INVARIANT_SUPPORT into the kernel did not lead to any different behaviour, in fact the experiments described above were run on this new kernel. Any suggestions for a next step? g. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 19 18:59:18 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 46A0BE27 for ; Fri, 19 Jul 2013 18:59:18 +0000 (UTC) (envelope-from hartzell@alacrity.alerce.com) Received: from griffon.alerce.com (griffon.alerce.com [206.125.171.162]) by mx1.freebsd.org (Postfix) with ESMTP id 305B5BFE for ; Fri, 19 Jul 2013 18:59:17 +0000 (UTC) Received: from griffon.alerce.com (localhost [127.0.0.1]) by griffon.alerce.com (Postfix) with ESMTP id 4FE3C2842A; Fri, 19 Jul 2013 11:59:16 -0700 (PDT) Received: from alacrity.alerce.com (75-149-38-78-SFBA.hfc.comcastbusiness.net [75.149.38.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by griffon.alerce.com (Postfix) with ESMTPSA id 2145028424; Fri, 19 Jul 2013 11:59:16 -0700 (PDT) Received: by alacrity.alerce.com (Postfix, from userid 503) id 43B63151AEF0; Fri, 19 Jul 2013 11:59:14 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20969.35970.217377.274868@gargle.gargle.HOWL> Date: Fri, 19 Jul 2013 11:59:14 -0700 To: hartzell@alerce.com Subject: Re: Help with filing a [maybe] ZFS/mmap bug. In-Reply-To: <20969.30467.601461.313726@gargle.gargle.HOWL> References: <20967.760.95825.310085@gargle.gargle.HOWL> <20968.14003.813473.517439@gargle.gargle.HOWL> <20130718192624.GA45917@ichotolot.servalan.com> <20969.30467.601461.313726@gargle.gargle.HOWL> X-Mailer: VM 8.2.0b under 24.2.1 (x86_64-apple-darwin) X-Virus-Scanned: ClamAV using ClamSMTP Cc: Richard Todd , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: hartzell@alerce.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 18:59:18 -0000 George Hartzell writes: > [...] > So, it would seem that there's something about the filesystem in which > my home directory resides that contributes to the problem. > [...] Another data point. I just ran through my test case, saving the tagged and transcoded files into /tmp, a zfs filesystem that was created back when I built up the system (contemporaneously with /usr/home). I was unable to trigger the bug there. As I control, I then ran through the test case, saving a directory in my home directory and triggered the bug. I then created a new directory /usr/home/foo (within the same zfs filesystem as my home directory). I was unable to trigger the bug there either. I then ran through all 165 flac files in the full "test case", saving the results to /usr/home/foo. After exiting picard and running flac -t on all of the files I had errors on many files, including the file in my single-file test case above. I did not even need to reboot. I then ran the single file test case, saving into /usr/foo (as above) and was now able to observe the error after a reboot. I then ran the single file test case (again to make sure I wasn't crazy), saving into /usr/foo (as above) and was now able to observe the error after a reboot. One more control. Create /usr/home/bar. Run single file test case. Reboot. This time I observed an invalid flac. Not sure what this means about the test case above. Sigh. g. From owner-freebsd-stable@FreeBSD.ORG Sat Jul 20 07:15:17 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BD658F8B; Sat, 20 Jul 2013 07:15:17 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4B3257C5; Sat, 20 Jul 2013 07:15:17 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-143-198.lns20.adl6.internode.on.net [118.210.143.198]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id r6K7EvQO027742 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 20 Jul 2013 16:45:03 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Trouble building release with docs From: "Daniel O'Connor" Date: Sat, 20 Jul 2013 16:44:56 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: To: freebsd-doc@freebsd.org X-Mailer: Apple Mail (2.1508) X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-stable stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jul 2013 07:15:17 -0000 Hi, I am trying to do a full (customised) release of 9.1 but I am having = trouble building the docs. If I use NODOC it builds fine, but without = that I get.. [andenes 7:04] /usr/src/release #/usr/bin/time make release = BUILDNAME=3D$BUILDNAME =20 make -C /usr/src/release BUILDNAME=3D9.1-GENESIS obj make -C /usr/src/release BUILDNAME=3D9.1-GENESIS ftp cdrom memstick cd /usr/src/release/doc && make all install clean 'FORMATS=3Dhtml txt' = INSTALL_COMPRESSED=3D'' URLS_ABSOLUTE=3DYES = DOCDIR=3D/usr/obj/usr/src/release/rdoc =3D=3D=3D> en_US.ISO8859-1 (all) =3D=3D=3D> en_US.ISO8859-1/relnotes (all) /usr/bin/grep '^' article.xml > = article.parsed.xml.tmp grep: article.xml: No such file or directory *** [article.parsed.xml] Error code 2 Stop in /usr/src/release/doc/en_US.ISO8859-1/relnotes. *** [all] Error code 1 Stop in /usr/src/release/doc/en_US.ISO8859-1. *** [all] Error code 1 Stop in /usr/src/release/doc. *** [reldoc] Error code 1 Stop in /usr/src/release. *** [release] Error code 1 Stop in /usr/src/release. 0.48 real 0.37 user 0.10 sys There is article.sgml though.. I have installed textproc/docproj and I = can build /usr/docs fine. I have /usr/src r253451 and /usr/doc r42325. I can copy a doc distfile from a 'real' release since I'm not = customising that, but it would be nice to know what I'm doing wrong :) Thanks. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@FreeBSD.ORG Sat Jul 20 13:17:34 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7AB8A8ED; Sat, 20 Jul 2013 13:17:34 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 3FFF9171; Sat, 20 Jul 2013 13:17:34 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6KDHXu7029874; Sat, 20 Jul 2013 07:17:33 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6KDHWHg029871; Sat, 20 Jul 2013 07:17:33 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 20 Jul 2013 07:17:32 -0600 (MDT) From: Warren Block To: "Daniel O'Connor" Subject: Re: Trouble building release with docs In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sat, 20 Jul 2013 07:17:33 -0600 (MDT) Cc: freebsd-doc@freebsd.org, freebsd-stable stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jul 2013 13:17:34 -0000 On Sat, 20 Jul 2013, Daniel O'Connor wrote: > Hi, > I am trying to do a full (customised) release of 9.1 but I am having trouble building the docs. If I use NODOC it builds fine, but without that I get.. > [andenes 7:04] /usr/src/release #/usr/bin/time make release BUILDNAME=$BUILDNAME > make -C /usr/src/release BUILDNAME=9.1-GENESIS obj > make -C /usr/src/release BUILDNAME=9.1-GENESIS ftp cdrom memstick > cd /usr/src/release/doc && make all install clean 'FORMATS=html txt' INSTALL_COMPRESSED='' URLS_ABSOLUTE=YES DOCDIR=/usr/obj/usr/src/release/rdoc > ===> en_US.ISO8859-1 (all) > ===> en_US.ISO8859-1/relnotes (all) > /usr/bin/grep '^' article.xml > article.parsed.xml.tmp > grep: article.xml: No such file or directory > *** [article.parsed.xml] Error code 2 > > Stop in /usr/src/release/doc/en_US.ISO8859-1/relnotes. > *** [all] Error code 1 > > Stop in /usr/src/release/doc/en_US.ISO8859-1. > *** [all] Error code 1 > > Stop in /usr/src/release/doc. > *** [reldoc] Error code 1 > > Stop in /usr/src/release. > *** [release] Error code 1 > > Stop in /usr/src/release. > 0.48 real 0.37 user 0.10 sys > > There is article.sgml though.. I have installed textproc/docproj and I can build /usr/docs fine. What does svn say about that file? % cd /usr/src/release/doc/en_US.ISO8859-1/relnotes/ % svn stat The article.sgml suggests a leftover file from an earlier /usr/src that was not removed before svn checkout. That does not explain why article.xml is missing, though. It is present on my 9-stable and 8-stable checkouts. Maybe a mixed or partial checkout? From owner-freebsd-stable@FreeBSD.ORG Sat Jul 20 14:46:56 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A0F4D910 for ; Sat, 20 Jul 2013 14:46:56 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 0DDF23FD for ; Sat, 20 Jul 2013 14:46:55 +0000 (UTC) Received: from alph.d.allbsd.org (p2049-ipbf1102funabasi.chiba.ocn.ne.jp [122.26.101.49]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r6KEkcPI022701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Jul 2013 23:46:48 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.5/8.14.5) with ESMTP id r6KEka7g049437; Sat, 20 Jul 2013 23:46:38 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sat, 20 Jul 2013 23:46:23 +0900 (JST) Message-Id: <20130720.234623.829852506076930312.hrs@allbsd.org> To: trashcan@odo.in-berlin.de Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) From: Hiroki Sato In-Reply-To: <20130718.123323.1730389945845032580.hrs@allbsd.org> References: <20130712.160358.1330135778606339435.hrs@allbsd.org> <20130718.123323.1730389945845032580.hrs@allbsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart0(Sat_Jul_20_23_46_23_2013_911)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Sat, 20 Jul 2013 23:46:49 +0900 (JST) X-Spam-Status: No, score=-89.1 required=13.0 tests=CONTENT_TYPE_PRESENT, DIRECTOCNDYN,DYN_PBL,QENCPTR2,RCVD_IN_PBL,RCVD_IN_RP_RNBL,SPF_SOFTFAIL, USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jul 2013 14:46:56 -0000 ----Security_Multipart0(Sat_Jul_20_23_46_23_2013_911)-- Content-Type: Multipart/Mixed; boundary="--Next_Part(Sat_Jul_20_23_46_23_2013_121)--" Content-Transfer-Encoding: 7bit ----Next_Part(Sat_Jul_20_23_46_23_2013_121)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hiroki Sato wrote in <20130718.123323.1730389945845032580.hrs@allbsd.org>: hr> Michael Grimm wrote hr> in : hr> hr> tr> On 12.07.2013, at 09:03, Hiroki Sato wrote: hr> tr> hr> tr> > Please let me know if the existing configurations and/or the new hr> tr> > formats do not work. hr> tr> hr> tr> First of all: great work! It is that much easier to deal with aliases, now. hr> tr> hr> tr> There is only one minor issue, if at all: hr> tr> hr> tr> rc.conf: hr> tr> | ifconfig_em0_ipv6="inet6 dead:beef:1111:2222::1 prefixlen 56" hr> tr> | ifconfig_em0_aliases="\ hr> tr> | inet6 dead:beef:1111:2222::2-3 prefixlen 56 \ hr> tr> | inet6 dead:beef:1111:2222::4 prefixlen 56 \ hr> tr> | inet6 dead:beef:1111:2222::5-6/56" hr> tr> hr> tr> ifconfig: hr> tr> | inet6 dead:beef:1111:2222::1 prefixlen 56 hr> tr> | inet6 dead:beef:1111:2222::2 prefixlen 64 hr> tr> | inet6 dead:beef:1111:2222::3 prefixlen 64 hr> tr> | inet6 dead:beef:1111:2222::4 prefixlen 56 hr> tr> | inet6 dead:beef:1111:2222::5 prefixlen 56 hr> tr> | inet6 dead:beef:1111:2222::6 prefixlen 56 hr> tr> hr> tr> Any combination of a range definition (2-3) *and* "prefixlen 56" is ignored hr> tr> whereas a range definition (5-6) *and* "/56" is interpreted as wanted. hr> tr> hr> tr> Well, that combination of a range and "prefix" isn't documented, thus I am hr> tr> not sure if that's an issue or a feature? hr> hr> It seems a bug. Thank you for your report. I am investigating it now. Can you test the attached patch? The old version (in stable/9 now) does not support "address range spec + options" properly and ignore the options part. The attached patch accepts options and treats "netmask" for inet and "prefixlen" in inet6 in a reasonable way so that the specified options do not conflict with the default /NN values. -- Hiroki ----Next_Part(Sat_Jul_20_23_46_23_2013_121)-- Content-Type: Text/X-Patch; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="network.subr.aliases.20130720-1.diff" Index: etc/network.subr =================================================================== --- etc/network.subr (revision 253489) +++ etc/network.subr (working copy) @@ -721,9 +721,14 @@ # ifalias_expand_addr() { + local _af _action - afexists $1 || return - ifalias_expand_addr_$1 $2 $3 + _af=$1 + _action=$2 + shift 2 + + afexists $_af || return + ifalias_expand_addr_$_af $_action $* } # ifalias_expand_addr_inet action addr @@ -731,19 +736,31 @@ # ifalias_expand_addr_inet() { - local _action _arg _cidr _cidr_addr + local _action _arg _cidr _cidr_addr _exargs local _ipaddr _plen _range _iphead _iptail _iplow _iphigh _ipcount local _retstr _c _action=$1 _arg=$2 + shift 2 + _exargs=$* _retstr= - case $_action:$_arg in + case $_action:$_arg:$_exargs in *:*--*) return ;; # invalid - tmp:*) echo $_arg && return ;; # already expanded - tmp:*-*) _action="alias" ;; # to be expanded - *:*-*) ;; # to be expanded - *:*) echo inet $_arg && return ;; # already expanded + tmp:*:*netmask*) # already expanded w/ netmask option + echo ${_arg%/[0-9]*} $_exargs && return + ;; + tmp:*:*) # already expanded w/o netmask option + echo $_arg $_exargs && return + ;; + tmp:*[0-9]-[0-9]*:*) _action="alias" ;; # to be expanded + *:*[0-9]-[0-9]*:*) ;; # to be expanded + *:*:*netmask*) # already expanded w/ netmask option + echo inet ${_arg%/[0-9]*} $_exargs && return + ;; + *:*:*) # already expanded w/o netmask option + echo inet $_arg $_exargs && return + ;; esac for _cidr in $_arg; do @@ -796,7 +813,7 @@ done for _c in $_retstr; do - ifalias_expand_addr_inet $_action $_c + ifalias_expand_addr_inet $_action $_c $_exargs done } @@ -805,20 +822,32 @@ # ifalias_expand_addr_inet6() { - local _action _arg _cidr _cidr_addr + local _action _arg _cidr _cidr_addr _exargs local _ipaddr _plen _ipleft _ipright _iplow _iphigh _ipcount local _ipv4part local _retstr _c _action=$1 _arg=$2 + shift 2 + _exargs=$* _retstr= - case $_action:$_arg in - *:*--*) return ;; # invalid - tmp:*) echo $_arg && return ;; - tmp:*-*) _action="alias" ;; - *:*-*) ;; - *:*) echo inet6 $_arg && return ;; + case $_action:$_arg:$_exargs in + *:*--*:*) return ;; # invalid + tmp:*:*prefixlen*) # already expanded w/ prefixlen option + echo ${_arg%/[0-9]*} $_exargs && return + ;; + tmp:*:*) # already expanded w/o prefixlen option + echo $_arg $_exargs && return + ;; + tmp:*[0-9a-zA-Z]-[0-9a-zA-Z]*:*)_action="alias" ;;# to be expanded + *:*[0-9a-zA-Z]-[0-9a-zA-Z]*:*) ;; # to be expanded + *:*:*prefixlen*) # already expanded w/ prefixlen option + echo inet6 ${_arg%/[0-9]*} $_exargs && return + ;; + *:*:*) # already expanded w/o prefixlen option + echo inet6 $_arg $_exargs && return + ;; esac for _cidr in $_arg; do @@ -872,7 +901,7 @@ fi for _c in $_retstr; do - ifalias_expand_addr_inet6 $_action $_c + ifalias_expand_addr_inet6 $_action $_c $_exargs done else # v4mapped/v4compat should handle as an IPv4 alias @@ -888,7 +917,7 @@ _retstr=`ifalias_expand_addr_inet \ tmp ${_ipv4part}${_plen:+/}${_plen}` for _c in $_retstr; do - ifalias_expand_addr_inet $_action $_c + ifalias_expand_addr_inet $_action $_c $_exargs done fi done ----Next_Part(Sat_Jul_20_23_46_23_2013_121)---- ----Security_Multipart0(Sat_Jul_20_23_46_23_2013_911)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlHqor8ACgkQTyzT2CeTzy1SjQCgkDjlVNixQRS34lwUjrIcBwET k/kAn3JZfZIz0kkswVa8LJJz3h8ZzaBU =UinY -----END PGP SIGNATURE----- ----Security_Multipart0(Sat_Jul_20_23_46_23_2013_911)---- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 20 16:14:17 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C6DB155D; Sat, 20 Jul 2013 16:14:17 +0000 (UTC) (envelope-from trashcan@odo.in-berlin.de) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [91.121.60.26]) by mx1.freebsd.org (Postfix) with ESMTP id 92A75A21; Sat, 20 Jul 2013 16:14:17 +0000 (UTC) Received: from sulu.fritz.box (p3EE2F8CF.dip0.t-ipconnect.de [62.226.248.207]) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 3byDfs5HY8zLP8; Sat, 20 Jul 2013 18:14:13 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) From: Michael Grimm In-Reply-To: <20130720.234623.829852506076930312.hrs@allbsd.org> Date: Sat, 20 Jul 2013 18:14:12 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <5C2419E4-D5B7-4F1A-AED0-90EF7330503C@odo.in-berlin.de> References: <20130712.160358.1330135778606339435.hrs@allbsd.org> <20130718.123323.1730389945845032580.hrs@allbsd.org> <20130720.234623.829852506076930312.hrs@allbsd.org> To: Hiroki Sato X-Mailer: Apple Mail (2.1508) Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jul 2013 16:14:17 -0000 On 20.07.2013, at 16:46, Hiroki Sato wrote: > Hiroki Sato wrote in = <20130718.123323.1730389945845032580.hrs@allbsd.org>: > hr> Michael Grimm wrote > hr> in : > hr> > hr> tr> On 12.07.2013, at 09:03, Hiroki Sato wrote: > hr> tr> > hr> tr> > Please let me know if the existing configurations and/or the = new > hr> tr> > formats do not work. > hr> tr> > hr> tr> First of all: great work! It is that much easier to deal with = aliases, now. > hr> tr> > hr> tr> There is only one minor issue, if at all: > hr> tr> > hr> tr> rc.conf: > hr> tr> | ifconfig_em0_ipv6=3D"inet6 dead:beef:1111:2222::1 prefixlen = 56" > hr> tr> | ifconfig_em0_aliases=3D"\ > hr> tr> | inet6 dead:beef:1111:2222::2-3 prefixlen 56 \ > hr> tr> | inet6 dead:beef:1111:2222::4 prefixlen 56 \ > hr> tr> | inet6 dead:beef:1111:2222::5-6/56" > hr> tr> > hr> tr> ifconfig: > hr> tr> | inet6 dead:beef:1111:2222::1 prefixlen 56 > hr> tr> | inet6 dead:beef:1111:2222::2 prefixlen 64 > hr> tr> | inet6 dead:beef:1111:2222::3 prefixlen 64 > hr> tr> | inet6 dead:beef:1111:2222::4 prefixlen 56 > hr> tr> | inet6 dead:beef:1111:2222::5 prefixlen 56 > hr> tr> | inet6 dead:beef:1111:2222::6 prefixlen 56 > hr> tr> > hr> tr> Any combination of a range definition (2-3) *and* "prefixlen = 56"is ignored > hr> tr> whereas a range definition (5-6) *and* "/56" is interpreted as = wanted. > hr> tr> > hr> tr> Well, that combination of a range and "prefix" isn't = documented, thus I am > hr> tr> not sure if that's an issue or a feature? > hr> > hr> It seems a bug. Thank you for your report. I am investigating = it now. >=20 > Can you test the attached patch? The old version (in stable/9 now) > does not support "address range spec + options" properly and ignore > the options part. >=20 > The attached patch accepts options and treats "netmask" for inet and > "prefixlen" in inet6 in a reasonable way so that the specified > options do not conflict with the default /NN values. I can confirm that your patch is working for my examples used before.=20 Now, a range definition and "prefixlen 56" is recognized properly: ifconfig: | inet6 dead:beef:1111:2222::2 prefixlen 56=20 | inet6 dead:beef:1111:2222::3 prefixlen 56=20 | inet6 dead:beef:1111:2222::4 prefixlen 56=20 | inet6 dead:beef:1111:2222::5 prefixlen 56=20 | inet6 dead:beef:1111:2222::6 prefixlen 56=20 Thanks and with kind regards, Michael From owner-freebsd-stable@FreeBSD.ORG Sat Jul 20 17:01:33 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 098FDDAC for ; Sat, 20 Jul 2013 17:01:33 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 77199B6A for ; Sat, 20 Jul 2013 17:01:32 +0000 (UTC) Received: from alph.d.allbsd.org (p2049-ipbf1102funabasi.chiba.ocn.ne.jp [122.26.101.49]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r6KH1G3a036238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Jul 2013 02:01:26 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.5/8.14.5) with ESMTP id r6KH1FSe050924; Sun, 21 Jul 2013 02:01:16 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sun, 21 Jul 2013 02:01:06 +0900 (JST) Message-Id: <20130721.020106.2296886900507045616.hrs@allbsd.org> To: trashcan@odo.in-berlin.de Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) From: Hiroki Sato In-Reply-To: <5C2419E4-D5B7-4F1A-AED0-90EF7330503C@odo.in-berlin.de> References: <20130718.123323.1730389945845032580.hrs@allbsd.org> <20130720.234623.829852506076930312.hrs@allbsd.org> <5C2419E4-D5B7-4F1A-AED0-90EF7330503C@odo.in-berlin.de> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Sun_Jul_21_02_01_06_2013_537)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Sun, 21 Jul 2013 02:01:26 +0900 (JST) X-Spam-Status: No, score=-89.3 required=13.0 tests=CONTENT_TYPE_PRESENT, DIRECTOCNDYN,DYN_PBL,RCVD_IN_PBL,RCVD_IN_RP_RNBL,SPF_SOFTFAIL, USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org Cc: freebsd-stable@FreeBSD.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jul 2013 17:01:33 -0000 ----Security_Multipart(Sun_Jul_21_02_01_06_2013_537)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Michael Grimm wrote in <5C2419E4-D5B7-4F1A-AED0-90EF7330503C@odo.in-berlin.de>: tr> On 20.07.2013, at 16:46, Hiroki Sato wrote: tr> > Hiroki Sato wrote in <20130718.123323.1730389945845032580.hrs@allbsd.org>: tr> > tr> > Can you test the attached patch? The old version (in stable/9 now) tr> > does not support "address range spec + options" properly and ignore tr> > the options part. tr> > tr> > The attached patch accepts options and treats "netmask" for inet and tr> > "prefixlen" in inet6 in a reasonable way so that the specified tr> > options do not conflict with the default /NN values. tr> tr> I can confirm that your patch is working for my examples used before. tr> tr> Now, a range definition and "prefixlen 56" is recognized properly: Thank you. Committed as r253505 and will be merged to stable/9. -- Hiroki ----Security_Multipart(Sun_Jul_21_02_01_06_2013_537)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlHqwlIACgkQTyzT2CeTzy0MowCfU+jDD+rx6ng76xs8wpFiAp94 RHYAnisDOX/D5ZPCpG09/oFjujhs/tcZ =Y4Hl -----END PGP SIGNATURE----- ----Security_Multipart(Sun_Jul_21_02_01_06_2013_537)---- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 20 17:11:52 2013 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D1AD8149; Sat, 20 Jul 2013 17:11:52 +0000 (UTC) (envelope-from trashcan@odo.in-berlin.de) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [91.121.60.26]) by mx1.freebsd.org (Postfix) with ESMTP id 9C5DCBDE; Sat, 20 Jul 2013 17:11:52 +0000 (UTC) Received: from sulu.fritz.box (p3EE2F8CF.dip0.t-ipconnect.de [62.226.248.207]) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 3byFxM6nJNzLVD; Sat, 20 Jul 2013 19:11:51 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: ipv6_addrs_IF aliases in rc.conf(5) From: Michael Grimm In-Reply-To: <20130721.020106.2296886900507045616.hrs@allbsd.org> Date: Sat, 20 Jul 2013 19:11:50 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <48537E80-58DE-43FF-BAE9-B7D2E58C8D9E@odo.in-berlin.de> References: <20130718.123323.1730389945845032580.hrs@allbsd.org> <20130720.234623.829852506076930312.hrs@allbsd.org> <5C2419E4-D5B7-4F1A-AED0-90EF7330503C@odo.in-berlin.de> <20130721.020106.2296886900507045616.hrs@allbsd.org> To: Hiroki Sato X-Mailer: Apple Mail (2.1508) Cc: "freebsd-stable@FreeBSD.org" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jul 2013 17:11:52 -0000 On 20.07.2013, at 19:01, Hiroki Sato wrote: > Michael Grimm wrote in = <5C2419E4-D5B7-4F1A-AED0-90EF7330503C@odo.in-berlin.de>: > tr> Now, a range definition and "prefixlen 56" is recognized properly: >=20 > Thank you. Well, actually, we do have to thank you! > Committed as r253505 and will be merged to stable/9. Great news and with kind regards, Michael From owner-freebsd-stable@FreeBSD.ORG Sat Jul 20 22:37:12 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A97A9B34; Sat, 20 Jul 2013 22:37:12 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 34D6585D; Sat, 20 Jul 2013 22:37:11 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-143-198.lns20.adl6.internode.on.net [118.210.143.198]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id r6KMaua7075578 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 21 Jul 2013 08:07:03 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: Trouble building release with docs Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: Date: Sun, 21 Jul 2013 08:06:56 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: <1636FC68-C225-492C-9599-26CA25A800AC@gsoft.com.au> References: To: Warren Block X-Mailer: Apple Mail (2.1508) X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-doc@freebsd.org, freebsd-stable stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 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, 20 Jul 2013 22:37:12 -0000 On 20/07/2013, at 22:47, Warren Block wrote: >> There is article.sgml though.. I have installed textproc/docproj and = I can build /usr/docs fine. >=20 > What does svn say about that file? >=20 > % cd /usr/src/release/doc/en_US.ISO8859-1/relnotes/ > % svn stat ? article.parsed.xml.tmp > The article.sgml suggests a leftover file from an earlier /usr/src = that was not removed before svn checkout. That does not explain why = article.xml is missing, though. It is present on my 9-stable and = 8-stable checkouts. Maybe a mixed or partial checkout? I got a response on IRC, apparently my docproj port is too new to build = the sgml release docs. I think I'll just skip it for now, none of the documentation there is of = interest to me anyway. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C