From owner-freebsd-stable@freebsd.org Mon Sep 11 09:15:59 2017 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 343A8E24D0D for ; Mon, 11 Sep 2017 09:15:59 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu01176b.smtpx.saremail.com (cu01176b.smtpx.saremail.com [195.16.151.151]) (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 6FC3D7D0D8 for ; Mon, 11 Sep 2017 09:15:57 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.41] (unknown [192.148.167.11]) by proxypop01.sare.net (Postfix) with ESMTPA id C5F039DD351 for ; Mon, 11 Sep 2017 11:09:11 +0200 (CEST) From: Borja Marcos Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Unusually high "Wired" memory Message-Id: <853D9198-6AB7-496F-B1C2-F8C5814114B6@sarenet.es> Date: Mon, 11 Sep 2017 11:09:08 +0200 To: FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2017 09:15:59 -0000 Hi, Since I=E2=80=99ve updated a machine to 11.1-STABLE I am seeing a rather = unusual growth of Wired memory. Any hints on what might have changed from 11-RELEASE to 11.1-RELEASE and = 11.1-STABLE? Thanks! From owner-freebsd-stable@freebsd.org Mon Sep 11 09:35:27 2017 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 BF981E00A0F for ; Mon, 11 Sep 2017 09:35:27 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu1176c.smtpx.saremail.com (cu1176c.smtpx.saremail.com [195.16.148.151]) (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 84E807DCC9 for ; Mon, 11 Sep 2017 09:35:26 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.41] (unknown [192.148.167.11]) by proxypop02.sare.net (Postfix) with ESMTPA id 9B5A79DC900; Mon, 11 Sep 2017 11:25:16 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusually high "Wired" memory From: Borja Marcos In-Reply-To: <853D9198-6AB7-496F-B1C2-F8C5814114B6@sarenet.es> Date: Mon, 11 Sep 2017 11:25:16 +0200 Cc: FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <280948FF-C17D-44FD-B57B-55EBD9848BDB@sarenet.es> References: <853D9198-6AB7-496F-B1C2-F8C5814114B6@sarenet.es> To: Borja Marcos X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2017 09:35:27 -0000 > On 11 Sep 2017, at 11:09, Borja Marcos wrote: >=20 >=20 > Hi, >=20 > Since I=E2=80=99ve updated a machine to 11.1-STABLE I am seeing a = rather unusual growth of Wired memory. >=20 > Any hints on what might have changed from 11-RELEASE to 11.1-RELEASE = and 11.1-STABLE? Evil Mailman scrubbed my attachment :/ http://frobula.crabdance.com:8001/Geigerfun/memoryzones.png Borja From owner-freebsd-stable@freebsd.org Mon Sep 11 14:03:01 2017 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 1CA02E0D6D9 for ; Mon, 11 Sep 2017 14:03:01 +0000 (UTC) (envelope-from vivek@khera.org) 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 F1B052861 for ; Mon, 11 Sep 2017 14:03:00 +0000 (UTC) (envelope-from vivek@khera.org) Received: by mailman.ysv.freebsd.org (Postfix) id F0F81E0D6D8; Mon, 11 Sep 2017 14:03:00 +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 F0842E0D6D7 for ; Mon, 11 Sep 2017 14:03:00 +0000 (UTC) (envelope-from vivek@khera.org) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 9700A285F for ; Mon, 11 Sep 2017 14:03:00 +0000 (UTC) (envelope-from vivek@khera.org) Received: by mail-wm0-x22b.google.com with SMTP id f199so40613383wme.0 for ; Mon, 11 Sep 2017 07:03:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=khera.org; s=google11; h=mime-version:from:date:message-id:subject:to; bh=HtLj2us8HVvhArm8jMFW/l6LOrnCy/RDriNZZAJNuUk=; b=Q1urvAdZ4O7XvUVFpJFCS2irjqOUxJPbYWDhrqv4x6+hWWobXDj2xqQgdkTladknIZ w77ul9tVQ5OE7X4AuWzYa8ITFK7b0F8PI9I6AqKpRF63dds6KmEZ4a24iNKlDrZko4Gh cTfoIYkiBioGT4OZlbKTgn5XXZ2OepdIOX8KA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=HtLj2us8HVvhArm8jMFW/l6LOrnCy/RDriNZZAJNuUk=; b=oBBqp8GGsffVja+EklPI4lP7/qWMDBzl4udxTSg7XMTdqWxHveXHT5UaRsbsmeEZ+g v/HdxJEK5a1iw0w4lHEKDh1UCInRCv1k8HRjuLipHgPN53f1J/Fnr2DZiquVaoqvquQB ky7hzUrhHTjHxxrznVMmlrAhTBVLkbFb2H8aV38wHTyMG+71ayF8+P1by1/bB/WiqUyw f3MJKIX3LTTite1S3PbFATg/6NLLV0Zxbg7XrBXzx9aVqoSZNzi8009hkaGpUVG4HudH A4PoK6IfTJEipS+cygzEUrjAf5p+XaAba64GT7Mnvbr43NCo4XzFtUrRBlTPuZHoLsvR RHDQ== X-Gm-Message-State: AHPjjUhXrux6fijwQiYogtwO22KAuEeEQHHZG0y1eelBXThHIC9mjJm0 qv4vBD/2bPi9Zih9Ulnnd9FIwUZfILz0hzWZev6/Ra2E X-Google-Smtp-Source: AOwi7QBP50QGSGtwSSzopnPo4yJC5fS5PADQop0v+lPYxGMzIRyRc4xS3n839XLmJNqqLK6FFSAIUNyqQi/Ff+XKvmo= X-Received: by 10.28.167.8 with SMTP id q8mr3263977wme.98.1505138578242; Mon, 11 Sep 2017 07:02:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.28.142.65 with HTTP; Mon, 11 Sep 2017 07:02:57 -0700 (PDT) From: Vick Khera Date: Mon, 11 Sep 2017 10:02:57 -0400 Message-ID: Subject: entropy lockup To: FreeBSD Stable List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2017 14:03:01 -0000 I just had a VM running in Google's cloud become totally useless, and I tracked it down to the save-entropy operation. Basically this process was sucking up all CPU, even when nothing else running other than my ssh shell: % ps axuw803 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND operator 803 100.0 0.1 8336 2096 - RL 08:55 48:20.14 dd if=/dev/random of=saved-entropy.1 bs=4096 count=1 The process is unkillable, and I cannot even get the system to shut down. That has been hanging for about 10 minutes so far, with the last output being System shutdown time has arrive90 second watchdSep 11 09:50:02 yertle init: /bin/sh on /etc/rc.shutdown terminated abnormally, going to single user mode Sep 11 09:50:47 init: some processes would not die; ps axl advised Waiting (max 60 seconds) for system process `vnlru' to stop... done Waiting (max 60 seconds) for system process `bufdaemon' to stop... done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining... 4 4 4 4 4 4 4 timed out 2 2 2 2 2 2 2 Running FreeBSD 11.1-p1 on a 1CPU standard machine in GCE. What's the proper recovery from this kind of lockup, or how to prevent it? I've never encountered this on a bare metal system, or other KVM based machines. From owner-freebsd-stable@freebsd.org Mon Sep 11 23:20:51 2017 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 8F41FE0687B for ; Mon, 11 Sep 2017 23:20:51 +0000 (UTC) (envelope-from morgan.s.reed@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6B16B77817 for ; Mon, 11 Sep 2017 23:20:51 +0000 (UTC) (envelope-from morgan.s.reed@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6743AE06879; Mon, 11 Sep 2017 23:20:51 +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 66F01E06878 for ; Mon, 11 Sep 2017 23:20:51 +0000 (UTC) (envelope-from morgan.s.reed@gmail.com) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (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 2042577815 for ; Mon, 11 Sep 2017 23:20:51 +0000 (UTC) (envelope-from morgan.s.reed@gmail.com) Received: by mail-qt0-x230.google.com with SMTP id q8so22353606qtb.5 for ; Mon, 11 Sep 2017 16:20:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pFqHRwmZOJb9tsGzYxwU/a9BNoQYq74G7o5erGGNj5w=; b=nwj1qWLVhuvl0ctuDmktnyqNgROwksTKsWWGAT5InGOOi5zZMdneO/w2SJGmQjV3YJ Eq0kFlVEQKwmQE3g/Zi+lsqxwe4UcptOEsLlDCa8Sb0wfmGdmDv8XJqOgTqMSr3RsndF 0sZcs6o1O5u5HZsqV5EKUxMA/Re2F283/fHqWOIKsFgWAgwdyX8/ZZ1RpG0ttW61CgKl wPel8hydyIVXr80OFVLhp0E1YrXUvQSwZLm2rI/dJZQsuBACTfKLUvZ2t3VwhEauXwYN bGFC/uy/CYZZecuq2egZwGUuDom7vmzdbbTlGeitvBbfiq1Op1tlySe0c3lFYnRzADAd sh5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pFqHRwmZOJb9tsGzYxwU/a9BNoQYq74G7o5erGGNj5w=; b=HR6I6vY1YMtL4vc7nI01D1uMQpDGUYs/rxKBJbdzWMeONWNhbaTG55JV46Tb976FvV Lbhys/bZ0RyzIzSiGMIK+1GENxIgTVb0XqrceZf1BWTwSXJIbbCJkg47l49ZYQs8MKuU Y3WRhybJG62FarZr+wPKRRVvNtX0s/m380pJ4MJSpolZ7tZV/NRu6rvkYPWwY5Cb4r6v O2uvFbeCk1dBgzy2TU1dt8WWCgpTzbF5889I4EEcS+3V3W+mdwWLNwaz9pXDJLW/mZt0 AdEposUwjfyhrY9thbRGugvMxOF0Cw7t71Pz/5m0BVefC6XNTtKSrtGI6HjiFyVqlNM3 1kYQ== X-Gm-Message-State: AHPjjUgE7zb5It5NYHi2OFkIV3oaJcDA8CKI919beFngMX6yXYA/gMi6 xPVJhdGRXldcLyEX1pzb0j7pbwBcI1Xq X-Google-Smtp-Source: AOwi7QBx5tMNAKjIC3IgJhzAdr5KMoxPnQG4sR9MUJgnuZkimi2xRKxY6Wz2o0OB2mQg4duYp1NDY2z+FiSN4nUlNng= X-Received: by 10.200.25.215 with SMTP id s23mr12672156qtk.229.1505172050173; Mon, 11 Sep 2017 16:20:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.91.201 with HTTP; Mon, 11 Sep 2017 16:20:29 -0700 (PDT) In-Reply-To: References: From: Morgan Reed Date: Tue, 12 Sep 2017 09:20:29 +1000 Message-ID: Subject: Re: entropy lockup To: Vick Khera Cc: FreeBSD Stable List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2017 23:20:51 -0000 In all likelihood the process wasn't "hung" per-se, more likely random hadn't been seeded yet and as such you *can't* get 4096b of entropy out of it (so the process was attempting to do its job, just nothing on the device). The issue is basically that there are very few "good" entropy sources in a VM environment, and as such (particularly on a machine which is only running SSH) there's not enough data available to seed random. Check 'man 4 random' for some discussion. On Tue, Sep 12, 2017 at 12:02 AM, Vick Khera wrote: > I just had a VM running in Google's cloud become totally useless, and I > tracked it down to the save-entropy operation. > > Basically this process was sucking up all CPU, even when nothing else > running other than my ssh shell: > > % ps axuw803 > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > operator 803 100.0 0.1 8336 2096 - RL 08:55 48:20.14 dd > if=/dev/random of=saved-entropy.1 bs=4096 count=1 > > > The process is unkillable, and I cannot even get the system to shut down. > That has been hanging for about 10 minutes so far, with the last output > being > > System shutdown time has arrive90 second watchdSep 11 09:50:02 yertle init: > /bin/sh on /etc/rc.shutdown terminated abnormally, going to single user > mode > Sep 11 09:50:47 init: some processes would not die; ps axl advised > Waiting (max 60 seconds) for system process `vnlru' to stop... done > Waiting (max 60 seconds) for system process `bufdaemon' to stop... done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining... 4 4 4 4 4 4 4 timed out > 2 2 2 2 2 2 2 > > > Running FreeBSD 11.1-p1 on a 1CPU standard machine in GCE. > > What's the proper recovery from this kind of lockup, or how to prevent it? > I've never encountered this on a bare metal system, or other KVM based > machines. > _______________________________________________ > 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" > -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 From owner-freebsd-stable@freebsd.org Mon Sep 11 23:34:30 2017 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 9860DE07481 for ; Mon, 11 Sep 2017 23:34:30 +0000 (UTC) (envelope-from ian@freebsd.org) 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 768607C1FD for ; Mon, 11 Sep 2017 23:34:30 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 72AC4E0747F; Mon, 11 Sep 2017 23:34:30 +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 72291E0747E for ; Mon, 11 Sep 2017 23:34:30 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from nov-007-i455.relay.mailchannels.net (nov-007-i455.relay.mailchannels.net [46.232.183.9]) (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 8B09E7C1F7 for ; Mon, 11 Sep 2017 23:34:23 +0000 (UTC) (envelope-from ian@freebsd.org) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 9483F5C1422 for ; Mon, 11 Sep 2017 23:34:13 +0000 (UTC) Received: from outbound1a.eu.mailhop.org (unknown [100.96.146.203]) (Authenticated sender: duocircle) by relay.mailchannels.net (Postfix) with ESMTPA id EDD6F5C10D3 for ; Mon, 11 Sep 2017 23:34:12 +0000 (UTC) X-Sender-Id: _forwarded-from|73.78.92.27 Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [172.20.107.195]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.9.14); Mon, 11 Sep 2017 23:34:13 +0000 X-MC-Relay: Junk X-MailChannels-SenderId: _forwarded-from|73.78.92.27 X-MailChannels-Auth-Id: duocircle X-Interest-Left: 0e0a14e077d5eb95_1505172853400_212957668 X-MC-Loop-Signature: 1505172853400:647474909 X-MC-Ingress-Time: 1505172853400 X-MHO-User: b3487f62-9749-11e7-a893-25625093991c X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id b3487f62-9749-11e7-a893-25625093991c; Mon, 11 Sep 2017 23:34:06 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id v8BNY5Nm013618; Mon, 11 Sep 2017 17:34:05 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1505172845.32063.90.camel@freebsd.org> Subject: Re: entropy lockup From: Ian Lepore To: Morgan Reed , Vick Khera Cc: FreeBSD Stable List Date: Mon, 11 Sep 2017 17:34:05 -0600 In-Reply-To: References: Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2017 23:34:30 -0000 On Tue, 2017-09-12 at 09:20 +1000, Morgan Reed wrote: > In all likelihood the process wasn't "hung" per-se, more likely > random > hadn't been seeded yet and as such you *can't* get 4096b of entropy > out of > it (so the process was attempting to do its job, just nothing on the > device). >=20 > The issue is basically that there are very few "good" entropy sources > in a > VM environment, and as such (particularly on a machine which is only > running SSH) there's not enough data available to seed random. >=20 > Check 'man 4 random' for some discussion. >=20 The save-entropy files get written from a crontab entry. =A0That means the system is already up and running, which means it's well past the point of hanging because it needs to be seeded. =A0Once it is seeded, it can never "run out of entropy". So all in all, this is a genuine problem of some sort. =A0The fact that the save-entropy process has accumulated 48+ minutes of cpu time is another problem indicator. =A0The process state is RL, runnable and waiting to acquire a lock, which seems contradictory (unless that means it's waiting for a spinlock maybe). -- Ian > On Tue, Sep 12, 2017 at 12:02 AM, Vick Khera wrote: >=20 > >=20 > > I just had a VM running in Google's cloud become totally useless, > > and I > > tracked it down to the save-entropy operation. > >=20 > > Basically this process was sucking up all CPU, even when nothing > > else > > running other than my ssh shell: > >=20 > > % ps axuw803 > > USER=A0=A0=A0=A0=A0PID=A0=A0%CPU %MEM=A0=A0VSZ=A0=A0RSS TT=A0=A0STAT = STARTED=A0=A0=A0=A0=A0TIME COMMAND > > operator 803 100.0=A0=A00.1 8336 2096=A0=A0-=A0=A0RL=A0=A0=A008:55=A0= =A0=A048:20.14 dd > > if=3D/dev/random of=3Dsaved-entropy.1 bs=3D4096 count=3D1 > >=20 > >=20 > > The process is unkillable, and I cannot even get the system to shut > > down. > > That has been hanging for about 10 minutes so far, with the last > > output > > being > >=20 > > System shutdown time has arrive90 second watchdSep 11 09:50:02 > > yertle init: > > /bin/sh on /etc/rc.shutdown terminated abnormally, going to single > > user > > mode > > Sep 11 09:50:47 init: some processes would not die; ps axl advised > > Waiting (max 60 seconds) for system process `vnlru' to stop... done > > Waiting (max 60 seconds) for system process `bufdaemon' to stop... > > done > > Waiting (max 60 seconds) for system process `syncer' to stop... > > Syncing disks, vnodes remaining... 4 4 4 4 4 4 4 timed out > > 2 2 2 2 2 2 2 > >=20 > >=20 > > Running FreeBSD 11.1-p1 on a 1CPU standard machine in GCE. > >=20 > > What's the proper recovery from this kind of lockup, or how to > > prevent it? > > I've never encountered this on a bare metal system, or other KVM > > based > > machines. > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebs > > d.org" > >=20 >=20 >=20 From owner-freebsd-stable@freebsd.org Tue Sep 12 06:28:00 2017 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 94008E1BD99 for ; Tue, 12 Sep 2017 06:28:00 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu1176c.smtpx.saremail.com (cu1176c.smtpx.saremail.com [195.16.148.151]) (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 02FE263E6A for ; Tue, 12 Sep 2017 06:27:59 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.41] (unknown [192.148.167.11]) by proxypop02.sare.net (Postfix) with ESMTPA id 7AA4A9DD33A; Tue, 12 Sep 2017 08:27:55 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusually high "Wired" memory From: Borja Marcos In-Reply-To: <280948FF-C17D-44FD-B57B-55EBD9848BDB@sarenet.es> Date: Tue, 12 Sep 2017 08:27:54 +0200 Cc: FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <532F967A-A839-4789-953D-29BC8D3AC350@sarenet.es> References: <853D9198-6AB7-496F-B1C2-F8C5814114B6@sarenet.es> <280948FF-C17D-44FD-B57B-55EBD9848BDB@sarenet.es> To: Borja Marcos X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 06:28:00 -0000 > On 11 Sep 2017, at 11:25, Borja Marcos wrote: >=20 >> Since I=E2=80=99ve updated a machine to 11.1-STABLE I am seeing a = rather unusual growth of Wired memory. >>=20 >> Any hints on what might have changed from 11-RELEASE to 11.1-RELEASE = and 11.1-STABLE? vmstat -z and vmstat -m follow % vmstat -z ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP UMA Kegs: 384, 0, 126, 4, 126, 0, 0 UMA Zones: 4736, 0, 143, 0, 143, 0, 0 UMA Slabs: 80, 0, 89605, 70495,14041377, 0, 0 UMA Hash: 256, 0, 4, 11, 15, 0, 0 4 Bucket: 32, 0, 27, 2348, 4568149, 0, 0 6 Bucket: 48, 0, 0, 0, 470783, 0, 0 8 Bucket: 64, 0, 0, 0, 6493588, 13, 0 12 Bucket: 96, 0, 0, 0, 2905574, 2, 0 16 Bucket: 128, 0, 28, 747, 1375609, 0, 0 32 Bucket: 256, 0, 0, 0, 1342213,14372, = 0 64 Bucket: 512, 0, 0, 0, 4462146,120046, = 0 128 Bucket: 1024, 0, 0, 0, 846934,11702, = 0 256 Bucket: 2048, 0, 0, 0, 402301,3139, 0 vmem btag: 56, 0, 18945, 10875, 367860, 216, 0 VM OBJECT: 240, 0, 28017, 37279, 5670269, 0, 0 RADIX NODE: 144, 0, 27077, 26410,19244770, 0, 0 MAP: 240, 0, 3, 61, 3, 0, 0 KMAP ENTRY: 128, 0, 6, 87, 6, 0, 0 MAP ENTRY: 128, 0, 4327, 3454, 5294482, 0, 0 VMSPACE: 2504, 0, 28, 128, 3950, 0, 0 fakepg: 104, 0, 4, 148, 4, 0, 0 mt_zone: 16400, 0, 307, 0, 307, 0, 0 16: 16, 0, 40214, 36843,86753581, 0, 0 32: 32, 0, 29825, 43925,312018796, 0, = 0 64: 64, 0, 44824, 186002,119290303, 0, = 0 128: 128, 0, 14044, 17669,192809899, 0, = 0 256: 256, 0, 26953, 42242,139829494, 0, = 0 512: 512, 0, 169943, 212729,97319297, 0, 0 1024: 1024, 0, 2844, 240,113460194, 0, = 0 2048: 2048, 0, 204, 40,134422120, 0, = 0 4096: 4096, 0, 8295, 170,19109860, 0, 0 8192: 8192, 0, 157, 12, 5847918, 0, 0 16384: 16384, 0, 8091, 78, 5635701, 0, 0 32768: 32768, 0, 127, 13, 3738362, 0, 0 65536: 65536, 0, 67, 21, 4328503, 0, 0 64 pcpu: 8, 0, 1764, 796, 2125, 0, 0 SLEEPQUEUE: 80, 0, 1691, 975, 1691, 0, 0 Files: 80, 0, 1111, 4789,13481817, 0, 0 filedesc0: 1104, 0, 50, 34, 3971, 0, 0 TURNSTILE: 136, 0, 1691, 1009, 1691, 0, 0 rl_entry: 40, 0, 696, 3104, 696, 0, 0 umtx pi: 96, 0, 0, 0, 0, 0, 0 umtx_shm: 88, 0, 0, 0, 0, 0, 0 MAC labels: 40, 0, 0, 0, 0, 0, 0 PROC: 1416, 0, 49, 311, 3970, 0, 0 THREAD: 1456, 0, 1458, 232, 35807, 0, 0 cpuset: 96, 0, 933, 1199, 1985, 0, 0 audit_record: 1248, 0, 0, 0, 0, 0, 0 mbuf_packet: 256, 1677735, 16377, 0,14185830, 0, = 0 mbuf: 256, 1677735, 5, 2008,14156009, 0, = 0 mbuf_cluster: 2048, 262144, 16377, 451, 2251293, 0, 0 mbuf_jumbo_page: 4096, 131072, 1, 12, 601300, 0, 0 mbuf_jumbo_9k: 9216, 38836, 0, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 21845, 0, 0, 0, 0, 0 g_bio: 376, 0,15235172, 248,477839025, 0, = 0 ttyinq: 160, 0, 135, 190, 735, 0, 0 ttyoutq: 256, 0, 72, 93, 392, 0, 0 FPU_save_area: 832, 0, 0, 0, 0, 0, 0 CTL IO: 672, 0, 0, 0, 0, 0, 0 beio: 368, 0, 0, 0, 0, 0, 0 taskq_zone: 48, 0, 0, 83, 4883426, 0, 0 VNODE: 472, 0, 116663, 57169, 7020248, 0, 0 VNODEPOLL: 120, 0, 0, 0, 0, 0, 0 BUF TRIE: 144, 0, 85, 52619, 111, 0, 0 S VFS Cache: 108, 0, 97780, 129125,12378111, 0, 0 STS VFS Cache: 148, 0, 0, 0, 0, 0, 0 L VFS Cache: 328, 0, 26016, 1452, 94458, 0, 0 LTS VFS Cache: 368, 0, 0, 0, 0, 0, 0 NAMEI: 1024, 0, 0, 4,434993266, 0, = 0 rentr: 24, 0, 0, 0, 0, 0, 0 DIRHASH: 1024, 0, 0, 0, 1265, 0, 0 NCLNODE: 576, 0, 0, 0, 0, 0, 0 Mountpoints: 816, 0, 17, 153, 17, 0, 0 pipe: 760, 0, 196, 29, 2200, 0, 0 range_seg_cache: 64, 0, 75978, 45170,15585219, 0, 0 metaslab_alloc_trace_cache: 64, 0, 0, 248, 9182890, = 0, 0 zio_cache: 1040, 0, 74, 592,242729543, 0, = 0 zio_link_cache: 48, 0, 8, 656,157320326, 0, = 0 lz4_ctx: 16384, 0, 0, 16, 3997609, 0, 0 abd_chunk: 4096, 0, 14581, 0,152519233, 0, = 0 sa_cache: 144, 0, 96841, 100286, 7578526, 0, 0 dnode_t: 728, 0, 197018, 167132, 6128636, 0, 0 arc_buf_hdr_t_full: 224, 0, 11863, 21865,31209006, 0, 0 arc_buf_hdr_t_l2only: 88, 0, 0, 0, 0, 0, = 0 arc_buf_t: 64, 0, 8919, 32001,16054622, 0, 0 dmu_buf_impl_t: 232, 0, 177685, 251803,18010985, 0, 0 zil_lwb_cache: 200, 0, 75, 165, 3881459, 0, 0 zfs_znode_cache: 264, 0, 96841, 78884, 7000414, 0, 0 procdesc: 136, 0, 0, 0, 0, 0, 0 AIO: 224, 0, 0, 0, 0, 0, 0 AIOP: 32, 0, 0, 0, 0, 0, 0 AIOCB: 752, 0, 0, 0, 0, 0, 0 AIOL: 128, 0, 0, 0, 0, 0, 0 AIOLIO: 280, 0, 0, 0, 0, 0, 0 ksiginfo: 112, 0, 305, 3125, 70925, 0, 0 itimer: 352, 0, 0, 0, 0, 0, 0 KNOTE: 128, 0, 283, 399,14191220, 0, 0 socket: 864, 260128, 67, 389, 20761, 0, 0 ipq: 56, 8236, 0, 0, 0, 0, 0 udp_inpcb: 464, 260128, 9, 15, 15472, 0, 0 udpcb: 32, 260250, 9, 241, 15472, 0, 0 tcp_inpcb: 464, 260128, 43, 29, 431, 0, 0 tcpcb: 1040, 260130, 43, 2, 431, 0, 0 tcptw: 88, 27810, 0, 0, 221, 0, 0 syncache: 168, 15364, 0, 0, 85, 0, 0 hostcache: 128, 15376, 2, 60, 2, 0, 0 sackhole: 32, 0, 0, 0, 0, 0, 0 tcpreass: 40, 16400, 0, 300, 6, 0, 0 sctp_ep: 1488, 260128, 0, 0, 0, 0, 0 sctp_asoc: 2408, 40000, 0, 0, 0, 0, 0 sctp_laddr: 48, 80012, 0, 0, 4, 0, 0 sctp_raddr: 736, 80000, 0, 0, 0, 0, 0 sctp_chunk: 152, 400010, 0, 0, 0, 0, 0 sctp_readq: 152, 400010, 0, 0, 0, 0, 0 sctp_stream_msg_out: 112, 400015, 0, 0, 0, 0, 0 sctp_asconf: 40, 400000, 0, 0, 0, 0, 0 sctp_asconf_ack: 48, 400060, 0, 0, 0, 0, 0 udplite_inpcb: 464, 260128, 0, 0, 0, 0, 0 ripcb: 464, 260128, 0, 0, 14, 0, 0 unpcb: 240, 260128, 14, 114, 4837, 0, 0 rtentry: 208, 0, 12, 121, 14, 0, 0 IPFW counters: 16, 0, 12, 500, 12, 0, 0 IPFW dynamic rule: 128, 16399, 0, 0, 0, 0, 0 selfd: 64, 0, 203, 2401, 736707, 0, 0 SWAPMETA: 288, 1011972, 23270, 1326, 3620240, 0, = 0 FFS inode: 152, 0, 19743, 303, 19749, 0, 0 FFS1 dinode: 128, 0, 0, 0, 0, 0, 0 FFS2 dinode: 256, 0, 19743, 222, 19749, 0, % vmstat -m Type InUse MemUse HighUse Requests Size(s) CAM periph 18 5K - 40 16,32,64,128,256 CAM I/O Scheduler 8 1K - 8 128 pci_link 16 2K - 16 32,128 acpi_perf 32 8K - 32 256 kbdmux 6 22K - 6 16,512,1024,2048,16384 LED 8 1K - 8 16,128 mps 20 479K - 90 = 16,32,64,128,256,512,1024,4096,8192,65536 entropy 0 0K - 279 4096 UART 6 5K - 6 16,1024 CAM queue 15 130K - 52 16,32,64,128,512,16384 USB 56 111K - 68 = 16,32,128,256,512,1024,2048,4096,16384,32768 USBdev 48 15K - 48 32,64,128,256,512,4096 DEVFS3 154 39K - 158 256 DEVFS1 129 65K - 132 512 DEVFS_RULE 55 26K - 55 64,512 DEVFS 16 1K - 17 16,128 DEVFSP 2 1K - 2 64 NFSD V4client 1 1K - 1 256 NFSD lckfile 1 1K - 1 256 NFSD session 1 1K - 1 1024 pfs_nodes 21 6K - 21 256 pfs_vncache 4 1K - 4 64 GEOM 147 29K - 596441 = 16,32,64,128,256,512,1024,2048,16384 raid_data 0 0K - 102 32,128,256 isadev 6 1K - 6 128 ctlmem 9 193K - 9 16,32,128,65536 cdev 4 1K - 4 256 filedesc 7 221K - 39 = 32,64,128,256,4096,16384,32768,65536 sigio 1 1K - 1 64 filecaps 0 0K - 38 16,64 kdtrace 1241 302K - 43495 64,256 kenv 119 12K - 122 16,32,64,128,8192 kqueue 432 1153K - 4424 64,256,2048,4096,8192 proc-args 281 10K - 20977 16,32,64,128,256 Fail Points 0 0K - 40 1024 hhook 13 4K - 13 256 ithread 322 53K - 322 32,128,256 KTRACE 100 13K - 100 128 linker 93 27K - 102 = 16,32,64,128,256,512,1024,2048,4096,8192 lockf 201 25K - 28143 64,128 loginclass 2 1K - 3 64 cache 1 1K - 1 32 devbuf 3162 10181K - 3701 = 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536 temp 151 12K - 98598294 = 16,32,64,128,256,512,1024,2048,4096,8192,16384,65536 module 198 25K - 198 128 mtx_pool 2 16K - 2 8192 osd 64 2K - 356 16,32,64,128,256 pmchooks 1 1K - 1 128 pgrp 25 4K - 692 128 session 24 3K - 630 128 proc 2 4K - 2 2048 subproc 409 373K - 4350 512,4096 cred 41 11K - 6082 256 plimit 23 6K - 9420 256 uidinfo 5 1K - 578 128,512 CAM dev queue 4 1K - 4 64 sysctl 0 0K - 226317 16,32,64 sysctloid 11418 585K - 11643 16,32,64,128 sysctltmp 0 0K - 872 16,32,64,128,256,1024 scsi_da 1 1K - 137 16,32,64,512 tidhash 1 4K - 1 4096 callout 33 9352K - 33 =20 umtx 3380 423K - 3380 128 p1003.1b 1 1K - 1 16 SWAP 2 4373K - 2 64 bus 1136 135K - 7806 16,32,64,128,256,512,1024 bus-sc 208 418K - 2527 = 16,32,128,256,512,1024,2048,4096,16384,65536 devstat 8 17K - 8 32,4096 eventhandler 100 8K - 100 64,128 taskqueue 101 26K - 101 16,32,256,8192 kobj 92 368K - 261 4096 Per-cpu 1 1K - 1 32 rman 340 36K - 788 32,128 sbuf 1 1K - 14277479 = 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536 toponodes 84 11K - 84 128 stack 0 0K - 402 256 taskqueue 360 42K - 663 16,32,64,128,256 Unitno 28 2K - 68456 32,64 vmem 3 320K - 9 256,16384,32768,65536 ioctlops 0 0K - 1084 256,512,1024 select 174 22K - 174 128 iov 0 0K - 33365941 16,64,128,256,512 msg 4 30K - 4 2048,4096,8192,16384 sem 4 106K - 4 2048,4096 shm 1 32K - 1 32768 tty 21 21K - 25 1024,2048 pts 2 1K - 2 256 mbuf_tag 0 0K - 6 32 shmfd 1 8K - 1 8192 soname 4 1K - 43270 16,32,128 pcb 38 1175K - 13620 16,32,128,1024,2048,8192 acl 0 0K - 45 4096 vfscache 4 8833K - 5 512 vfs_hash 1 2048K - 2 =20 vnodes 1 1K - 1 256 mount 196 8K - 468 16,32,64,128,256 statfs 0 0K - 740359 512 vnodemarker 0 0K - 36693 512 fadvise 0 0K - 1 32 arc4random 1 16K - 1 16384 BPF 5 1K - 5 128 ifnet 6 11K - 6 128,2048 ifaddr 82 17K - 82 = 16,32,64,128,256,512,2048,4096 ether_multi 22 2K - 22 16,32,64 clone 6 1K - 6 128 lltable 24 7K - 36 256,512 routetbl 25 4K - 28 32,64,128,512 igmp 5 1K - 5 128 in_mfilter 2 2K - 2 1024 in_multi 3 1K - 3 256 ip_moptions 4 1K - 4 64,256 sctp_a_it 0 0K - 4 16 sctp_vrf 1 1K - 1 64 sctp_ifa 5 1K - 5 128 sctp_ifn 3 1K - 3 128 sctp_iter 0 0K - 4 256 hostcache 1 32K - 1 32768 tcpfunc 1 1K - 1 32 syncache 1 68K - 1 =20 in6_mfilter 1 1K - 1 1024 in6_multi 15 2K - 15 32,256 ip6_moptions 2 1K - 2 32,256 ip6opt 3 1K - 3 256 mld 5 1K - 5 128 ip6ndp 6 1K - 6 64,256 IpFw/IpAcct 33 52K - 50 = 16,32,64,128,256,512,1024,2048,4096,8192,16384 rpc 2 16K - 2 8192 audit_evclass 187 6K - 232 32 pagedep 1 256K - 7 256 inodedep 1 2048K - 17 512 bmsafemap 1 8K - 11 256,8192 newblk 1 2048K - 8 256 freeblks 0 0K - 7 128 freefile 0 0K - 6 64 diradd 0 0K - 12 128 dirrem 0 0K - 12 128 freework 1 1K - 8 128,256 jaddref 0 0K - 12 128 jremref 0 0K - 12 128 jnewblk 0 0K - 7 128 jseg 0 0K - 11 128 jsegdep 0 0K - 31 64 sbdep 0 0K - 5 64 jblocks 2 1K - 2 128,256 softdep 1 1K - 1 512 ufs_dirhash 37 19K - 113 = 16,32,64,128,256,512,1024,8192 ufs_mount 3 13K - 3 512,4096,8192 vm_pgdata 2 1025K - 2 128 UMAHash 11 4279K - 52 = 512,1024,2048,4096,8192,16384,32768,65536 acpiintr 1 1K - 1 64 acpica 2572 248K - 87354 = 16,32,64,128,256,512,1024,2048 acpitask 1 64K - 1 65536 memdesc 1 4K - 1 4096 acpisem 93 12K - 93 128 apmdev 1 1K - 1 128 madt_table 0 0K - 1 4096 acpidev 67 5K - 67 64 CAM SIM 4 1K - 4 256 CAM XPT 81 8K - 1588085 = 16,32,64,128,256,512,1024,2048,65536 CAM DEV 11 22K - 21 2048 CAM CCB 17 34K - 136755855 2048 io_apic 3 6K - 3 2048 CAM path 19 1K - 85 32 MCA 65 21K - 65 128,256,512 msi 45 6K - 45 128 nexusdev 3 1K - 3 16 solaris 315427 375503K - 960543367 = 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536 kstat_data 8 1K - 8 64 sfs_nodes 26 13K - 26 512 fdesc_mount 1 1K - 1 16 From owner-freebsd-stable@freebsd.org Tue Sep 12 13:40:26 2017 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 1642DE09E0E for ; Tue, 12 Sep 2017 13:40:26 +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 B4FFB71E1F for ; Tue, 12 Sep 2017 13:40:25 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3xs5X705zvz1R0 for ; Tue, 12 Sep 2017 15:40:23 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received:received:received; s=jakla4; t= 1505223621; x=1507815622; bh=0831rpM59laQ6taHf++1RVSZqaYPCwKb5Hw 7LWxCdIE=; b=Gv081uflD9/GnDe+utdsCu1fIaZ3UDqWiPOPct1QGngkEtMJJ2m SEgm8QyiQmK1HnreBGiQsLdDl+t7jR1kjRITH98aL6Ev40pEP8RdPZ4zpEveUbP2 roncGWe2scu75YyGUaG4Sx5eS7klpJvffrmYA6H6+u5j1xZyzLndcBIY= 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 3DurVr08lw7b for ; Tue, 12 Sep 2017 15:40:21 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3xs5X54cYmz1Qy for ; Tue, 12 Sep 2017 15:40:21 +0200 (CEST) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3xs5X54P38zCW for ; Tue, 12 Sep 2017 15:40:21 +0200 (CEST) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by nabiralnik.ijs.si with HTTP (HTTP/1.1 POST); Tue, 12 Sep 2017 15:40:21 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 12 Sep 2017 15:40:21 +0200 From: Mark Martinec To: freebsd-stable@freebsd.org Subject: 11.1 coredumping in sendfile, as used by a uwsgi process Organization: Jozef Stefan Institute Message-ID: <5f5dbe776ed9600b6b5f9ed2750f8e1d@ijs.si> X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 13:40:26 -0000 A couple of days ago I have upgraded an Intel box from FreeBSD 10.3 to 11.1-RELEASE-p1, and reinstalled all the packages, built on the same OS version. This host is running nginx web server with an uwsgi as a backend. The file system is ZFS (recent as of 10.3, zpool not yet upgraded to new 11.1 features). Ever since the upgrade, this host is crashing/rebooting two or three times per day. The reported crash location is always the same: it is in a sendfile function (same addresses each time), the running process is always uwsgi: Sep 12 15:03:12 xxx syslogd: kernel boot file is /boot/kernel/kernel Sep 12 15:03:12 xxx kernel: [22677] Sep 12 15:03:12 xxx kernel: [22677] Sep 12 15:03:12 xxx kernel: [22677] Fatal trap 12: page fault while in kernel mode Sep 12 15:03:12 xxx kernel: [22677] cpuid = 7; apic id = 07 Sep 12 15:03:12 xxx kernel: [22677] fault virtual address = 0xe8 Sep 12 15:03:12 xxx kernel: [22677] fault code = supervisor write data, page not present Sep 12 15:03:12 xxx kernel: [22677] instruction pointer = 0x20:0xffffffff80afefb2 Sep 12 15:03:12 xxx kernel: [22677] stack pointer = 0x28:0xfffffe02397da5a0 Sep 12 15:03:12 xxx kernel: [22677] frame pointer = 0x28:0xfffffe02397da5e0 Sep 12 15:03:12 xxx kernel: [22677] code segment = base 0x0, limit 0xfffff, type 0x1b Sep 12 15:03:12 xxx kernel: [22677] = DPL 0, pres 1, long 1, def32 0, gran 1 Sep 12 15:03:12 xxx kernel: [22677] processor eflags = interrupt enabled, resume, IOPL = 0 Sep 12 15:03:12 xxx kernel: [22677] current process = 34504 (uwsgi) Sep 12 15:03:12 xxx kernel: [22677] trap number = 12 Sep 12 15:03:12 xxx kernel: [22677] panic: page fault Sep 12 15:03:12 xxx kernel: [22677] cpuid = 7 Sep 12 15:03:12 xxx kernel: [22677] KDB: stack backtrace: Sep 12 15:03:12 xxx kernel: [22677] #0 0xffffffff80aada97 at kdb_backtrace+0x67 Sep 12 15:03:12 xxx kernel: [22677] #1 0xffffffff80a6bb76 at vpanic+0x186 Sep 12 15:03:12 xxx kernel: [22677] #2 0xffffffff80a6b9e3 at panic+0x43 Sep 12 15:03:12 xxx kernel: [22677] #3 0xffffffff80edf832 at trap_fatal+0x322 Sep 12 15:03:12 xxx kernel: [22677] #4 0xffffffff80edf889 at trap_pfault+0x49 Sep 12 15:03:12 xxx kernel: [22677] #5 0xffffffff80edf0c6 at trap+0x286 Sep 12 15:03:12 xxx kernel: [22677] #6 0xffffffff80ec3641 at calltrap+0x8 Sep 12 15:03:12 xxx kernel: [22677] #7 0xffffffff80a6a2af at sendfile_iodone+0xbf Sep 12 15:03:12 xxx kernel: [22677] #8 0xffffffff80a69eae at vn_sendfile+0x124e Sep 12 15:03:12 xxx kernel: [22677] #9 0xffffffff80a6a4dd at sendfile+0x13d Sep 12 15:03:12 xxx kernel: [22677] #10 0xffffffff80ee0394 at amd64_syscall+0x6c4 Sep 12 15:03:12 xxx kernel: [22677] #11 0xffffffff80ec392b at Xfast_syscall+0xfb Sep 12 15:03:12 xxx kernel: [22677] Uptime: 6h17m57s Sep 12 15:03:12 xxx kernel: [22677] Dumping 983 out of 8129 MB:..2%..12%..22%..31%..41%..51%..61%..72%..82%..92%Copyright (c) 1992-2017 The FreeBSD Project. Sep 12 15:03:12 xxx kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Sep 12 15:03:12 xxx kernel: The Regents of the University of California. All rights reserved. Sep 12 15:03:12 xxx kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Sep 12 15:03:12 xxx kernel: FreeBSD 11.1-RELEASE-p1 #0: Wed Aug 9 11:55:48 UTC 2017 [...] Sep 12 15:03:12 xxx savecore: reboot after panic: page fault Sep 12 15:03:12 xxx savecore: writing core to /var/crash/vmcore.4 This host with the same services was very stable under 10.3, same ZFS pool. We have several other hosts running 11.1 with no incidents, running various services (but admittedly no other host has a comparably busy web server). Interestingly the nginx has a sendfile feature enabled too, but this does not cause a crash (on this or other hosts), only the sendfile as used by uwsgi seems to be the problem. For the time being I have disabled the use of sendfile in uwsgi, we'll see is this avoids the trouble. Suggestions? Mark From owner-freebsd-stable@freebsd.org Tue Sep 12 13:46:26 2017 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 449B4E0A57F for ; Tue, 12 Sep 2017 13:46:26 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::22c]) (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 CCA147256D for ; Tue, 12 Sep 2017 13:46:25 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wr0-x22c.google.com with SMTP id k20so22602493wre.4 for ; Tue, 12 Sep 2017 06:46:25 -0700 (PDT) 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-language; bh=C1u6q1RvucIVAZPSkYEfhIr5c6st7sJinQBTrMP8axs=; b=0OympJ1eomrK6By9/d3pXEetg3wLhCh9jxcWTa3wEiJAOvDrxtsgUXJep7Bx+gn3y9 VmmoBRPQwLAUm+6jOBplccr9ECcJlGLu4B1DdXraIYAwBeqzfqvD4usYSDs6Tyq1ig5b WDglJTh+t6n9Y19T5L7vve3lmfYBwPhvELm1SGsqTwb59AmUsfckF/HcTxNDzFMdEt5h rjChlqemomMgOw8Psno5iFmUWIuZQ641aenY74jtjrxPy68KHsAGaaem7jcU+O+qulr7 SZWsZRGSPcBhV7gqVPrhe0eGrzD46RxxdJJ4yhF8L7uDTAIIYZKPLKjsSnBnzJEkJto6 t71w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=C1u6q1RvucIVAZPSkYEfhIr5c6st7sJinQBTrMP8axs=; b=jgzEixaq17Rfe3xphu1EtvIpdmym1HpXfj7Qd+NDl9QOKUxyjjbFZtAILAeSv/UvXA MNCdc3HL1sJuj/XtNIzaWmKp7KVFLQYNBxo7nAhsYJQjS2mzp17CQckADdQfo/Lkht6+ wVNDjz6oC47MG+sa6ziHHLhqLD79XHtfb3xtXUrra2rP4LhlincEjq7iNFsTfEFIGycg 4B5NhGJbvE6XdoXgcVvAUmNOcnw87IlRcQIfW5bTRe/2tJQH1FiK/r5E/rjk6EBLHlMN JOYALBFEEngGgJmm4wqJWinivbPRqBZYdDNC+oIeD6vlQxbsOYmYpnBnqqma4TWOMgUY Qj1w== X-Gm-Message-State: AHPjjUiGORQd00r+OCfZxXHi45A6gUrF11SSm8wBVHc59sqR+jzUgPDT I+RWVJcGKB6OxA5Z2GAF5w== X-Google-Smtp-Source: ADKCNb4uXv1uL1BBsOd+4hpPFbebADAttYZbZST1hm809QEhMbOhtN9X7DE4aRK2tH2AI76o2mShpw== X-Received: by 10.223.152.6 with SMTP id v6mr12365960wrb.40.1505223983253; Tue, 12 Sep 2017 06:46:23 -0700 (PDT) Received: from [10.10.1.111] ([185.97.61.1]) by smtp.gmail.com with ESMTPSA id f89sm2109274wmh.18.2017.09.12.06.46.21 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Sep 2017 06:46:21 -0700 (PDT) Subject: Re: 11.1 coredumping in sendfile, as used by a uwsgi process To: freebsd-stable@freebsd.org References: <5f5dbe776ed9600b6b5f9ed2750f8e1d@ijs.si> From: Steven Hartland Message-ID: Date: Tue, 12 Sep 2017 14:46:22 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <5f5dbe776ed9600b6b5f9ed2750f8e1d@ijs.si> Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 13:46:26 -0000 Could you post the decoded crash info from /var/crash/... I would also create a bug report: https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Base%20System     Regards     Steve On 12/09/2017 14:40, Mark Martinec wrote: > A couple of days ago I have upgraded an Intel box from FreeBSD 10.3 to > 11.1-RELEASE-p1, and reinstalled all the packages, built on the same > OS version. > This host is running nginx web server with an uwsgi as a backend. > The file system is ZFS (recent as of 10.3, zpool not yet upgraded > to new 11.1 features). > > Ever since the upgrade, this host is crashing/rebooting two or three > times > per day. The reported crash location is always the same: it is in a > sendfile > function (same addresses each time), the running process is always uwsgi: > > > Sep 12 15:03:12 xxx syslogd: kernel boot file is /boot/kernel/kernel > Sep 12 15:03:12 xxx kernel: [22677] > Sep 12 15:03:12 xxx kernel: [22677] > Sep 12 15:03:12 xxx kernel: [22677] Fatal trap 12: page fault while in > kernel mode > Sep 12 15:03:12 xxx kernel: [22677] cpuid = 7; apic id = 07 > Sep 12 15:03:12 xxx kernel: [22677] fault virtual address     = 0xe8 > Sep 12 15:03:12 xxx kernel: [22677] fault code                = > supervisor write data, page not present > Sep 12 15:03:12 xxx kernel: [22677] instruction pointer       = > 0x20:0xffffffff80afefb2 > Sep 12 15:03:12 xxx kernel: [22677] stack pointer             = > 0x28:0xfffffe02397da5a0 > Sep 12 15:03:12 xxx kernel: [22677] frame pointer             = > 0x28:0xfffffe02397da5e0 > Sep 12 15:03:12 xxx kernel: [22677] code segment              = base > 0x0, limit 0xfffff, type 0x1b > Sep 12 15:03:12 xxx kernel: [22677]                   = DPL 0, pres 1, > long 1, def32 0, gran 1 > Sep 12 15:03:12 xxx kernel: [22677] processor eflags  = interrupt > enabled, resume, IOPL = 0 > Sep 12 15:03:12 xxx kernel: [22677] current process           = 34504 > (uwsgi) > Sep 12 15:03:12 xxx kernel: [22677] trap number               = 12 > Sep 12 15:03:12 xxx kernel: [22677] panic: page fault > Sep 12 15:03:12 xxx kernel: [22677] cpuid = 7 > Sep 12 15:03:12 xxx kernel: [22677] KDB: stack backtrace: > Sep 12 15:03:12 xxx kernel: [22677] #0 0xffffffff80aada97 at > kdb_backtrace+0x67 > Sep 12 15:03:12 xxx kernel: [22677] #1 0xffffffff80a6bb76 at vpanic+0x186 > Sep 12 15:03:12 xxx kernel: [22677] #2 0xffffffff80a6b9e3 at panic+0x43 > Sep 12 15:03:12 xxx kernel: [22677] #3 0xffffffff80edf832 at > trap_fatal+0x322 > Sep 12 15:03:12 xxx kernel: [22677] #4 0xffffffff80edf889 at > trap_pfault+0x49 > Sep 12 15:03:12 xxx kernel: [22677] #5 0xffffffff80edf0c6 at trap+0x286 > Sep 12 15:03:12 xxx kernel: [22677] #6 0xffffffff80ec3641 at calltrap+0x8 > Sep 12 15:03:12 xxx kernel: [22677] #7 0xffffffff80a6a2af at > sendfile_iodone+0xbf > Sep 12 15:03:12 xxx kernel: [22677] #8 0xffffffff80a69eae at > vn_sendfile+0x124e > Sep 12 15:03:12 xxx kernel: [22677] #9 0xffffffff80a6a4dd at > sendfile+0x13d > Sep 12 15:03:12 xxx kernel: [22677] #10 0xffffffff80ee0394 at > amd64_syscall+0x6c4 > Sep 12 15:03:12 xxx kernel: [22677] #11 0xffffffff80ec392b at > Xfast_syscall+0xfb > Sep 12 15:03:12 xxx kernel: [22677] Uptime: 6h17m57s > Sep 12 15:03:12 xxx kernel: [22677] Dumping 983 out of 8129 > MB:..2%..12%..22%..31%..41%..51%..61%..72%..82%..92%Copyright (c) > 1992-2017 The FreeBSD Project. > Sep 12 15:03:12 xxx kernel: Copyright (c) 1979, 1980, 1983, 1986, > 1988, 1989, 1991, 1992, 1993, 1994 > Sep 12 15:03:12 xxx kernel: The Regents of the University of > California. All rights reserved. > Sep 12 15:03:12 xxx kernel: FreeBSD is a registered trademark of The > FreeBSD Foundation. > Sep 12 15:03:12 xxx kernel: FreeBSD 11.1-RELEASE-p1 #0: Wed Aug  9 > 11:55:48 UTC 2017 > [...] > Sep 12 15:03:12 xxx savecore: reboot after panic: page fault > Sep 12 15:03:12 xxx savecore: writing core to /var/crash/vmcore.4 > > > This host with the same services was very stable under 10.3, same ZFS > pool. > > We have several other hosts running 11.1 with no incidents, running > various > services (but admittedly no other host has a comparably busy web server). > Interestingly the nginx has a sendfile feature enabled too, but this does > not cause a crash (on this or other hosts), only the sendfile as used > by uwsgi seems to be the problem. > > For the time being I have disabled the use of sendfile in uwsgi, we'll > see > is this avoids the trouble. > > Suggestions? > >   Mark > _______________________________________________ > 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 Sep 12 14:29:52 2017 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 E4628E0C1A3 for ; Tue, 12 Sep 2017 14:29:52 +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 9E89873DB5 for ; Tue, 12 Sep 2017 14:29:52 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.ijs.si (Postfix) with ESMTPS id 3xs6dC0PHKz11v for ; Tue, 12 Sep 2017 16:29:51 +0200 (CEST) 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=1505226589; x=1507818590; bh=VVQ CK/JzkOW7EEM8prF+WEYN6WYPHuNkcg5b83fGQiA=; b=B7Nxg/3hpQLSlxw11X7 04NGSvwMISpd2lE5xYMqaAuLCEtSpGe597fPyKxXm5ATBIWycn+wJWxoOIlJr6G2 Dpc1jByKB6cz3ghHLvA9SQbGN+QLJdwXqoxjHUqAwFRbT+gptm81MeYK9B9TIqJ7 D+T1mycfuDxYc4WIIKLWs7R0= 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 UfT7PDGAlaAj for ; Tue, 12 Sep 2017 16:29:49 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 3xs6d95x7Bz11s for ; Tue, 12 Sep 2017 16:29:49 +0200 (CEST) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 3xs6d95g8Tzr2 for ; Tue, 12 Sep 2017 16:29:49 +0200 (CEST) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by nabiralnik.ijs.si with HTTP (HTTP/1.1 POST); Tue, 12 Sep 2017 16:29:49 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 12 Sep 2017 16:29:49 +0200 From: Mark Martinec To: freebsd-stable@freebsd.org Subject: Re: 11.1 coredumping in sendfile, as used by a uwsgi process Organization: Jozef Stefan Institute In-Reply-To: References: <5f5dbe776ed9600b6b5f9ed2750f8e1d@ijs.si> Message-ID: X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 14:29:53 -0000 2017-09-12 15:46, Steven Hartland wrote: > Could you post the decoded crash info from /var/crash/... Using crashinfo(8) I suppose? > I would also create a bug report: > https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Base%20System Done (with additional info): Bug 222259 - 11.1-R crashing in sendfile syscall, as used by a uwsgi process https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222259 Mark From owner-freebsd-stable@freebsd.org Tue Sep 12 15:06:48 2017 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 96EF6E0DA6B for ; Tue, 12 Sep 2017 15:06:48 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 00204755C0 for ; Tue, 12 Sep 2017 15:06:47 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Tue, 12 Sep 2017 17:03:50 +0200 Authentication-Results: connect.ultra-secure.de; auth=pass (login); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 127.0.0.10 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=127.0.0.10; helo=connect.ultra-secure.de; envelope-from= Received: from connect.ultra-secure.de (webmail [127.0.0.10]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id B956DD0E-8727-488B-AF68-C5FD020E0FDA.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Tue, 12 Sep 2017 17:03:48 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 12 Sep 2017 17:03:47 +0200 From: rainer@ultra-secure.de To: freebsd-stable@freebsd.org Subject: Mirror the freebsd-update server? Message-ID: X-Sender: rainer@ultra-secure.de User-Agent: Roundcube Webmail/1.2.0 X-Haraka-GeoIP: --, , NaNkm X-Haraka-GeoIP-Received: X-Haraka-p0f: os="undefined undefined" link_type="undefined" distance=undefined total_conn=undefined shared_ip=Y X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 252, bad: 0, connections: 252, history: 252, pass:all_good, relaying X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 15:06:48 -0000 Hi, is it possible or even allowed to just mirror one of the freebsd-update servers locally? I don't want to build the patches myself (I have no custom kernels, but best I can do is not completely f' it up - so why bother?). I have between 100 und 200 servers that need updates - and on upgrades, it kind of pulls on my nerves. Unfortunately, I'm not in a position to cache them via squid or so. From owner-freebsd-stable@freebsd.org Tue Sep 12 16:30:01 2017 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 3443CE113D1 for ; Tue, 12 Sep 2017 16:30:01 +0000 (UTC) (envelope-from c.brinkhaus@t-online.de) Received: from mailout11.t-online.de (mailout11.t-online.de [194.25.134.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8F987C41F for ; Tue, 12 Sep 2017 16:30:00 +0000 (UTC) (envelope-from c.brinkhaus@t-online.de) Received: from fwd04.aul.t-online.de (fwd04.aul.t-online.de [172.20.26.149]) by mailout11.t-online.de (Postfix) with SMTP id 8CA5C42576E9 for ; Tue, 12 Sep 2017 18:29:52 +0200 (CEST) Received: from esprimo.local (TnIhIQZFohwtf50LeEsIMIws7d0G92fo2mNy-dbb4rXTqPV63dQhAGq4LaWjOsMgdm@[93.197.159.182]) by fwd04.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1dro4M-1w2wm80; Tue, 12 Sep 2017 18:29:50 +0200 Received: from esprimo.local (localhost [127.0.0.1]) by esprimo.local (Postfix) with ESMTP id C8C564E070 for ; Tue, 12 Sep 2017 18:30:14 +0200 (CEST) Received: (from chris@localhost) by esprimo.local (8.15.2/8.15.2/Submit) id v8CGUEth010361 for freebsd-stable@freebsd.org; Tue, 12 Sep 2017 18:30:14 +0200 (CEST) (envelope-from chris) Date: Tue, 12 Sep 2017 18:30:14 +0200 From: Christoph Brinkhaus To: freebsd-stable@freebsd.org Subject: Re: 11.1 coredumping in sendfile, as used by a uwsgi process Message-ID: <20170912163014.GA1578@esprimo.local> References: <5f5dbe776ed9600b6b5f9ed2750f8e1d@ijs.si> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-ID: TnIhIQZFohwtf50LeEsIMIws7d0G92fo2mNy-dbb4rXTqPV63dQhAGq4LaWjOsMgdm X-TOI-MSGID: 982d8ce8-4162-48eb-945a-6f37146fcf7c X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 16:30:01 -0000 On Tue, Sep 12, 2017 at 04:29:49PM +0200, Mark Martinec wrote: Hello Mark! > 2017-09-12 15:46, Steven Hartland wrote: > > Could you post the decoded crash info from /var/crash/... > > Using crashinfo(8) I suppose? > > > I would also create a bug report: > > https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Base%20System > > Done (with additional info): > > Bug 222259 - 11.1-R crashing in sendfile syscall, as used by a uwsgi > process > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222259 > I have had issues on a quite weak system, it has 2G RAM. Since FreeBSD-11.1 zfs arc is compressed by default which takes some resources. With that feature disabled by vfs.zfs.compressed_arc_enabled="0" in /boot/loader.conf the system is as stable as it has been before. I am not sure if there is a relation to your specific situation. Kind regards, Christoph From owner-freebsd-stable@freebsd.org Tue Sep 12 21:45:23 2017 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 C06AAE20041 for ; Tue, 12 Sep 2017 21:45:23 +0000 (UTC) (envelope-from chris@theory14.net) Received: from bacon.theory14.net (bacon.theory14.net [45.55.200.27]) by mx1.freebsd.org (Postfix) with ESMTP id 9F978643A9 for ; Tue, 12 Sep 2017 21:45:23 +0000 (UTC) (envelope-from chris@theory14.net) Received: from remote.theory14.net (remote.theory14.net [173.79.116.36]) by bacon.theory14.net (Postfix) with ESMTPSA id C4829126014; Tue, 12 Sep 2017 17:45:17 -0400 (EDT) Received: from anubis.int.theory14.net (anubis.int.theory14.net [192.168.10.50]) by remote.theory14.net (Postfix) with ESMTPS id 8AF406042; Tue, 12 Sep 2017 17:45:17 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Mirror the freebsd-update server? From: Chris Gordon In-Reply-To: Date: Tue, 12 Sep 2017 17:45:17 -0400 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <38999763-9687-4FA2-9072-62A9606448EC@theory14.net> References: To: rainer@ultra-secure.de X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 21:45:23 -0000 > On Sep 12, 2017, at 11:03 AM, rainer@ultra-secure.de wrote: >=20 > Hi, >=20 > is it possible or even allowed to just mirror one of the = freebsd-update servers locally? >=20 > I don't want to build the patches myself (I have no custom kernels, = but best I can do is not completely f' it up - so why bother?). >=20 > I have between 100 und 200 servers that need updates - and on = upgrades, it kind of pulls on my nerves. >=20 >=20 > Unfortunately, I'm not in a position to cache them via squid or so. Take a look at https://www.freebsd.org/doc/en/articles/hubs/index.html. = This doc discusses setting up a mirror (found via quick Google search). Chris =20= From owner-freebsd-stable@freebsd.org Tue Sep 12 21:49:34 2017 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 F23DCE202DA for ; Tue, 12 Sep 2017 21:49:34 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id 72F586458D for ; Tue, 12 Sep 2017 21:49:33 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Tue, 12 Sep 2017 23:47:31 +0200 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 6F2AC598-98E8-4CCD-BB0B-415912A1D8BC.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Tue, 12 Sep 2017 23:47:25 +0200 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Mirror the freebsd-update server? From: Rainer Duffner In-Reply-To: <38999763-9687-4FA2-9072-62A9606448EC@theory14.net> Date: Tue, 12 Sep 2017 23:48:35 +0200 Cc: freebsd-stable Message-Id: References: <38999763-9687-4FA2-9072-62A9606448EC@theory14.net> To: Chris Gordon X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=15 total_conn=10 shared_ip=N X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 3924, bad: 1, connections: 4350, history: 3923, asn_score: 457, asn_connections: 469, asn_good: 457, asn_bad: 0, pass:asn, asn_all_good, relaying Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 21:49:35 -0000 > Am 12.09.2017 um 23:45 schrieb Chris Gordon : >=20 > Take a look at https://www.freebsd.org/doc/en/articles/hubs/index.html = . This doc = discusses setting up a mirror (found via quick Google search). Yes, but it doesn=E2=80=99t talk about freebsd-update - which is quite a = different beast than FTP/WWW mirrors? From owner-freebsd-stable@freebsd.org Tue Sep 12 21:52:24 2017 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 B8531E20707 for ; Tue, 12 Sep 2017 21:52:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (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 809BA649B7 for ; Tue, 12 Sep 2017 21:52:24 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1drt6R-00074Q-RE; Tue, 12 Sep 2017 23:52:19 +0200 Date: Tue, 12 Sep 2017 23:52:19 +0200 From: Kurt Jaeger To: Chris Gordon Cc: rainer@ultra-secure.de, freebsd-stable@freebsd.org Subject: Re: Mirror the freebsd-update server? Message-ID: <20170912215219.GG81427@home.opsec.eu> References: <38999763-9687-4FA2-9072-62A9606448EC@theory14.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <38999763-9687-4FA2-9072-62A9606448EC@theory14.net> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 21:52:24 -0000 Hi! > > is it possible or even allowed to just mirror one of the freebsd-update servers locally? [...] > Take a look at https://www.freebsd.org/doc/en/articles/hubs/index.html. > This doc discusses setting up a mirror (found via quick Google > search). That's a mirror of some FTP server, but a fbsd-update repo is somewhat different. A fbsd-update repo setup is described here: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-update-server/article.html -- pi@opsec.eu +49 171 3101372 3 years to go ! From owner-freebsd-stable@freebsd.org Tue Sep 12 22:10:17 2017 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 C1506E21431 for ; Tue, 12 Sep 2017 22:10:17 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 82872652AB for ; Tue, 12 Sep 2017 22:10:17 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-oi0-x231.google.com with SMTP id x190so36014032oix.3 for ; Tue, 12 Sep 2017 15:10:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=c+w85l+GoLmD6RoG4OuM4ERhNeXhoyNtJYQI7lFCNok=; b=Q+1bQPEYg9oCV1Y1Ra77DCeZcIjtRs8H/ev1xS7bJ/rjTsPB7l5m9VORUedujPmDkg 6SgXRmRwLlq1E83HqAVu7Mp3utzv5zmU1rJhU01LRYzOx2KGu5csm2KnBR+T2hgEbaxK nkWBz0FgpXBMFqqd7O9JZYzXd/IbHjIZQqM6faK5mRTHKG3pWsQz/VXXxtPJydjPF39S VAjHiZhXelXzrVwwmwNBRPJh+nOjDmkVTQ+fln5dZziSZ4Ff1DdKPkiFL0FIYNykAjb2 NVmVQIONnDJRoZbsoLNxemeMG3MUdMJS5V+0PPijEXhCHVwME+QS2kjqAuZNFVl6/N2w mbmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=c+w85l+GoLmD6RoG4OuM4ERhNeXhoyNtJYQI7lFCNok=; b=mSry8ivkvKMhToZHDuZ0RMa2wGBhrjUVuHnA2Hc0Ar7c4fod+8J4Dc/XfRP+bF6xQU XbksH0hfotooM3frhwJ5KFWRRuESSr12utctQQdWy7Kt8LJb993C+BKF3iBrvvuW7nnG irtH1Sds+TyR5Pkxi7KxkfDjUJfZ3cLFvpaVbeLo3Db5JjF/TnV4TYGUQMk/V1Mn7JNz XYwhojdWwr3VQHHFciCB3SVtXwGlgQx+pC9laxxaUf2CqeVGdxilF6SLCw+Fzbr62gy5 SgdjbfxvlFpBjnjlrM27yUUrn5rihEI2oHbv5jjFF0Udda7SIo/bfEaJiDM7EfUUmkp4 OygQ== X-Gm-Message-State: AHPjjUifiDsCBXe+cTOkwXtQJOrBva/Hw6M+8/abhswK3oq2FB4Y5WQr 5Gr+fwhLA35WCiUXHIQfl5Rex4v/7y4rhME= X-Google-Smtp-Source: AOwi7QB/+rgrE+1ZnPvsurc3agG+Q/DqmEsVZzTlXohcL7PI/EjJRbs28xVhM8E0veLLMvhqpnbjpR7gTkLNk4fSlyg= X-Received: by 10.202.184.4 with SMTP id i4mr7881440oif.269.1505254216753; Tue, 12 Sep 2017 15:10:16 -0700 (PDT) MIME-Version: 1.0 Sender: jtubnor@gmail.com Received: by 10.157.42.114 with HTTP; Tue, 12 Sep 2017 15:09:56 -0700 (PDT) In-Reply-To: <20170912215219.GG81427@home.opsec.eu> References: <38999763-9687-4FA2-9072-62A9606448EC@theory14.net> <20170912215219.GG81427@home.opsec.eu> From: Jason Tubnor Date: Wed, 13 Sep 2017 08:09:56 +1000 X-Google-Sender-Auth: bB6UQQFExDY0QExDz7n1Zq59I3s Message-ID: Subject: Re: Mirror the freebsd-update server? To: Kurt Jaeger Cc: Chris Gordon , freebsd-stable , rainer@ultra-secure.de Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Sep 2017 22:10:17 -0000 On 13 September 2017 at 07:52, Kurt Jaeger wrote: > Hi! > > > > is it possible or even allowed to just mirror one of the > freebsd-update servers locally? > [...] > > > Take a look at https://www.freebsd.org/doc/en/articles/hubs/index.html. > > This doc discusses setting up a mirror (found via quick Google > > search). > > That's a mirror of some FTP server, but a fbsd-update repo is > somewhat different. A fbsd-update repo setup is described here: > > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/ > freebsd-update-server/article.html > I found this useful. I made some adjustments for what I needed but those updates are sweet now :-) https://wiki.freebsd.org/VladimirKrstulja/Guides/FreeBSDUpdateReverseProxy From owner-freebsd-stable@freebsd.org Wed Sep 13 00:04:00 2017 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 58CE8E002D3 for ; Wed, 13 Sep 2017 00:04:00 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from connect.ultra-secure.de (connect.ultra-secure.de [88.198.71.201]) by mx1.freebsd.org (Postfix) with ESMTP id CDB706A116 for ; Wed, 13 Sep 2017 00:03:59 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (Haraka outbound); Wed, 13 Sep 2017 02:01:15 +0200 Authentication-Results: connect.ultra-secure.de; iprev=pass; auth=pass (plain); spf=none smtp.mailfrom=ultra-secure.de Received-SPF: None (connect.ultra-secure.de: domain of ultra-secure.de does not designate 217.71.83.52 as permitted sender) receiver=connect.ultra-secure.de; identity=mailfrom; client-ip=217.71.83.52; helo=[192.168.1.200]; envelope-from= Received: from [192.168.1.200] (217-071-083-052.ip-tech.ch [217.71.83.52]) by connect.ultra-secure.de (Haraka/2.6.2-toaster) with ESMTPSA id 1585C361-DA25-4FC0-94B1-3BE6628915C6.1 envelope-from (authenticated bits=0) (version=TLSv1/SSLv3 cipher=AES256-SHA verify=NO); Wed, 13 Sep 2017 02:01:12 +0200 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Mirror the freebsd-update server? From: Rainer Duffner In-Reply-To: Date: Wed, 13 Sep 2017 02:03:53 +0200 Cc: freebsd-stable Message-Id: <746F3D00-FE25-4784-BB5A-CD6A3D8147BC@ultra-secure.de> References: <38999763-9687-4FA2-9072-62A9606448EC@theory14.net> <20170912215219.GG81427@home.opsec.eu> To: Jason Tubnor X-Mailer: Apple Mail (2.3124) X-Haraka-GeoIP: EU, CH, 451km X-Haraka-ASN: 24951 X-Haraka-GeoIP-Received: X-Haraka-ASN: 24951 217.71.80.0/20 X-Haraka-ASN-CYMRU: asn=24951 net=217.71.80.0/20 country=CH assignor=ripencc date=2003-08-07 X-Haraka-FCrDNS: 217-071-083-052.ip-tech.ch X-Haraka-p0f: os="Mac OS X " link_type="DSL" distance=15 total_conn=12 shared_ip=Y X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on spamassassin X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 X-Haraka-Karma: score: 6, good: 3926, bad: 1, connections: 4352, history: 3925, asn_score: 459, asn_connections: 471, asn_good: 459, asn_bad: 0, pass:asn, asn_all_good, relaying Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2017 00:04:00 -0000 > Am 13.09.2017 um 00:09 schrieb Jason Tubnor : >=20 > I found this useful. I made some adjustments for what I needed but = those > updates are sweet now :-) > = https://wiki.freebsd.org/VladimirKrstulja/Guides/FreeBSDUpdateReverseProxy= = "This is a simple cache. That means it doesn't consider the files as a = whole repository, which in turn means updates to your cache are not = atomic. It'd be advised to nuke your cache before your update run, as = its point is only to retain the files in a local cache for some short = period of time required for all your machines to be updated.=E2=80=9C The problem is, my updates don=E2=80=99t work that way. These servers all belong to different customers (well, some have a = couple) and I can=E2=80=99t patch them in =E2=80=9Esome short period of = time=E2=80=9C. It=E2=80=99s continuous process. I have other stuff to do. And I have to negotiate downtimes etc. From owner-freebsd-stable@freebsd.org Wed Sep 13 13:58:43 2017 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 072C4E226F8; Wed, 13 Sep 2017 13:58:43 +0000 (UTC) (envelope-from 0110001101100100b@gmail.com) Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::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 BFE9065697; Wed, 13 Sep 2017 13:58:42 +0000 (UTC) (envelope-from 0110001101100100b@gmail.com) Received: by mail-ua0-x229.google.com with SMTP id q29so397963uaf.3; Wed, 13 Sep 2017 06:58:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=PUD3YbT9UI2VFK5JIKj5qaZFNorKG1Ffd2+eq4zOrgc=; b=O047JRqJ3VZxLLLN3ZE/2/sXxI7g36VGO9GPtQMcujfgcfhRotKK42tuCoJM2PVJe/ xdedB2Atgx/au+dxaIhI8nbgIOkMFAXluKHAHNdXBtjz7LGqe95dsoFjPAvfBjGNSMaE Q3DmXchzhy/XQc9EMDkscXBDdQrSGy8PK/K669g/jc4uRuNyv19GZx7ST7+DucVycJp5 NqyEjA7kFBPlZl7uPnEEu3SsNaqlIHpUwSNLKl8pkIP027/krZjqKp4lxQWiaKhMsOqq MLS/oYN/uApnuGC5NxYrsMhZtq/QuOLq5UFf6Rbn8Jji4iEBwFutGJ7zb729542JXISt 1S7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=PUD3YbT9UI2VFK5JIKj5qaZFNorKG1Ffd2+eq4zOrgc=; b=UQe97RefJaO4EfVT1BbnY5qsrdQpmxL8iFkdS6FN5hXaY6IFEu2wQRN3b6intAcLce XT+kHZYnFfBHR+XPZHid212kzfpsyVfHVkjOTaSsPB+EX2Ov3VK8i3Osm9BaA2E0yj6v cJLkt3asJd9DB1JVjM/xzzh2Cy+RFtiZTsqIhDe0+20EH3Hc5R/ybatZerdDEPLdTz88 DmmAvMpr45LdQNuqLkaqV1RiULRGC72CGUnKfhrVAjeYRD8K7PMIGqPNkmi0SQ/BWsz5 9EL+MirVGja68XAZxrrZ+apmkgoAQvyX1wDGkcLcGdwH6WKEyPgFrsqHF4c7XiIGuxJg YPIA== X-Gm-Message-State: AHPjjUjCI1P8WSy6zNe4I1pswLRagh0Kafk0WFhuVBq4ZVnYMafnZSLQ GeqDEw3fkRYSFPaxjpko7twUNBvTYPdgMIX+xVkgVteA X-Google-Smtp-Source: AOwi7QBuTv8RtaHzw5DoxdOkSf6x6ns1b8RQqQ9vqcwQ6dfQMAkTUkxgZ7Rb1LEOMfInOLXmvm/tNy0Hld/i6jtTVtU= X-Received: by 10.176.9.206 with SMTP id e14mr13179978uah.126.1505311121321; Wed, 13 Sep 2017 06:58:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.82.220 with HTTP; Wed, 13 Sep 2017 06:58:40 -0700 (PDT) From: "Mr. Binary" <0110001101100100b@gmail.com> Date: Wed, 13 Sep 2017 15:58:40 +0200 Message-ID: Subject: crashes after upgrade to 11.1-RELEASE AMD64 / libgcc5 To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2017 13:58:43 -0000 Hey! I have upgraded from 11.0 to 11.1-RELEASE, I get constantly crashing applications, is web browser.. this may be related to libgcc5.. any hints how to prevent? Firefox / Chrome / Iridium GTK, Otter QT5.. Program received signal SIGSEGV, Segmentation fault. 0x0000000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1 (gdb) bt #0 0x0000000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1 #1 0x0000000000000000 in ?? () Program received signal SIGSEGV, Segmentation fault. 0x0000000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1 ... -- 0110001101100100 From owner-freebsd-stable@freebsd.org Wed Sep 13 15:56:59 2017 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 219C8E0284B for ; Wed, 13 Sep 2017 15:56:59 +0000 (UTC) (envelope-from dnelson1@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::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 9B9956AF2B for ; Wed, 13 Sep 2017 15:56:58 +0000 (UTC) (envelope-from dnelson1@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id 80so1777236lfy.4 for ; Wed, 13 Sep 2017 08:56:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to:cc:content-transfer-encoding; bh=M9PRK6Y0V78I++3Kv3R8ZoWSIGWy0EDlk/jkGjtgBzU=; b=gtdVKadP2EuYrOf5Dvdd3eRU9ZuLKOXpCAr/yLGpHkmFY61mkAdk/xan08Yv3ZNDP2 6Ev1zwQajKmCRW6E+J15lilcA1C6Ei9pi4m/tiAP0d1y2lhED8GQ2lxXMSkzu2JtXI8t FK6rBlQACpbA7QgaKkIMc9Ah9jbHqjazf1nSbdoI4EgghoDB/KE/VUUOUob2ntbR1l35 QZBaK9aEpNlZvopHxPjeA7/eBzPOU970dJEp1MAdFIlLLIb2LqY03gPYSttaZwZUCAPi BbqbawGfLGpsTC+ujf98LuGfzAh7vdhX2kiDwkWK1BIrwD3Y7VbpU/HMJSkc8zGlwXC7 PXig== X-Gm-Message-State: AHPjjUjraUveCxrszJUsznOdGBA78XbkWTxXQ3D1RM6sPZW5pAGuS5od 8hA6q1ilU9SFP3h8mMhItNGl7FiE1VVjV8GYvlg= X-Google-Smtp-Source: AOwi7QBRcRGoJjCE6rKJ5ghi2vuCy4TFTUnf1oJSVdxGhd8KG51vpYPA7VboMRg5yKngKhXPyEKFnbSMgLAbQREclhc= X-Received: by 10.46.83.85 with SMTP id t21mr368992ljd.188.1505318216583; Wed, 13 Sep 2017 08:56:56 -0700 (PDT) MIME-Version: 1.0 Sender: dnelson1@gmail.com Received: by 10.25.37.209 with HTTP; Wed, 13 Sep 2017 08:56:55 -0700 (PDT) From: Dan Nelson Date: Wed, 13 Sep 2017 10:56:55 -0500 X-Google-Sender-Auth: 9EOf6XWrxGRFIRsbCSJQn10DVxU Message-ID: Subject: Re: Unusually high "Wired" memory To: Borja Marcos Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Sep 2017 15:56:59 -0000 2017-09-12 1:27 GMT-05:00 Borja Marcos : > > > > On 11 Sep 2017, at 11:25, Borja Marcos wrote: > > > >> Since I=E2=80=99ve updated a machine to 11.1-STABLE I am seeing a rath= er unusual growth of Wired memory. > >> > >> Any hints on what might have changed from 11-RELEASE to 11.1-RELEASE a= nd 11.1-STABLE? > > vmstat -z and vmstat -m follow > > % vmstat -z > ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP > [...] > g_bio: 376, 0,15235172, 248,477839025, 0, 0 > [...] I think this is the problem - you're leaking g_bio objects (5.7 GB currently allocated if you multiply SIZE*USED). I'm seeing the same thing and it looks like it started after the recent ZFS merges from -current. I have filed a bugreport with some more info ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222288 ). From owner-freebsd-stable@freebsd.org Thu Sep 14 01:54:58 2017 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 6E958E1C339 for ; Thu, 14 Sep 2017 01:54:58 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 2573C83D70; Thu, 14 Sep 2017 01:54:58 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-qk0-x233.google.com with SMTP id a128so4555458qkc.5; Wed, 13 Sep 2017 18:54:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=coWos+EU4Fb1qsu7GDY+R8a+fwee4Zd6cCjbRd3mZa8=; b=jxbG0YaImzQbTAOFiaP37mQXI5TpC3c++KCQTzV6woLnHjToQYwRwctlPyqrEFryEd ZF+rRCXQ+gkPnRBJVRRMqsZ0RTCz8NElVipR9To4qmNA5xsJIhOPCQ6HVC7o28YaiT4e MgZDLjyOerM+ImATmpkGBjXjeP/vo521BVeOmQhaQ/nCcmnMI3bjy9MNosInOqzSPSmo 4PDusbYcWwrLSRJzWbZgSAZgsW55BemFO63/Sckg9EsUreMSIPsrJQfSv1SHOA8MxHDh xeY5eWI/aLqHI6XAighmWh+gH5/gCgS6j5ZijG5/6R9003zDVO9C3KIvL6p2aWyzaz/A HGTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=coWos+EU4Fb1qsu7GDY+R8a+fwee4Zd6cCjbRd3mZa8=; b=dEtIDaA//xi74OOL4YXnUsjF9jQsVwKfuMmb4vmFD0/nTHdDZEfnTdeinKB2iZN+1k lX5CNUS30BCxJNo4aB2ryZ07Y5IZ169O10z1EjgBmSP5pQrns9cRVPXwXomhTaJol/Pz UGJxtqeh9Jvc+AJi7zlljx2wbCSMDqayExhJ2sjMAA63NfavCTCHzQc6W7zgz1FmyTQX 2wxPhFiinShtpglIWvOISxFuIdqE5KdOMkWPaje72AgcCvMH7TMcIXEICeKxsu3fSwSA idcjX3TTaZcvBXrILgV0A3ViBi6orBVimgiud4o2+HUC1UuE/6XxGia7BRhmi1YsVc39 vM2A== X-Gm-Message-State: AHPjjUilZW9phtNZ08eKFa4d8TsrKNMXtouauORU6+polFviRbkFGaZd kymhsTJF8KxQt3stiwhwJpa1B6Tr1t3CUS9i5w== X-Google-Smtp-Source: AOwi7QDehbs2lyLp03nayNasW5qiHjRktzeNc2J7+0J1er9HXZD5oPAWuot0JEsk1uZ8PaWSEsYzTaFhSDaGdiQoBuE= X-Received: by 10.55.71.6 with SMTP id u6mr607533qka.166.1505354097182; Wed, 13 Sep 2017 18:54:57 -0700 (PDT) MIME-Version: 1.0 Sender: sepherosa@gmail.com Received: by 10.140.21.20 with HTTP; Wed, 13 Sep 2017 18:54:56 -0700 (PDT) In-Reply-To: <20170908010400.0fb81bc4@akips.com> References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> <20170907150711.025e4e41@akips.com> <20170908010400.0fb81bc4@akips.com> From: Sepherosa Ziehau Date: Thu, 14 Sep 2017 09:54:56 +0800 X-Google-Sender-Auth: ShoHNLKRAIr2ilQUtTkwN2GnqI0 Message-ID: Subject: Re: 11.1 running on HyperV hn interface hangs To: Paul Koch Cc: Julian Elischer , freebsd-stable@freebsd.org, Hongjiang Zhang Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2017 01:54:58 -0000 If you have any updates on this, please let me know. There is still time for 10.4. On Thu, Sep 7, 2017 at 11:04 PM, Paul Koch wrote: > On Thu, 7 Sep 2017 13:51:11 +0800 > Sepherosa Ziehau wrote: > >> Weird, your traffic pattern does not even belong to anything heavy. >> Sending is mainly UDP, which will never be able to saturate the TX >> buffer ring causing the RXBUF ACK sending failure. This is weird. > > It's a bit tricky. The poller is very fast. We ping every device every 15 > seconds, and collect every MIB object every 60 seconds. The poller "rate > limits" itself by dividing each minute into 100ms time slots and only sends a > specific amount of pings/snmp packets in each time slot. The problem is, it > blasts the request packets out really fast at the start of each time slot, > and then sits in a receive loop until the next time slot comes around. The > requests are not paced over the 100ms, therefore it will blast out a lot > of packets in a few milliseconds. > > We use to use a 1 second rate limiting time slot, and didn't interlace > ping/snmp requests, but we found certain interface types on Cisco 6509 > switches couldn't keep up with back-to-back pings and would lose them. > > >> Anyhow, make sure to test this patch: >> 8762017-Sep-07 02:19 hn_inc_txbr.diff > > Yep. Might take a bit of time to test though because we'll need to get the > customer to spin up a test VM on the same platform, and they are fairly > remote (Perth, Australia). We don't run any Microsoft servers/HyperV setups > in our lab. > > Paul. > -- > Paul Koch | Founder | CEO > AKIPS Network Monitor | akips.com > Brisbane, Australia -- Tomorrow Will Never Die From owner-freebsd-stable@freebsd.org Thu Sep 14 02:41:33 2017 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 6D0D0E1F30D for ; Thu, 14 Sep 2017 02:41:33 +0000 (UTC) (envelope-from amutu@amutu.com) Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 1D79D9F9 for ; Thu, 14 Sep 2017 02:41:33 +0000 (UTC) (envelope-from amutu@amutu.com) Received: by mail-qk0-x232.google.com with SMTP id j5so4736454qkd.0 for ; Wed, 13 Sep 2017 19:41:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amutu-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TvmqYPpkLPsh9EiL/ZQ4S+/Xiij+QsxkIjiYOAciJZQ=; b=ouH+TOWrobE9sJs/OvuwTQE7HvdQ94q7Q+FwRyxKOMR3/ZIpISyJxImVXRc7LRem0n XbnRa3VMSU+5wn3BcWjfwWuvfBDHdx0cRchzzwDtwfCjcjDXUIazGlnj+7rmRICSZrNQ 4O33vT1c5WaxIwseBC27CFMP2k/CXkfvSEKqkQXUrEIvc7LA7CTfFkjeF9HSm6p4x3oZ B4mh4GU4L+wlik5+MxtYC9/8HeqSW5zcBnb3Q5F2K9fnDRYMOCm0mz64mBwge+FbrRiK 0UzfweuLkLMFmJWP7mTqUBm5qGogRfgDkCC2wS4CkheuBIJ5hyZtn61Hmt/4SqWv3SOH SW5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TvmqYPpkLPsh9EiL/ZQ4S+/Xiij+QsxkIjiYOAciJZQ=; b=sGQiyRA3XRh+HbUf0Ztqlmj7epTS5Q9ALAvFTul/zpBhoAgRJcMCXO3pIjp4FWfgn5 QK0wHwX/tr/gqMvuRGZC/ek1Dt93LGP0ebir+YkwLOC7+sanDHHH+ZfhnprBQq3pow8p Xv9svIgqb2uGewJMBPQknSrKpqmUkOUXC9JowaBzwPEujPg4dNBZdHOao1tjHplQueQy 76P3/Etesn+J8MMZ6psOv3vmW+Zp8SfxsmTDMTW5CDgd2jef2Da6TP30mN6aKSOVNDvX wSk14ONeg5iM7wK0mhqilnz3/QJwozrx2h02wMCeRCb2FCwEKnOmKb9q89EWuISIPhdo s+oQ== X-Gm-Message-State: AHPjjUiY1hg1PrJ+dJiVAYHT+UCyMLO+6i4FAOyT6lfpbOFnOvxYoDeA eDtiDR6ExKijJ6L8LQWeef8o X-Received: by 10.55.10.76 with SMTP id 73mr674667qkk.205.1505356891723; Wed, 13 Sep 2017 19:41:31 -0700 (PDT) Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com. [209.85.220.172]) by smtp.gmail.com with ESMTPSA id s90sm10464739qkl.81.2017.09.13.19.41.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Sep 2017 19:41:30 -0700 (PDT) Received: by mail-qk0-f172.google.com with SMTP id b23so4743050qkg.1; Wed, 13 Sep 2017 19:41:30 -0700 (PDT) X-Google-Smtp-Source: AOwi7QDomLa/8yF5hMDXk58sPDG8WosZbIggD+Bl5ejzc9VZvKaW+3gxx+kYnhpkGc3+PZZqleciwrAViZbbLcidTKI= X-Received: by 10.233.221.3 with SMTP id r3mr695177qkf.219.1505356890164; Wed, 13 Sep 2017 19:41:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.43.74 with HTTP; Wed, 13 Sep 2017 19:41:09 -0700 (PDT) In-Reply-To: References: From: Jov Date: Thu, 14 Sep 2017 10:41:09 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: crashes after upgrade to 11.1-RELEASE AMD64 / libgcc5 To: "Mr. Binary" <0110001101100100b@gmail.com> Cc: freebsd-stable@freebsd.org, FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2017 02:41:33 -0000 There is a similar PR for libgcc[1]. It's crash TensorFlow on 11.1-Release. I make the tensorflow port on 11.0-R and test it on 11.0R,10.3R, all work well. But now it is not working on 11.1R, even 11.0R jail on 11.1R get the same crash. [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221880 2017-09-13 21:58 GMT+08:00 Mr. Binary <0110001101100100b@gmail.com>: > Hey! > > I have upgraded from 11.0 to 11.1-RELEASE, I get constantly crashing > applications, is web browser.. this may be related to libgcc5.. any > hints how to prevent? > > Firefox / Chrome / Iridium GTK, Otter QT5.. > > Program received signal SIGSEGV, Segmentation fault. > 0x0000000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1 > (gdb) bt > #0 0x0000000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1 > #1 0x0000000000000000 in ?? () > > Program received signal SIGSEGV, Segmentation fault. > 0x0000000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1 > > ... > > -- > 0110001101100100 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Thu Sep 14 06:19:12 2017 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 CE784E02647; Thu, 14 Sep 2017 06:19:12 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 8DD6C66668; Thu, 14 Sep 2017 06:19:12 +0000 (UTC) (envelope-from tomek.cedro@gmail.com) Received: by mail-ua0-x230.google.com with SMTP id l24so2929279uaa.5; Wed, 13 Sep 2017 23:19:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2BNn7CnpHYcWxyvpuDU/BWgXeQUpzClU7NgG4Mvt6L8=; b=cNQGk+xh7wAgdbqYOS30y48LA/PUeZrRu25wizhVKOthgQyl+p4EQX5dOI6EAmpBRq Hvgvx1nGE8x1qIivessboEJXjPUYyD1c9V5WkbyuspRV8f7LtaK4XQDR7Hmq6wiZP8Nr 6QeJnjBIoERnuZEVWyD+GRX/Wq/AbXyD4QZxw+pvpwqK7fR2cgWTeXa8rykLz/6KmVit ZbMH1hzPGDJwE3nNCIaqTxRxJ2GsUna4sAImAFJYn7u9Uz6b1F99pE3VtUe4sSGwcuYU AKikWKoOzDVrHLjcwg8hATRdYTKiU6e86x/ZhwFNNanrgMArBE+oZgfYcTodSiz0nSRP K4Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=2BNn7CnpHYcWxyvpuDU/BWgXeQUpzClU7NgG4Mvt6L8=; b=AS6az9rbHUP4tyxcBrEHOZwiSJX1gloWvVOqJiLz6Mru3FFDbPUHK8Y0UB2iKatvxu BH2Te3ZXIdDLS5LZni0Pp9WreNLUZBBpNe+vfFqD+TOlSpbKoVGAlESmFgT5x6VZha5G OesL1ZZ4pdB8S+NCQD9vUUKROrjbU7wJEtlskW3z+6CQynwu1/eFjg7LjNXAg7UuYZn2 qCt+3w87SJ/IXAcqjJffCdKOZIXHwHySdU/DjUik9Kb/UTdRk5V63KiHGEDkLbNyHF1h 8Z14yzbDtDL9TDHnYFRRYVFUz9kj3o1OHgcNU27eak3BRFmG8j95hGeJZYQ32NsW7JOD Tkew== X-Gm-Message-State: AHPjjUhKZACKGIaukDIwAWnymhSxV4R7Z9H73ixzDyIM1f6jEhHe0Ni6 hxJb6a340spQXBAK6w9nVdGPwOdHuPMrEvYZrDg= X-Google-Smtp-Source: ADKCNb7dl1J9EbEgxf+h5wW684ptllZqOsZeoGcgRzuvN0uEkz5jx65pCkfbwNGFT3lLeludFy0DWZSdScHBF4fY8f8= X-Received: by 10.176.70.75 with SMTP id z11mr16747908uab.43.1505369951006; Wed, 13 Sep 2017 23:19:11 -0700 (PDT) MIME-Version: 1.0 Sender: tomek.cedro@gmail.com Received: by 10.176.20.35 with HTTP; Wed, 13 Sep 2017 23:19:09 -0700 (PDT) Received: by 10.176.20.35 with HTTP; Wed, 13 Sep 2017 23:19:09 -0700 (PDT) In-Reply-To: References: From: Tomasz CEDRO Date: Thu, 14 Sep 2017 08:19:09 +0200 X-Google-Sender-Auth: 03geFbsKNfvpUAlflbKcarvFBcw Message-ID: Subject: Re: crashes after upgrade to 11.1-RELEASE AMD64 / libgcc5 To: 0110001101100100b <0110001101100100b@gmail.com> Cc: FreeBSD Questions Mailing List , FreeBSD Stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2017 06:19:12 -0000 Here too! I did a fresh install on a second partition the same machine, no problem observed.. for some reason freebsd-upgrade -r fails to create a stable system or there is some sort of base/pkg mismatch after... -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Sep 13, 2017 15:58, "Mr. Binary" <0110001101100100b@gmail.com> wrote: Hey! I have upgraded from 11.0 to 11.1-RELEASE, I get constantly crashing applications, is web browser.. this may be related to libgcc5.. any hints how to prevent? Firefox / Chrome / Iridium GTK, Otter QT5.. Program received signal SIGSEGV, Segmentation fault. 0x0000000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1 (gdb) bt #0 0x0000000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1 #1 0x0000000000000000 in ?? () Program received signal SIGSEGV, Segmentation fault. 0x0000000806bdec19 in ?? () from /usr/local/lib/gcc5/libgcc_s.so.1 ... -- 0110001101100100 _______________________________________________ freebsd-questions@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Thu Sep 14 08:25:46 2017 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 2F128E07BE4 for ; Thu, 14 Sep 2017 08:25:46 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from cu1176c.smtpx.saremail.com (cu1176c.smtpx.saremail.com [195.16.148.151]) (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 E9BFF6A44E for ; Thu, 14 Sep 2017 08:25:44 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from [172.16.8.41] (unknown [192.148.167.11]) by proxypop02.sare.net (Postfix) with ESMTPA id 75C8A9DD83A; Thu, 14 Sep 2017 10:25:34 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Unusually high "Wired" memory From: Borja Marcos In-Reply-To: Date: Thu, 14 Sep 2017 10:25:33 +0200 Cc: FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Dan Nelson X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2017 08:25:46 -0000 > On 13 Sep 2017, at 17:56, Dan Nelson via freebsd-stable = wrote: >=20 > 2017-09-12 1:27 GMT-05:00 Borja Marcos : >>=20 >>=20 >>> On 11 Sep 2017, at 11:25, Borja Marcos wrote: >>>=20 >>>> Since I=E2=80=99ve updated a machine to 11.1-STABLE I am seeing a = rather unusual growth of Wired memory. >>>>=20 >>>> Any hints on what might have changed from 11-RELEASE to = 11.1-RELEASE and 11.1-STABLE? >>=20 >> vmstat -z and vmstat -m follow >>=20 >> % vmstat -z >> ITEM SIZE LIMIT USED FREE REQ FAIL = SLEEP >> [...] >> g_bio: 376, 0,15235172, 248,477839025, 0, = 0 >> [...] >=20 >=20 > I think this is the problem - you're leaking g_bio objects (5.7 GB > currently allocated if you multiply SIZE*USED). I'm seeing the same > thing and it looks like it started after the recent ZFS merges from > -current. I have filed a bugreport with some more info ( > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222288 ). Confirmed, thank you :) Going back to RELENG-11.1 solved it, so the slip must be quite recent. Borja. From owner-freebsd-stable@freebsd.org Thu Sep 14 11:11:56 2017 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 79BAAE10070 for ; Thu, 14 Sep 2017 11:11:56 +0000 (UTC) (envelope-from artemrts@ukr.net) Received: from frv191.fwdcdn.com (frv191.fwdcdn.com [212.42.77.191]) (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 3A2556F5FA for ; Thu, 14 Sep 2017 11:11:55 +0000 (UTC) (envelope-from artemrts@ukr.net) Received: from [10.10.1.23] (helo=frv199.fwdcdn.com) by frv191.fwdcdn.com with esmtp ID 1dsRQM-0003tl-MW for freebsd-stable@freebsd.org; Thu, 14 Sep 2017 13:31:10 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Type:MIME-Version:Message-Id:To:Subject:From:Date:Sender: Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=GxmL3FNKtkJ2GuZN64r0YRj2RO0cBC5QP1OLijOBOOc=; b=jASnY5F1lp5YAHQLnFLMhEhger 9B+kEAf1atA+cS0Sh4ByxGQggDZyhjD0/fct+uUxs3KLX0xp9hOeWYxEFUOKsqFndhUafo8FibgDA uyo9qkct/N2qGV4wPkk9RERSo5vks+Fe/ODSr7UDMhLhs/1NsNTk4vRrC4MFF8rRWPPo=; Received: from [10.10.10.52] (helo=frv52.fwdcdn.com) by frv199.fwdcdn.com with smtp ID 1dsRQB-0003g5-GN for freebsd-stable@freebsd.org; Thu, 14 Sep 2017 13:30:59 +0300 Date: Thu, 14 Sep 2017 13:30:59 +0300 From: wishmaster Subject: The system works unstable To: freebsd-stable X-Mailer: mail.ukr.net 5.0 Message-Id: <1505383551.980800557.o68y1kwi@frv52.fwdcdn.com> Received: from artemrts@ukr.net by frv52.fwdcdn.com; Thu, 14 Sep 2017 13:30:59 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2017 11:11:56 -0000 Hi! My 11.0-STABLE system had been working stable for a three last years, but became unstable a week ago. The system just freezes about once/2 days (at night) and no responsive via network, nothing in the console. Before the first freezing I had made updates of applications in the base system and jails. Options VIMAGE and Linux compat. are enabled. The first thought was bad sectors on the HDD, but  dd if=/dev/ada0 of=/dev/null bs=128k rejected this one. How can I debug this situation? Thank, Vit From owner-freebsd-stable@freebsd.org Thu Sep 14 11:27:49 2017 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 48786E1107E for ; Thu, 14 Sep 2017 11:27:49 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::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 CCED570221 for ; Thu, 14 Sep 2017 11:27:48 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wr0-x235.google.com with SMTP id c23so45202wrg.9 for ; Thu, 14 Sep 2017 04:27:48 -0700 (PDT) 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-language; bh=wkSDHPKPWnfW3Fr1atlEPXnMBl72urT7PYHCyvzPSiU=; b=ahI+zbNMtE5bYE5fFWo/rMGHWkDlQi4O3HgNX62IjxKmqXIRggxZeLweDi87/bbSrn PxiTjg1N9FN0Aj5agGg8OUlaVjFB+T3Fo3pTjaQZEHXD/GI39ZPMCw1whaD/ZzWzbH+v gIkPjOso0FC8cF68GgwknnLpsignTPMxmgjsZHnV3N/SeEMfdJk0qHbptVkWf1UnZv0w JNOPTbNwfmkORZ0EbHxyzY+cIVVvN6eUSA1RRVqIqsLCzmjzS2Jfbav7ZBrV0JTQnry4 ZjrmXFGnELUZ/xUS8cwqHZzz34T3JT2INGWON4r24erEUioAP90DeVF209cAWPnVSq4W 7CYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=wkSDHPKPWnfW3Fr1atlEPXnMBl72urT7PYHCyvzPSiU=; b=RMYdD7OSXGh5MchCsbsQfdIsLHjG3JxJNxW8fBkCxQCcmWgnQ4eSh4naLXdpAoXwNU OGhnh99WPZSdS+6lf3NWSfTbNXVwz1/+HU4lP+INpSyFRzacBeDvZB6ANQzzv8S55gPQ csQ/DtW/7JOCxq/zs2hI+4u33T2aIiQLX+uPANL06pQIohuRjcSrZs6WGmSEBVZIqX3F nX5yXFiI685eFHx4rWyc08Ld1rj61S1H/bQ8v2mDKjQK/eL8CHcRtWHk+QuPHmgsNzgN FTAiTQfT0YyZMGwDawiWLaaLoOWMak8b1dvv6tg6VGpxwmccap9XQft0uYtZXuPFA+Y0 A81A== X-Gm-Message-State: AHPjjUgbe97rMmt/6TI/n/GC4sX8i8Bgle+jEawW4XeAXiYlhmVf1WtI js2bWU+6/Zm3aKTpDFV6/w== X-Google-Smtp-Source: ADKCNb6nS3v1rt0xmV5z4woRiYvmY/lTidX/cA4JkBChSBRzGjlLP08gMfjgyJnX09Dl+pkiq2qApQ== X-Received: by 10.223.156.199 with SMTP id h7mr15284173wre.170.1505388466788; Thu, 14 Sep 2017 04:27:46 -0700 (PDT) Received: from [10.10.1.111] ([185.97.61.1]) by smtp.gmail.com with ESMTPSA id q19sm21627000wrb.17.2017.09.14.04.27.45 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Sep 2017 04:27:45 -0700 (PDT) Subject: Re: The system works unstable To: freebsd-stable@freebsd.org References: <1505383551.980800557.o68y1kwi@frv52.fwdcdn.com> From: Steven Hartland Message-ID: <20153687-4322-07f4-4018-abd32b5777c5@multiplay.co.uk> Date: Thu, 14 Sep 2017 12:27:46 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <1505383551.980800557.o68y1kwi@frv52.fwdcdn.com> Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Sep 2017 11:27:49 -0000 If you have remote console via IPMI it might be an idea to leave an active top session so you can see the last point at which the machine stopped. It may provided a pointer to bad process e.g. eating all the machine RAM.     Regards     Steve On 14/09/2017 11:30, wishmaster wrote: > Hi! > > My 11.0-STABLE system had been working stable for a three last years, but became unstable a week ago. The system just freezes about once/2 days (at night) and no responsive via network, nothing in the console. > Before the first freezing I had made updates of applications in the base system and jails. > Options VIMAGE and Linux compat. are enabled. > > The first thought was bad sectors on the HDD, but  dd if=/dev/ada0 of=/dev/null bs=128k rejected this one. > > How can I debug this situation? > > Thank, > Vit > _______________________________________________ > 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 Fri Sep 15 04:16:31 2017 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 35E45E23810 for ; Fri, 15 Sep 2017 04:16:31 +0000 (UTC) (envelope-from paul.koch@akips.com) Received: from mail.akips.com (mail.akips.com [45.32.79.107]) (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 1F5BF76E72; Fri, 15 Sep 2017 04:16:30 +0000 (UTC) (envelope-from paul.koch@akips.com) Date: Fri, 15 Sep 2017 14:07:37 +1000 From: Paul Koch To: Sepherosa Ziehau Cc: Julian Elischer , freebsd-stable@freebsd.org, Hongjiang Zhang Subject: Re: 11.1 running on HyperV hn interface hangs Message-ID: <20170915140737.73ab6136@akips.com> In-Reply-To: References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> <20170907150711.025e4e41@akips.com> <20170908010400.0fb81bc4@akips.com> Organization: AKIPS MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Sep 2017 04:16:31 -0000 On Thu, 14 Sep 2017 09:54:56 +0800 Sepherosa Ziehau wrote: > If you have any updates on this, please let me know. There is still > time for 10.4. Still working on it. We are trying to replicate the FreeBSD 11.1 running in a Hyper-V VM setup in our test lab. We have ping/snmp/netflow network simulators that can create large amounts of real network traffic to see if it reliably triggers the problem. Paul. -- Paul Koch | Founder | CEO AKIPS Network Monitor | akips.com Brisbane, Australia From owner-freebsd-stable@freebsd.org Sat Sep 16 23:38:52 2017 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 A0F83E10725 for ; Sat, 16 Sep 2017 23:38:52 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "alchemy.franken.de", Issuer "alchemy.franken.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A2EF67A67; Sat, 16 Sep 2017 23:38:51 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.15.2/8.15.2/ALCHEMY.FRANKEN.DE) with ESMTPS id v8GNcnJP018855 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 17 Sep 2017 01:38:49 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.15.2/8.15.2/Submit) id v8GNcn7l018854; Sun, 17 Sep 2017 01:38:49 +0200 (CEST) (envelope-from marius) Date: Sun, 17 Sep 2017 01:38:49 +0200 From: Marius Strobl To: freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: FreeBSD 10.4-RC1 Now Available Message-ID: <20170916233849.GM20729@alchemy.franken.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 16 Sep 2017 23:38:52 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 The first RC build of the 10.4-RELEASE release cycle is now available. Installation images are available for: o amd64 GENERIC o i386 GENERIC o ia64 GENERIC o powerpc GENERIC o powerpc64 GENERIC64 o sparc64 GENERIC o armv6 BEAGLEBONE o armv6 CUBOX-HUMMINGBOARD o armv6 GUMSTIX o armv6 PANDABOARD o armv6 RPI-B o armv6 WANDBOARD Note regarding arm/armv6 images: For convenience for those without console access to the system, a freebsd user with a password of freebsd is available by default for ssh(1) access. Additionally, the root user password is set to root. It is strongly recommended to change the password for both users after gaining access to the system. Installer images and memory stick images are available here: https://download.freebsd.org/ftp/releases/ISO-IMAGES/10.4/ The image checksums follow at the end of this e-mail. If you notice problems you can report them through the Bugzilla PR system or on the -stable mailing list. If you would like to use SVN to do a source based update of an existing system, use the "releng/10.4" branch. A list of changes since 10.3-RELEASE is available in the releng/10.4 release notes: https://www.freebsd.org/releases/10.4R/relnotes.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 10.4-RELEASE cycle progresses. === Noteworthy Changes Since 10.4-BETA4 === o An upstream fix for zlib compression has been merged. The bug had caused the embedded Tomcat web server of UniFi Controllers to send out incorrectly compressed responses. o The Linux statfs ftype is now aware of ZFS. o A bug in bsdinstall(8) causing ifconfig_$INTERFACE lines to be added to /etc/rc.conf for unsuccessful DHCP attempts has been addressed. o The usermod command of the pw(8) utility now correctly handles empty secondary group lists (`pw usermod -G ''`) and its useradd command no longer will add entries with invalid user names, e. g. ones containing spaces. o The zfs(8) error message displayed when rejecting a checksum selection now no longer suggests unsupported hash algorithms itself. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): https://download.freebsd.org/ftp/releases/VM-IMAGES/10.4-RC1/ The partition layout is: ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label) ~ 1 GB - freebsd-swap GPT partition type (swapfs GPT label) ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VHD, VMDK, and raw disk image formats. The image download size is approximately 160 MB and 128 MB respectively (amd64/i386), decompressing to a 21 GB sparse image. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: Created AMI in ap-south-1 region: ami-b00543df Created AMI in eu-west-2 region: ami-940a19f0 Created AMI in eu-west-1 region: ami-b88143c1 Created AMI in ap-northeast-2 region: ami-723de61c Created AMI in ap-northeast-1 region: ami-baa469dc Created AMI in sa-east-1 region: ami-a9215cc5 Created AMI in ca-central-1 region: ami-99c27bfd Created AMI in ap-southeast-1 region: ami-a5acd9c6 Created AMI in ap-southeast-2 region: ami-5d12f53f Created AMI in eu-central-1 region: ami-3fd36550 Created AMI in us-east-1 region: ami-034bad79 Created AMI in us-east-2 region: ami-87f2d0e2 Created AMI in us-west-1 region: ami-ac2c1acc Created AMI in us-west-2 region: ami-c33ac9bb === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-10.4-RC1 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 10.4-RC1 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 9.x. Alternatively, the user can install misc/compat9x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 10.4-RC1 amd64 GENERIC: SHA512 (FreeBSD-10.4-RC1-amd64-bootonly.iso) = d4083ea68740c87009483311cd768fe8c1d707a457f5145f0bffeba66e5e86ebab62e0642c34c0fc9d5e4a42d883ab39c14d95a2a131dfd37c26e24e79b43814 SHA512 (FreeBSD-10.4-RC1-amd64-bootonly.iso.xz) = ceeab0b438d5f4f63ae38f1bda03b2603e1ed582584926c7f1aa1b7612fca27735be277a6c94078eba50e4c52d3fa7a079541345653f76b9a98b08c647676ee4 SHA512 (FreeBSD-10.4-RC1-amd64-disc1.iso) = e1b2462ce1133df02f02b6a09b8d18068b4ab55e41e9514097a777766644747f5d2d48430b8156f86bf1bad409abd454afa2bdcb97e7e8cac8a0f41b82f16e76 SHA512 (FreeBSD-10.4-RC1-amd64-disc1.iso.xz) = 394ae8bae8868c36182ca421b04dc6de8fbb1eb91e85ff95e06b9376c672810f27c975fd8c2cfa85822db2b1fb5e926b93bbab7e47977babd4105da49c35246d SHA512 (FreeBSD-10.4-RC1-amd64-dvd1.iso) = 2aec026e8d24db90b9a1b01288bd2f8a7a7509a2c6be995b5c50340f570bf899e59e0cac79cd7b8f6b06f7f3f3e59441b94be000f060454b5fe711dc47b2ed48 SHA512 (FreeBSD-10.4-RC1-amd64-dvd1.iso.xz) = 50d8d00e2cb191e73ff6d8f4dae3ca5d9c9ec412a347d1630a3dfec231ec53ede60c0e5559259a790be74a5b89c2c20f9c9c2d0b0ee15d39976603a2d59275a8 SHA512 (FreeBSD-10.4-RC1-amd64-memstick.img) = 4bd8306f80bea886e0861fcc0388664731d8a8aa2d55a3a6e71b4ca6465c74a0ba930e99fe945b3e37db37f21c77d2ac7738cef725230127d1b4f4bb6dacce45 SHA512 (FreeBSD-10.4-RC1-amd64-memstick.img.xz) = c4281c8acdd6c1833b75d6366755c6b50fd78db2250b1c5befeaab3afaebbbf50a6c38bc6c8702de7b3ddfb59bb79b261cd3f269e4de920b92f86fd29a8756bc SHA512 (FreeBSD-10.4-RC1-amd64-mini-memstick.img) = 6f99ca9761777befc17de8869f1b79989548babb914053e30e8917bb1bcddde3d649e4296245127ecc15cd0fdcad8bc363c777fcea14c85b8e19b30e2b5af3d2 SHA512 (FreeBSD-10.4-RC1-amd64-mini-memstick.img.xz) = 203e629e9ece81ba16db6c8d516bba7631ef5ca260a23679b437f636382889be1fe3092868c5bc3ae06637cd7e9a772629c9718527d635f9f980d38d918de22f SHA512 (FreeBSD-10.4-RC1-amd64-uefi-bootonly.iso) = a0496688f785c222c04756f0634ad92cf0f527d9ed9f405a11ac9f6dea5146ede40e70be84716e2fca1c2bb7ce6b887a3de4af2746b4c0deb6e53aa747f8ed53 SHA512 (FreeBSD-10.4-RC1-amd64-uefi-bootonly.iso.xz) = 3c3776e4d8579477390df4276dc4974fb9b34ae74d1a9b4c9e206a2187edfad64db99b977de4bd4ac089e41441e9536ca59916b29ab2b3681f29f0af11c009f2 SHA512 (FreeBSD-10.4-RC1-amd64-uefi-disc1.iso) = be48416f6a74273a1def3f73ea9eb1ea531b2014b8bf68b1a680cd2a3242f0f0cb745ffe8955a786fdd80c796b73075a1535cc118015f893a417b2788fb25cfd SHA512 (FreeBSD-10.4-RC1-amd64-uefi-disc1.iso.xz) = f3db9a5e52495009f39e3b8180fb2521d05bf5fffb3711214de59f2949a104bedb34d610a0489c0caf7eeb4f524510a0d843ede393ae63bf6ebea2ed568ae502 SHA512 (FreeBSD-10.4-RC1-amd64-uefi-dvd1.iso) = d26b2dfded05a9ab1b16886e813b3b26f35f3a08802f7164b4a96c38e43e4f37dea679858f1fe1045905d0a00a54dfffd060c113f4b2f05023d820ad636aa207 SHA512 (FreeBSD-10.4-RC1-amd64-uefi-dvd1.iso.xz) = 4157f0e45577737df37a69009704114913c0c2fb6830494268b4e34fde6d9bffd88ea4ebe7d80d4d4a7de5694e14d27af2b3c8444768cf392d77d3f85e2d7a38 SHA512 (FreeBSD-10.4-RC1-amd64-uefi-memstick.img) = 576f21094ede83540c9a8692525977e350b91d579ac7f8229ee1558f553f7e9136a6e9df81b78e0e9a71778d9adbcfc657dfed381472fbe033c31b4a36df9ef0 SHA512 (FreeBSD-10.4-RC1-amd64-uefi-memstick.img.xz) = 008b529ffef465a0141cdaa2f565bcad915120f74e9b6b444a24fea6b7ee24d4a85476111a156cb3c8fe9c6520590db6050d6b26dc685f2123b257961f916c5b SHA512 (FreeBSD-10.4-RC1-amd64-uefi-mini-memstick.img) = 15fada0168ef3044152f4fb3a6b5f07b5a5e1173cd102298533fb2d35a844f7c844a434a17c7d3e3e896b91e4b56739acd0ba45a60cbaf60f3a5a88a7e28fbfd SHA512 (FreeBSD-10.4-RC1-amd64-uefi-mini-memstick.img.xz) = 51ff8e324830f6d8653ce6cb6409f30e94511027c881afd112e7ac002dd89a0a851f4544ef7ff04ae3bb2523dafe18272d51e826c91b893fd299fada4855274d SHA256 (FreeBSD-10.4-RC1-amd64-bootonly.iso) = bb692e5ee22a43530860d46293391ee32b65931372006039a8e15789f85745d5 SHA256 (FreeBSD-10.4-RC1-amd64-bootonly.iso.xz) = 7b993a18438c79e27b12d853f02a85cf587e1bba27b80ac3a8a9563d4b9bb471 SHA256 (FreeBSD-10.4-RC1-amd64-disc1.iso) = b37b94a51bad2c2542f07727f607e4816609eeebc6976c9631b600a96f72d1d4 SHA256 (FreeBSD-10.4-RC1-amd64-disc1.iso.xz) = 8f1e8de2f7a35dde12da1862572a31a6efb4fa93eecfa0880733ea3df1be6084 SHA256 (FreeBSD-10.4-RC1-amd64-dvd1.iso) = fb8bff7fd572b68ea9d2d3e7b6ab41db6f29ccc8ff7cc9dea08e5ad86d84f71d SHA256 (FreeBSD-10.4-RC1-amd64-dvd1.iso.xz) = af8cc2d9d327d616502ba9a69fe4fc8d11a64198b9449336b5485d9ef4478da8 SHA256 (FreeBSD-10.4-RC1-amd64-memstick.img) = bb643ae807f7a10c603c5f29910023cdc403695d36f97ae51750e2f88589e445 SHA256 (FreeBSD-10.4-RC1-amd64-memstick.img.xz) = ec949bb17b9f72ff46c618d6c8d441c725f4e4c53e493f85bbf8721c3ccec015 SHA256 (FreeBSD-10.4-RC1-amd64-mini-memstick.img) = 80482a8cb4ac11f39e070b1642cace668145435d937b0f39bee80ccf067adc48 SHA256 (FreeBSD-10.4-RC1-amd64-mini-memstick.img.xz) = 4495b88b226b51569e13c8dbc68f9b9a874db95168cecf1a052c8e656389d0b6 SHA256 (FreeBSD-10.4-RC1-amd64-uefi-bootonly.iso) = 9e54e1a7246fc0c36006e99cebc419f1c032320dccd25ce0fb1ec617fb7a0ecf SHA256 (FreeBSD-10.4-RC1-amd64-uefi-bootonly.iso.xz) = 80f0d717b1f1ce6a8b14148e12a76f8b4c733ac0317b08bc9af7b198ff392edf SHA256 (FreeBSD-10.4-RC1-amd64-uefi-disc1.iso) = 778ef4525c8eb72d49a0e42f6ea6f3ba2a03082ae9cc9a5061c0562722bde434 SHA256 (FreeBSD-10.4-RC1-amd64-uefi-disc1.iso.xz) = 25d9b39a7d9c71ba2205a0b77f6af40f0bb6481077f46828aff334bb3bccdcc1 SHA256 (FreeBSD-10.4-RC1-amd64-uefi-dvd1.iso) = c5af130afdf5101d17aa469d748d92ce5222edf3728e0b8f4f3ed1bf6b08846c SHA256 (FreeBSD-10.4-RC1-amd64-uefi-dvd1.iso.xz) = 68d863a9e2ae3ff7b1e11470c7836ca7523f66deaabba0966ee45de5619902db SHA256 (FreeBSD-10.4-RC1-amd64-uefi-memstick.img) = c0a76bc09da76b252733c908b366cb8ebe04d10e9c4ea2949ecdd6235396e124 SHA256 (FreeBSD-10.4-RC1-amd64-uefi-memstick.img.xz) = dfb6495d9cb0a79635fbab41e2b2358e6fc02d5a1836743b47f9fa54dc9839a5 SHA256 (FreeBSD-10.4-RC1-amd64-uefi-mini-memstick.img) = f183e3dd578ee1f89021785e38805eb8788ae581be32bb1b9866953da28346fb SHA256 (FreeBSD-10.4-RC1-amd64-uefi-mini-memstick.img.xz) = af9946ba9cb7fc242bbafa75a4cd301e153f706e8460320a10a97aeee6301e60 o 10.4-RC1 i386 GENERIC: SHA512 (FreeBSD-10.4-RC1-i386-bootonly.iso) = 0d0d558ec01da328f08c4d582a47722f817bb8ec371876f6b16c394ad0e2f57c4531c815ebef153b168ec668c6cc2f9166176ba07e86c366a29fa005a7ef2881 SHA512 (FreeBSD-10.4-RC1-i386-bootonly.iso.xz) = 014b3f406278d8390294eda14dddb7acb55146e7d01d346f3e09ca8b84d83bf7360ecaaff34401b94a85ee376009db6ed11efc3edd8b1029f4356bfb2406bdd2 SHA512 (FreeBSD-10.4-RC1-i386-disc1.iso) = 798efd39f74e93218451831c764717aea3a4769a58a5f38a2b2014b11c94709c0ab527bdd350ec19f2385351d0dba7ed19eb0241c165952840191704798fc864 SHA512 (FreeBSD-10.4-RC1-i386-disc1.iso.xz) = d0e07e3a8c0b9df67c0b2f4c40cc0555cc32fcda9a6b96204e17955ba125e3c00fb57c70bd9c6e7d6218dcb2f0b6eea430005588df4a53c0e0ea28904472de2d SHA512 (FreeBSD-10.4-RC1-i386-dvd1.iso) = d9ee6061519c8ada24ce7420e329737b6cabbfa5cb5cab22e14a77f9074e3cceda3d69232b9d6328025e19c699e1de0599e1e432b85a9aab41bf82e042bb9281 SHA512 (FreeBSD-10.4-RC1-i386-dvd1.iso.xz) = afc5c66e8ca1f95c3cbf0d375c525dd0ea127b04584a2267e1ede21c438b3362d15dcb89027bf43c3472a582d25c5d73cf485221a8fb6ce5bd61e0099e09e99e SHA512 (FreeBSD-10.4-RC1-i386-memstick.img) = d1b3d27bc96fbf58b93d38b9503e07eb7d57d87436f9f9049cb75f68e1d033b2cf538ecdac7aece5d82f5206f60c25267d2d1eb5323ad721e9b0b9e4566d37bd SHA512 (FreeBSD-10.4-RC1-i386-memstick.img.xz) = fd0f5eb006f48a157aba3b74225a04e8cd578a2f2414e192d578db842adfc24e1a25e4b600005b1704b6e8e9ee724288491e169b4abcb9b627b5ef3cb282a3c3 SHA512 (FreeBSD-10.4-RC1-i386-mini-memstick.img) = fe1aea26c3ac499b542ed436eca0b99e4c986992de3bf7ce3019fdd36cbcd51c2b4a9ff9245b4f7d66542037cb2c9026320cc4f8a3438c136e53c37d862f9de7 SHA512 (FreeBSD-10.4-RC1-i386-mini-memstick.img.xz) = 04d9b67d88ce698bfe22f3a1f8934ffc3d9ba1b4685e05b71dc50d5c9ea02c5caf7362c67e8684b1065bca2eac46587e4446d12c801afcbc3fec8252df34998f SHA256 (FreeBSD-10.4-RC1-i386-bootonly.iso) = 96af04ce26844e096a5d8ca5fe086134f6bd7b6d3e2633d4e64b417036622f29 SHA256 (FreeBSD-10.4-RC1-i386-bootonly.iso.xz) = 2620b8aa12f188a8f1950e0220179773ad701e594fc9f4b343a1e1a8fcd7ec8b SHA256 (FreeBSD-10.4-RC1-i386-disc1.iso) = 5bc2171aa68d73a72be2a233c328ec9e708b91cf09d6d81e40af035b523f0cff SHA256 (FreeBSD-10.4-RC1-i386-disc1.iso.xz) = 690cb31a08734b635f082de75774f13293e97c6cfc47ebe445c57caff9384350 SHA256 (FreeBSD-10.4-RC1-i386-dvd1.iso) = 8c1e38952e4ff246f6bc8c28c2ce7b2252a56d0e34d2bc2abda93c7d0807deba SHA256 (FreeBSD-10.4-RC1-i386-dvd1.iso.xz) = 64d0b9a55e50f119e75ab50e2cf794a7f63e5f4cb400047fa7b68ea63a712a60 SHA256 (FreeBSD-10.4-RC1-i386-memstick.img) = 2b9048cba89d317895e1ad727af1a65008a3fa192521f1cb834ecc5174cfaa5d SHA256 (FreeBSD-10.4-RC1-i386-memstick.img.xz) = 594ccde494103dee35b6dd735fb987713c8b2992e410b892333d79f5543694cf SHA256 (FreeBSD-10.4-RC1-i386-mini-memstick.img) = 8accbb50f17fcd11ad6a945d119b850f1bacc70f04abb15c09d406fb4250902d SHA256 (FreeBSD-10.4-RC1-i386-mini-memstick.img.xz) = 8a947328ae0f8261175cb3bf588412dfc0ce1fc3aadd08bd4f89235195662454 o 10.4-RC1 ia64 GENERIC: SHA512 (FreeBSD-10.4-RC1-ia64-bootonly.iso) = e5d0b53826dd79ec5744a2eed7f0b144843915bca45c28bcb0b5350dfa6a3d1f05fe72d1621efe7ee5c1ffaca5c2855e93fcc653b5e682bd6d86d046051c1f2c SHA512 (FreeBSD-10.4-RC1-ia64-bootonly.iso.xz) = 04ee76741af46ca2d43d1f47d680a48f012949ee2013e293e22740604dfcb20d09c65d2ebddbe7fd444c2159921337096ac6e0d0a7c4118327f2360e12c0b6e6 SHA512 (FreeBSD-10.4-RC1-ia64-disc1.iso) = 14ba1790bfb78187634e3f10dd6d443955e24095ca20c1ae876a5a23719df3666d35fa54c3ad15f2d7b1383d7c9fe39e34cf2c06cb72e7d4cea1e5a9da7d9c2f SHA512 (FreeBSD-10.4-RC1-ia64-disc1.iso.xz) = aa5da381dc831cc98e1eeb08ef5d4c4cfa21c3bb81d22116d3e5722fb285ce7c59731828d805f09987c1410570e7f776b2572b2872425b5f4f23a1495a742a58 SHA512 (FreeBSD-10.4-RC1-ia64-dvd1.iso) = 6759a64350eea3e444ef033dd0ec2f5f62c73bff63bd35d1a5661ad7765468d6fd57ed680a6556a21dd93eb0a1b78786a8d4163cc17b4b3efd4aa9ab1bb3e387 SHA512 (FreeBSD-10.4-RC1-ia64-dvd1.iso.xz) = c4f5fe5080c3e23f203a81d4e37915baffaca40dcb543ede968e95e833deee1381dfe15381a22c0e393340b3308dd4656d873007a773fa9eaea50dda6a865834 SHA512 (FreeBSD-10.4-RC1-ia64-memstick.img) = 8422086ab7ed89462178da43a9b8c82fec0340af93c8baf6ee886c79038e317614ae138849ba5f87540c614b20fdc221cb0335113e2f3887219c6b5f1ec0fc3d SHA512 (FreeBSD-10.4-RC1-ia64-memstick.img.xz) = 7c79106588569aa92246b2a3abbbf88c42327ddf8a1d0382c2361d05fa30b5e2bde3de5b9824704cbe03f6fdd2fe2293309c2f08ecc6779ccf8019d34c82d9e9 SHA512 (FreeBSD-10.4-RC1-ia64-mini-memstick.img) = 498777f857984321c3b5be9afe7d2aff2c518553c77263041e70bb0cb98500ad759774fdb0e17a4a0d9f193742dadb4459ec267887cbf85e391cf41a1b192960 SHA512 (FreeBSD-10.4-RC1-ia64-mini-memstick.img.xz) = 3abd97867432b1af5a030baaf5eaf15a60b2936cffc02d79c274d18e64922670521cdd292a97b3aaa4d3beb4eca2e6db1f94204a2429b8ef475078b829eea07d SHA256 (FreeBSD-10.4-RC1-ia64-bootonly.iso) = eef31a3d88192fb84515e97548b62b3361e0e21a4e00a7e8af18cfd465cf0310 SHA256 (FreeBSD-10.4-RC1-ia64-bootonly.iso.xz) = 6c558ea56570c071e764c8005a7aed205bb0f6c206a41b5d7fefc05aa4ed2891 SHA256 (FreeBSD-10.4-RC1-ia64-disc1.iso) = 8988954b8772f9a5ca53ef2da318f0125260021ab5a5df383326931b923cf90b SHA256 (FreeBSD-10.4-RC1-ia64-disc1.iso.xz) = cccd5b6607ba316ded97ba66010231c9a1cc6a2792546c629d924bbe26ce37ae SHA256 (FreeBSD-10.4-RC1-ia64-dvd1.iso) = 7b780350de096cb15724541203f6ed97ba2224c4c40013479b0fd2483295e03c SHA256 (FreeBSD-10.4-RC1-ia64-dvd1.iso.xz) = 032467e4ab46af17c3e8e4507cab9399ac10db6d49d5bbf0f8133da5757b11fa SHA256 (FreeBSD-10.4-RC1-ia64-memstick.img) = f57bbe70e11d02ec9768dc45b973ebf2b5bc32e07db084cd3390bf2c48b4fe8d SHA256 (FreeBSD-10.4-RC1-ia64-memstick.img.xz) = 1de689d5b9fc234d144ddddcd133633f168aee3340ad3256b621a7ae2a2884f8 SHA256 (FreeBSD-10.4-RC1-ia64-mini-memstick.img) = 81d543f7a474c205c75d877a6076d78d6aa13836bfb54cc34be625af7fa9410f SHA256 (FreeBSD-10.4-RC1-ia64-mini-memstick.img.xz) = 45d5353da5fb0b9a118946c4c8517ccea536eede67a3de5e5276a0be84991c52 o 10.4-RC1 powerpc GENERIC: SHA512 (FreeBSD-10.4-RC1-powerpc-bootonly.iso) = 929f4549db6c71f451c554c99d957df7e004ab9967fa655ebcce887f87b8862107f07e98d9933fc6bdb96228eccb646c85fd0941508b3a1a41e9b0c1cb8c3230 SHA512 (FreeBSD-10.4-RC1-powerpc-bootonly.iso.xz) = ac9f1c73b2db7f9eff2740b7da2c5b81c37138cde0f1fc985bc59a4abc6926205121992d227e7d7c723ac7d7229af44e1a62e0b3b673e9b0720e58a33dc4529f SHA512 (FreeBSD-10.4-RC1-powerpc-disc1.iso) = 453c69c3ab0fbea6168c1f74955cef9c53c3128c2d763113eca0406ecb8ff9551e753bf75fd43b2038b7a8ef7222153f62e0e432e74ba28532c22779503ef5f1 SHA512 (FreeBSD-10.4-RC1-powerpc-disc1.iso.xz) = 815c9e03f6252697a778c5d2c310839dd8863ebeee71d1ef496becc4c7aee414bac0b5c75c1c3f2cd5bf0d1f1241ad07a279e869a53255ac60ded2afdade7390 SHA512 (FreeBSD-10.4-RC1-powerpc-dvd1.iso) = dcf73aae5fafbac4eb3c1cba2d4027ed31f4e066f6fe571ad3fbeec79da204af1ef0d0706675013f25b81482a2ea269d79a49b945def2d024654165a50a96ab2 SHA512 (FreeBSD-10.4-RC1-powerpc-dvd1.iso.xz) = f3be21cdd42d92712c0e6ad158599450dec66c8262381c1afd885c76ec2c1f7233411787bea208991f4b2c6109e0aa7b62179efd178b3bb5a4edca8a25b146c9 SHA512 (FreeBSD-10.4-RC1-powerpc-memstick.img) = 6dbc73d687d32c4b5299cf3586fbe6237cea503e9368c7b3df46ad246ab7119597c84882f8d754808d0aa09a749f4b7eee0d8c8706705234d28721fcd61b2167 SHA512 (FreeBSD-10.4-RC1-powerpc-memstick.img.xz) = ab4d8d803466b6707ebc3d70c2728d236f785047b6fcf09353ba8123a74ea472bfb4cbc33d11833a6359781ec3fa3503ede7113aceab427f1005963077a3f864 SHA512 (FreeBSD-10.4-RC1-powerpc-mini-memstick.img) = e29ab2efe26136ec6ea75b06b6a31ad80f0b9b031b9b60157f9dabf944238d981ea05eaab152f7c435cac5ebd114c85bd0dd2bc85d26cf3b6d71a03f708ad8d3 SHA512 (FreeBSD-10.4-RC1-powerpc-mini-memstick.img.xz) = 7ef46df81390c2eff1bccc96ee7741230c0d17044cf1b6ef16fe461448443d468f13cec7467536b6349f088cc2d0cf6718e700e2ad6ff1843f81a5f8ff134c68 SHA256 (FreeBSD-10.4-RC1-powerpc-bootonly.iso) = db475fa230f1a783e032bbf882e03000af2a8acc1b88ad81af6664917bd6b311 SHA256 (FreeBSD-10.4-RC1-powerpc-bootonly.iso.xz) = fd5dfc12209413bf98184303e2371affb1a7f098b2352a58aca71d3f0939ee6d SHA256 (FreeBSD-10.4-RC1-powerpc-disc1.iso) = 768827a9266c2e40501b916a8d61e4ca7c76d890268e99358187df4a0d512055 SHA256 (FreeBSD-10.4-RC1-powerpc-disc1.iso.xz) = 94e4cd4a947c9e7aa7f4f903e33d97d4c48a33dcc8c27db6a6667c4c663f91f6 SHA256 (FreeBSD-10.4-RC1-powerpc-dvd1.iso) = d2b2257eaede60b26153acd46a121d4574d03e473981c4e21252cfeaa48d1a8d SHA256 (FreeBSD-10.4-RC1-powerpc-dvd1.iso.xz) = da6cbeb926ff527a6716e3de9e5cee4ae14ce91eb99626d6ab78c8c02c3dc291 SHA256 (FreeBSD-10.4-RC1-powerpc-memstick.img) = 3c1432876ae69ece5325adcf7697e2612a9d20ea3d8ae2a06e0d217ede5a8803 SHA256 (FreeBSD-10.4-RC1-powerpc-memstick.img.xz) = 3269065ec60b38c8479809002867dc651f3a0f27a21c90b7639f24f45b59f0aa SHA256 (FreeBSD-10.4-RC1-powerpc-mini-memstick.img) = 560e9274d568c97da5cdc27829f8dc08f53f0437071b4b5679acc3dafdd5d791 SHA256 (FreeBSD-10.4-RC1-powerpc-mini-memstick.img.xz) = 19f6ef702e5d3d6dc074e909bd5f06a0c5905d8628dd708e6a98c21824ef1a42 o 10.4-RC1 powerpc64 GENERIC64: SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-bootonly.iso) = c6bd79d9c829ed9a27f72d533625366c5bf0d57e45569cffeb91bfb58aa7b2bd8a3da6d2702b680e6178b026fff9e4ef48e5629b2dd25c60752a043afc694dbc SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-bootonly.iso.xz) = 336e5223bc29c2634a9d26c35f0e659b65d79d369cbefe66aa1487aeb1e703f88ce8ab23fa862b8abb2ce2dcdf30a9769f55e0f30b3ab508769af75dbb5ad4ef SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-disc1.iso) = 2c29ca448a49af9c40da0cc00a930a0535c398801921489a99f9b36a4d3037f973e09f6de289e5c2fe549b84d26d81ca4bc67dfaf51bafde9ebc87cdc2f0d2a4 SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-disc1.iso.xz) = 222242c190a5b0cfae1db788395062bee44042d011c100b9114cd838e5ec2a27b5de84c068fa5f67d5223eb5060c7232989e6e3ba08a2f65a41210e73a2eb76e SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-dvd1.iso) = bea90c40ab4d7ae515218590efede444aafa9191a1e7a22f781e114fb129242fd6e561bdc9c643eec06fc69a66ecb98aa7a6234f7504b9f78a0c80be962f9cea SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-dvd1.iso.xz) = 0fb40dd9fb4d53d06d5452ec565fef670f1ffb1990d239f6307d19b8fc1122ead0b2e3c3fbc5a12386fb2776113d60bab86ce6ab1a8cba39c528d6821e75b006 SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-memstick.img) = 378777441200980b87907e91182d818cd139fb868391d1074679740fe471a6b1f9e245fc4210f9b228df1a8628f5409532a8339e945171276904ec511819765a SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-memstick.img.xz) = 707afd4fd4f0938a8d2be94c06df4a6c99b9a53aff065b03ea280b0dd58ff932fe7cb42538cc0bdbf83652479db906584b7c8d706fbbe811b2d120ad9ea219b7 SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-mini-memstick.img) = 83c64cb99aa027bb0b3ee94325fdaaced1925cd9712d01163ff890fc7649e22ac7d3961b7a2504e3452c6234ba4fd0ca16443c0d25436930a93b1294f80f5b2e SHA512 (FreeBSD-10.4-RC1-powerpc-powerpc64-mini-memstick.img.xz) = ac7a556f08f468846d15fa7e4aa3eabb4e2dabb74839b5fdd648857bfb25f7cb7e8335843a3db8905e068ea4b1da65543c0cb2131d69372a955de207baa29653 SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-bootonly.iso) = e69c53d231b397dfd8de4f8193a9a714c0507fee4f6904e9297152b4f0fee5ca SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-bootonly.iso.xz) = 9ffe42ea1c5ac70b2ad9ee2f8c53656ba9f583aec80334cd8c7392bf2085df62 SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-disc1.iso) = ea56f9c0b5eeee208bd63bfb4d04882ca0543c33a26555a19e74fe0746a3853b SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-disc1.iso.xz) = 8ec06d0fae99b248aca2060efb46be77ca2649af4b68c280e47d81ef84d804f8 SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-dvd1.iso) = ffee59f73c3ac30498fa2ce704282b3944c31e286f05ebfae2c8e5af8f57efa3 SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-dvd1.iso.xz) = ed7633448c3fdbabbf9f18b9e64dbf74649667393388eb47769ebb4ec1b7706a SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-memstick.img) = d7a6657483fa1a5c06c87483be7f9bb7e4ea3497c374a3db796b042efed87cda SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-memstick.img.xz) = 1f8e4bd15c80b16d4ae70703d3f9520f1a7683b28050e04a979e919b6507d287 SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-mini-memstick.img) = b3d99f2dd1357247b5347298b98965020bf54f09bf63c9fb38572874b5a44f7d SHA256 (FreeBSD-10.4-RC1-powerpc-powerpc64-mini-memstick.img.xz) = 1322efbae64e90020e4a58704369fe9b1dbedb937ecef3e498710df1646a3fba o 10.4-RC1 sparc64 GENERIC: SHA512 (FreeBSD-10.4-RC1-sparc64-bootonly.iso) = 7aaa2895ebf3ed3cef8ca694520838057203471154ae46cb8c38bc1a08091e1a453b094e222d6fb834948e558a53637d178972ec5d6b799173f0a884344c7944 SHA512 (FreeBSD-10.4-RC1-sparc64-bootonly.iso.xz) = bc1e7418852682cb420a8c2672c214585cc5c185d5b36256d6388b33657c2982da2af33ad51f9ef49d196e0c051a582cc72a57887f159744eebb9b7b3eb0c7c3 SHA512 (FreeBSD-10.4-RC1-sparc64-disc1.iso) = 85326ed36e3a045d66889a88711d2dd57943d23478822eba1bc1fe05ee19bde0c3eab73525133edbcaa18f60bbab7b0c50b122346a646819c0fa94d90809d0be SHA512 (FreeBSD-10.4-RC1-sparc64-disc1.iso.xz) = 7607c58afc2774bc782d1a3895390ed5c719bbd47533e201bf0ef09dbe77d3761140d40870b925f2597714ecf8e82c9deec30d78dbc3d4b31a040dab1cde6abe SHA512 (FreeBSD-10.4-RC1-sparc64-dvd1.iso) = 0abad217b60b4d824530da1db139e1dcb5111d7c49f0adc0188c45c364503294ea36e73af8c934246c791a0234ff00a0c8a7d71d33182f509d70e249ce1f50fc SHA512 (FreeBSD-10.4-RC1-sparc64-dvd1.iso.xz) = 5cffe365d5913e97883772cf334f15a0a656d7cdab65ec873cddc3a7b2c5f6ac2af3c3592d9181f00f39461d0f39d94e2b212a398c649493013b079c78cefc40 SHA256 (FreeBSD-10.4-RC1-sparc64-bootonly.iso) = 7b0d954099897cb318425d0559ec89c58eb8bc4e77146c9f80dbec5c25321250 SHA256 (FreeBSD-10.4-RC1-sparc64-bootonly.iso.xz) = 54d7f318f273c4dea087c329084f7a2a887da943dcbf8b5cd3c1b7f20aa48c40 SHA256 (FreeBSD-10.4-RC1-sparc64-disc1.iso) = 9e70352abe853ba0318a291f9fae5502cd8fcda1352ebc117d9736f600513e00 SHA256 (FreeBSD-10.4-RC1-sparc64-disc1.iso.xz) = 5c2ff21206a89dc852278b22a6ea4e463b84f552ce13be5788c8ecfd56d2f919 SHA256 (FreeBSD-10.4-RC1-sparc64-dvd1.iso) = bd04c854ff0ab8ac5d879329be6619963124d71f3e45cbceadf6a2ce73a42eaf SHA256 (FreeBSD-10.4-RC1-sparc64-dvd1.iso.xz) = 2b883b4d2e3e65f25a7bf42ad6ac74e1eab70f333a21f897d577165d6ca30fd4 o 10.4-RC1 armv6 BEAGLEBONE: SHA512 (FreeBSD-10.4-RC1-arm-armv6-BEAGLEBONE.img.xz) = 67257db70eb504924b350f71d5b42cdb088d61f1cc6f56fa4861c87f2735d41f781366f7ef78b61092b1f5b86449c52fa19a3eea06d622a4b3b53901c46995bf SHA256 (FreeBSD-10.4-RC1-arm-armv6-BEAGLEBONE.img.xz) = 01985b9430d77f34f529f3cf07a302d231057eaac5aad79cc13c9f0f6c643736 o 10.4-RC1 armv6 CUBOX-HUMMINGBOARD: SHA512 (FreeBSD-10.4-RC1-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = d3dc99d27ccebca49c483aac51768436f30cb9d68e7afc9c90bce89003d1bb4c10d3b09fa7e668a11893c35d18cd95627fe8e3b042938c067d65e6c1e4995f55 SHA256 (FreeBSD-10.4-RC1-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = 331461420f76baac31789bb32cf292fe47c930a56abc08d0077b66b091e69ff5 o 10.4-RC1 armv6 GUMSTIX: SHA512 (FreeBSD-10.4-RC1-arm-armv6-GUMSTIX.img.xz) = c782bd86e30860bb542451b28ac709fe7c775b15f77a60884c867fa163c05c3fd821944933c0787b7241bf30ad951a10fae421a9ca8437421c0c5402683eda1c SHA256 (FreeBSD-10.4-RC1-arm-armv6-GUMSTIX.img.xz) = d40d8ed7c8371359e28dde29a45ad0d9d07c72ca622168984bf7b6a1812cab38 o 10.4-RC1 armv6 RPI-B: SHA512 (FreeBSD-10.4-RC1-arm-armv6-RPI-B.img.xz) = a6ea2a48bd3df2e769f42a59136c01dd97568077a53e4ba6846213c56d02ecfdd41520a220507e67828b4a0c23c6e41734dd1da8769364b44ea59940c4cc1a0b SHA256 (FreeBSD-10.4-RC1-arm-armv6-RPI-B.img.xz) = 6ef11cb192cc08aca70787b2e787f1bd8c7f6ae47cafac1876f3cb16eebe0fe8 o 10.4-RC1 armv6 PANDABOARD: SHA512 (FreeBSD-10.4-RC1-arm-armv6-PANDABOARD.img.xz) = 4afb25c59f1099e56f63fc6104a6e4ebc500f0767e35d504165e9dc8fa4a77091b91b7275605eb3a65724adb7e3f1ecc30d500a7f56389422ca6dfec8c9ee65d SHA256 (FreeBSD-10.4-RC1-arm-armv6-PANDABOARD.img.xz) = 1da1d40c372014d4139a68b91aef0db073fc2b2ae68e89cea29d00a8b0ed0db0 o 10.4-RC1 armv6 WANDBOARD: SHA512 (FreeBSD-10.4-RC1-arm-armv6-WANDBOARD.img.xz) = 14dfb0c7108bc688e04230322297d792fffbf43cce48fc7764062884d8743a886d81384c686ba2b74dfab6f30fc3474260104c6f1e84169aa2a9f93d83e45829 SHA256 (FreeBSD-10.4-RC1-arm-armv6-WANDBOARD.img.xz) = 0c80f31ac8d6e98019697f310433ab7edf44f2b41d4f555526bcf0ff70f9e52a == VM IMAGE CHECKSUMS == o 10.4-RC1 amd64: SHA512 (FreeBSD-10.4-RC1-amd64.qcow2.xz) = 6b25e640346f654ea72ba47de912a2598873f5c97b79472cce78881eae403a3410c3c1abfbd95f6e61774f3d2a0d73aca72b56aedb2c718f99b2bdb9b5f6437f SHA512 (FreeBSD-10.4-RC1-amd64.raw.xz) = 0f390ea795ee9cf0e012d009d38304b637ae0062fb3540ce509a67358b34376cea1ab56f85af2cd669ade9a308c0c77d510e7ae94547cd4fcb859b607e48e8e8 SHA512 (FreeBSD-10.4-RC1-amd64.vhd.xz) = d42cc68d9077c33131efac53ca504d63456c0cda801d99e1176cc51405f01586ce6ad7cea8f0269a7f962f7ff8e503b6b54f999ed7f146d14eeafe8fe50d051f SHA512 (FreeBSD-10.4-RC1-amd64.vmdk.xz) = e7cfdc178862883c734f59cd1682b6f3dc4c4af97845d39b046deee2e48b7443304c6e098e3f9b911ffd8a9832c391e9d217aae6ae4caa42bbc1a3a493acf148 SHA256 (FreeBSD-10.4-RC1-amd64.qcow2.xz) = 2e186b0ec40bab17d864b14adfe94ce90b2f92319d841ca6f2b4ed3c1877ded2 SHA256 (FreeBSD-10.4-RC1-amd64.raw.xz) = 8168e09075cd7ba50cd71dacc3bd9a6df090280d014f3b1c7439dfd842083e0e SHA256 (FreeBSD-10.4-RC1-amd64.vhd.xz) = 485a59a4f094d576640b7b475ef1d948b92d6fc814a4a6d5b736a2dd8f48a74e SHA256 (FreeBSD-10.4-RC1-amd64.vmdk.xz) = f52f0749fa54c8b4b5886282ff17dae5b036e5475a0360f3d20e05fd4285dfeb o 10.4-RC1 i386: SHA512 (FreeBSD-10.4-RC1-i386.qcow2.xz) = 5405d50d26e1568bd6778dce314029549ac4623980aca466ede4902412835c443322beae6bb1a5772d8ded7011ba0dd0513a0933afb4f7c99774595e925fda79 SHA512 (FreeBSD-10.4-RC1-i386.raw.xz) = eee72c5722b436c26e8877d477e017cab57fcae8708c8a7b9b845dab6cca20bbbf52504beb79bdfe412820681f44898aa89d93498db749b74e81d18a7c4a9183 SHA512 (FreeBSD-10.4-RC1-i386.vhd.xz) = 542bad4f0109b68aef9f07963404d10d47db6fc342fcf77101abab5d20ae357511455070376c993d0a21e71093af4331ce312ad1399a49122717d34e4f0b419d SHA512 (FreeBSD-10.4-RC1-i386.vmdk.xz) = c856c961d128d3b156c53fde593ba4440e274edd0f9dcca76484a4744b088bfcb76ec6c1d41dc14f746b2e3d671a5ee932228f42e9d2e93ccd6ad208fcb326f6 SHA256 (FreeBSD-10.4-RC1-i386.qcow2.xz) = a71c63b7a663f9142d8c024d546b41bfe3f70fb33ba5f512a29c660a2d0b38ba SHA256 (FreeBSD-10.4-RC1-i386.raw.xz) = a627ec8f15872b1f06185b5ec3188271d7fa572b3812261ec1515643d192f709 SHA256 (FreeBSD-10.4-RC1-i386.vhd.xz) = 9e1ece32871d4e0e99ba0322af1f36c1a03b8f2413495843b8eda82441a89fae SHA256 (FreeBSD-10.4-RC1-i386.vmdk.xz) = 18123187c0658737e0be4f00148e0cd09761b7cf3e53b232af0aa86e0dcb0cb8 Regards Marius -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJZvbYJXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1M0Q5QjQzNTVGOTU5ODBGQzVENzZCMDIy MEI3MERFMTNGMUQxRTRGAAoJECC3DeE/HR5Pb7sP/iaiZwN+stxt7Bnir6T07IcR 42v8vRUhAK6uXYiRxvmk+u7HNOHvC9xEgdB+itVZmpXD3w+7woR7TEOLzbwqnfE4 TlV7c7qm1X/iZUTRKNKfOlX++JRpmWnrbHhhCEUDWpv8or/at3+CI0gVIdmJ9bjn on/bCn18pulB2J1AC588ST9K+191KK/eng0zfwZO5v8JEN74OE69E/9pKedQLPl/ N2CbBvGjhJlNid5BBSAkr4oGmLT7flFS2NTOQgh5oVHwf5vVRK4vwIOsPwbSn0x+ hhHf13YMKueQ0Tc2/FnnRkqTM+0Sc82n5FotpDgJ2f2uf6wkrIIrF8QKOFH949q4 Q21kJAk2qI9L5y44hjvbir0pfnRVZxzAtbD7dXd4H+S09M0I84XwGT+2cqeCRZ7S fow3zPpCdnssVQZyFwMgES1frOC+A/uwUSBjPFVT7ImUsHjztuWfKK9dPG5Sunea YXFBP7loLVnWN5TBEtL1K/OEa0elVHqV2aryN+7Zl5UDHME3MV5GAjegfXtf9qjo IT/Uq3VCcviHXwSUQA9R6anN+Cd4jyHgFCwysns6ecSIcuakQkz71VUWcXqK6lWI Fl8s+kPUBHm9+xXHDb+weBdSL/rRM4A05CsspyVyvYuWj1INJJqTvaIx0B6dLXBJ lVOjh8ZWE59+mbTGNhV3 =0LVn -----END PGP SIGNATURE-----