From owner-freebsd-stable@freebsd.org Sun Nov 1 09:34:22 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88B06A231FF; Sun, 1 Nov 2015 09:34:22 +0000 (UTC) (envelope-from andre@fbsd.ata.myota.org) Received: from mail.myota.org (mail.myota.org [85.10.206.105]) by mx1.freebsd.org (Postfix) with ESMTP id 35C8D1DC5; Sun, 1 Nov 2015 09:34:21 +0000 (UTC) (envelope-from andre@fbsd.ata.myota.org) Received: from x55b58667.dyn.telefonica.de (x55b58667.dyn.telefonica.de [85.181.134.103]) (authenticated bits=128) by mail.myota.org (8.15.2/8.15.2) with ESMTPA id tA19VGs5052335; Sun, 1 Nov 2015 10:31:18 +0100 (CET) (envelope-from andre@fbsd.ata.myota.org) Received: from stationary.client ([192.168.128.2]) by gate.local (8.15.2/8.15.2) with ESMTP id tA19VGUn048838; Sun, 1 Nov 2015 10:31:16 +0100 (CET) (envelope-from andre@fbsd.ata.myota.org) Received: from submit.client ([127.0.0.1]) by voyager.local (8.15.2/8.15.2) with ESMTP id tA19VGOC005493; Sun, 1 Nov 2015 10:31:16 +0100 (CET) (envelope-from andre@fbsd.ata.myota.org) Received: (from user@localhost) by voyager.local (8.15.2/8.15.2/Submit) id tA19VG7N005492; Sun, 1 Nov 2015 10:31:16 +0100 (CET) (envelope-from andre@fbsd.ata.myota.org) Date: Sun, 1 Nov 2015 10:31:16 +0100 From: Andre Albsmeier To: Mark Martinec Cc: freebsd-stable@freebsd.org, current@freebsd.org, andre@fbsd.ata.myota.org Subject: Re: Segmentation fault running ntpd Message-ID: <20151101093116.GA5457@voyager> References: <20150718120956.GC1155@albert.catwhisker.org> <86pozwbvds.fsf@desk.des.no> <20151030113449.GF13438@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Echelon: fraud, FBI, United, USCODE, PGP X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Not delayed on 85.10.206.105, ACL: AUTH(59), Origin: DE, OS: FreeBSD 9.x or newer X-Greylist: Not delayed on 192.168.128.1, ACL: RFC_Nets(54), Origin: , OS: unknown X-Virus-Scanned: clamav-milter 0.98.7 at colo X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 01 Nov 2015 09:34:22 -0000 On Fri, 30-Oct-2015 at 19:47:59 +0100, Mark Martinec wrote: > Not sure if it's the same issue, but it sure looks like it is. > > I have upgraded a couple of hosts (amd64) from 10.2-RELEASE-p5 > to 10.2-RELEASE-p6, i.e. the freebsd-upgrade essentially just > replaced the /usr/sbin/ntpd with a new one; then I restarted > the ntpd. > > On all host but one this was successful: the new ntpd starts > fine and works normally. But on one of these machines the > ntpd process immediately crashes with SIGSEGV. That machine > has an Intel Xeon cpu. It is not apparent to me in what way > this machine differs from others, I'll add my observations here: I am using an ntp.conf with a single server entry: server ntp.some.domain.org ntp.some.domain.org is a CNAME pointing to gate.some.domain.org and the latter contains an A record pointing to 192.168.128.1. After updating 9.3-STABLE to the latest version (one which includes ntp 4.2.8p4), ntpd crashes: Nov 1 09:38:38 voyager kernel: pid 4443 (ntpd), uid 0: exited on signal 11 This happens in line 871 of ntpd.c where mlockall() is called: && 0 != mlockall(MCL_CURRENT|MCL_FUTURE)) It does NOT crash with MCL_FUTURE only. It does crash with MCL_CURRENT only. When adding rlimit memlock -1 to ntpd.conf it does NOT crash (as mlockall() won't be called anymore). When specifying the IP address (192.168.128.1) as the server it does NOT crash. When specifying gate.some.domain.org as the server it also does NOT crash. tcpdump shows in this case: 09:49:59.542310 IP 192.168.128.2.21102 > 192.168.128.1.53: 7639+ A? gate.some.domain.org. (41) 09:49:59.542578 IP 192.168.128.1.53 > 192.168.128.2.21102: 7639* 1/1/0 A 192.168.128.1 (71) 09:49:59.542612 IP 192.168.128.2.52455 > 192.168.128.1.53: 42047+ AAAA? gate.some.domain.org. (41) 09:49:59.542792 IP 192.168.128.1.53 > 192.168.128.2.52455: 42047* 0/1/0 (88) When reverting the server entry back to ntp.some.domain.org it crashes and tcpdump shows: 09:36:05.172552 IP 192.168.128.2.17836 > 192.168.128.1.53: 49768+ A? ntp.some.domain.org. (40) 09:36:05.173320 IP 192.168.128.1.53 > 192.168.128.2.17836: 49768* 2/1/0 CNAME gate.some.domain.org., A 192.168.128.1 (89) 09:36:05.173361 IP 192.168.128.2.22611 > 192.168.128.1.53: 63808+ AAAA? ntp.some.domain.org. (40) 09:36:05.173595 IP 192.168.128.1.53 > 192.168.128.2.22611: 63808* 1/1/0 CNAME gate.some.domain.org. (106) The probability for crashing increases with the speed and the number of cores of the machine: On my old single-core Pentiums it never crashes, on my quad-cores i7-3770K it always crashes. The (asynchronous) resolving of the names start in line 3876 of ntp_config.c: getaddrinfo_sometime(curr_peer->addr->address, If we put the mlockall() call directly before this line, the crash is gone. Maybe you want to play around with rlimit, CNAMES, IPs and so on... -Andre Anyone else seeing this? > 2015-10-30 12:34, je David Wolfskill napisal > > On Fri, Oct 30, 2015 at 09:42:07AM +0100, Dag-Erling Smørgrav wrote: > >> David Wolfskill writes: > >> > ... > >> > bound to 172.17.1.245 -- renewal in 43200 seconds. > >> > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped) > >> > Starting Network: lo0 em0 iwn0 lagg0. > >> > ... > >> > >> Did you find a solution? I'm wondering if the ntpd problems people > >> are > >> reporting on freebsd-security@ are related. I vaguely recall hearing > >> that this had been traced to a pthread bug, but can't find anything > >> about it in commit logs or mailing list archives. > >> .... > > > > I don't recall finding "a solution" per se; that said, I also don't > > recall seeing an occurrence of the above for enough time that I'm not > > sure when I sent that message. :-} > > > > As a reality check: > > > > g1-252(11.0-C)[1] ls -lT /*.core > > -rw-r--r-- 1 root wheel 13783040 Aug 18 04:19:03 2015 /ntpd.core > > g1-252(11.0-C)[2] > > > > So -- among other points -- my last sighting of whatever was causing > > that was the day I built: > > > > FreeBSD 11.0-CURRENT #157 r286880M/286880:1100079: Tue Aug 18 > > 04:45:25 PDT 2015 > > root@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 > > > > Note that the machines where I run head get updated daily (unless > > there's enough of a problem with head that I can't build it or can't > > boot it (and I'm unable to circumvent the issue within a reasonable > > time)) -- and while I do attempt to run ntpd on the machines, the above > > failure is more "annoying" than "crippling" in my particular case. > > > > And I'm presently running: > > > > FreeBSD 11.0-CURRENT #227 r290138M/290138:1100084: Thu Oct 29 > > 05:12:58 PDT 2015 > > root@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 > > > > and building head @r290190 as I type. > > > > And FWIW, I *suspect* that one of the issues involved (in my case) > > was a ... lack of determinism ... in events involving getting the > > (wireless) network connectivity into a usable state as part of the > > initial transition to multi-user mode. (I only have evidence at > > the moment of the issue on my laptop; my build machine, which only > > uses a wired NIC, has no /ntpd.core file. It and my laptop are updated > > pretty much in lock-step; it runs a completely GENERIC kernel, while > > the laptop runs a modestly customized one based on GENERIC.) > > > > Peace, > > david > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Micro$oft: Which virus will you get today? From owner-freebsd-stable@freebsd.org Tue Nov 3 09:12:03 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84FC6A1E2FD for ; Tue, 3 Nov 2015 09:12:03 +0000 (UTC) (envelope-from nicolas.gilles@gmail.com) Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B5801E71 for ; Tue, 3 Nov 2015 09:12:03 +0000 (UTC) (envelope-from nicolas.gilles@gmail.com) Received: by vkex70 with SMTP id x70so5511271vke.3 for ; Tue, 03 Nov 2015 01:12:02 -0800 (PST) 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 :content-type:content-transfer-encoding; bh=7Cftp/DnY7mcJwJfYC7vfMxs6e+hEqLn5EILhlQ+CQw=; b=RW1LHm4AQjenjzJcsXm37CaOqAIklPcYo8dacduDDOI3HiBWspb9kYHH/xMPHwxo64 0s52xUNnnepTQ3fF2ZKGmiZayuH515/fBcQsVt8AvmjNHr3+MSoDfqFMKm/6AdY3FOTS jGQBP+cU5mmkDOH/hG5DHMZXdTE1uMFZ0NDKNvCTkJ7vB1b5EDKWCyoZgCHg2qZwWlv7 tu+XpdRxxarPZKSKi2Ffe0zk/pPBzmLjeetQiiULPFY3GqkGMB0HerfRt6B0zPcmh2Sy I5eCxxKlAykKgpgUTBUogSsrtqERkoz9ZHOgGAUqhBm1IYFGRJDGrRHnDAtEte5wBNb1 RstQ== MIME-Version: 1.0 X-Received: by 10.31.3.75 with SMTP id 72mr18255400vkd.3.1446541922319; Tue, 03 Nov 2015 01:12:02 -0800 (PST) Received: by 10.31.106.199 with HTTP; Tue, 3 Nov 2015 01:12:02 -0800 (PST) In-Reply-To: <563263ED.1070402@multiplay.co.uk> References: <449F8F4D-425D-46B5-BB9C-BE5A0CD11C55@smkelly.org> <563263ED.1070402@multiplay.co.uk> Date: Tue, 3 Nov 2015 10:12:02 +0100 Message-ID: Subject: Re: ZFS, SSDs, and TRIM performance From: Nicolas Gilles To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 03 Nov 2015 09:12:03 -0000 Not sure about the Samsung XS1715, but lots of SSDs seem to suck at large amounts of TRIM in general leading a "let me pause everything for a while" symptom. In fact I think there is work in ZFS to make TRIMs work better, and to throttle them in case large amounts are freed to avoid this kind of starvation. -- Nicolas On Thu, Oct 29, 2015 at 7:22 PM, Steven Hartland wrote: > If you running NVMe, are you running a version which has this: > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D285767 > > I'm pretty sure 10.2 does have that, so you should be good, but best to > check. > > Other questions: > 1. What does "gstat -d -p" show during the stalls? > 2. Do you have any other zfs tuning in place? > > On 29/10/2015 16:54, Sean Kelly wrote: >> >> Me again. I have a new issue and I=E2=80=99m not sure if it is hardware = or >> software. I have nine servers running 10.2-RELEASE-p5 with Dell OEM=E2= =80=99d >> Samsung XS1715 NVMe SSDs. They are paired up in a single mirrored zpool = on >> each server. They perform great most of the time. However, I have a prob= lem >> when ZFS fires off TRIMs. Not during vdev creation, but like if I delete= a >> 20GB snapshot. >> >> If I destroy a 20GB snapshot or delete large files, ZFS fires off tons o= f >> TRIMs to the disks. I can see the kstat.zfs.misc.zio_trim.success and >> kstat.zfs.misc.zio_trim.bytes sysctls skyrocket. While this is happening= , >> any synchronous writes seem to block. For example, we=E2=80=99re running= PostgreSQL >> which does fsync()s all the time. While these TRIMs happen, Postgres jus= t >> hangs on writes. This causes reads to block due to lock contention as we= ll. >> >> If I change sync=3Ddisabled on my tank/pgsql dataset while this is >> happening, it unblocks for the most part. But obviously this is not an i= deal >> way to run PostgreSQL. >> >> I=E2=80=99m working with my vendor to get some Intel SSDs to test, but a= ny ideas >> if this could somehow be a software issue? Or does the Samsung XS1715 ju= st >> suck at TRIM and SYNC? >> >> We=E2=80=99re thinking of just setting the vfs.zfs.trim.enabled=3D0 tuna= ble for now >> since WAL segment turnover actually causes TRIM operations a lot, but >> unfortunately this is a reboot. But disabling TRIM does seem to fix the >> issue on other servers I=E2=80=99ve tested with the same hardware config= . >> > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://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 Nov 3 09:57:25 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E38C1A23262 for ; Tue, 3 Nov 2015 09:57:25 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 76168175A for ; Tue, 3 Nov 2015 09:57:24 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wicll6 with SMTP id ll6so7781655wic.1 for ; Tue, 03 Nov 2015 01:57:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay_co_uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-type:content-transfer-encoding; bh=ZYUoe6kMa+qCyNVlT8LBkZPAUGgwAq5Iv/PYM0k8FQw=; b=st8d4nbxl/JOE9mXhKUdU/WsxwxIxCxfbpXzui3rR8a/NIbQxLnVWWw5XFyLJkVHTj YjqjGxMxuNTGxxpE1aLu+dmURm2FoYxeea412WJ4iV/LrtyMtqRh4O+b5M/DaHVTko3I IntPJ6zyukCx5n8iHAD8kMLH+zQSSi8dAJ8aVjGzmp8M5rzK1dVjk72iBNgv3PBtSHhM 7JVAAzO5IXa2sMRLqun6jYovyifUKyPQhoh+r5W5U+uH7JFvYNSsdHXkF4411Oq9fpfE 41tDFOivMhqQriJsnBFO1fRjA6m5zEF0oJYFwe9zPzqXW3DTmlAWA1LsLXvvCadyoY8m EttA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=ZYUoe6kMa+qCyNVlT8LBkZPAUGgwAq5Iv/PYM0k8FQw=; b=g3wNZUQHMfYOvSrv82iIqV6IjKYFVZrrHlcXEvdZ6/SWDaabKPfMEEzcaCCugdlcNR XYIROdSZLy4OVtDazkH7XmvBAGSxIfYjBoxvbHFTcc4o3/jWGT3n9u0gl4zC9xaTi65h 0vimmUqrAD/ca1iVweSQjfamnRjOfMSfGvvFZfuyn9RgrxiVjPdum3+VxX6/uKre47EU QZJ8f1j9hGs18JRx1vXk/qD14rJNBnCPlBN3VqnTcvn/SYoVAmI5Xu7DmOF5kJ47Rth4 R6AjgAEIcZdODUYK96/QP84OyXnh91P34+YBmAhn4iqjFym0XRQM542c4G5Qz35/jMhG EHmw== X-Gm-Message-State: ALoCoQl6WMLa8pJYx9xKZj9XnX17fqUPGsLwQDnn1+wwvFU5Cl6FAC+okHbkHYXicSsaupZlEZIp X-Received: by 10.194.142.166 with SMTP id rx6mr28418171wjb.54.1446544643123; Tue, 03 Nov 2015 01:57:23 -0800 (PST) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id 199sm22420556wml.22.2015.11.03.01.57.21 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Nov 2015 01:57:21 -0800 (PST) Subject: Re: ZFS, SSDs, and TRIM performance To: freebsd-stable@freebsd.org References: <449F8F4D-425D-46B5-BB9C-BE5A0CD11C55@smkelly.org> <563263ED.1070402@multiplay.co.uk> From: Steven Hartland Message-ID: <56388502.5080809@multiplay.co.uk> Date: Tue, 3 Nov 2015 09:57:22 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 03 Nov 2015 09:57:26 -0000 This is something we've already done in FreeBSD, both myself and a others have iterated a few times on this very thing. There's currently nothing outstanding that I'm aware so its important to capture the details as people experience them to see if there is any more work to do in this area. On 03/11/2015 09:12, Nicolas Gilles wrote: > Not sure about the Samsung XS1715, but lots of SSDs seem to suck at > large amounts of TRIM in general leading a "let me pause everything > for a while" symptom. In fact I think there is work in ZFS to make > TRIMs work better, and to throttle them in case large amounts are > freed to avoid this kind of starvation. > > -- Nicolas > > > On Thu, Oct 29, 2015 at 7:22 PM, Steven Hartland > wrote: >> If you running NVMe, are you running a version which has this: >> https://svnweb.freebsd.org/base?view=revision&revision=285767 >> >> I'm pretty sure 10.2 does have that, so you should be good, but best to >> check. >> >> Other questions: >> 1. What does "gstat -d -p" show during the stalls? >> 2. Do you have any other zfs tuning in place? >> >> On 29/10/2015 16:54, Sean Kelly wrote: >>> Me again. I have a new issue and I’m not sure if it is hardware or >>> software. I have nine servers running 10.2-RELEASE-p5 with Dell OEM’d >>> Samsung XS1715 NVMe SSDs. They are paired up in a single mirrored zpool on >>> each server. They perform great most of the time. However, I have a problem >>> when ZFS fires off TRIMs. Not during vdev creation, but like if I delete a >>> 20GB snapshot. >>> >>> If I destroy a 20GB snapshot or delete large files, ZFS fires off tons of >>> TRIMs to the disks. I can see the kstat.zfs.misc.zio_trim.success and >>> kstat.zfs.misc.zio_trim.bytes sysctls skyrocket. While this is happening, >>> any synchronous writes seem to block. For example, we’re running PostgreSQL >>> which does fsync()s all the time. While these TRIMs happen, Postgres just >>> hangs on writes. This causes reads to block due to lock contention as well. >>> >>> If I change sync=disabled on my tank/pgsql dataset while this is >>> happening, it unblocks for the most part. But obviously this is not an ideal >>> way to run PostgreSQL. >>> >>> I’m working with my vendor to get some Intel SSDs to test, but any ideas >>> if this could somehow be a software issue? Or does the Samsung XS1715 just >>> suck at TRIM and SYNC? >>> >>> We’re thinking of just setting the vfs.zfs.trim.enabled=0 tunable for now >>> since WAL segment turnover actually causes TRIM operations a lot, but >>> unfortunately this is a reboot. But disabling TRIM does seem to fix the >>> issue on other servers I’ve tested with the same hardware config. >>> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://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 Nov 3 15:20:02 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51631A25F03 for ; Tue, 3 Nov 2015 15:20:02 +0000 (UTC) (envelope-from haramrae@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD34D17A2 for ; Tue, 3 Nov 2015 15:20:01 +0000 (UTC) (envelope-from haramrae@gmail.com) Received: by wmll128 with SMTP id l128so90000814wml.0 for ; Tue, 03 Nov 2015 07:20:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=a4v9DnFagqohEsVI2Rf7nls8hwPtfif7uXAGtrxHCCM=; b=rdaVwmIjxieiOO+08Q2/P9YIDvNumeTByIMHBLfJpwPSIN+CrakYc/L0917FTHgXLP pI8V8FgDrTfbvR3Fzx6VL8axUD/rxpVd05Mi3I3ICaQkoqIpZEns2CjWzMamBjXChEoc MfTyVOleoBbKlIZOdRV6FKGkNBZ3Dyz9etdXZKmjWw6RnZyH68PXfzqoUp+XhV1TveeP kutukSO+tmhK5y+wNpEI527itNXng1SN1IxTvaGSm1KgMPEydi8SAuYJEsVFF9Ls4QIi 6/iJdkL7fp0b77MaMyDiMa85o2SBPxYn9kDH6AQpKuUEJ7LKiCzoX2yRwsGJg4S5rOGa QPIA== X-Received: by 10.28.11.13 with SMTP id 13mr19308752wml.4.1446564000265; Tue, 03 Nov 2015 07:20:00 -0800 (PST) Received: from hollewijn.internal (8d690a59.ftth.concepts.nl. [141.105.10.89]) by smtp.gmail.com with ESMTPSA id v191sm23838332wmd.24.2015.11.03.07.19.59 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Nov 2015 07:19:59 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: hostapd loses connectivity on ath0 From: Alban Hertroys In-Reply-To: Date: Tue, 3 Nov 2015 16:19:58 +0100 Cc: freebsd-stable Content-Transfer-Encoding: quoted-printable Message-Id: References: <61705059-E85C-4887-BBCD-D2690D27D24A@gmail.com> To: Adrian Chadd X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 03 Nov 2015 15:20:02 -0000 > On 26 Oct 2015, at 22:10, Adrian Chadd wrote: >=20 > hiya, >=20 > you should try -head. >=20 > But there's some long standing issues hiding around in the AR9227 code > somewhere where they occasionally go deaf and I never figured out > why... :( Frankly, I'm not too eager attempting to run -head on my home = gateway/firewall/wifi AP/file server, especially not if there is little = chance that this issue is fixed there. I don't have a whole lot of spare = time to mess with it and outside of that I need a working server. In the mean time, I noticed these messages in my daily security run = output after several restarts of hostapd over the last couple of weeks: +ath0: ath_tx_default_comp: bf 0xfffffe0001359fc8: seqno 2659: bf_next = not NULL! +ath0: ath_tx_default_comp: bf 0xfffffe00013407c8: seqno 2660: bf_next = not NULL! +ath0: ath_tx_default_comp: bf 0xfffffe000135c2d8: seqno 2661: bf_next = not NULL! +wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost (I'm guessing a lockup of the card is imminent again) Is that any help in getting closer to the cause? Is there any info I = might be able to provide when it locks up again? If this isn't a = hardware bug, I would like to see this fixed if possible in the current = constraints. Or should I just swap my ath card for a different model (or brand)? If = so, which are safe? Regards, > On 26 October 2015 at 13:27, Alban Hertroys = wrote: >> At random times my devices suddenly fail to connect to Wifi on my = ath0 device. Issueing /etc/rc.d/hostapd restart usually resolves the = issue, but at some point that also hung. >>=20 >> Shutting down to single user mode in the hung state only partially = succeeded, in the sense that ifconfig, hostapd and a few other = network-related processes kept "running" - I assume the hangup of = hostapd was caused by a hung process somewhere in that tree. >>=20 >> The system is: >>=20 >> uname -a >> FreeBSD solfertje 10.2-PRERELEASE FreeBSD 10.2-PRERELEASE #19 = r286718: Thu Aug 13 10:00:32 CEST 2015 = dalroi@solfertje:/usr/obj/usr/src/sys/ANTELOPE amd64 >>=20 >> It's quite possible that I've misconfigured something, so here's the = relevant lines of my configs=E2=80=A6 >>=20 >> rc.conf: >>=20 >> # Outside interface >> ifconfig_fxp0=3D"DHCP" >> ifconfig_fxp0_ipv6=3D"inet6 accept_rtadv" >>=20 >> # Wireless >> wlans_ath0=3D"wlan0" >>=20 >> create_args_wlan0=3D"wlanmode hostap" >>=20 >> ifconfig_wlan0=3D"mode ng channel 9:ht/40" >> ifconfig_wlan0_ipv6=3D"inet6 accept_rtadv" >>=20 >> # Bridged interfaces (see example at man 4 bridge) >> cloned_interfaces=3D"bridge0" >> ifconfig_bridge0=3D"addm em0 stp em0 addm wlan0 stp wlan0 up" >> ifconfig_bridge0_alias0=3D"inet 10.236.150.1/24" >> ifconfig_bridge0_ipv6_alias0=3D"inet6 = fe80::6efd:b9ff:fe68:db36%bridge0" >>=20 >> # Internal wired ethernet (should that be above the bridge = declaration?) >> ifconfig_em0=3D"up" >> ifconfig_em0_ipv6=3D"inet6 accept_rtadv" >>=20 >> hostapd_enable=3D"YES" >>=20 >> #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>=20 >> hostapd.conf: >>=20 >> interface=3Dwlan0 >> driver=3Dbsd >> debug=3D1 >> ctrl_interface=3D/var/run/hostapd >> ctrl_interface_group=3Dwheel >> ssid=3Dfoo >> country_code=3DNL >> ieee80211d=3D1 >> hw_mode=3Dg >> wpa=3D2 >> wpa_passphrase=3Dnonononono >> wpa_key_mgmt=3DWPA-PSK >> wpa_pairwise=3DCCMP >>=20 >>=20 >> The ath0 device is: >> pciconf -lv ath0 >> ath0@pci0:5:6:0: class=3D0x028000 card=3D0x0300168c = chip=3D0x002d168c rev=3D0x01 hdr=3D0x00 >> vendor =3D 'Atheros Communications Inc.' >> device =3D 'AR9227 Wireless Network Adapter' >> class =3D network >>=20 >> In case it's relevant: All connected devices get their IPv4 addresses = through DHCP from this machine, the machine itself gets it's IPv4 = external address from my upstream provider, the internal addresses are = hardwired per interface. DHCP is configured to use hostnames (instead of = IP's) that get looked up in Bind9 on the same machine. >>=20 >>=20 >> Google did find some people on the internet with apparently the same = problem, but nobody seems to have found (or posted) a resolution. >>=20 >> Am I doing something wrong? If not, is this a known issue? What's the = next step? >>=20 >> Alban Hertroys >> -- >> If you can't see the forest for the trees, >> cut the trees and you'll find there is no forest. >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://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 Nov 3 18:00:58 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AED4EA25F54 for ; Tue, 3 Nov 2015 18:00:58 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1DDAD1597 for ; Tue, 3 Nov 2015 18:00:57 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id tA3Hlxe3088762; Wed, 4 Nov 2015 04:48:00 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 4 Nov 2015 04:47:59 +1100 (EST) From: Ian Smith To: Jeremy Chadwick cc: freebsd-stable@freebsd.org Subject: Re: stable/10: high load average when box is idle In-Reply-To: <20151027050508.GA7612@icarus.home.lan> Message-ID: <20151104025748.F10372@sola.nimnet.asn.au> References: <20151027050508.GA7612@icarus.home.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 03 Nov 2015 18:00:58 -0000 On Mon, 26 Oct 2015 22:05:08 -0700, Jeremy Chadwick wrote: > (I am not subscribed to the mailing list, please keep me CC'd) > > Issue: a stable/10 system that has an abnormally high load average (e.g. > 0.15, but may be higher depending on other variables which I can't > account for) when the machine is definitely idle (i.e. cannot be traced > to high interrupt usage per vmstat -i, cannot be traced to a userland > process or kernel thread, etc.). > > This problem has been discussed many times on the FreeBSD mailing lists > and the FreeBSD forum (including some folks seeing it on 9.x, but my > complaint here is focused on 10.x so please focus there). > > I'd politely like to request that anyone experiencing this, or who has > experienced it (and if you know when it stopped or why, including what > you may have done, include that), to chime in on this ticket from 2012 > (made for 9.x but style of issue still applies; c#5 is quite valid): > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173541 > > For those still experiencing it, I'd suggest reading c#8 and seeing if > sysctl kern.eventtimer.periodic=1 relieves the problem for you. (At > this time I would not suggest leaving that set indefinitely, as it does > seem to increase the interrupt rate in cpuX:timer in vmstat -i. But for > me kern.eventtimer.periodic=1 "fixes" the issue) Jeremy, I've waited till now to reply, despite really welcoming serious discussion of these LA issues. Rather than joining the PR thread just yet, I'm going to report a short summary of findings, having monitored this ever since it turned up, originally noticed on 9.2 about 2 years ago; I have an embarrasing amount of data to report when appropriate. Like yourself, I think this is far from 'cosmetic' as is oft suggested, especially in some fairly ill-informed forum posts but also various list posts. I've been watching load averages since OS/2 through FreeBSD 2.2 till present and some Linux systems, and have never before seen anything like this, especially on virtually entirely idle systems. While the LAs reported during (say) make -j4 buildworld appear more same, who knows? I'm not suggesting that I think there's any sort of performance hit from this; so far I don't, but 'cosmetic' suggests that it doesn't matter .. I've just brought my 9.3-R Lenovo X200 up to stable/9 to be sure nothing had changed in this respect; it hasn't. So despite your desire to focus on 10.x, and your issue being with systems using LAPIC event counters, I think there are related - but different - manifestations of the issue/s. Firstly, the '0.6' LA at idle often seen in the various reports you've so thoroughly referenced including bug 173541, seems to occur most often (if not entirely) on laptops with Core 2 and Core 2 Duo processors that by default use the HPET as the event counter (and not in per-cpu mode, as eventtimers(4) would imply). I see long-term 15 minute LAs of ~0.55 to ~0.67, from completely idle to idle with X running, 200% idle shown. On these systems, switching to using LAPIC does indeed 'fix' the issue, resulting in genuine 0.00 0.00 0.00 LAs when completely idle, with say 0.10-0.15 short-term when poking it a bit with X running - however C3 is unavailable using LAPIC, pushing power consumption on battery from less than 8W to almost 12W (idle, screen off, lid down) ie ~+50% consumption or ~-33% battery life - so is not a viable solution for laptops actually used away from mains power. Correspondingly, system temperatures are consistently up to 20% higher - on AC or battery - when using LAPIC. So your problem is while using LAPIC, mine and others while using HPET, and despite some semi-obvious relatedness, there are differences, and I don't want to tromp on or confuse the issue you're chasing, yet think there's some underlying - possibly just mathematical? - issues here. I've spent some days trying to follow the HPET and LAPIC code, but it's been too long since I thought I had a tiny grip on any of this, before mav@ turned it on its head - for which we're of course grateful :) eg: /sys/x86/x86/local_apic.c /sys/amd64/include/apicvar.h /sys/dev/acpica/acpi_hpet.[ch] There are some other differences between HPET and LAPIC behaviour on mine best seesn in systat -vm, especially regarding interrupt usage, both in one-shot and periodic modes for both, that require posting quite a lot of data .. so I guess I'm wondering if that's appropriate now? I should add that I'm having some health issues that make it difficult for me to spend much time digging deeply into code or much testing, so that's made me a bit reluctant to dive into this .. but I can't resist! cheers, Ian From owner-freebsd-stable@freebsd.org Tue Nov 3 19:06:02 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD509A25073 for ; Tue, 3 Nov 2015 19:06:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88EEA192B for ; Tue, 3 Nov 2015 19:06:02 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iofz202 with SMTP id z202so29180025iof.2 for ; Tue, 03 Nov 2015 11:06:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=EVcrOH8fbRl2KlATLoTYXwptbtpOK38RhELFSqsTGdE=; b=FLV3PSh/2s7t9P9Bq7C0p1t1K+NDPiuAGFr6cPjlaIQggh9AbByVacZ4R0zdsDuN6F MfHe3ja6B8HV/fAN+sOg37rrtLn/7WKUcWhY8q1WxCSbBj2mCqMrikBLdD88K6WuDueZ Hxm6OnGiZjsOUXbkqqOSzO+kZL9ltFYrZWPtyq+2Ud8aaF+dBUFyGUjPDkJTgGXkaZag gvrk5wYcaqwEeIMBqideD/OvU2lxfq2IT70XwvBE+qswHVrnLtJs3fxO5mb8vbRD/Etu riuyVqpsR35pATJeop6wNWl4ioh9zLe7DHEFT/rUc2Ec8IpMJ/pEw/AHZLmqzNq0DwLD vFGw== MIME-Version: 1.0 X-Received: by 10.107.3.72 with SMTP id 69mr28765750iod.75.1446577561989; Tue, 03 Nov 2015 11:06:01 -0800 (PST) Received: by 10.36.46.66 with HTTP; Tue, 3 Nov 2015 11:06:01 -0800 (PST) In-Reply-To: References: <61705059-E85C-4887-BBCD-D2690D27D24A@gmail.com> Date: Tue, 3 Nov 2015 11:06:01 -0800 Message-ID: Subject: Re: hostapd loses connectivity on ath0 From: Adrian Chadd To: Alban Hertroys Cc: freebsd-stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 03 Nov 2015 19:06:02 -0000 Hi, The stable/10 code doesn't have all the fixes I did over the last two years. Just disable 11n (ifconfig wlan0 -ht) and use that. :-) Sorry! -adrian On 3 November 2015 at 07:19, Alban Hertroys wrote: > >> On 26 Oct 2015, at 22:10, Adrian Chadd wrote: >> >> hiya, >> >> you should try -head. >> >> But there's some long standing issues hiding around in the AR9227 code >> somewhere where they occasionally go deaf and I never figured out >> why... :( > > Frankly, I'm not too eager attempting to run -head on my home gateway/fir= ewall/wifi AP/file server, especially not if there is little chance that th= is issue is fixed there. I don't have a whole lot of spare time to mess wit= h it and outside of that I need a working server. > > In the mean time, I noticed these messages in my daily security run outpu= t after several restarts of hostapd over the last couple of weeks: > +ath0: ath_tx_default_comp: bf 0xfffffe0001359fc8: seqno 2659: bf_next no= t NULL! > +ath0: ath_tx_default_comp: bf 0xfffffe00013407c8: seqno 2660: bf_next no= t NULL! > +ath0: ath_tx_default_comp: bf 0xfffffe000135c2d8: seqno 2661: bf_next no= t NULL! > +wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost > > (I'm guessing a lockup of the card is imminent again) > > Is that any help in getting closer to the cause? Is there any info I migh= t be able to provide when it locks up again? If this isn't a hardware bug, = I would like to see this fixed if possible in the current constraints. > > Or should I just swap my ath card for a different model (or brand)? If so= , which are safe? > > Regards, > > >> On 26 October 2015 at 13:27, Alban Hertroys wrote: >>> At random times my devices suddenly fail to connect to Wifi on my ath0 = device. Issueing /etc/rc.d/hostapd restart usually resolves the issue, but = at some point that also hung. >>> >>> Shutting down to single user mode in the hung state only partially succ= eeded, in the sense that ifconfig, hostapd and a few other network-related = processes kept "running" - I assume the hangup of hostapd was caused by a h= ung process somewhere in that tree. >>> >>> The system is: >>> >>> uname -a >>> FreeBSD solfertje 10.2-PRERELEASE FreeBSD 10.2-PRERELEASE #19 r286718: = Thu Aug 13 10:00:32 CEST 2015 dalroi@solfertje:/usr/obj/usr/src/sys/ANT= ELOPE amd64 >>> >>> It's quite possible that I've misconfigured something, so here's the re= levant lines of my configs=E2=80=A6 >>> >>> rc.conf: >>> >>> # Outside interface >>> ifconfig_fxp0=3D"DHCP" >>> ifconfig_fxp0_ipv6=3D"inet6 accept_rtadv" >>> >>> # Wireless >>> wlans_ath0=3D"wlan0" >>> >>> create_args_wlan0=3D"wlanmode hostap" >>> >>> ifconfig_wlan0=3D"mode ng channel 9:ht/40" >>> ifconfig_wlan0_ipv6=3D"inet6 accept_rtadv" >>> >>> # Bridged interfaces (see example at man 4 bridge) >>> cloned_interfaces=3D"bridge0" >>> ifconfig_bridge0=3D"addm em0 stp em0 addm wlan0 stp wlan0 up" >>> ifconfig_bridge0_alias0=3D"inet 10.236.150.1/24" >>> ifconfig_bridge0_ipv6_alias0=3D"inet6 fe80::6efd:b9ff:fe68:db36%bridge0= " >>> >>> # Internal wired ethernet (should that be above the bridge declaration?= ) >>> ifconfig_em0=3D"up" >>> ifconfig_em0_ipv6=3D"inet6 accept_rtadv" >>> >>> hostapd_enable=3D"YES" >>> >>> #=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> >>> hostapd.conf: >>> >>> interface=3Dwlan0 >>> driver=3Dbsd >>> debug=3D1 >>> ctrl_interface=3D/var/run/hostapd >>> ctrl_interface_group=3Dwheel >>> ssid=3Dfoo >>> country_code=3DNL >>> ieee80211d=3D1 >>> hw_mode=3Dg >>> wpa=3D2 >>> wpa_passphrase=3Dnonononono >>> wpa_key_mgmt=3DWPA-PSK >>> wpa_pairwise=3DCCMP >>> >>> >>> The ath0 device is: >>> pciconf -lv ath0 >>> ath0@pci0:5:6:0: class=3D0x028000 card=3D0x0300168c chip=3D0x002= d168c rev=3D0x01 hdr=3D0x00 >>> vendor =3D 'Atheros Communications Inc.' >>> device =3D 'AR9227 Wireless Network Adapter' >>> class =3D network >>> >>> In case it's relevant: All connected devices get their IPv4 addresses t= hrough DHCP from this machine, the machine itself gets it's IPv4 external a= ddress from my upstream provider, the internal addresses are hardwired per = interface. DHCP is configured to use hostnames (instead of IP's) that get l= ooked up in Bind9 on the same machine. >>> >>> >>> Google did find some people on the internet with apparently the same pr= oblem, but nobody seems to have found (or posted) a resolution. >>> >>> Am I doing something wrong? If not, is this a known issue? What's the n= ext step? >>> >>> Alban Hertroys >>> -- >>> If you can't see the forest for the trees, >>> cut the trees and you'll find there is no forest. >>> >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g" > From owner-freebsd-stable@freebsd.org Wed Nov 4 14:31:36 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 097B2A26F5B for ; Wed, 4 Nov 2015 14:31:36 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB9431E7E for ; Wed, 4 Nov 2015 14:31:35 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by iody8 with SMTP id y8so54988663iod.1 for ; Wed, 04 Nov 2015 06:31:35 -0800 (PST) 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=V4pcFbtgEwb56INSLzwSlMWAsEmZItQB3RUOruHnhyg=; b=tC5xtIxgdI598HicfxE4idAh5RCoX4l4B3meeYpNxEQF3KWZ757rUkgscLv2hVy2Vk RPdH6TxwgclAA6aJhxAbfsfFefouAygvS9AWNSVvZ6s7zx754QCPuzRhLNGizrfBwhJP +MU052spAlyT51yMzb2SUMr2/FwIvD4FbmlOCtfH87ymf/pEJGlnl3UY1AIIiuzZL07m nC2CQG8psQpEPg71Oq40gEyQYsU7GxAqVDjvI7J4KqxJ9XitnLLVYBi7lxG9VrstPUnt HuSpPb/yiMOez4Coald8mk74660N5v1F/TTu5jf64866twihfXcBnNDvsw4OATiREcB6 uk6Q== MIME-Version: 1.0 X-Received: by 10.107.10.204 with SMTP id 73mr3879087iok.22.1446647495264; Wed, 04 Nov 2015 06:31:35 -0800 (PST) Received: by 10.107.46.8 with HTTP; Wed, 4 Nov 2015 06:31:35 -0800 (PST) In-Reply-To: <20151104025748.F10372@sola.nimnet.asn.au> References: <20151027050508.GA7612@icarus.home.lan> <20151104025748.F10372@sola.nimnet.asn.au> Date: Wed, 4 Nov 2015 14:31:35 +0000 Message-ID: Subject: Re: stable/10: high load average when box is idle From: Tom Evans To: Ian Smith Cc: FreeBSD Stable Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 04 Nov 2015 14:31:36 -0000 On Tue, Nov 3, 2015 at 5:47 PM, Ian Smith wrote: > Like yourself, I think this is far from 'cosmetic' as is oft suggested, > especially in some fairly ill-informed forum posts but also various list > posts. I've been watching load averages since OS/2 through FreeBSD 2.2 > till present and some Linux systems, and have never before seen anything > like this, especially on virtually entirely idle systems. While the LAs > reported during (say) make -j4 buildworld appear more same, who knows? > > I'm not suggesting that I think there's any sort of performance hit from > this; so far I don't, but 'cosmetic' suggests that it doesn't matter .. > Have you read mav's explanation on the PR? It certainly seems a valid explanation of why it is probably a cosmetic issue - that is, we could wake up more to get a truly perfect load average, but why bother? ISTM, the problem reports are of the form "My server is idle and it is reporting a non-idle load average below 1", and not "My server is supposedly idle, but is doing actual work causing the load average to be higher than it should be". Is there any evidence that we have the latter and not the former? Cheers Tom From owner-freebsd-stable@freebsd.org Wed Nov 4 16:15:14 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5CE00A26120; Wed, 4 Nov 2015 16:15:14 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 03237120A; Wed, 4 Nov 2015 16:15:13 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 3nrY3f0DmXz1KF; Wed, 4 Nov 2015 17:15:10 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:references:in-reply-to:organization :subject:subject:from:from:date:date:content-transfer-encoding :content-type:content-type:mime-version:received:received :received:received; s=jakla4; t=1446653701; x=1449245702; bh=R/E qCjLfDRbb1JG/+3u3oCZRm8Ct7G80LTS7xaHc/IM=; b=BNn05J52o2b6VfCl9+6 tyvRy4+nGOjvKLYwkqyEMdzhHCNq51deBxT++Q+9cYnwICeC5Rq+7yaxKL+QpNEr zeYFemRclvaXiKeqb92KAn7dEqUrO/lyqLaSLKTMUeyOdpGixlUh/p6/kOBXbMbM dcS+oCHV0Mqro8+x3VIQp4vU= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id Dfo489RngLgM; Wed, 4 Nov 2015 17:15:01 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3nrY3T4DMvz1KC; Wed, 4 Nov 2015 17:15:01 +0100 (CET) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3nrY3T1nsDzlg; Wed, 4 Nov 2015 17:15:01 +0100 (CET) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by nabiralnik.ijs.si with HTTP (HTTP/1.1 POST); Wed, 04 Nov 2015 17:15:01 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Wed, 04 Nov 2015 17:15:01 +0100 From: Mark Martinec To: freebsd-stable@freebsd.org, current@freebsd.org Subject: Re: Segmentation fault running ntpd Organization: Jozef Stefan Institute In-Reply-To: <20151101093116.GA5457@voyager> References: <20150718120956.GC1155@albert.catwhisker.org> <86pozwbvds.fsf@desk.des.no> <20151030113449.GF13438@albert.catwhisker.org> <20151101093116.GA5457@voyager> Message-ID: <9145a2d0228d9d025b2b0b6b5612726c@mailbox.ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.1.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 04 Nov 2015 16:15:14 -0000 Upgrading 10.2-RELEASE-p6 to 10.2-RELEASE-p7 now solved ntpd crashes (apparently fixed by: FreeBSD Errata Notice FreeBSD-EN-15:20.vm). Thanks!!! Mark On 2015-11-01 10:31, Andre Albsmeier wrote: > On Fri, 30-Oct-2015 at 19:47:59 +0100, Mark Martinec wrote: >> Not sure if it's the same issue, but it sure looks like it is. >> >> I have upgraded a couple of hosts (amd64) from 10.2-RELEASE-p5 >> to 10.2-RELEASE-p6, i.e. the freebsd-upgrade essentially just >> replaced the /usr/sbin/ntpd with a new one; then I restarted >> the ntpd. >> >> On all host but one this was successful: the new ntpd starts >> fine and works normally. But on one of these machines the >> ntpd process immediately crashes with SIGSEGV. That machine >> has an Intel Xeon cpu. It is not apparent to me in what way >> this machine differs from others, > > I'll add my observations here: > > I am using an ntp.conf with a single server entry: > > server ntp.some.domain.org > > ntp.some.domain.org is a CNAME pointing to gate.some.domain.org > and the latter contains an A record pointing to 192.168.128.1. > > After updating 9.3-STABLE to the latest version (one which includes ntp > 4.2.8p4), ntpd crashes: > > Nov 1 09:38:38 voyager kernel: pid 4443 (ntpd), uid 0: exited on signal > 11 > > This happens in line 871 of ntpd.c where mlockall() is called: > > && 0 != mlockall(MCL_CURRENT|MCL_FUTURE)) > > It does NOT crash with MCL_FUTURE only. > It does crash with MCL_CURRENT only. > > When adding > > rlimit memlock -1 > > to ntpd.conf it does NOT crash (as mlockall() won't be called anymore). > > When specifying the IP address (192.168.128.1) as the server it > does NOT crash. > > When specifying gate.some.domain.org as the server it also does > NOT crash. tcpdump shows in this case: > > 09:49:59.542310 IP 192.168.128.2.21102 > 192.168.128.1.53: 7639+ A? > gate.some.domain.org. (41) > 09:49:59.542578 IP 192.168.128.1.53 > 192.168.128.2.21102: 7639* 1/1/0 > A 192.168.128.1 (71) > 09:49:59.542612 IP 192.168.128.2.52455 > 192.168.128.1.53: 42047+ > AAAA? gate.some.domain.org. (41) > 09:49:59.542792 IP 192.168.128.1.53 > 192.168.128.2.52455: 42047* 0/1/0 > (88) > > When reverting the server entry back to ntp.some.domain.org > it crashes and tcpdump shows: > > 09:36:05.172552 IP 192.168.128.2.17836 > 192.168.128.1.53: 49768+ A? > ntp.some.domain.org. (40) > 09:36:05.173320 IP 192.168.128.1.53 > 192.168.128.2.17836: 49768* > 2/1/0 CNAME gate.some.domain.org., A 192.168.128.1 (89) > 09:36:05.173361 IP 192.168.128.2.22611 > 192.168.128.1.53: 63808+ > AAAA? ntp.some.domain.org. (40) > 09:36:05.173595 IP 192.168.128.1.53 > 192.168.128.2.22611: 63808* > 1/1/0 CNAME gate.some.domain.org. (106) > > The probability for crashing increases with the speed and the > number of cores of the machine: On my old single-core Pentiums > it never crashes, on my quad-cores i7-3770K it always crashes. > > The (asynchronous) resolving of the names start in line 3876 of > ntp_config.c: > > getaddrinfo_sometime(curr_peer->addr->address, > > If we put the mlockall() call directly before this line, the > crash is gone. > > Maybe you want to play around with rlimit, CNAMES, IPs and > so on... > > -Andre > > Anyone else seeing this? >> 2015-10-30 12:34, je David Wolfskill napisal >> > On Fri, Oct 30, 2015 at 09:42:07AM +0100, Dag-Erling Smørgrav wrote: >> >> David Wolfskill writes: >> >> > ... >> >> > bound to 172.17.1.245 -- renewal in 43200 seconds. >> >> > pid 544 (ntpd), uid 0: exited on signal 11 (core dumped) >> >> > Starting Network: lo0 em0 iwn0 lagg0. >> >> > ... >> >> >> >> Did you find a solution? I'm wondering if the ntpd problems people >> >> are >> >> reporting on freebsd-security@ are related. I vaguely recall hearing >> >> that this had been traced to a pthread bug, but can't find anything >> >> about it in commit logs or mailing list archives. >> >> .... >> > >> > I don't recall finding "a solution" per se; that said, I also don't >> > recall seeing an occurrence of the above for enough time that I'm not >> > sure when I sent that message. :-} >> > >> > As a reality check: >> > >> > g1-252(11.0-C)[1] ls -lT /*.core >> > -rw-r--r-- 1 root wheel 13783040 Aug 18 04:19:03 2015 /ntpd.core >> > g1-252(11.0-C)[2] >> > >> > So -- among other points -- my last sighting of whatever was causing >> > that was the day I built: >> > >> > FreeBSD 11.0-CURRENT #157 r286880M/286880:1100079: Tue Aug 18 >> > 04:45:25 PDT 2015 >> > root@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 >> > >> > Note that the machines where I run head get updated daily (unless >> > there's enough of a problem with head that I can't build it or can't >> > boot it (and I'm unable to circumvent the issue within a reasonable >> > time)) -- and while I do attempt to run ntpd on the machines, the above >> > failure is more "annoying" than "crippling" in my particular case. >> > >> > And I'm presently running: >> > >> > FreeBSD 11.0-CURRENT #227 r290138M/290138:1100084: Thu Oct 29 >> > 05:12:58 PDT 2015 >> > root@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY amd64 >> > >> > and building head @r290190 as I type. >> > >> > And FWIW, I *suspect* that one of the issues involved (in my case) >> > was a ... lack of determinism ... in events involving getting the >> > (wireless) network connectivity into a usable state as part of the >> > initial transition to multi-user mode. (I only have evidence at >> > the moment of the issue on my laptop; my build machine, which only >> > uses a wired NIC, has no /ntpd.core file. It and my laptop are updated >> > pretty much in lock-step; it runs a completely GENERIC kernel, while >> > the laptop runs a modestly customized one based on GENERIC.) >> > >> > Peace, >> > david >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to >> "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Thu Nov 5 01:59:35 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 644D7A26369; Thu, 5 Nov 2015 01:59:35 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoom.lafn.org (zoom.lafn.org [108.92.93.123]) by mx1.freebsd.org (Postfix) with ESMTP id 3DEC01FA2; Thu, 5 Nov 2015 01:59:34 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from [10.0.1.12] (static-71-177-216-148.lsanca.fios.verizon.net [71.177.216.148]) (authenticated bits=0) by zoom.lafn.org (8.14.7/8.14.9) with ESMTP id tA51nG6G053938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Nov 2015 17:49:17 -0800 (PST) (envelope-from bc979@lafn.org) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: Segmentation fault running ntpd From: Doug Hardie In-Reply-To: <9145a2d0228d9d025b2b0b6b5612726c@mailbox.ijs.si> Date: Wed, 4 Nov 2015 17:49:15 -0800 Cc: current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3178C067-4C33-49E1-9ED7-501EDEFDB256@lafn.org> References: <20150718120956.GC1155@albert.catwhisker.org> <86pozwbvds.fsf@desk.des.no> <20151030113449.GF13438@albert.catwhisker.org> <20151101093116.GA5457@voyager> <9145a2d0228d9d025b2b0b6b5612726c@mailbox.ijs.si> To: freebsd-stable X-Mailer: Apple Mail (2.3096.5) X-Virus-Scanned: clamav-milter 0.98 at zoom.lafn.org X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 05 Nov 2015 01:59:35 -0000 > On 4 November 2015, at 08:15, Mark Martinec = wrote: >=20 > Upgrading 10.2-RELEASE-p6 to 10.2-RELEASE-p7 now solved ntpd crashes > (apparently fixed by: FreeBSD Errata Notice FreeBSD-EN-15:20.vm). >=20 > Thanks!!! >=20 > Mark >=20 ntpdc hangs when you do a peers command on 9.3. Eventually it returns a = no response from the server. However, ntpq works just fine and nagios = is able to get the status without problems. Both of those did not work = properly before. =E2=80=94 Doug From owner-freebsd-stable@freebsd.org Thu Nov 5 02:17:10 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B846EA26778 for ; Thu, 5 Nov 2015 02:17:10 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 953C81AF0 for ; Thu, 5 Nov 2015 02:17:10 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound1.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Thu, 5 Nov 2015 02:17:31 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id tA52H2lD047687; Wed, 4 Nov 2015 19:17:02 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1446689822.91534.386.camel@freebsd.org> Subject: Re: Segmentation fault running ntpd From: Ian Lepore To: Doug Hardie , freebsd-stable Cc: current@freebsd.org Date: Wed, 04 Nov 2015 19:17:02 -0700 In-Reply-To: <3178C067-4C33-49E1-9ED7-501EDEFDB256@lafn.org> References: <20150718120956.GC1155@albert.catwhisker.org> <86pozwbvds.fsf@desk.des.no> <20151030113449.GF13438@albert.catwhisker.org> <20151101093116.GA5457@voyager> <9145a2d0228d9d025b2b0b6b5612726c@mailbox.ijs.si> <3178C067-4C33-49E1-9ED7-501EDEFDB256@lafn.org> Content-Type: text/plain; charset="windows-1251" X-Mailer: Evolution 3.16.5 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 05 Nov 2015 02:17:10 -0000 On Wed, 2015-11-04 at 17:49 -0800, Doug Hardie wrote: > > On 4 November 2015, at 08:15, Mark Martinec < > > Mark.Martinec+freebsd@ijs.si> wrote: > > > > Upgrading 10.2-RELEASE-p6 to 10.2-RELEASE-p7 now solved ntpd > > crashes > > (apparently fixed by: FreeBSD Errata Notice FreeBSD-EN-15:20.vm). > > > > Thanks!!! > > > > Mark > > > > ntpdc hangs when you do a peers command on 9.3. Eventually it > returns a no response from the server. However, ntpq works just fine > and nagios is able to get the status without problems. Both of those > did not work properly before. > > — Doug The protocol used by ntpdc is no longer supported by ntpd, and that change came along for the ride with the security and bugfixes that were recently merged back to the 9 and 10 branches. Everything that can be done with ntpdc on older releases can now be done using ntpq with the new release. The ntpdc program itself is still present so that you can still administer remote servers running older code, since they won't be able to do everything via ntpq. -- Ian From owner-freebsd-stable@freebsd.org Thu Nov 5 17:10:11 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B85F3A2706B for ; Thu, 5 Nov 2015 17:10:11 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F97418EA for ; Thu, 5 Nov 2015 17:10:10 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: by wicfv8 with SMTP id fv8so13925700wic.0 for ; Thu, 05 Nov 2015 09:10:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bris_ac_uk.20150623.gappssmtp.com; s=20150623; h=date:from:message-id:to:subject:reply-to; bh=aC05cs73uSlQfL8w3LEAHPh7Z62SxaXJaUcyfi+KNj0=; b=BZOCViI7A+oebO/qbVf8kNACmq/gdP6v4PK3OSebByi49/trP7skgKYV8w66kY9xvX tP3At5+mbbWNe0qqDBJQupvlXuFY7U3XCCF2tpkQat+VfvZG2F8iNebmeoAWEloysf+4 iVvIM+U1PrTrvHNNuLRmk3R6F6/GTkr1Vzms2mNgXd3nh914xrNvHH++cuhr3FWGXPOt PDzE/XcT24BcXyyrbuSub1jPlkIVuVYLObSyt2jtjVT51jjIATGRevsGJq/rzbeu4QxV eR3WiragC8sdCfdIT5gUGad/oeM2KFojlzi1dS5XASq9P0wjxwWKyTumsce1LCsGmsbj v8hQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:message-id:to:subject:reply-to; bh=aC05cs73uSlQfL8w3LEAHPh7Z62SxaXJaUcyfi+KNj0=; b=cznZjD9jBdRoTu6YjJKHnr+5AAl7rU0T2w6vMS8Sgy3ShyDbY7qZqbmmugcweAuH4d v6OzRbxXGhwK01Rn+aVOhC+P0S5ffnFO8xex7CMNaEmkAj5MJTp01qZO8DFLxWj+yGXX ICDwTnoHILDjccmLo/dMDND7ldF0BrfeWGWuFnQkWKXmeGwneAd/ChetaB505XqpfyH6 XGT9eraxMG64K3DyYfDJT389NxoLRymrePuCASIUHVhhu6RdJHPiyXltQmUOm76LdZFx vmOqrzFBQqaHePIfRSPnIyJDvyjRnONY2uLZrKLbT+YihvaVwrOTCFecfRZ1qPn+Fn1I /8aA== X-Gm-Message-State: ALoCoQlZEWIkv98LeUl/GQRG+De1HJaAYHHL2sSLObdJ4As9RiSVXxaunbPBJDklzFac8C2nQfiq X-Received: by 10.194.58.142 with SMTP id r14mr11527341wjq.37.1446743408990; Thu, 05 Nov 2015 09:10:08 -0800 (PST) Received: from mech-as222.men.bris.ac.uk (mech-as222.men.bris.ac.uk. [137.222.170.4]) by smtp.gmail.com with ESMTPSA id 20sm35108455wmh.8.2015.11.05.09.10.08 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Nov 2015 09:10:08 -0800 (PST) Date: Thu, 05 Nov 2015 09:10:08 -0800 (PST) X-Google-Original-Date: Thu, 5 Nov 2015 17:10:07 GMT Received: from mech-as222.men.bris.ac.uk (localhost [127.0.0.1]) by mech-as222.men.bris.ac.uk (8.15.2/8.15.2) with ESMTP id tA5HA735098364 for ; Thu, 5 Nov 2015 17:10:07 GMT (envelope-from mexas@mech-as222.men.bris.ac.uk) Received: (from mexas@localhost) by mech-as222.men.bris.ac.uk (8.15.2/8.15.2/Submit) id tA5HA7nH098363 for freebsd-stable@freebsd.org; Thu, 5 Nov 2015 17:10:07 GMT (envelope-from mexas) From: Anton Shterenlikht Message-Id: <201511051710.tA5HA7nH098363@mech-as222.men.bris.ac.uk> To: freebsd-stable@freebsd.org Subject: ia64: pcpu.h: No such file or directory Reply-To: mexas@bris.ac.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 05 Nov 2015 17:10:11 -0000 On ia64 10.2-STABLE #17 r289997 I get a panic as soon as I start poudriere bulk I see in core.txt: http://eis.bris.ac.uk/~mexas/core.txt Reading symbols from /boot/kernel/nullfs.ko.symbols...done. Loaded symbols for /boot/kernel/nullfs.ko.symbols #0 doadump (textdump=18810336) at pcpu.h:85 85 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=18810336) at pcpu.h:85 If I remember correctly poudriere loads nullfs. Anton From owner-freebsd-stable@freebsd.org Thu Nov 5 19:30:07 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02DDAA26DF9 for ; Thu, 5 Nov 2015 19:30:07 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 66700115D for ; Thu, 5 Nov 2015 19:30:05 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. (bsdrookie.norma.com [192.168.7.144]) by elf.hq.norma.perm.ru (8.14.9/8.14.9) with ESMTP id tA5JTxbm048727 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 6 Nov 2015 00:30:00 +0500 (YEKT) (envelope-from emz@norma.perm.ru) To: freebsd-stable@freebsd.org From: "Eugene M. Zheganin" Subject: unable to boot a healthy zfs pool: all block copies unavailable X-Enigmail-Draft-Status: N1110 Message-ID: <563BAE37.2090205@norma.perm.ru> Date: Fri, 6 Nov 2015 00:29:59 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (elf.hq.norma.perm.ru [192.168.3.10]); Fri, 06 Nov 2015 00:30:00 +0500 (YEKT) X-Spam-Status: No hits=-102.9 bayes=0.0000 testhits ALL_TRUSTED=-1, AWL=0.007, BAYES_00=-1.9, USER_IN_WHITELIST=-100 autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on elf.hq.norma.perm.ru X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 05 Nov 2015 19:30:07 -0000 Hi. Today one of my zfs pool disks dies, I was unable to change it on the fly (video board was blocking it) so I powered off, changed disk (not in root pool) and all of a sudden I realized that i cannot boot: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool zroot gptzfsboot: failed to mount default pool zroot It was first reboot since October, 16th, when I installed recent -STABLE and upgraded zpool. I was pretty confident that I've installed loaders, but I tried to reinstall them - no luck. Then I built today's STABLE and installed loaders from it - same issue. I've even tried to install less recent loaders from a server nearby - same issue. Two years ago I have encountered similar (if not identical) issue: https://lists.freebsd.org/pipermail/freebsd-stable/2013-December/076317.html The main difference was it was i386. Now I have an amd64 machine. I even updated it's BIOS, and I still cannot boot. Zpool is fine: I'm writing this message from this exact machine, however, I had to boot it from today -STABLE from an USB stick. I've read about the zfsboottest utility and tried it on my unbootable pool - after the bried info about it (traated as healthy) it said "OK". I guess no errors were encountered. So... what can I do to restore the ability to boot from my root pool ? Thanks. Eugene. P.S. Some info about the pool below. let me know if it's not enough - I'll post more. [root@bsdrookie:/]# zpool list NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT zroot 1,79T 690G 1,12T - 14% 37% 1.00x ONLINE - [root@bsdrookie:/]# zfs list NAME USED AVAIL REFER MOUNTPOINT zroot 704G 1,05T 2,07G legacy zroot/crypted 516G 1,06T 502G - zroot/jails 2,16G 1,05T 2,03G /usr/local/public/jails zroot/tmp 223M 1,05T 223M /tmp zroot/usr 182G 1,05T 17,0G /usr zroot/usr/home 145G 1,05T 145G /usr/home zroot/usr/ports 17,0G 1,05T 2,79G /usr/ports zroot/usr/ports/distfiles 14,3G 1,05T 14,3G /usr/ports/distfiles zroot/usr/ports/packages 384K 1,05T 384K /usr/ports/packages zroot/usr/public 2,11G 1,05T 2,11G /usr/local/public zroot/usr/src 1,56G 1,05T 1,56G /usr/src zroot/var 1,19G 1,05T 83,7M /var zroot/var/crash 992M 1,05T 992M /var/crash zroot/var/db 113M 1,05T 39,7M /var/db zroot/var/db/pkg 73,1M 1,05T 73,1M /var/db/pkg zroot/var/empty 144K 1,05T 144K /var/empty zroot/var/log 2,53M 1,05T 2,53M /var/log zroot/var/mail 272K 1,05T 272K /var/mail zroot/var/run 520K 1,05T 520K /var/run zroot/var/tmp 22,7M 1,05T 22,7M /var/tmp From owner-freebsd-stable@freebsd.org Thu Nov 5 22:00:04 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C877DA26188 for ; Thu, 5 Nov 2015 22:00:04 +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 E35DD1B09 for ; Thu, 5 Nov 2015 22:00:03 +0000 (UTC) (envelope-from avg@FreeBSD.org) 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 XAA13292; Thu, 05 Nov 2015 23:59:54 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZuSZW-0006nw-DJ; Thu, 05 Nov 2015 23:59:54 +0200 Subject: Re: unable to boot a healthy zfs pool: all block copies unavailable To: "Eugene M. Zheganin" , freebsd-stable@FreeBSD.org References: <563BAE37.2090205@norma.perm.ru> From: Andriy Gapon X-Enigmail-Draft-Status: N1110 Message-ID: <563BD121.4020404@FreeBSD.org> Date: Thu, 5 Nov 2015 23:58:57 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <563BAE37.2090205@norma.perm.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 05 Nov 2015 22:00:05 -0000 On 05/11/2015 21:29, Eugene M. Zheganin wrote: > Hi. > > Today one of my zfs pool disks dies, I was unable to change it on the > fly (video board was blocking it) so I powered off, changed disk (not in > root pool) and all of a sudden I realized that i cannot boot: > > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zroot > gptzfsboot: failed to mount default pool zroot > > It was first reboot since October, 16th, when I installed recent -STABLE > and upgraded zpool. I was pretty confident that I've installed loaders, > but I tried to reinstall them - no luck. Then I built today's STABLE and > installed loaders from it - same issue. I've even tried to install less > recent loaders from a server nearby - same issue. > > Two years ago I have encountered similar (if not identical) issue: > https://lists.freebsd.org/pipermail/freebsd-stable/2013-December/076317.html > The main difference was it was i386. Now I have an amd64 machine. I even > updated it's BIOS, and I still cannot boot. Zpool is fine: I'm writing > this message from this exact machine, however, I had to boot it from > today -STABLE from an USB stick. > > I've read about the zfsboottest utility and tried it on my unbootable > pool - after the bried info about it (traated as healthy) it said "OK". > I guess no errors were encountered. > > So... what can I do to restore the ability to boot from my root pool ? It could be that your BIOS is not able to read past 1TB (512 * INT_MAX). That seems to be a rather common problem for consumer motherboards. Here is an example of how it looked for me: https://people.freebsd.org/~avg/IMAG1099.jpg Fortunately, it wasn't a root pool that got the error. > P.S. Some info about the pool below. let me know if it's not enough - > I'll post more. > > [root@bsdrookie:/]# zpool list > NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT > zroot 1,79T 690G 1,12T - 14% 37% 1.00x ONLINE - > > [root@bsdrookie:/]# zfs list > NAME USED AVAIL REFER MOUNTPOINT > zroot 704G 1,05T 2,07G legacy > zroot/crypted 516G 1,06T 502G - > zroot/jails 2,16G 1,05T 2,03G /usr/local/public/jails > zroot/tmp 223M 1,05T 223M /tmp > zroot/usr 182G 1,05T 17,0G /usr > zroot/usr/home 145G 1,05T 145G /usr/home > zroot/usr/ports 17,0G 1,05T 2,79G /usr/ports > zroot/usr/ports/distfiles 14,3G 1,05T 14,3G /usr/ports/distfiles > zroot/usr/ports/packages 384K 1,05T 384K /usr/ports/packages > zroot/usr/public 2,11G 1,05T 2,11G /usr/local/public > zroot/usr/src 1,56G 1,05T 1,56G /usr/src > zroot/var 1,19G 1,05T 83,7M /var > zroot/var/crash 992M 1,05T 992M /var/crash > zroot/var/db 113M 1,05T 39,7M /var/db > zroot/var/db/pkg 73,1M 1,05T 73,1M /var/db/pkg > zroot/var/empty 144K 1,05T 144K /var/empty > zroot/var/log 2,53M 1,05T 2,53M /var/log > zroot/var/mail 272K 1,05T 272K /var/mail > zroot/var/run 520K 1,05T 520K /var/run > zroot/var/tmp 22,7M 1,05T 22,7M /var/tmp > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Andriy Gapon From owner-freebsd-stable@freebsd.org Thu Nov 5 22:00:56 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2472BA26313 for ; Thu, 5 Nov 2015 22:00:56 +0000 (UTC) (envelope-from dustinwenz@ebureau.com) Received: from internet06.ebureau.com (internet06.ebureau.com [65.127.24.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "internet06.ebureau.com", Issuer "internet06.ebureau.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 026C71CDD for ; Thu, 5 Nov 2015 22:00:55 +0000 (UTC) (envelope-from dustinwenz@ebureau.com) Received: from localhost (localhost [127.0.0.1]) by internet06.ebureau.com (Postfix) with ESMTP id BBD954755BF6 for ; Thu, 5 Nov 2015 15:51:46 -0600 (CST) X-Virus-Scanned: amavisd-new at ebureau.com Received: from internet06.ebureau.com ([127.0.0.1]) by localhost (internet06.ebureau.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2_4QZQXDvUKy for ; Thu, 5 Nov 2015 15:51:46 -0600 (CST) Received: from square.office.ebureau.com (unknown [10.10.20.22]) by internet06.ebureau.com (Postfix) with ESMTPSA id 0D1AE4755BEB for ; Thu, 5 Nov 2015 15:51:46 -0600 (CST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: Question about "pcpu" rctl From: Dustin Wenz In-Reply-To: <91178832-EBB8-498C-9651-E29C2844D4C5@ebureau.com> Date: Thu, 5 Nov 2015 15:51:45 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <91178832-EBB8-498C-9651-E29C2844D4C5@ebureau.com> To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 05 Nov 2015 22:00:56 -0000 As far as I know, pcpu has never worked for limiting beyond a single = core. I submitted a patch for kern/kern_racct.c that should fix it: =20 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D189870 Please update the bug if it does or doesn't resolve the issue. Maybe = that will prompt a committer to apply it to stable. - .Dustin >=20 > Anyone can advise me please? > Thanks! > From: John Dison via freebsd-stable > To: "stable at freebsd.org" =20 > Sent: Tuesday, September 15, 2015 1:00 PM > Subject: Question about "pcpu" rctl >=20 > Hello and have a nice day! >=20 > I try to limit cpu usage for multi-threaded process on a multi-core = machine. > I use the following command: > # rctl -a user:myusernm:pcpu:deny=3D200/user > And I expect (please correct me if I am wrong) that all processes = running with uid=3Dmyusernm will consume 200% of CPU in total. > But after that I see that multi-threaded process continues to consume = all available cores on my machine. > rctl command reports:# rctluser:myusernm:pcpu:deny=3D200 > What am I doing wrong? >=20 From owner-freebsd-stable@freebsd.org Fri Nov 6 00:11:31 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47683A25493 for ; Fri, 6 Nov 2015 00:11:31 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mx1.eichornenterprises.com (mx1.eichornenterprises.com [104.236.13.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.eichornenterprises.com", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 055341A9D for ; Fri, 6 Nov 2015 00:11:30 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mail.eichornenterprises.com (cpe-184-59-147-149.neo.res.rr.com [184.59.147.149]) by mx1.eichornenterprises.com (OpenSMTPD) with ESMTP id 999bd878; Thu, 5 Nov 2015 19:11:20 -0500 (EST) Received: by mail.eichornenterprises.com (OpenSMTPD) with ESMTPSA id 0353c398 TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 5 Nov 2015 19:11:20 -0500 (EST) Message-ID: <1446768676.1335.14.camel@michaeleichorn.com> Subject: Re: unable to boot a healthy zfs pool: all block copies unavailable From: "Michael B. Eichorn" To: "Eugene M. Zheganin" , freebsd-stable@freebsd.org Date: Thu, 05 Nov 2015 19:11:16 -0500 In-Reply-To: <563BAE37.2090205@norma.perm.ru> References: <563BAE37.2090205@norma.perm.ru> Content-Type: multipart/signed; micalg="sha-512"; protocol="application/x-pkcs7-signature"; boundary="=-6dyqXfb8AHC806jFxO7l" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 06 Nov 2015 00:11:31 -0000 --=-6dyqXfb8AHC806jFxO7l Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2015-11-06 at 00:29 +0500, Eugene M. Zheganin wrote: > Hi. >=20 > Today one of my zfs pool disks dies, I was unable to change it on the > fly (video board was blocking it) so I powered off, changed disk (not > in > root pool) and all of a sudden I realized that i cannot boot: >=20 > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool zroot > gptzfsboot: failed to mount default pool zroot >=20 > It was first reboot since October, 16th, when I installed recent=20 > -STABLE > and upgraded zpool. I was pretty confident that I've installed loaders, > but I tried to reinstall them - no luck. Then I built today's STABLE > and > installed loaders from it - same issue. I've even tried to install less > recent loaders from a server nearby - same issue. >=20 > Two years ago I have encountered similar (if not identical) issue: > https://lists.freebsd.org/pipermail/freebsd-stable/2013-December/076317 > .html > The main difference was it was i386. Now I have an amd64 machine. I > even > updated it's BIOS, and I still cannot boot. Zpool is fine: I'm writing > this message from this exact machine, however, I had to boot it from > today -STABLE from an USB stick. >=20 > I've read about the zfsboottest utility and tried it on my unbootable > pool - after the bried info about it (traated as healthy) it said "OK". > I guess no errors were encountered. >=20 > So... what can I do to restore the ability to boot from my root pool ? >=20 > Thanks. > Eugene I had something similar happen to me in the last month with a the installer zfs setup. Unfortunately it was a critical system so I didn't have time for diagnostics. My pants-on-fire solution was that since the pool was a mirror, swap a disk out with my spare, reinstall, and send/receive the data back. Not pretty, but it was my personal mail/file/web/everything-not-on-the-firewall server. The pool was accessible from the installer shell and on import to the fresh system, it just wouldn't boot. Also in my case it was RELEASE not STABLE, and yes it was consumer grade hardware. TLDR: Not just you. Reinstall? --=-6dyqXfb8AHC806jFxO7l Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCCEqAw ggYwMIIFGKADAgECAgMOXcYwDQYJKoZIhvcNAQELBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu dCBDQTAeFw0xNTA2MTMyMDI0NDZaFw0xNjA2MTQwMDM1NTBaMEgxHzAdBgNVBAMMFmlrZUBtaWNo YWVsZWljaG9ybi5jb20xJTAjBgkqhkiG9w0BCQEWFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDJVdWALPz5h2s5zUQGIJYl6Vp8FPtZNko8q/3s crCsxXJLprMaDdpnqTsmkbmEfKvsqPQE6HVOpGxVRTl/tCm+VvouW9eY9ITMigb1OnHdU13CKO0j drgeU1nHst0qxwsIofRD7nC4dakT6exnrVndlBmLrf/bLPh2qOM8YK5qKK6m33fE7AyYrwiYAWFT 3fERI7LakjaabrIoS/Y1rCdL5FaCTMOlRbZyduc8HkrgjT2JW+i4fVcKyGL5gExBJWfS3q1uGFaB ie6pYtl8lZPtvN0JSfibP003RBoLgzqHJKW91RL0qNeDjKZi/5nrlU398l9UoVvLLO3KxoPBXKCx AgMBAAGjggLcMIIC2DAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcD AgYIKwYBBQUHAwQwHQYDVR0OBBYEFJZqarc6CcrOs6eAwOgrMznk5ZWWMB8GA1UdIwQYMBaAFFNy 7ZKc4NrLAVx8fpY1TvLUuFGCMCEGA1UdEQQaMBiBFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggFM BgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3 dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2Vy dGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBh Y2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0 YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2Ug aW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8w LTAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUH AQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIu Y2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20v MA0GCSqGSIb3DQEBCwUAA4IBAQB4K8iQw+0FRn3xEnB3vIIu2Vi4C3ZGnOMWP90FFXLrZ6uAu9AK xVCjXUVP6nAEsOopTMu769vVecdBvg0KO2i5aTDTdTLX4g9d020g4OLWW1NiynAkX8oKqJLqZ53q vHK4zP4KWPS3bSqDWVCosTMfI+H6tkg+6G3gS0HHoHTLKZhIT3z6PQZAfeofM7ed6NOdAcj0J2lP ODHzzz7Y9x4wMwYJdidorzUDVYkNIkim8ak7hK9F60NadA5w/BirFATSlzRyV0h1tl6oNisEaQcq tGvy6UoCTDhzaJ7pQValfDXJ/A47P0hNj/CX/PmkY1wQHsEJz2pbh5lqteP/fO0rMIIGMDCCBRig AwIBAgIDDl3GMA0GCSqGSIb3DQEBCwUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN MTUwNjEzMjAyNDQ2WhcNMTYwNjE0MDAzNTUwWjBIMR8wHQYDVQQDDBZpa2VAbWljaGFlbGVpY2hv cm4uY29tMSUwIwYJKoZIhvcNAQkBFhZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBIjANBgkqhkiG 9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyVXVgCz8+YdrOc1EBiCWJelafBT7WTZKPKv97HKwrMVyS6az Gg3aZ6k7JpG5hHyr7Kj0BOh1TqRsVUU5f7Qpvlb6LlvXmPSEzIoG9Tpx3VNdwijtI3a4HlNZx7Ld KscLCKH0Q+5wuHWpE+nsZ61Z3ZQZi63/2yz4dqjjPGCuaiiupt93xOwMmK8ImAFhU93xESOy2pI2 mm6yKEv2NawnS+RWgkzDpUW2cnbnPB5K4I09iVvouH1XCshi+YBMQSVn0t6tbhhWgYnuqWLZfJWT 7bzdCUn4mz9NN0QaC4M6hySlvdUS9KjXg4ymYv+Z65VN/fJfVKFbyyztysaDwVygsQIDAQABo4IC 3DCCAtgwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUF BwMEMB0GA1UdDgQWBBSWamq3OgnKzrOngMDoKzM55OWVljAfBgNVHSMEGDAWgBRTcu2SnODaywFc fH6WNU7y1LhRgjAhBgNVHREEGjAYgRZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBTAYDVR0gBIIB QzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBD QSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBs aWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQvMC0wK6ApoCeG JWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8w OQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9j YTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5j bGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG 9w0BAQsFAAOCAQEAeCvIkMPtBUZ98RJwd7yCLtlYuAt2RpzjFj/dBRVy62ergLvQCsVQo11FT+pw BLDqKUzLu+vb1XnHQb4NCjtouWkw03Uy1+IPXdNtIODi1ltTYspwJF/KCqiS6med6rxyuMz+Clj0 t20qg1lQqLEzHyPh+rZIPuht4EtBx6B0yymYSE98+j0GQH3qHzO3nejTnQHI9CdpTzgx888+2Pce MDMGCXYnaK81A1WJDSJIpvGpO4SvRetDWnQOcPwYqxQE0pc0cldIdbZeqDYrBGkHKrRr8ulKAkw4 c2ie6UFWpXw1yfwOOz9ITY/wl/z5pGNcEB7BCc9qW4eZarXj/3ztKzCCBjQwggQcoAMCAQICAR4w DQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0 Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1 NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1 cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7 zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8 VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+ jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQO Jebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB /wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAf BgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3dy5z dGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3Js MIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3Rh cnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t L2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhjjF6uHLkjd02h cdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4n4bGGdKo3awP Wp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8C h507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893 gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0 PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBm unwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2L L9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwF i2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhE puP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMYIDnzCCA5sCAQEwgZQwgYwxCzAJ BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRh bCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDl3GMA0GCWCGSAFlAwQCAwUAoIIB2zAYBgkqhkiG9w0B CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTExMDYwMDExMTZaME8GCSqGSIb3DQEJ BDFCBEAno2xb3Rgk2mJtGwuNCgr0HlFOyi9P0U+kexEKrpp/2bUTL4K1EgHQhUMqLWYLBTZPAMu0 oagsfSxwI1sutnlTMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu dCBDQQIDDl3GMIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoT DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25p bmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50 IENBAgMOXcYwDQYJKoZIhvcNAQEBBQAEggEABaK+p8QG3x8gn18Ru4syMIM+lwNy/3WDxmW2aJ4/ Q7rUgnrgqi1AMPQaJyxJJcVjOZ6I30mmcO/QdKriKBJNQxllnO1Bx2yIuHhN/7d31x8nkbKSRJA6 yMHhI7vkZsOpjOWJUaIWQCHlKXXMoqtli54yjyo2bXF/kdE9jmEhTkSotlSmVylZJe3WeIe4rVCU P7hWL1j6wwAV8SX2KqURRGQ/beZ8VE7vlpGJ/oTzt+50nvKHIGYoI7Fcks8QIYPmvLLu2TvurPFz JsVR5GZVjcOWHhwIXiBnR2RqIg/R11vYAKYHeTIiPGu9baBAXu7s6wL7yTMvKVnSfY9Y4/G4AwAA AAAAAA== --=-6dyqXfb8AHC806jFxO7l-- From owner-freebsd-stable@freebsd.org Fri Nov 6 05:54:07 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68360A28B65 for ; Fri, 6 Nov 2015 05:54:07 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 97C131980 for ; Fri, 6 Nov 2015 05:54:05 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. (bsdrookie.norma.com [192.168.7.144]) by elf.hq.norma.perm.ru (8.14.9/8.14.9) with ESMTP id tA65rpKu001996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 6 Nov 2015 10:53:53 +0500 (YEKT) (envelope-from emz@norma.perm.ru) Subject: Re: unable to boot a healthy zfs pool: all block copies unavailable To: freebsd-stable@freebsd.org References: <563BAE37.2090205@norma.perm.ru> <563BD121.4020404@FreeBSD.org> From: "Eugene M. Zheganin" X-Enigmail-Draft-Status: N1110 Message-ID: <563C406F.3090003@norma.perm.ru> Date: Fri, 6 Nov 2015 10:53:51 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <563BD121.4020404@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (elf.hq.norma.perm.ru [192.168.3.10]); Fri, 06 Nov 2015 10:53:54 +0500 (YEKT) X-Spam-Status: No hits=-102.9 bayes=0.0000 testhits ALL_TRUSTED=-1, BAYES_00=-1.9,USER_IN_WHITELIST=-100 autolearn=ham autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on elf.hq.norma.perm.ru X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 06 Nov 2015 05:54:07 -0000 Hi. On 06.11.2015 02:58, Andriy Gapon wrote: > > It could be that your BIOS is not able to read past 1TB (512 * INT_MAX). That > seems to be a rather common problem for consumer motherboards. > Here is an example of how it looked for me: > https://people.freebsd.org/~avg/IMAG1099.jpg > Fortunately, it wasn't a root pool that got the error. Mine looks way different: yours shows the pool info, mine shows 'BTX halted' message: http://zhegan.in/files/cannot-read-MOS.jpg . I'm running the latest BIOS for this motherboard (Gigabyte Z77P-D3, updated yesterday, stilll it's only 2012h year). If it's still the BIOS-related bug, what wokraround can I use - reslice the disk and create the root pool inside first Tb, right ? Thanks. Eugene. From owner-freebsd-stable@freebsd.org Fri Nov 6 16:00:05 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEF84A27CC8 for ; Fri, 6 Nov 2015 16:00:04 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B638C1A23 for ; Fri, 6 Nov 2015 16:00:04 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by oiww189 with SMTP id w189so44107895oiw.3 for ; Fri, 06 Nov 2015 08:00:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=d3Qx1x8QFh06xAJKqmWSIDUSqGh3FOH4ITmaaNwh7wA=; b=hJDQfjnY10GRa5Vax4l0bhBhX8pn8jQphZkewdtSVi4DU5sk5LTLDPyQN/dyv/cz88 VhkH35ntnMVzAPtBtGSK10kTBD9PPQ3g48KClrlp4QkQ0dWZeMCJkN1yuNJXU1VM72+7 OmHFk8ssiPb95fFa3WWP/T2RKNn0TERIgxEgklchcJf3+lROKVfL+QGC2FGbHlQWyfii 4e5r7yogmzA1pY9+050Rpu9uxr9IL7tQaHyUrAng8ne1smA7gcU9tUwEhwAYZwrSFWLY vBPofErXmzYR4YJVgz8qzbzs91RY+mN8JEWCE1nkbJ3NhKnlLjCi5Z3HCak++WH7+2Vk DqfQ== MIME-Version: 1.0 X-Received: by 10.202.212.68 with SMTP id l65mr1331404oig.54.1446825604130; Fri, 06 Nov 2015 08:00:04 -0800 (PST) Sender: asomers@gmail.com Received: by 10.202.1.206 with HTTP; Fri, 6 Nov 2015 08:00:04 -0800 (PST) In-Reply-To: <563C406F.3090003@norma.perm.ru> References: <563BAE37.2090205@norma.perm.ru> <563BD121.4020404@FreeBSD.org> <563C406F.3090003@norma.perm.ru> Date: Fri, 6 Nov 2015 09:00:04 -0700 X-Google-Sender-Auth: _fgib-Umi5_Snplv2IKoX2US_yc Message-ID: Subject: Re: unable to boot a healthy zfs pool: all block copies unavailable From: Alan Somers To: "Eugene M. Zheganin" Cc: FreeBSD Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 06 Nov 2015 16:00:05 -0000 On Thu, Nov 5, 2015 at 10:53 PM, Eugene M. Zheganin wrote: > Hi. > > On 06.11.2015 02:58, Andriy Gapon wrote: >> >> It could be that your BIOS is not able to read past 1TB (512 * INT_MAX). That >> seems to be a rather common problem for consumer motherboards. >> Here is an example of how it looked for me: >> https://people.freebsd.org/~avg/IMAG1099.jpg >> Fortunately, it wasn't a root pool that got the error. > Mine looks way different: yours shows the pool info, mine shows 'BTX > halted' message: http://zhegan.in/files/cannot-read-MOS.jpg . I'm > running the latest BIOS for this motherboard (Gigabyte Z77P-D3, updated > yesterday, stilll it's only 2012h year). If it's still the BIOS-related > bug, what wokraround can I use - reslice the disk and create the root > pool inside first Tb, right ? > > Thanks. > Eugene. I notice that my 10.2-RELEASE VM prints the same message about "all block copies unavailable" and then continues to boot just fine. So I wonder if that part is just red herring. There is another possibility here: I have seen a bug where ZFS attempts to open the root pool's vdevs by path (eg ada0p3) but can't find them because disks have been replaced and no longer have their old devnames. So vdev_geom searches through the list of geom providers looking for any provider with the correct ZFS GUID. Normally it would find the right devname (eg ada1p3). But sometimes, because the disks are partitioned, it will find the wrong partition first (eg ada1). Since ZFS has labels at both the beginning and the end of each vdev, vdev_geom will see the label at the end of ada1 (really, it's the label at the end of ada1p3, but it shares the same LBA that a label at the end of ada1 would) and think that it opened ada1 successfully. vdev_geom_open will then return, and at some later date another part of ZFS will fail to read the MOS, and your boot will fail. If this is the case, then there are three possible solutions: 1) Fix vdev_geom. I'm currently testing a patch to do just that. 2) With power off, shuffle disks around until the boot disks have the same devnames that they had the last time you successfully booted. If this is a SATA-only computer, swapping cables between different mobo ports should be enough. 3) Boot from your USB stick and carefully (oh so carefully!) erase the ZFS labels at the end of the boot disk. Don't touch the labels at the beginning. If your boot pool is mirrored, it should be sufficient to erase the labels on one disk only. -Alan From owner-freebsd-stable@freebsd.org Fri Nov 6 16:39:22 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14430A28999 for ; Fri, 6 Nov 2015 16:39:22 +0000 (UTC) (envelope-from t07453fca5e-e9324760ef94f000-11a89e250b5e493e8a272eb67ec4a9d8@bounce.twitter.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E9E4018B4 for ; Fri, 6 Nov 2015 16:39:21 +0000 (UTC) (envelope-from t07453fca5e-e9324760ef94f000-11a89e250b5e493e8a272eb67ec4a9d8@bounce.twitter.com) Received: by mailman.ysv.freebsd.org (Postfix) id EA0ACA28998; Fri, 6 Nov 2015 16:39:21 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E98DAA28997 for ; Fri, 6 Nov 2015 16:39:21 +0000 (UTC) (envelope-from t07453fca5e-e9324760ef94f000-11a89e250b5e493e8a272eb67ec4a9d8@bounce.twitter.com) Received: from spring-chicken-bk.twitter.com (spring-chicken-bk.twitter.com [199.16.156.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A684C18B3 for ; Fri, 6 Nov 2015 16:39:21 +0000 (UTC) (envelope-from t07453fca5e-e9324760ef94f000-11a89e250b5e493e8a272eb67ec4a9d8@bounce.twitter.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=twitter.com; s=dkim-201406; t=1446827952; bh=GFIucccB1ch5bnoGo+3jGXuBJOfUL/nfBgjps2e6wcw=; h=Date:From:To:Subject:MIME-Version:Content-Type:Message-ID; b=lqAzmxeThKSdXNWXN3oq5Z4YI6/h/DrSt55Ot3iIYEaPUtObuvxlXJzG9yhnjkuAM VDOVhoqxNBR/x2GXRpWZZyquGfoTlnqOM0Kb7xLAT72JDxlnhO8A1O54pa0h2Rd83R Uqq1ibFPr2eMJbe9nud7ROlZ9BcEV/w79aU3h5i2h7ci5bJp2MZLdApUNKTkzpjM/l 4VCf6Yodo5WTTceHvBvDf61XF8UPv4H2Qb5QztjwCoIKn7E4vn6+UMNdOwekfVpTKU 0C3ntrD0aQvuYZtGcJ9k+87/Lsp6sV4P/T7MgkGIFVgKTMUNxSjfbo9FfAhR+lkd8l tgp3WScfJUxqg== X-MSFBL: eyJ1Ijoic3RhYmxlQGZyZWVic2Qub3JnQHVzYiMjMjRAMjQ0QDQxMjgwMzQzODNA MEA4NmM3YWZhMDEwZjM2MjZiMTdlNWU2NjBhZjFiMGIwNTRmZTIzMjU0IiwiYiI6 ImF0bGEtYXh3LTA1LXNyMS1FdmVyeXRoaW5nLjE5NiIsInIiOiJzdGFibGVAZnJl ZWJzZC5vcmciLCJnIjoiRXZlcnl0aGluZyJ9 Date: Fri, 06 Nov 2015 16:39:12 +0000 From: Twitter To: RICKON ZIEMSKI Subject: Confirm your Twitter account, RICKON ZIEMSKI MIME-Version: 1.0 Feedback-ID: 0040162518f58f41d1f0:16481b2a2bd9895cc9f3f73eb2597daffdce:none:twitterESP Message-ID: <92.11.27055.0B7DC365@twitter.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 06 Nov 2015 16:39:22 -0000 RICKON ZIEMSKI, Confirm your email address to complete your Twitter account. It's easy - just click on the button below. Click on the link below or copy and paste it into a browser: https://twitter.com/i/redirect?url=https%3A%2F%2Ftwitter.com%2Faccount%2Fconfirm_user_email%2F4128034383%2F4C86D-8FBE7-144682%3Ft%3D1%26cn%3DZW1haWxfY29uZmlybV9pbml0%26sig%3Dc5eed0287fd435e109b820a66866ca13e87b0460%26al%3D1%26iid%3D11a89e250b5e493e8a272eb67ec4a9d8%26ac%3D1%26autoactions%3D1446827952%26uid%3D4128034383%26nid%3D244%2B308&t=1&cn=ZW1haWxfY29uZmlybV9pbml0&sig=a3d2b7cb120a7163ef75b74fbd6acec0d530c57f&iid=11a89e250b5e493e8a272eb67ec4a9d8&uid=4128034383&nid=244+308 From owner-freebsd-stable@freebsd.org Fri Nov 6 22:41:33 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13A78A28E82 for ; Fri, 6 Nov 2015 22:41:33 +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 2290A1E58; Fri, 6 Nov 2015 22:41:31 +0000 (UTC) (envelope-from avg@FreeBSD.org) 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 AAA02186; Sat, 07 Nov 2015 00:41:24 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZuphD-0008Qa-Sq; Sat, 07 Nov 2015 00:41:23 +0200 Subject: Re: unable to boot a healthy zfs pool: all block copies unavailable To: Alan Somers , "Eugene M. Zheganin" References: <563BAE37.2090205@norma.perm.ru> <563BD121.4020404@FreeBSD.org> <563C406F.3090003@norma.perm.ru> Cc: FreeBSD From: Andriy Gapon Message-ID: <563D2C5C.9000609@FreeBSD.org> Date: Sat, 7 Nov 2015 00:40:28 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 06 Nov 2015 22:41:33 -0000 On 06/11/2015 18:00, Alan Somers wrote: > I notice that my 10.2-RELEASE VM prints the same message about "all > block copies unavailable" and then continues to boot just fine. Is that on a system with only one ZFS pool or are there more of them? -- Andriy Gapon From owner-freebsd-stable@freebsd.org Fri Nov 6 22:47:47 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8763A2706E for ; Fri, 6 Nov 2015 22:47:47 +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 3A1D91168 for ; Fri, 6 Nov 2015 22:47:46 +0000 (UTC) (envelope-from avg@FreeBSD.org) 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 AAA02267; Sat, 07 Nov 2015 00:47:45 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ZupnN-0008Qy-6F; Sat, 07 Nov 2015 00:47:45 +0200 Subject: Re: unable to boot a healthy zfs pool: all block copies unavailable To: "Eugene M. Zheganin" , freebsd-stable@FreeBSD.org References: <563BAE37.2090205@norma.perm.ru> <563BD121.4020404@FreeBSD.org> <563C406F.3090003@norma.perm.ru> From: Andriy Gapon X-Enigmail-Draft-Status: N1110 Message-ID: <563D2DD9.4000003@FreeBSD.org> Date: Sat, 7 Nov 2015 00:46:49 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <563C406F.3090003@norma.perm.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 06 Nov 2015 22:47:48 -0000 On 06/11/2015 07:53, Eugene M. Zheganin wrote: > Hi. > > On 06.11.2015 02:58, Andriy Gapon wrote: >> >> It could be that your BIOS is not able to read past 1TB (512 * INT_MAX). That >> seems to be a rather common problem for consumer motherboards. >> Here is an example of how it looked for me: >> https://people.freebsd.org/~avg/IMAG1099.jpg >> Fortunately, it wasn't a root pool that got the error. > Mine looks way different: yours shows the pool info, mine shows 'BTX > halted' message: http://zhegan.in/files/cannot-read-MOS.jpg . My output is more verbose because I've added some extra diagnostics. Also, as I've said, in my case is complain was not about a root pool. > I'm > running the latest BIOS for this motherboard (Gigabyte Z77P-D3, updated > yesterday, stilll it's only 2012h year). Fun fact - my problem is also with the latest BIOS for my motherboard. The previous BIOS version does not have the problem. > If it's still the BIOS-related > bug, what wokraround can I use - reslice the disk and create the root > pool inside first Tb, right ? That's what I would do to be sure that I'm safe. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Fri Nov 6 22:49:20 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39CD4A27105 for ; Fri, 6 Nov 2015 22:49:20 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0311812C6; Fri, 6 Nov 2015 22:49:20 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by oies6 with SMTP id s6so31521258oie.1; Fri, 06 Nov 2015 14:49:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=SmQcm1Y03VLQTJEleJ/qwiDfII2igq/AxLbFlFa9Vjg=; b=MnUD4+o/GBxxuCxuyMD3vYMFXiayQaIHWAZgqQEcJfQb9LXrlyhZyTJea2T/BddngW d1jgd3CuOPF9JgOLa0GQO4EJs8xPvvwKjZeTxSJgQTib11sOzkcieCVWZ0M+fhSJnRm2 FQVyZJZDnVzruCaTiNTSrgjR+lIqzNt+3tukaXI9rnNikbppeTwadcfgNMrzEf6Fa2z6 iSIzx6iADCM8YOPjSKZJC3miHO39JA5mwoYPjXpyt/l3ZR1EQhgaSY4u8B9cs9kWM6DV K196sKlzeypkbkNk4Aa+c6tHbLrPnb9Ew06khWy1XOS7ne2RxbhFFCpsuOx/5MK4re0h ezQQ== MIME-Version: 1.0 X-Received: by 10.202.228.5 with SMTP id b5mr9642964oih.100.1446850159472; Fri, 06 Nov 2015 14:49:19 -0800 (PST) Sender: asomers@gmail.com Received: by 10.202.1.206 with HTTP; Fri, 6 Nov 2015 14:49:19 -0800 (PST) In-Reply-To: <563D2C5C.9000609@FreeBSD.org> References: <563BAE37.2090205@norma.perm.ru> <563BD121.4020404@FreeBSD.org> <563C406F.3090003@norma.perm.ru> <563D2C5C.9000609@FreeBSD.org> Date: Fri, 6 Nov 2015 15:49:19 -0700 X-Google-Sender-Auth: 1JsHCRqmkBPBKfurN6ai19Aqz5w Message-ID: Subject: Re: unable to boot a healthy zfs pool: all block copies unavailable From: Alan Somers To: Andriy Gapon Cc: "Eugene M. Zheganin" , FreeBSD Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 06 Nov 2015 22:49:20 -0000 On Fri, Nov 6, 2015 at 3:40 PM, Andriy Gapon wrote: > On 06/11/2015 18:00, Alan Somers wrote: >> I notice that my 10.2-RELEASE VM prints the same message about "all >> block copies unavailable" and then continues to boot just fine. > > Is that on a system with only one ZFS pool or are there more of them? Ahh, you're probably right. That system has two pools. -Alan From owner-freebsd-stable@freebsd.org Sat Nov 7 11:58:42 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50AE2A27C86 for ; Sat, 7 Nov 2015 11:58:42 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D0E4D1462 for ; Sat, 7 Nov 2015 11:58:41 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id tA7BwYj8063364 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 7 Nov 2015 12:58:35 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id tA7BwYTa063361 for ; Sat, 7 Nov 2015 12:58:34 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Sat, 7 Nov 2015 12:58:34 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD stable Subject: Merging r286233 to stable/10? Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 07 Nov 2015 11:58:42 -0000 Hi, Would someone please consider merging r286233 to stable/10? -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-stable@freebsd.org Sat Nov 7 12:25:52 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E568A289A2 for ; Sat, 7 Nov 2015 12:25:52 +0000 (UTC) (envelope-from 0xf10e@fsfe.org) Received: from mail-2.alumni.tu-berlin.de (mail-2.alumni.tu-berlin.de [130.149.5.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E99601836 for ; Sat, 7 Nov 2015 12:25:51 +0000 (UTC) (envelope-from 0xf10e@fsfe.org) X-tubIT-Incoming-IP: 92.225.12.29 Received: from x5ce10c1d.dyn.telefonica.de ([92.225.12.29] helo=Android-2) by mailbox.alumni.tu-berlin.de (exim-4.76) with esmtpsa [UNKNOWN:AES256-SHA:256] for id 1Zv2Lh-0000Xs-P5; Sat, 07 Nov 2015 13:12:01 +0100 In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: Merging r286233 to stable/10? From: Florian Ermisch <0xf10e@fsfe.org> Date: Sat, 07 Nov 2015 12:12:00 +0000 To: FreeBSD stable Message-ID: <972F7EC1-8D7B-4162-9AD4-AB0791E726E7@fsfe.org> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 07 Nov 2015 12:25:52 -0000 To provide some context for other ppl wondering: > Add missing exception number to EL0 > sync. abort on ARM64 > > When doing a data abort from userland > it is possible to get more than one data > abort inside the same exception level. > Add an appropriate exception number to > allow nesting of data_abort handler for > EL0. https://lists.freebsd.org/pipermail/svn-src-head/2015-August/074870.html Regards, Florian Am 7. November 2015 12:58:34 MEZ, schrieb "Trond Endrestøl" : > Hi, > > Would someone please consider merging r286233 to stable/10? From owner-freebsd-stable@freebsd.org Sat Nov 7 12:40:13 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADC1BA28E22 for ; Sat, 7 Nov 2015 12:40:13 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FCDF1161 for ; Sat, 7 Nov 2015 12:40:12 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id tA7Ce8MK063578 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sat, 7 Nov 2015 13:40:08 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id tA7Ce8lS063575 for ; Sat, 7 Nov 2015 13:40:08 +0100 (CET) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Sat, 7 Nov 2015 13:40:08 +0100 (CET) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: FreeBSD stable Subject: Re: Merging r286233 to stable/10? In-Reply-To: <972F7EC1-8D7B-4162-9AD4-AB0791E726E7@fsfe.org> Message-ID: References: <972F7EC1-8D7B-4162-9AD4-AB0791E726E7@fsfe.org> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 07 Nov 2015 12:40:13 -0000 On Sat, 7 Nov 2015 12:12-0000, Florian Ermisch wrote: > To provide some context for other ppl wondering: My bad. I meant r286223. This one: https://svnweb.freebsd.org/base?view=revision&revision=286223 -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-stable@freebsd.org Sat Nov 7 13:48:44 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22327A28F56 for ; Sat, 7 Nov 2015 13:48:44 +0000 (UTC) (envelope-from rizzo.unipi@gmail.com) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D08B1A67 for ; Sat, 7 Nov 2015 13:48:43 +0000 (UTC) (envelope-from rizzo.unipi@gmail.com) Received: by lfs39 with SMTP id 39so52776596lfs.3 for ; Sat, 07 Nov 2015 05:48:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=MQAi6Q/BOyJ+73VZqGfgjXvD2TMZaUPa63y7I5s/aXk=; b=E8PESWZBBM88GJ9S7K2SZa0ZtHWiz9Hb6AsCuM2Vrq057K2WOJhxWg2+1X/FIqM3Hu jAGyAyaqKoAAPCMZGCVi78T/9/EubzwzlGwSuXSUjJw2F5eIRmCWvFAegQoJ4j5DiCr0 o8HZCjtoS3Zy/HukQqF6lI/mhTbKTOfEiphQcEk850Q3sYLe0UJVKPi+w+d3D5OTy3aU ASJFQilTRM0K89pis/Zbszvd43JYXZGQ1sK7QXDbPhKa8a/VmQ9qu8mfhNe7qoQ7s35f BjCmOtg2lVyDVyf+R6iWULBm/FQ1dfygJdw4OKKLopUXOlcmNKJeBJrbWJarNZC4AQm6 DF6A== MIME-Version: 1.0 X-Received: by 10.25.88.129 with SMTP id m123mr5828016lfb.23.1446904121715; Sat, 07 Nov 2015 05:48:41 -0800 (PST) Sender: rizzo.unipi@gmail.com Received: by 10.114.78.3 with HTTP; Sat, 7 Nov 2015 05:48:41 -0800 (PST) In-Reply-To: References: Date: Sat, 7 Nov 2015 14:48:41 +0100 X-Google-Sender-Auth: f9V1zQ1cL8TEPOpp0LvWWu86H5Y Message-ID: Subject: Re: Merging r286233 to stable/10? From: Luigi Rizzo To: =?UTF-8?Q?Trond_Endrest=C3=B8l?= Cc: FreeBSD stable Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 07 Nov 2015 13:48:44 -0000 Request to all: would you mind a brief English summary with this kind of requests? It would attract relevant people's attention much more than a commit id. Cheers Luigi On Saturday, November 7, 2015, Trond Endrest=C3=B8l < Trond.Endrestol@fagskolen.gjovik.no> wrote: > Hi, > > Would someone please consider merging r286233 to stable/10? > > -- > +-------------------------------+------------------------------------+ > | Vennlig hilsen, | Best regards, | > | Trond Endrest=C3=B8l, | Trond Endrest=C3=B8l, = | > | IT-ansvarlig, | System administrator, | > | Fagskolen Innlandet, | Gj=C3=B8vik Technical College, Norway, = | > | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | > | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | > +-------------------------------+------------------------------------+ > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > " > --=20 -----------------------------------------+------------------------------- Prof. Luigi RIZZO, rizzo@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL +39-050-2217533 . via Diotisalvi 2 Mobile +39-338-6809875 . 56122 PISA (Italy) -----------------------------------------+------------------------------- From owner-freebsd-stable@freebsd.org Sat Nov 7 15:43:25 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FC96A288D5 for ; Sat, 7 Nov 2015 15:43:25 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6DED410FF for ; Sat, 7 Nov 2015 15:43:25 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by pabfh17 with SMTP id fh17so152988807pab.0 for ; Sat, 07 Nov 2015 07:43:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:to:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=xpfx88pAQGyjwlN5zVlb6Iwq+Djp6jCFegyGRELQZ8Y=; b=RqbV+2L/f2dpdITTj3TenNjLemgyNZjB1WaE+rhwvdbOHnHOg67AEgLSlwYZYhV6Tp Z9nBp4c1cYWYExLXlyAYVIaRDqqY5lGEhBW026G2huW2NSMhKzXEFohnhyu2pTnGBFTn ukvHdpgHLgktmH4z0drTgA/AQqILPynGDLPX0ozMFLxqAeWwo2Mk3Nl45D8iNsjaN3eR gDJ1WSM+cfxXBOUrp2sIUD5vihsSnozfzi4hSYdq6pC+OEcpV1tPR6alYU9M7JKcuqUH 368j52dn5gg5YeCIL33OTXFvdyvhDb6Z5h8zRNWfW37Bdir72+V4H2n/hU3lpYLPBnkV vUxg== X-Received: by 10.68.129.40 with SMTP id nt8mr26300239pbb.118.1446911005059; Sat, 07 Nov 2015 07:43:25 -0800 (PST) Received: from ?IPv6:2001:44b8:31ae:7b01:24b2:4122:9f12:3ce6? (2001-44b8-31ae-7b01-24b2-4122-9f12-3ce6.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:24b2:4122:9f12:3ce6]) by smtp.gmail.com with ESMTPSA id fk8sm6511336pab.33.2015.11.07.07.43.23 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 07 Nov 2015 07:43:24 -0800 (PST) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: Merging r286233 to stable/10? References: To: Luigi Rizzo , =?UTF-8?Q?Trond_Endrest=c3=b8l?= Cc: FreeBSD stable From: Kubilay Kocak Message-ID: <563E1C10.5080007@FreeBSD.org> Date: Sun, 8 Nov 2015 02:43:12 +1100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Thunderbird/42.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 07 Nov 2015 15:43:25 -0000 On 8/11/2015 12:48 AM, Luigi Rizzo wrote: > Request to all: would you mind a brief English summary with this kind of > requests? It would attract relevant people's attention much more than a > commit id. Yep, this and ideally a Bugzilla issue reference so mfc-stableX flag can be set on the issue, and re-opened if necessary getting the relevant original committers attention > Cheers > Luigi > > On Saturday, November 7, 2015, Trond Endrestøl < > Trond.Endrestol@fagskolen.gjovik.no> wrote: > >> Hi, >> >> Would someone please consider merging r286233 to stable/10? >> From owner-freebsd-stable@freebsd.org Sat Nov 7 15:44:55 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A41D2A28970 for ; Sat, 7 Nov 2015 15:44:55 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 737351230; Sat, 7 Nov 2015 15:44:55 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by padhx2 with SMTP id hx2so144712711pad.1; Sat, 07 Nov 2015 07:44:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=tijH9qAMX5bEt7LQbrxB6WhhgPCk8demr8Se0Er5K9g=; b=pFMJ1jHi5Xi1b+tSILed3WysI7dlRkhOLZG/nsg+qWkC4OxKn1ph41ekira6/IsAuV tFIiOqbYh5TtGvF3sucXoIMrcfIrskh/6tkJ6X8M/O28nLiVCVuaJrxWyg+k52a0eTLk tPSmoNltGWUxZDhnCFEMwbu196KMrGASQeuE5jtwZ1bDjYqU8UfTzmDxnvrZuBMrem3L ylYna3MWC0IDHC9kPm2/2CL/P68OOuT4dFMZOc4azuBPByrc7pKY+mj73/Bk9mdV09pN 71NE1GabnIfHzqWqQbwxPHzsvmzco/lb0w4rnqj/d0bT6RTK4DlQIc7UzrkUqi31+ibZ rZig== X-Received: by 10.66.221.105 with SMTP id qd9mr26628118pac.46.1446911095122; Sat, 07 Nov 2015 07:44:55 -0800 (PST) Received: from ?IPv6:2001:44b8:31ae:7b01:24b2:4122:9f12:3ce6? (2001-44b8-31ae-7b01-24b2-4122-9f12-3ce6.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:24b2:4122:9f12:3ce6]) by smtp.gmail.com with ESMTPSA id ho3sm6550930pbb.18.2015.11.07.07.44.52 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 07 Nov 2015 07:44:54 -0800 (PST) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: Merging r286233 to stable/10? References: Cc: =?UTF-8?Q?Trond_Endrest=c3=b8l?= , FreeBSD stable , smh@FreeBSD.org From: Kubilay Kocak Message-ID: <563E1C6A.3000305@FreeBSD.org> Date: Sun, 8 Nov 2015 02:44:42 +1100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Thunderbird/42.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 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, 07 Nov 2015 15:44:55 -0000 On 7/11/2015 10:58 PM, Trond Endrestøl wrote: > Hi, > > Would someone please consider merging r286233 to stable/10? > cc'ing original committer :)