From owner-freebsd-stable@freebsd.org Sun Jun 17 14:27:39 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7B461020ABA for ; Sun, 17 Jun 2018 14:27:39 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:401:2100::5:8a0e]) (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 583C77010B for ; Sun, 17 Jun 2018 14:27:39 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae] (p200300E97F3E03016061D32E91BFAAAE.dip0.t-ipconnect.de [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 417xQH1z1nz9mJ for ; Sun, 17 Jun 2018 16:27:35 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net From: Michael Grimm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 Message-Id: Date: Sun, 17 Jun 2018 16:27:33 +0200 To: freebsd-stable@FreeBSD.org X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,RDNS_NONE,TW_VU autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.kaan-bock.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 14:27:39 -0000 Hi, I am running service jails (VNET/bridge/epair) and a host at = 11.2-PRERELEASE r335282, upgraded from r334874 today. All syslog messages at each jail become forwarded to syslogd running at = the host. This setup worked for years. Today not a single syslog message = becomes forwarded to the host's syslogd. Host's syslogd can be reached from inside every jail, e.g.: jtest> nc -4vuw 1 10.x.y.z 514=20 Connection to 10.x.y.z 514 port [udp/syslog] succeeded! logger doesn't throw any error. No message will be forwarded to the = host's syslogd either: jtest> logger -4 10.x.y.z HELLO jtest> I cannot find any hint in src/UPDATING.=20 What did I miss? Anyone else with a silenced syslogd? Anyone running my setup with a noisy syslogd? Thank you in advance and regards, Michael From owner-freebsd-stable@freebsd.org Sun Jun 17 14:50:32 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2AF401021D95 for ; Sun, 17 Jun 2018 14:50:32 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 BB70970F3E for ; Sun, 17 Jun 2018 14:50:31 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fUZ0f-0005Ws-OG; Sun, 17 Jun 2018 15:50:29 +0100 Date: Sun, 17 Jun 2018 15:50:29 +0100 From: Gary Palmer To: Michael Grimm Cc: freebsd-stable@FreeBSD.org Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 Message-ID: <20180617145029.GB44323@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 14:50:32 -0000 On Sun, Jun 17, 2018 at 04:27:33PM +0200, Michael Grimm wrote: > Hi, > > I am running service jails (VNET/bridge/epair) and a host at 11.2-PRERELEASE r335282, upgraded from r334874 today. > > All syslog messages at each jail become forwarded to syslogd running at the host. This setup worked for years. Today not a single syslog message becomes forwarded to the host's syslogd. > > Host's syslogd can be reached from inside every jail, e.g.: > > jtest> nc -4vuw 1 10.x.y.z 514 > Connection to 10.x.y.z 514 port [udp/syslog] succeeded! > > logger doesn't throw any error. No message will be forwarded to the host's syslogd either: > > jtest> logger -4 10.x.y.z HELLO > jtest> > > I cannot find any hint in src/UPDATING. > > What did I miss? > Anyone else with a silenced syslogd? > Anyone running my setup with a noisy syslogd? Hi, UDP is connectionless, so the client has no way of knowing if the connection succeeded or not. If you put in port 515 I suspect you'd get the same result from your 'nc' attempt. Is syslogd on the host running with '-s'? If so, that'll stop it from accepting any remote log events. Regards, Gary From owner-freebsd-stable@freebsd.org Sun Jun 17 14:58:17 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A044B102211E for ; Sun, 17 Jun 2018 14:58:17 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [IPv6:2001:41d0:302:1100::7:9a96]) (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 2F94D71395; Sun, 17 Jun 2018 14:58:16 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae] (p200300E97F3E03016061D32E91BFAAAE.dip0.t-ipconnect.de [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 417y5d0z7Pz8GY; Sun, 17 Jun 2018 16:58:13 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 From: Michael Grimm In-Reply-To: <20180617145029.GB44323@in-addr.com> Date: Sun, 17 Jun 2018 16:58:11 +0200 Cc: freebsd-stable@FreeBSD.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180617145029.GB44323@in-addr.com> To: Gary Palmer X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=1.4 required=5.0 tests=RDNS_NONE,TW_VU autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.mer-waases.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 14:58:17 -0000 On 17. Jun 2018, at 16:50, Gary Palmer wrote: > On Sun, Jun 17, 2018 at 04:27:33PM +0200, Michael Grimm wrote: >> Host's syslogd can be reached from inside every jail, e.g.: >>=20 >> jtest> nc -4vuw 1 10.x.y.z 514=20 >> Connection to 10.x.y.z 514 port [udp/syslog] succeeded! >=20 > UDP is connectionless, so the client has no way of knowing if the > connection succeeded or not. If you put in port 515 I suspect you'd > get the same result from your 'nc' attempt. You are right :-) > Is syslogd on the host running with '-s'? If so, that'll stop it > from accepting any remote log events. No, syslogd at the host is running with the following flags only: syslogd_flags=3D"-vv -b 10.x.y.z -a 10.x.y.0/24" All syslogd within jails (empty flags needed to prevent syslogd of = opening sockets) ... syslogd_flags=3D"" =E2=80=A6 and /etc/syslog.conf with: *.* @10.x.y.z Regards, Michael= From owner-freebsd-stable@freebsd.org Sun Jun 17 15:52:42 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3AE31023865 for ; Sun, 17 Jun 2018 15:52:42 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [IPv6:2001:41d0:302:1100::7:9a96]) (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 3BF5173164; Sun, 17 Jun 2018 15:52:42 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae] (p200300E97F3E03016061D32E91BFAAAE.dip0.t-ipconnect.de [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 417zJJ3TrFz8by; Sun, 17 Jun 2018 17:52:32 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 From: Michael Grimm In-Reply-To: Date: Sun, 17 Jun 2018 17:52:31 +0200 Cc: ed@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: freebsd-stable@FreeBSD.org X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=1.4 required=5.0 tests=RDNS_NONE,TW_VU autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.mer-waases.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 15:52:42 -0000 On 17. Jun 2018, at 16:27, Michael Grimm wrote: > Hi, >=20 > I am running service jails (VNET/bridge/epair) and a host at = 11.2-PRERELEASE r335282, upgraded from r334874 today. >=20 > All syslog messages at each jail become forwarded to syslogd running = at the host. This setup worked for years. Today not a single syslog = message becomes forwarded to the host's syslogd. I do believe that this commit might be the cause:=20 = https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?revisi= on=3D335059&view=3Dmarkup&sortby=3Dfile But I do have to admit, that I do not understand what changed and what = would cause my syslogd become silenced, though. Any hints? >=20 > Host's syslogd can be reached from inside every jail, e.g.: >=20 > jtest> nc -4vuw 1 10.x.y.z 514=20 > Connection to 10.x.y.z 514 port [udp/syslog] succeeded! >=20 > logger doesn't throw any error. No message will be forwarded to the = host's syslogd either: >=20 > jtest> logger -4 10.x.y.z HELLO > jtest> >=20 > I cannot find any hint in src/UPDATING.=20 >=20 > What did I miss? > Anyone else with a silenced syslogd? > Anyone running my setup with a noisy syslogd? >=20 > Thank you in advance and regards, > Michael >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Sun Jun 17 16:07:07 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9ED01000279 for ; Sun, 17 Jun 2018 16:07:07 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 45A5F73A04 for ; Sun, 17 Jun 2018 16:07:06 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 8DD5B62A5; Mon, 18 Jun 2018 01:07:04 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 1BA05716F; Mon, 18 Jun 2018 01:07:04 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id D18E7716E; Mon, 18 Jun 2018 01:07:03 +0900 (JST) Date: Mon, 18 Jun 2018 01:06:20 +0900 (JST) Message-Id: <20180618.010620.1946151016518038027.yasu@utahime.org> To: freebsd-stable@FreeBSD.org Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 From: Yasuhiro KIMURA In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 16:07:07 -0000 From: Michael Grimm Subject: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 Date: Sun, 17 Jun 2018 16:27:33 +0200 > I am running service jails (VNET/bridge/epair) and a host at 11.2-PRERELEASE r335282, upgraded from r334874 today. There was a large MFC about syslogd at r335059: https://svnweb.freebsd.org/base?view=revision&revision=335059 ---------------------------------------------------------------------- MFC r309925, r309931, r309933, r310035, r310278, r310310, r310311, r310323, r310349, r310350, r310351, r310352, r310383, r310384, r310385, r310386, r310393, r310453, r310456, r310494, r310504, r310528, r310890, r310893, r310974, r311918, r312921, r313357, r314563, r314585, r314642, r315322, r315618, r315620, r315622, r315643, r316951, r316973, r326338, r326339, r326573, r331270, r332099, r332110, r332111, r332118, r332165, r332510 and r332511. This commit brings syslogd(8) in sync with the copy in HEAD. The key improvement of this change is that it adds support for RFC 5424 log ingestion and exposition (enabled by passing in -O rfc5424). This allows for saner logging in environments with multiple time zones. The list of changes to merge back were obtained by running: svn mergeinfo --show-revs eligible \ ^/head/usr.sbin/syslogd ^/stable/11/usr.sbin/syslogd Of the commits listed, r314436, r325188 and r326025 were excluded, as they affect a significant number of unrelated files (SPDX and 4-clause license renumbering). Due to the large number of directly committed changes on this branch, I had no choice but to perform the merge as follows: svn merge --accept=theirs-full -c ^/head . This would, however, cause some unrelated changes, such as undoing the r333356 (MFC of r332877) and still adding the SPDX tag to syslogd.c. These have been reverted manually. Requested by: Dave Cottlehuber Thanks to: dim@ for sharing his insight on hackers@ ---------------------------------------------------------------------- So how about take following steps? 1. svn update -r 335058 /usr/src 2. Rebuild and reinstall /usr/sbin/syslogd and /usr/bin/wall on both host and jail. 3. Restart syslogd on both host and jail. And if the problem is dissapeared, then you should open bug report. Best, --- Yasuhiro KIMURA From owner-freebsd-stable@freebsd.org Sun Jun 17 16:34:50 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A28BA1000F6A for ; Sun, 17 Jun 2018 16:34:50 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:401:2100::5:8a0e]) (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 3CD0F74BAD for ; Sun, 17 Jun 2018 16:34:50 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae] (p200300E97F3E03016061D32E91BFAAAE.dip0.t-ipconnect.de [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 4180F30TB7zBVF for ; Sun, 17 Jun 2018 18:34:47 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net From: Michael Grimm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 Date: Sun, 17 Jun 2018 18:34:45 +0200 References: <20180618.010620.1946151016518038027.yasu@utahime.org> To: freebsd-stable@FreeBSD.org In-Reply-To: <20180618.010620.1946151016518038027.yasu@utahime.org> Message-Id: <71F1E4E9-F974-4E59-B021-181B4DF1BD5B@ellael.org> X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,RDNS_NONE,TW_SV autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.kaan-bock.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 16:34:50 -0000 On 17. Jun 2018, at 18:06, Yasuhiro KIMURA wrote: > There was a large MFC about syslogd at r335059: > So how about take following steps? > > 1. svn update -r 335058 /usr/src > 2. Rebuild and reinstall /usr/sbin/syslogd and /usr/bin/wall on both > host and jail. > 3. Restart syslogd on both host and jail. That's what I have started already in the meantime :-) > And if the problem is dissapeared, then you should open bug report. I will report and open a bug report if needed. Thank you and kind regards, Michael From owner-freebsd-stable@freebsd.org Sun Jun 17 17:27:59 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67898100309D for ; Sun, 17 Jun 2018 17:27:59 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D11147692F for ; Sun, 17 Jun 2018 17:27:58 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-wm0-x22a.google.com with SMTP id l15-v6so12319197wmc.1 for ; Sun, 17 Jun 2018 10:27:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xw1yRy9XmOZM9RhDz3gmlGEvxU4XN4mWhUy1SMsM/bI=; b=bsFaaL9doybVfaUEDTgQTQ4kzxkxNJmAmQ89BvyW5az6zaWENZC10UhHkybiJPN1ht F+PXaRyRmIZXWeRIjZFa3j8qzejRELlbfW3ap+noil9POBFIh4U0z/+qfixwyDv9WNtN 5C0kBNlUP3nXAoNFxKPaSoqyOV08hX4JZKrUn7/aIW+smoPiuEGdmv8CGMsySfbvodA/ N+clQXgocBqvqi2+d1W8AcGHH+MxGpl315mNHumQpePdBu4bZgaaCTz87aaCP2jMELuo 4nVAFRxGoxm1oxzmi2rfLLzSC2C1gyPwW2iovshAjzJOgCRNprTvsBHPyr/61CjPYOUc m17w== 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=xw1yRy9XmOZM9RhDz3gmlGEvxU4XN4mWhUy1SMsM/bI=; b=YsOQRO73lheNp02SCL+SJCX55xrvc2M2/ElT9xyEWik76iy2BXVUuFvoxwErG/Meo+ rhmPB96kEfsS5nLDpr80Pox6GPmhBrDdkSGfVUwetiQwfpg4pJ+IB4M9bIgdgoQ46sAA h9jh8inx6R8Rf3GtzTCQgZa8jCEzT96CoZD2WzqD6ZhGl2V0CoogK+gsTkpA5BON6lm3 9EOm8g5JVd5jURKExxYPe46JUWvNVpsXTh1KGIAF2bTzYQ+eeieDeQuIr9GdlwJYKEpd nu3inM7X9VT1nBEbN+o1Qc3xRlN+KycMLn5I5yVtBLZoibPEWAyl7M0dedPFcZJCk2t7 oshg== X-Gm-Message-State: APt69E1bwyk8wqvFC6sVebEKEUZxV5ZllATz9OFGqT40HhbtKTJBV/n5 dJ+uMu2BvYmQSthDPx3qbric0xWW6YdCk4V+O9AF2w== X-Google-Smtp-Source: ADUXVKL8rniVCLgsxhVL/2fG1OfsYQCpe8mtpLJFF7r0r0efnMcpG1NtaT/XKnvjKRF/HYXMqa8Fp3fgIB6iIHsSIm4= X-Received: by 2002:aa7:d3cb:: with SMTP id o11-v6mr8645462edr.104.1529256476303; Sun, 17 Jun 2018 10:27:56 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:8e0d:0:0:0:0:0 with HTTP; Sun, 17 Jun 2018 10:27:25 -0700 (PDT) In-Reply-To: References: From: Ed Schouten Date: Sun, 17 Jun 2018 19:27:25 +0200 Message-ID: Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 To: Michael Grimm Cc: FreeBSD-STABLE Mailing List , "ed@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 17:27:59 -0000 Hi Michael, 2018-06-17 17:52 GMT+02:00 Michael Grimm : > I do believe that this commit might be the cause: > https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?revision=335059&view=markup&sortby=file Thanks for reporting this issue. I just did some debugging on my system and I think I was able to reproduce this issue. It seems as if I made a tiny mistake in how I implemented the RFC 5426 UDP message size limiting. Could you please give the following patch for syslogd a try? Index: usr.sbin/syslogd/syslogd.c =================================================================== --- usr.sbin/syslogd/syslogd.c (revision 334706) +++ usr.sbin/syslogd/syslogd.c (working copy) @@ -1613,8 +1613,8 @@ struct iovec *last; size_t diff; - while (size > il->totalsize) { - diff = size - il->totalsize; + while (il->totalsize > size) { + diff = il->totalsize - size; last = &il->iov[il->iovcnt - 1]; if (diff >= last->iov_len) { /* Remove the last iovec entirely. */ It should be sufficient to apply this to just the 'client' syslogd. There is no need to patch the central (storage) server. -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands From owner-freebsd-stable@freebsd.org Sun Jun 17 20:04:30 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD87C1007F37 for ; Sun, 17 Jun 2018 20:04:30 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:401:2100::5:8a0e]) (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 478347C653; Sun, 17 Jun 2018 20:04:29 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae] (p200300E97F3E03016061D32E91BFAAAE.dip0.t-ipconnect.de [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 4184tw6FypzGY; Sun, 17 Jun 2018 22:04:24 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 From: Michael Grimm In-Reply-To: Date: Sun, 17 Jun 2018 22:04:22 +0200 Cc: "ed@FreeBSD.org" , FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Ed Schouten X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,RDNS_NONE,TW_SV autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.kaan-bock.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 20:04:30 -0000 Hi Ed -- > On 17. Jun 2018, at 19:27, Ed Schouten wrote: >=20 > Hi Michael, >=20 > 2018-06-17 17:52 GMT+02:00 Michael Grimm : >> I do believe that this commit might be the cause: >> = https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?revisi= on=3D335059&view=3Dmarkup&sortby=3Dfile >=20 > Thanks for reporting this issue. I just did some debugging on my > system and I think I was able to reproduce this issue. It seems as if > I made a tiny mistake in how I implemented the RFC 5426 UDP message > size limiting. Could you please give the following patch for syslogd a > try? >=20 > Index: usr.sbin/syslogd/syslogd.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- usr.sbin/syslogd/syslogd.c (revision 334706) > +++ usr.sbin/syslogd/syslogd.c (working copy) > @@ -1613,8 +1613,8 @@ > struct iovec *last; > size_t diff; >=20 > - while (size > il->totalsize) { > - diff =3D size - il->totalsize; > + while (il->totalsize > size) { > + diff =3D il->totalsize - size; > last =3D &il->iov[il->iovcnt - 1]; > if (diff >=3D last->iov_len) { > /* Remove the last iovec entirely. */ >=20 > It should be sufficient to apply this to just the 'client' syslogd. > There is no need to patch the central (storage) server. Sorry for my late response, and:=20 Thanks, your patch fixed it! I am not that much experienced, but that's what I did: #) svn update -r 335059 #) applied your patch #) recompiled world and kernel #) reinstalled world and kernel #) reinstalled my jail's basejail (ezjail technology) #) reboot -> return of syslogd clients being able to send syslog messages from = jails to host's syslogd I hope that this is sufficient prove that your patch will work? Thank you very much and with kind regards, Michael From owner-freebsd-stable@freebsd.org Sun Jun 17 20:46:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD891100963F for ; Sun, 17 Jun 2018 20:46:38 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::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 642F27E796 for ; Sun, 17 Jun 2018 20:46:37 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-wm0-x22c.google.com with SMTP id e16-v6so10897365wmd.0 for ; Sun, 17 Jun 2018 13:46:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=UzPdIDVJP54hfUnsR+MAUaKMkPcQ8EOp/vr/plw8OcY=; b=Af/IIPcQuOHIUvf2kmkctoSGTLwYf6XXT0DHu0Jmhuy6w/DQBBcQlm6OIglP7pHkEb qQnfwFIp6071DPc+00bun9tGVnDeH38cg4rNKM30CPOwT6YaEEh/SLXPCc8PZwI96y9F QYjeOusEDAy99a9L8h3aWyoG6bk+jb37/PvdiEt0tNXn3aYiiWIjMiJjwNhfafxpOc1x qyk84guHspewnmVvpePkU298JtGsM+pBb+Ja+TMB6TUXkDv/i/BCZD/VwG+sQ8NtjPsW VHR9+EZh3+Gwdh2QmMzJlEwqHN30P6ZcdVQXFHoDlHHz5GAWs6/lN013sqS41FPK21Gp M++A== 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=UzPdIDVJP54hfUnsR+MAUaKMkPcQ8EOp/vr/plw8OcY=; b=bfI524TFzYdc42IoQERXI+2Cgs9txl6/GNBslR8vRZxdJftbP2E9BjR74wAB4pCIbI iqTNYQGuq5Jr+YaQX8WABEPcqA/4bYFZ9LX+xf1EXLdXLQvoewKwrWWCXQskNtEpq8wv y9qBw/KJ3T2KxhkySatjOKR8+fN+niefm0HmkkC2mt7IXR0opp52apqy8FAIRHs7/GBm Or9dyhF770KUSO1kVa2pMOBfQAY5uzYCdrWHlK6ezj6GovpBud/nWxJahHte3gSFu9Ai 4zH8N1Kqqpe1Cn/qHwudrC4z6rvoFDqmKciqvRv3Qfs1Th/N4kZ8UvcVyBmkArr958Zk 8+DA== X-Gm-Message-State: APt69E22RlzPbvGSUyeSSvTkeDApJasV8ALhGLBbhQY0ZKbfTIHjv77/ EfKLWaoyy6dTaV1sdBpggmJA9dTatXtxrKydLqeyEYYl X-Google-Smtp-Source: ADUXVKI3fDPH/Z9TDPKfTLRwhwYVvBr0VLBMDZ0SDxZVZ7OLac6Bh93A1qoGozBNOTeHU9xKlgNdz+GcOscElyme5QI= X-Received: by 2002:a50:b84e:: with SMTP id k14-v6mr8912119ede.307.1529268395906; Sun, 17 Jun 2018 13:46:35 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:add4:0:0:0:0:0 with HTTP; Sun, 17 Jun 2018 13:46:35 -0700 (PDT) X-Originating-IP: [203.99.129.1] From: Jonathan Chen Date: Mon, 18 Jun 2018 08:46:35 +1200 Message-ID: Subject: regression: tmpfs in /etc/fstab results in boot stoppage To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 20:46:39 -0000 Hi, I've updated to r335297 on STABLE-11. My root fs is ZFS, and /etc/fstab is: # Device Mountpoint FStype Options Dump Pass# /dev/gpt/irontree-swap none swap sw 0 0 tmpfs /home/jonc/.cache tmpfs rw,size=512m,late 0 2 My /etc/rc.conf also contains: background_fsck="NO" When I reboot the system, the kernel boots; but the startup scripts fail with: fsck: exec fsck_tmpfs for tmpfs in /sbin/:/usr/sbin: No such file or directory THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: tmpfs: tmpfs (/home/jonc/.cache) The system continues booting up as usual once I exit single-user mode. The system used to boot up with any intervention prior to this. Cheers. -- Jonathan Chen From owner-freebsd-stable@freebsd.org Sun Jun 17 21:01:02 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39AB61009FA6 for ; Sun, 17 Jun 2018 21:01:02 +0000 (UTC) (envelope-from bugzilla-noreply@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 BB8A77F225 for ; Sun, 17 Jun 2018 21:01:01 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7C3F91009FA4; Sun, 17 Jun 2018 21:01:01 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A1DF1009FA3 for ; Sun, 17 Jun 2018 21:01:01 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A12C7F220 for ; Sun, 17 Jun 2018 21:01:01 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3D19619606 for ; Sun, 17 Jun 2018 21:01:00 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w5HL103g047768 for ; Sun, 17 Jun 2018 21:01:00 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w5HL10Wi047738 for stable@FreeBSD.org; Sun, 17 Jun 2018 21:01:00 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201806172101.w5HL10Wi047738@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: stable@FreeBSD.org Subject: Problem reports for stable@FreeBSD.org that need special attention Date: Sun, 17 Jun 2018 21:01:00 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 21:01:02 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 227213 | FreeBSD 10.4 kernel deadlocks on sysctlmemlock 1 problems total for which you should take action. From owner-freebsd-stable@freebsd.org Sun Jun 17 21:17:16 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 038D7100B1BF for ; Sun, 17 Jun 2018 21:17:16 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::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 63D2A8020C for ; Sun, 17 Jun 2018 21:17:15 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTP id w5HLGwqu081279; Mon, 18 Jun 2018 00:17:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w5HLGwqu081279 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w5HLGwPF081278; Mon, 18 Jun 2018 00:16:58 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 18 Jun 2018 00:16:58 +0300 From: Konstantin Belousov To: Jonathan Chen Cc: freebsd-stable@freebsd.org Subject: Re: regression: tmpfs in /etc/fstab results in boot stoppage Message-ID: <20180617211658.GU2493@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 21:17:16 -0000 On Mon, Jun 18, 2018 at 08:46:35AM +1200, Jonathan Chen wrote: > Hi, > > I've updated to r335297 on STABLE-11. My root fs is ZFS, and /etc/fstab is: > > # Device Mountpoint FStype Options Dump Pass# > /dev/gpt/irontree-swap none swap sw 0 0 > tmpfs /home/jonc/.cache tmpfs rw,size=512m,late 0 2 > > My /etc/rc.conf also contains: > background_fsck="NO" > > When I reboot the system, the kernel boots; but the startup scripts fail with: > > fsck: exec fsck_tmpfs for tmpfs in /sbin/:/usr/sbin: No such file or directory > THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: > tmpfs: tmpfs (/home/jonc/.cache) > > The system continues booting up as usual once I exit single-user mode. > The system used to boot up with any intervention prior to this. You specified fsck pass for tmpfs mount, which makes no sense and cannot work since there is no fsck_tmpfs. Fix you fstab. From owner-freebsd-stable@freebsd.org Sun Jun 17 22:16:57 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2017100CCEF for ; Sun, 17 Jun 2018 22:16:56 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5532E826BA for ; Sun, 17 Jun 2018 22:16:55 +0000 (UTC) (envelope-from jonc@chen.org.nz) Received: by mail-wm0-x22e.google.com with SMTP id r15-v6so11052818wmc.1 for ; Sun, 17 Jun 2018 15:16:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chen-org-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yHJvNcJQtbdfosycGp6JXq53RTb7YloTbbaZSO5OKMQ=; b=mZW2uxxjKtg5bIyaS40RjgduKt5pI6l6qcZfelPg+3L+JobgBgxqpvZn3YWcvQTDsL 2crhS1Sh/Q6bzEvzI6FMmIniU0X+pDUvgDOyQh2W5thqEnMALOyKFZ7V2g9JidzJHgdu s2QhHXP18MPdcAZ0QmDCJDkOypxx8zlMlITq8VI1JStB/AJHLSkwwq3HdbKkqd7p28ei VaziozBzy8FFUSgOJf9nyPsMXSG/L8e6Dis3AUTRvbr2IMwG1cET8lg82ZGw32XxjfeV Wg71sMfFQpkc19HqV4U+IQvurWnE5ScXt90jLxOFHwKL5kvE0gAOWlTo04hqRQwUsPlo c7aw== 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=yHJvNcJQtbdfosycGp6JXq53RTb7YloTbbaZSO5OKMQ=; b=LjRt69wnI+Vbd9h6NcBl9RqZa7V9M9YCuTQ75bGFYddQuQy+o4oQUikOQ6u6SpN/ax ZJnmkFL9/MbzaCK8zfjPBI5n+sB5kOB5Miy4j3e9OT6JF4VxMIYXWidVJK679PTPdIGE vhAACmSHe3HftvzNgjU/8hUdhZkMND5e8RJIeQsRhHVJWITUVocQxoBOS9x5yegcNUD/ hVK9D6CBoJLfvopMJk6IUoFHzNFEKQoBGBylbwKFHTPVD2UCdBOrDmUuJdgETgbLxKC3 k747K8TjiLmE/wmkU9I9Fd4fPMCDe0EAup5DkCKeLdgq67qBsyHMxa/1AZ71idn3TpOG WVkQ== X-Gm-Message-State: APt69E1YxbTG0eljZjjW5xSVffS5BrFAr4+XyLgIeqagO59gew65nQYn ndtAcAfWlBegG5Yw+2I83jSNbLKx+XLHcGy2kt7f7w== X-Google-Smtp-Source: ADUXVKIWeX4afUidXV3m2pIKaWBNLtV2s+tk+4Vf1XdQaO4AqK6YYxNcsVTCtriYt02V4H69KztgQ/JZT2TioYaeh3Q= X-Received: by 2002:a50:c211:: with SMTP id n17-v6mr9166960edf.11.1529273813904; Sun, 17 Jun 2018 15:16:53 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:add4:0:0:0:0:0 with HTTP; Sun, 17 Jun 2018 15:16:53 -0700 (PDT) X-Originating-IP: [203.99.129.1] In-Reply-To: <20180617211658.GU2493@kib.kiev.ua> References: <20180617211658.GU2493@kib.kiev.ua> From: Jonathan Chen Date: Mon, 18 Jun 2018 10:16:53 +1200 Message-ID: Subject: Re: regression: tmpfs in /etc/fstab results in boot stoppage To: Konstantin Belousov Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 22:16:57 -0000 On 18 June 2018 at 09:16, Konstantin Belousov wrote: > On Mon, Jun 18, 2018 at 08:46:35AM +1200, Jonathan Chen wrote: >> Hi, >> >> I've updated to r335297 on STABLE-11. My root fs is ZFS, and /etc/fstab is: >> >> # Device Mountpoint FStype Options Dump Pass# >> /dev/gpt/irontree-swap none swap sw 0 0 >> tmpfs /home/jonc/.cache tmpfs rw,size=512m,late 0 2 >> >> My /etc/rc.conf also contains: >> background_fsck="NO" >> >> When I reboot the system, the kernel boots; but the startup scripts fail with: >> >> fsck: exec fsck_tmpfs for tmpfs in /sbin/:/usr/sbin: No such file or directory >> THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: >> tmpfs: tmpfs (/home/jonc/.cache) >> >> The system continues booting up as usual once I exit single-user mode. >> The system used to boot up with any intervention prior to this. > > You specified fsck pass for tmpfs mount, which makes no sense and cannot > work since there is no fsck_tmpfs. Fix you fstab. Yup. That was the problem. That'll teach me to cut and paste. Sorry for the noise. -- Jonathan Chen From owner-freebsd-stable@freebsd.org Sun Jun 17 22:19:05 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64422100CE41; Sun, 17 Jun 2018 22:19:05 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 0DE6F8288F; Sun, 17 Jun 2018 22:19:04 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7AC4E21AED; Sun, 17 Jun 2018 18:19:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 17 Jun 2018 18:19:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=V0+kaAtZ23Q6DOUuAawVEveOc2TCUacM11mHsFKjE/c=; b=k0L1JHLe Z7ezm3jpSYtmbZ2bI4kcoJT6WCLRda40/0F7s3Dj+XnlFPPqtoINrTc4ObGfxprF IX5eCFqWGBuJ0oLPutScg4XXN459gaLlO31Qi3faO6RDw8QP+7g+X+qAyEuTLCSA G39Ss2IYsAnV/tjSpRgP98GeIcqHM7ifDFuvQmQk8G052vkNfN/juFlK4vpZPwh5 wo+PEoqVGt8RiN8FpuEk4J7X3rNhxuuhTX/mLSsqVFWKMv7QhXnwXKj8pGJlH753 De+M8FrGjsySAhGdwe8LtrtnsdsJIStyp8sqqxTN094kw2Xc9MpyW6mU7N57DE2w x2/86pb7FqmkjA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=V0+kaAtZ23Q6DOUuAawVEveOc2TCU acM11mHsFKjE/c=; b=cL6+xZh2aOiYaM/vI812jJDQqXXzVYFPONLq2TNAQseQg h0nUHMkosT/KHL42ZJPUv7OfYeq11rcxDRO9WGJaPPUlD/24OzA0elMVCGBHW0uo 4Ij7sxkBOlveVKApGq1ZRHAbYwBNYDQFEcsKBdkepf+AC5AOJDKUzJ73kQSvqw5Z eW+/XpJVm/wA4JaMfzXncnXJp8cQsDWhyqpJHFL3HM3EKM/Sx12hebFvImQc6/WN 8xJS4TNk++QTce8KPgh++fCTZynBpHliA06E1Avq1nVKuJ6pu5/NRKDoIpHoh8+c DCGBe3sE2RcwAqev2oE4ip5O8P5PhaRVX6v7ACGww== X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id B0034E4115; Sun, 17 Jun 2018 18:19:03 -0400 (EDT) To: freebsd-stable@freebsd.org From: tech-lists Subject: lightly loaded system eats swap space Organization: none Cc: freebsd-questions@freebsd.org Message-ID: Date: Sun, 17 Jun 2018 23:19:02 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 22:19:05 -0000 Hello list, context is (server) freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, E5-2630 @2.3GHz, generic kernel. There's one bhyve guest on this server (using 4x cpu and 16GB RAM, also freebsd-11-stable) There have been no special options for zfs configuration on the server, apart from several datasets having the compressed property set (lz4). The server runs nothing else really apart from sshd and it uses ntpd to sync local time. How come such a lightly loaded server with plenty of resources is eating up swap? If I run two bhyve instances, i.e. two of the same size as indicated above, so 32GB used for the bhyves, I'll get out-of-swapspace errors in the daily logs: +swap_pager_getswapspace(24): failed +swap_pager_getswapspace(24): failed +swap_pager_getswapspace(24): failed Here's top, with one bhyve instance running: last pid: 49494; load averages: 0.12, 0.13, 0.88 up 29+11:36:06 22:52:45 54 processes: 1 running, 53 sleeping CPU: 0.4% user, 0.0% nice, 0.4% system, 0.3% interrupt, 98.9% idle Mem: 8664K Active, 52M Inact, 4797M Laundry, 116G Wired, 1391M Buf, 4123M Free ARC: 108G Total, 1653M MFU, 105G MRU, 32K Anon, 382M Header, 632M Other 103G Compressed, 104G Uncompressed, 1.00:1 Ratio Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 49491 root 1 4 0 16444K 12024K select 9 0:12 6.49% ssh 32868 root 12 20 0 9241M 4038M kqread 2 23.2H 1.30% bhyve 49490 root 1 20 0 10812K 6192K sbwait 5 0:02 0.88% sftp From the looks of it, a huge amount of ram is wired. Why is that, and how would I debug it? A server of similar spec which is running freebsd-current with seven bhyve instances doesn't have this issue: last pid: 41904; load averages: 0.26, 0.19, 0.15 up 17+01:06:11 23:14:13 27 processes: 1 running, 26 sleeping CPU: 0.1% user, 0.0% nice, 0.3% system, 0.0% interrupt, 99.6% idle Mem: 17G Active, 6951M Inact, 41G Laundry, 59G Wired, 1573M Buf, 1315M Free ARC: 53G Total, 700M MFU, 52G MRU, 512K Anon, 182M Header, 958K Other 53G Compressed, 69G Uncompressed, 1.30:1 Ratio, 122M Overhead Swap: 35G Total, 2163M Used, 33G Free, 6% Inuse thanks, -- J. From owner-freebsd-stable@freebsd.org Sun Jun 17 23:04:37 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D80F100E214 for ; Sun, 17 Jun 2018 23:04:37 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::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 D3B58840F6 for ; Sun, 17 Jun 2018 23:04:36 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-it0-x231.google.com with SMTP id j135-v6so9582760itj.1 for ; Sun, 17 Jun 2018 16:04:36 -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=DGl5qb2Klbqts1gLgGrahYlFpV3vpYKevXc1oK+Q8o8=; b=reFKOvAB4wAGhSnN1SmCCz7DHjU48Rz3S4V9+NH6ENHw1prJz9zxi9R95jHh77CYFB TQpFvCZxEfqswDjNnRFfKbZGX/l4MRqLXYlrpUYPzwsAbLuxYo2aDcXY1bMa2QkUZnTa QiUamlV5KYfgjZEN8Vsbl5w66SZAFxq6dlnY6YwYoApoXvCUeTxX58T+2Ybobimycb3y PYT2I1Vc1u1D/zevVGUdW+BvgZeu4cnsRszIfTN7NnGt2L852y9bDBnf0u9MseWm7GCh G9eO8wqSVaLGZJOLQqw79L77l210zbxaVbqVBb0ndMrov+9OK0CIBk26f1pMg42Pwx0/ 02aA== 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=DGl5qb2Klbqts1gLgGrahYlFpV3vpYKevXc1oK+Q8o8=; b=DcyCskpXZarGLwAfMBWFRlctmPlGdhTf6TJkOAx31PhievL6y1aZaKTKO6+tNfovlo t8zX9szRxC71UI+QnRaiDc7rCAh64RcTFAQLTRSeqKEBBR5ViCDmioADRy+uU63LbtM4 HDO6O01BUb/hCahlPmO+EoZ8SZcdXcf2oxE1W6oDehh423KU1wL16Ez3Z2+aQcbzNuJl Oxzy8qQ5wLukuBYkyNJt1mJQ2tgrlcmtHCLS2McXorXV0tgdpS13JI3Fn6OdCdEHMrMX DJ9uHBr8GB+6tMIFcTHEI4Jvq4o6/gfVB45c93Jb4gljbV2HKAyBxlRYa6aS0bMReWIX ZXZw== X-Gm-Message-State: APt69E1GPviGMdhe/BZWYQTA8rQc0ht+kEVZpWXOfdfxwCuGD8Poksre mJ8sX6lTRKClj3g+886WVxWCCScmLUplBc4x4YJEJQ== X-Google-Smtp-Source: ADUXVKJ+K06cKwdUsAKynrSlO4FfVZwl9/KfJboTofrdHNQI1ySAhGdcOOEfXrY4SsU+QQ9ZUw8HEFZV3OyAO6KiMYs= X-Received: by 2002:a24:ec44:: with SMTP id g65-v6mr8343067ith.18.1529276676168; Sun, 17 Jun 2018 16:04:36 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:8d5c:0:0:0:0:0 with HTTP; Sun, 17 Jun 2018 16:04:35 -0700 (PDT) In-Reply-To: References: From: Adam Date: Sun, 17 Jun 2018 18:04:35 -0500 Message-ID: Subject: Re: lightly loaded system eats swap space To: tech-lists Cc: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2018 23:04:37 -0000 On Sun, Jun 17, 2018 at 5:19 PM, tech-lists wrote: > Hello list, > > context is (server) > freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, E5-2630 > @2.3GHz, generic kernel. > > There's one bhyve guest on this server (using 4x cpu and 16GB RAM, also > freebsd-11-stable) > > There have been no special options for zfs configuration on the server, > apart from several datasets having the compressed property set (lz4). > > The server runs nothing else really apart from sshd and it uses ntpd to > sync local time. > > How come such a lightly loaded server with plenty of resources is eating > up swap? If I run two bhyve instances, i.e. two of the same size as > indicated above, so 32GB used for the bhyves, I'll get out-of-swapspace > errors in the daily logs: > > +swap_pager_getswapspace(24): failed > +swap_pager_getswapspace(24): failed > +swap_pager_getswapspace(24): failed > > Here's top, with one bhyve instance running: > > last pid: 49494; load averages: 0.12, 0.13, 0.88 > > up 29+11:36:06 22:52:45 > 54 processes: 1 running, 53 sleeping > CPU: 0.4% user, 0.0% nice, 0.4% system, 0.3% interrupt, 98.9% idle > Mem: 8664K Active, 52M Inact, 4797M Laundry, 116G Wired, 1391M Buf, 4123M > Free > ARC: 108G Total, 1653M MFU, 105G MRU, 32K Anon, 382M Header, 632M Other > 103G Compressed, 104G Uncompressed, 1.00:1 Ratio > Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU > COMMAND > 49491 root 1 4 0 16444K 12024K select 9 0:12 6.49% ssh > 32868 root 12 20 0 9241M 4038M kqread 2 23.2H 1.30% bhyve > 49490 root 1 20 0 10812K 6192K sbwait 5 0:02 0.88% sftp > > From the looks of it, a huge amount of ram is wired. Why is that, and how > would I debug it? > That seems to be shown in the output you provided: ARC: 108G Total, 1653M MFU, 105G MRU, 32K Anon, 382M Header, 632M Other > > A server of similar spec which is running freebsd-current with seven bhyve > instances doesn't have this issue: > Based upon the output neither ram nor swap seems like similar spec so I wonder if you could say what you mean by that. -- Adam From owner-freebsd-stable@freebsd.org Mon Jun 18 04:47:44 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEFC0101658B; Mon, 18 Jun 2018 04:47:43 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::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 2C0016DEC8; Mon, 18 Jun 2018 04:47:43 +0000 (UTC) (envelope-from michaelsprivate@gmail.com) Received: by mail-wr0-x22b.google.com with SMTP id d2-v6so15253577wrm.10; Sun, 17 Jun 2018 21:47:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FIpIzt2fCLYBjQDP4IzSgyZWUMxU9Zd4asZZe8s1FnI=; b=jex3euNIB+mFSVQvv+CNV0ouk8Y1OdqsHr+p5GgvBBciTwM/zKAuERRgwQknc9a5jT dyy3+inezWmDLLKKpRYnLe3L3Ae2fNMC2bQrIkGZiBYONvl6qiiZE0NCmyaDKTklE9ev o9Hcwji1g9aOv8+luLucFnj007HRqh/seN7ZX0lCnxmI2KhrpFobq8WO/wUj/QTdW756 2yfHz0iaAiXghndn2emHFMfGl3A08tR2dF1SpVD5iwpkaGPloZJYgP9pFldv76LSN8dl W4xyZ1ki1QoaSbeRjJar2iqA5pAYiHDT2pdRMOFMB02x6ijKFJs6ooO55c8LYERkxMzD 4IBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FIpIzt2fCLYBjQDP4IzSgyZWUMxU9Zd4asZZe8s1FnI=; b=GayWcqCxRsFuU8iS3E2ng10uOKpP6pFsq14ZAcSw9q0j30WBpNGEJpwmjqiYNoFaIo jHv78tS1ksserct+/D4zDaCwtPZJ4skV67m7Ahg6zdwdIhtyD4Mc/0MbAP3u/cHyfSLb w5HEA4yKGefxrpdoQnMj0ja6G0GRNFGeKL5hDBsTRtcBjvBLnvO7gX5aRJZJFQFd7fhK B0AjC8L08IlEEFtvMmqRbwXtZrkc8JdF8ijeewMf94azkCAqUbQBJ7yidH6txzguZpJc KGzVcqXPiaDZT+l6rt0YJewHG4Gds4cX5ToCcNR+0U91NvZiE7rC+M+8HNZwtoOjzyZl eI5A== X-Gm-Message-State: APt69E3aht6TM7LD6cl6A4azFiR5nlUkKOaXAyuVNfDadrtEcXcuY2zC JlrXiwoF60ZfQg0HpWZQmS2Xc30DgyyBCbGmtDs+mA== X-Google-Smtp-Source: ADUXVKI4dKlpGO5UojqaiE/U10Sr3muuOPh5/4ir+DZjPI6dYmLxf+eJ5G9LRMHM1vxd9NTF0ZzoSCqMS4Oelasfbac= X-Received: by 2002:adf:efcf:: with SMTP id i15-v6mr9458643wrp.195.1529297261899; Sun, 17 Jun 2018 21:47:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Michael Schuster Date: Mon, 18 Jun 2018 06:47:30 +0200 Message-ID: Subject: Re: lightly loaded system eats swap space To: tech-lists@zyxst.net Cc: freebsd-stable@freebsd.org, freeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 04:47:44 -0000 I'd suggest - if you haven't done so yet - you familiarize yourself with DTrace and write a probe that fires when swap_pager_getswapspace() fails, to print execname and both kernel and userland stacks (or aggregations thereof). That should give you a starting idea of what's going on. HTH Michael On Mon, Jun 18, 2018 at 12:20 AM tech-lists wrote: > Hello list, > > context is (server) > freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, > E5-2630 @2.3GHz, generic kernel. > > There's one bhyve guest on this server (using 4x cpu and 16GB RAM, also > freebsd-11-stable) > > There have been no special options for zfs configuration on the server, > apart from several datasets having the compressed property set (lz4). > > The server runs nothing else really apart from sshd and it uses ntpd to > sync local time. > > How come such a lightly loaded server with plenty of resources is eating > up swap? If I run two bhyve instances, i.e. two of the same size as > indicated above, so 32GB used for the bhyves, I'll get out-of-swapspace > errors in the daily logs: > > +swap_pager_getswapspace(24): failed > +swap_pager_getswapspace(24): failed > +swap_pager_getswapspace(24): failed > > Here's top, with one bhyve instance running: > > last pid: 49494; load averages: 0.12, 0.13, 0.88 > > > up 29+11:36:06 22:52:45 > 54 processes: 1 running, 53 sleeping > CPU: 0.4% user, 0.0% nice, 0.4% system, 0.3% interrupt, 98.9% idle > Mem: 8664K Active, 52M Inact, 4797M Laundry, 116G Wired, 1391M Buf, > 4123M Free > ARC: 108G Total, 1653M MFU, 105G MRU, 32K Anon, 382M Header, 632M Other > 103G Compressed, 104G Uncompressed, 1.00:1 Ratio > Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU > COMMAND > 49491 root 1 4 0 16444K 12024K select 9 0:12 6.49% ssh > 32868 root 12 20 0 9241M 4038M kqread 2 23.2H 1.30% bhyve > 49490 root 1 20 0 10812K 6192K sbwait 5 0:02 0.88% sftp > > From the looks of it, a huge amount of ram is wired. Why is that, and > how would I debug it? > > A server of similar spec which is running freebsd-current with seven > bhyve instances doesn't have this issue: > > last pid: 41904; load averages: 0.26, 0.19, 0.15 > > > up 17+01:06:11 23:14:13 > 27 processes: 1 running, 26 sleeping > CPU: 0.1% user, 0.0% nice, 0.3% system, 0.0% interrupt, 99.6% idle > Mem: 17G Active, 6951M Inact, 41G Laundry, 59G Wired, 1573M Buf, 1315M Free > ARC: 53G Total, 700M MFU, 52G MRU, 512K Anon, 182M Header, 958K Other > 53G Compressed, 69G Uncompressed, 1.30:1 Ratio, 122M Overhead > Swap: 35G Total, 2163M Used, 33G Free, 6% Inuse > > thanks, > -- > J. > _______________________________________________ > 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" > -- Michael Schuster http://recursiveramblings.wordpress.com/ recursion, n: see 'recursion' From owner-freebsd-stable@freebsd.org Mon Jun 18 06:03:11 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6FD310186B6 for ; Mon, 18 Jun 2018 06:03:11 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 1EEB770437 for ; Mon, 18 Jun 2018 06:03:11 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-wm0-x231.google.com with SMTP id j15-v6so13173807wme.0 for ; Sun, 17 Jun 2018 23:03:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OfjJxwPKj8walpZvgWG1v9H6b4L2F8u0QOJEJh2Tfj4=; b=jNY+c28u9jOqfEU25zB+wLfzBnMMt7NbYoKo/yqgIk3CWS2z7ALo3dAH3IEJDmuV5b Bj5skVcmUdfsfrI0klSE+FTU+7OeFoUPmUJRKbHATgIaMQlnr1B4gmNkZKIbxDa7ZPiy IstBwBpQ8H08ZFp++ZTikY/3Rv7z8FvqUokwa9xf1pvliJtVGSf5nGm2GVTYwVTMhv0A Vpned6vHPTN15BMDhqHF0RKjVWmJF0FFY0CXoFh9whwHSTOGXKsy5dms7BtYPIzTILye bE/4YEZZCoILu7Fh2oXqxV8LUUMrdVH9E33uVb/FNofyGHmFW0BD3e8LK8jrUiPVeaOd Hrfg== 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=OfjJxwPKj8walpZvgWG1v9H6b4L2F8u0QOJEJh2Tfj4=; b=pKoWFhqgG5lPTyBf2k0rg/d1h96wSgneEb5DCCTSWy5bWDpTCcEj7GcWD2uSGgLoZi o1qlc/eJ/lB+InM1ZeNNVbecClP7f06Qb48Izd32GRtxz4LmIDayt4ABEPgpBQi883t/ cjZGkcDYT3bQDQVYgCqArhHpLEtgXV79pbg8lvqWBFlEDhlLAWpn9uoE87WQDVrKUzt8 JPMIrUhX3pGclQlbUg6ej9ps2MTAnCk/QeyJMWe8xxca8OP7vhKdAN3pfi62537bpwTT mii2BcooESH6EaOVK5xU/Fw8RxYq3WxbTx1lC8bIKmSl+uRPjgQ4Um1heLME7OqxssEF hG/g== X-Gm-Message-State: APt69E0VuYHtvtmgqUpZdTnUm6WCOO6HRH/MdJ0IzQc7GNlKsKLIdItR 9r2+ldRwGErGhIk2PaRu/pKon4oPEYvJnj1+G9eAY8v1 X-Google-Smtp-Source: ADUXVKLV3IIst7b//84sogavFVo8ghQatrjXy8iY2XhfqklyvIY/ufVbsueImQK82jjumNAZUMvC3ghE+VJ6de1ccWY= X-Received: by 2002:a50:a4c6:: with SMTP id x6-v6mr9967108edb.247.1529301789902; Sun, 17 Jun 2018 23:03:09 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:8e0d:0:0:0:0:0 with HTTP; Sun, 17 Jun 2018 23:02:39 -0700 (PDT) In-Reply-To: References: From: Ed Schouten Date: Mon, 18 Jun 2018 08:02:39 +0200 Message-ID: Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 To: Michael Grimm Cc: "ed@FreeBSD.org" , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 06:03:11 -0000 Hi Michael, 2018-06-17 22:04 GMT+02:00 Michael Grimm : > Thanks, your patch fixed it! That's awesome. Thanks for confirming! > I am not that much experienced, but that's what I did: > > #) svn update -r 335059 > #) applied your patch > #) recompiled world and kernel > #) reinstalled world and kernel > #) reinstalled my jail's basejail (ezjail technology) > #) reboot > -> return of syslogd clients being able to send syslog messages from jails to host's syslogd > > I hope that this is sufficient prove that your patch will work? Yes, that's all right. I've just committed the patch (r335314) and will MFC it to 11-STABLE before the end of the week. Best regards, -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands From owner-freebsd-stable@freebsd.org Mon Jun 18 08:09:51 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 512BD101B6EB; Mon, 18 Jun 2018 08:09:51 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from out3-6.antispamcloud.com (out3-6.antispamcloud.com [185.201.18.6]) (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 975B873952; Mon, 18 Jun 2018 08:09:49 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from [153.92.8.106] (helo=srv31.niagahoster.com) by mx63.antispamcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1fUpEQ-0008UW-S8; Mon, 18 Jun 2018 10:09:47 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sumeritec.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=gEm3wPRsPyXS+NBGJb0ZPpZrCK8tkcecH8QqJGoCZwI=; b=MZlpsvT7UwW1LOWsUfyzJ/2+eQ v4ngofrjMx0YiJVyZ2SorKNYCOv2mt6R55WPxr4utmpeq1jk6A+KX9h4nlDv2OWWqWjlDmi6OMAGI cIvJWjBMDdTs0A6wPUhQ47SGDroSram1oC5zxipxW0uviuFGFtr2J+1X8moBj8o6vr8xqJZqtRDpD NR2nsXVv8sGps7F4i/covkaRnuD5+0kgjfz7dS5O4mH6P/EOlh61Kt45P4T4A2vPp6TBLMTyqXedw 5OfRGoKHRWSoetxTua2UaG12kCrU9HAKgt0jMmfwadoYnT1qZL0zB2Ut45Ma49OcpNHp4Kr4e+4gn CkZBftpQ==; Received: from [182.1.72.71] (port=32711 helo=X220.sumeritec.com) by srv31.niagahoster.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1fUpDd-0003cT-BC; Mon, 18 Jun 2018 15:08:59 +0700 Date: Mon, 18 Jun 2018 16:08:55 +0800 From: Erich Dollansky To: tech-lists Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: lightly loaded system eats swap space Message-ID: <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AuthUser: freebsd.ed.lists@sumeritec.com X-Originating-IP: 153.92.8.106 X-AntiSpamCloud-Domain: out.niagahoster.com X-AntiSpamCloud-Username: niaga Authentication-Results: antispamcloud.com; auth=pass (login) smtp.auth=niaga@out.niagahoster.com X-AntiSpamCloud-Outgoing-Class: unsure X-AntiSpamCloud-Outgoing-Evidence: Combined (0.18) X-Recommended-Action: accept X-Filter-ID: EX5BVjFpneJeBchSMxfU5p5jyUuEFMeN2cEyxxflSzZ602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvOxaIwtUujoNIbErZzpBhdLdEykimEPJz4vxqAiX1/2grEjPCm4qLXWOIcJ1SaAOv+E97 oYmPBbBAsV+DMshiwIE28GaeyXb21dqEKgSafnP/Mp45niFjeaUIyWeLiZh8HRHC7j0cH9qYAB+8 Oassortaa40DxZPJuLUk3zkVKd8pc5mP6beSNHbKMQV1UfbiBMGP2I5RYRSmbGUKmPwb/U/j7EPL wyGgl1sc65WprSUMgaPs2PA/qMxQjIOZ02+g36bePP2vPavjKAUoKoL3CGcdvPFDEz7R9/UOaW/v I7B2yElvtk5NPfDFZk3jTGCd3X5p4tfRXn9GXx0PGKb8QzR/dsDIYtLZ61S65fJkYnwYPd7PgJ21 do/DsP4UY720aanDqIp7f9Bai3KEJ2RCApd28MKf35lHSvC6UyDhqkhDvCrJPmnnTHzVkpybMK7Z Tbvt6GDUgdrZfAzl/jONbZ14ZLY2UdqVTemi56GybUZSiB21pHej2SFGhAsaBaDjcNMgpnPA4ArU w8PAJ1qwLFEKaEyTdes6XxPEv8tlVo7TASJFC/49WOPBr5nlEUI4xI/jB0mTXNbnVkP2a/1kv6aa TQIXVemLMQyS0cqq3YQH+Bp9fvjrDTz0Dpt4Djlx/9dlrSeaoi6z0YGno18Dfl95/KWPgXY0/CRn 1glPS7LZERWeKKG4PAQYNyavp7c49IaLafRhF942nH+VU7bp5fwCHfMORCxn7EdDYJVq4nbCj0eN oSqjcN2FHYd5YcmyzumZW2vgEKPnZ9526t9hURnOigMtC9V8e3cV/Nd1154bUM0N+mCvDsNLKlp9 9LNuspzRPA8gEmeeAc/z3AcElOuR9EN4ujzBRLyRvEVDdlK4MC0RrojGu/TPp47Nf3SHfZnckpWa LvahyBjmQxBKOzu4VQ9aiX/F2wgrcsHmO+ktO2ytyEUe9V1chRGDCq/XyvjntSixwIccyyWwrjj1 e/0= X-Report-Abuse-To: spam@quarantine1.antispamcloud.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 08:09:51 -0000 Hi, On Sun, 17 Jun 2018 23:19:02 +0100 tech-lists wrote: > freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, > Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse this might not be related but I noticed that your swap space is small compared to RAM size. I noticed on a much smaller Raspberry Pi, that it runs into trouble when there is no swap even there is enough RAM available. Is it easily possible for you to add some GB of swap space and let the machine run then? How much swap do the other machines have? Erich From owner-freebsd-stable@freebsd.org Mon Jun 18 12:01:49 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D24981001D55 for ; Mon, 18 Jun 2018 12:01:48 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 76D977B399 for ; Mon, 18 Jun 2018 12:01:48 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id F190121EB9 for ; Mon, 18 Jun 2018 08:01:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 18 Jun 2018 08:01:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=FCswhxQBVk2etLJOALpduT3gZLkkr QB/NvLJsGz/Ups=; b=bnQWPIxdcM4UPPft/ofgaE9MyeyGXxf5wo4EPjoi6aCiI jDoaGT9jzUtkYT6TnX9EVcU1G5CdUSRVQLyFd39eyStTh84YqFeonl3dW9/LFb+B nu6ReQQ6kVQs3JteiGAma42oWkRkg52fvSMgG818VLWbpYqi+k/jZ412qBG/JtvH sFV8IRlx02xa3pVHhf7fmUeCl0ZJE/Q+pqvtciVtwewpP9BJgc8WRbfyauqh0qCa SpqbofH/g2gLMgb0tjudU7B9QIptxkLFBOjpXBjWn4nMhLdXVxIpWMAdxUxxKQD2 6htGUd8EBEmPm1+VmCl8bhD3gXrV7/2lv/WOeC35g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=FCswhx QBVk2etLJOALpduT3gZLkkrQB/NvLJsGz/Ups=; b=FqRTEk7H/lihhHDuj3wdJf 13uCrJecppp+olsGCZAsK/8Ik7RtGXKVCqY6RyX8dYqZksx/suYukDVBLZGaQ6LR V7m0LLICMmh+vAzlNH78dc/iazNeci0XR3DYI9lyUuYijlu3sT+r3rACokFyE3Q6 x9b57XhdmBsXNwgA2WnYYIl1aOkrvh5hxmB9Kwqv3HVa6NH57MDZBL/7xxhL38EJ yGRry1wKU8B9qFEWU9s8LLD4IxthKswe8USferp64QUuJwDSAcOjg4ioni/Lm0G8 +DKN0FcMmQ/89CSPvI1q5Tmp82llxqXuP5amzjtSezzsbtuQkM06ZHBM3wtMNibg == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 80C87E4AB7 for ; Mon, 18 Jun 2018 08:01:41 -0400 (EDT) Subject: Re: lightly loaded system eats swap space References: To: freebsd-stable@freebsd.org From: tech-lists Organization: none Message-ID: <7817cd74-ba4e-100d-72a2-050d387f90b4@zyxst.net> Date: Mon, 18 Jun 2018 13:01:40 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 12:01:49 -0000 On 18/06/2018 00:04, Adam wrote: > Based upon the output neither ram nor swap seems like similar spec so I > wonder if you could say what you mean by that. server with the problem: last pid: 62387; load averages: 0.07, 0.10, 0.08 up 30+01:30:01 12:46:40 48 processes: 1 running, 47 sleeping CPU: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 5404K Active, 1218M Inact, 4927M Laundry, 117G Wired, 1392M Buf, 2116M Free ARC: 109G Total, 2982M MFU, 105G MRU, 288K Anon, 385M Header, 638M Other 104G Compressed, 105G Uncompressed, 1.01:1 Ratio Swap: 4096M Total, 3383M Used, 713M Free, 82% Inuse This server runs 1 bhyve instance using 16GB. It has 128GB RAM. server without a problem: last pid: 84491; load averages: 0.03, 0.02, 0.02 up 17+14:39:31 12:47:33 27 processes: 1 running, 26 sleeping CPU: % user, % nice, % system, % interrupt, % idle Mem: 2915M Active, 25G Inact, 9947M Laundry, 28G Wired, 1572M Buf, 59G Free ARC: 22G Total, 3379M MFU, 19G MRU, 781K Anon, 64M Header, 974K Other 22G Compressed, 29G Uncompressed, 1.33:1 Ratio, 121M Overhead Swap: 35G Total, 3747M Used, 32G Free, 10% Inuse This server runs 10 bhyve instances of various RAM sizes, from 4GB to 32GB. It also has 128GB RAM installed. This is what I mean by "similar spec", I mean in terms of RAM. This server doesn't usually show swap as being in use, but I can actually account for this, as there is memory overcommitment here. My point is that 'server with problem' should not show a resources issue with just one bhyve instance using 16GB RAM but apparently it is, and I don't know why. I am starting the VMs by hand, without any third-party application, and I'm not wiring memory on the command line. thanks, -- J. From owner-freebsd-stable@freebsd.org Mon Jun 18 12:23:22 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F29710037E6 for ; Mon, 18 Jun 2018 12:23:22 +0000 (UTC) (envelope-from dave+freebsd@fullard.ca) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 2D7C57C333 for ; Mon, 18 Jun 2018 12:23:21 +0000 (UTC) (envelope-from dave+freebsd@fullard.ca) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 9297E20A9B for ; Mon, 18 Jun 2018 08:23:21 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute4.internal (MEProxy); Mon, 18 Jun 2018 08:23:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fullard.ca; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=zFq0sBOw9LxNNrt4PQhLsgjBuzXPZ Qsy87OuWG7t66E=; b=WAL/XU5Xws3McNjq9zqMOWKPyOimYgvqKG33+cZXEp9oU T16094Pf+wgFxn2f4va9FhnAZOOhN8TLlrr5TPd9CqdRYyg9PoGo4PKFM9GprdAL kZUT6QA3z+xou1PFqCDjKhOd6Z5KoYmvyBs4o/5LYXTzc4r3Pbh3TD7BinAjGTTe I3L6EJJVCFz9v+5BRdsujjWM2JIjEmbHEWf23Wral15yPZPgLmJiWJhan2eF4TFF 9Bq9HqhVxYsLJaUISWNQpc47Mu2+933sUgqR5ehzBWSXkg+3dqODmu6IZd4RS/vy WC3N5aGd+J+P8w1pGF5zGQVe55f2qeci7iYCJW0Mw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=zFq0sB Ow9LxNNrt4PQhLsgjBuzXPZQsy87OuWG7t66E=; b=HwAHSirhu+5NzteFZEwRay xW7+cQy+t6tpKs35vi3tI8LTyeuuj3dL665tsjXEja73AkLlbrMXoky+lJIbC65f Mf4XVwwVfs+/sj1EWObiqO9UdzBRZAvHWnADieOVGBEFACQ7hnjlDiT5pJy/biqi NdhQqR5Ci+SOnRemEHejxAOsuVzCYixk5usjWK72wn7zlctKYtrYwDa1jo7dxvZ7 2y7i3ORYy/3YMc8cc0BXmpaancu/h/UXtLqQtlbqWTgpD8omuffLjXp85j3cK7nt O4nwjqp+d3QFXAetT7SKkq9IP306xI1m3IFl80IubFcNx5OBPRCRmkPoFEjJ4jVQ == X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 5C875BA43D; Mon, 18 Jun 2018 08:23:21 -0400 (EDT) Message-Id: <1529324601.427299.1411679552.7868D498@webmail.messagingengine.com> From: David Fullard To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-498d70f2 References: Date: Mon, 18 Jun 2018 08:23:21 -0400 In-Reply-To: Subject: Re: lightly loaded system eats swap space X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 12:23:22 -0000 I've noticed you've got a rather large ZFS ARC. You could try limiting the ZFS max ARC size by setting the vfs.zfs.arc_max sysctl. On Sun, Jun 17, 2018, at 6:19 PM, tech-lists wrote: > Hello list, > > context is (server) > freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, > E5-2630 @2.3GHz, generic kernel. > > There's one bhyve guest on this server (using 4x cpu and 16GB RAM, also > freebsd-11-stable) > > There have been no special options for zfs configuration on the server, > apart from several datasets having the compressed property set (lz4). > > The server runs nothing else really apart from sshd and it uses ntpd to > sync local time. > > How come such a lightly loaded server with plenty of resources is eating > up swap? If I run two bhyve instances, i.e. two of the same size as > indicated above, so 32GB used for the bhyves, I'll get out-of-swapspace > errors in the daily logs: > > +swap_pager_getswapspace(24): failed > +swap_pager_getswapspace(24): failed > +swap_pager_getswapspace(24): failed > > Here's top, with one bhyve instance running: > > last pid: 49494; load averages: 0.12, 0.13, 0.88 > > > up 29+11:36:06 22:52:45 > 54 processes: 1 running, 53 sleeping > CPU: 0.4% user, 0.0% nice, 0.4% system, 0.3% interrupt, 98.9% idle > Mem: 8664K Active, 52M Inact, 4797M Laundry, 116G Wired, 1391M Buf, > 4123M Free > ARC: 108G Total, 1653M MFU, 105G MRU, 32K Anon, 382M Header, 632M Other > 103G Compressed, 104G Uncompressed, 1.00:1 Ratio > Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU > COMMAND > 49491 root 1 4 0 16444K 12024K select 9 0:12 6.49% ssh > 32868 root 12 20 0 9241M 4038M kqread 2 23.2H 1.30% bhyve > 49490 root 1 20 0 10812K 6192K sbwait 5 0:02 0.88% sftp > > From the looks of it, a huge amount of ram is wired. Why is that, and > how would I debug it? > > A server of similar spec which is running freebsd-current with seven > bhyve instances doesn't have this issue: > > last pid: 41904; load averages: 0.26, 0.19, 0.15 > > > up 17+01:06:11 23:14:13 > 27 processes: 1 running, 26 sleeping > CPU: 0.1% user, 0.0% nice, 0.3% system, 0.0% interrupt, 99.6% idle > Mem: 17G Active, 6951M Inact, 41G Laundry, 59G Wired, 1573M Buf, 1315M Free > ARC: 53G Total, 700M MFU, 52G MRU, 512K Anon, 182M Header, 958K Other > 53G Compressed, 69G Uncompressed, 1.30:1 Ratio, 122M Overhead > Swap: 35G Total, 2163M Used, 33G Free, 6% Inuse > > thanks, > -- > J. > _______________________________________________ > 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 Mon Jun 18 12:27:26 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D98C81003A78; Mon, 18 Jun 2018 12:27:25 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 807CC7C4A3; Mon, 18 Jun 2018 12:27:25 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 2E4A121D94; Mon, 18 Jun 2018 08:27:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 18 Jun 2018 08:27:25 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=HbgY62XQgLlcfknk80spNdlcrqZKs vY329SIbF2cgWk=; b=mGDuNleII9Gb7EizDUNCqRYWEWZ6qxPZzy+EVVKGflotE RBiFCV7RXhvQ477fGNNZWdq2XVpLq7JBLCDfEc1yQVouTx8M5u/mv1YUNlKszJ36 GdVL9EnHA7Jr70InCIUCY3sMyBGbgKBySlGMu+p05zuV4ZN7j3hlSoDzZlo9gT1s FBS+YLE16LgDn2645pLFfHMa4q8zOgwlwkuCCPGzuAc4bTgT+ZcGrRErjJa9HvrY ZJkZRWOIY+4X8JXBG0K6Cn3OfmlAsasavEMI/As4UHyBdwjJkxoYoOXsvRbz5lRh pbHtkq47ECv+ocFmO97UuoxhHNbMLOJ9R7GEjsgRg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=HbgY62 XQgLlcfknk80spNdlcrqZKsvY329SIbF2cgWk=; b=lsZkJF4FOp6O5YrKIIDIj9 +UDEDkJm91mx++6qgKUYF4llnt+MNX10sAhBPabuQ1yOMbttzdDf+sVLQkMCtlb7 i/GSo3TtwCafOTJiqVQu9fWfwRA3vgXafaeUol5qnwl8MbvO0/MsO31ORAapVyD8 1rN1/wOyph/8owMibwC90+YHgIH4jJ4GcVy3tQ4B0b/zBuoWjnZeOa4C+EJjnPPb oTKqrCO+f37NqSNZX+GYZYRDewhHunEvnyQbhLViYJkVJHpdr17zYoQQNEfqj7Rh 41iNRROKdftLepD0MNEdC7e5aK1UKXuc0x6lIu6a4fHGxX6Ul9aQj6VKGtTGPXUQ == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 6D55FE446F; Mon, 18 Jun 2018 08:27:24 -0400 (EDT) Subject: Re: lightly loaded system eats swap space References: <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> To: freebsd-stable@freebsd.org Cc: freebsd-questions@freebsd.org From: tech-lists Organization: none Message-ID: Date: Mon, 18 Jun 2018 13:27:23 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 12:27:26 -0000 On 18/06/2018 09:08, Erich Dollansky wrote: > Hi, > > On Sun, 17 Jun 2018 23:19:02 +0100 > tech-lists wrote: > >> freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, >> Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse > > this might not be related but I noticed that your swap space is small > compared to RAM size. I noticed on a much smaller Raspberry Pi, that it > runs into trouble when there is no swap even there is enough RAM > available. Is it easily possible for you to add some GB of swap space > and let the machine run then? > > How much swap do the other machines have? Hi, Yes, the machine with the problem uses the default 4GB swap. That's all the swap it has. The machine without issue has a swapfile installed on a SSD in addition to the default 4GB swap. problematic machine: Device 512-blocks Used Avail Capacity /dev/ada0p3 8388608 3.3G 714M 83% machine without a problem, it has swapfile installed: Device 512-blocks Used Avail Capacity /dev/ada0s1b 8262248 1.7G 2.2G 44% /dev/md0 65536000 1.9G 29G 6% Total 73798248 3.7G 32G 10% I added the swapfile a long time ago on this machine due to the same issue. But my problem isn't so much an out of swapspace problem; all this is, is a symptom. My problem is "why is it swapping out at all on a 128GB system and why is what's swapped out not being swapped back in again". thanks, -- J. From owner-freebsd-stable@freebsd.org Mon Jun 18 12:45:34 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25EB51004E23; Mon, 18 Jun 2018 12:45:34 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (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 9C8757D17C; Mon, 18 Jun 2018 12:45:33 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-io0-x243.google.com with SMTP id g22-v6so16675854iob.7; Mon, 18 Jun 2018 05:45:33 -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=X7GGfWcpVoVkltKL5FQgGVyHe5nBeav5QBdJBYf5Hbg=; b=hvCOLjVg8sf04QLwK0lah8XaNZmWj/sB7vt3pYT1ibBcu0ljGywJbTQ453Eeg9Elb8 peF2lf2krwVzMUaMhiUkANXFjrMcHg4cWtFl+z6DF7Y7TpViNv7kzdn/6BIzMTvzoqyR vRku5KrTRjPoftMB3OlcLcMOQ7TGss7T/Kgt6KqgVXXU6IkIw6SJy9mAIQwjc4eyZ267 OCZ5uSIVAmuCONnbfmjbMd71JhnXlySqz6kH1J3OoErI8UlQ/kMoNs5G2MTRS59QugUi bFDKF9a4nX2e4pCfhpEvHCzWzi63IuAqndYuBfZSqfcEPnagJvwVAtABLtFnhpjPlTiR U8Qw== 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=X7GGfWcpVoVkltKL5FQgGVyHe5nBeav5QBdJBYf5Hbg=; b=PyKMKHkn3CLaUXpD3um9/ZlRSkJeDtCF92wCk8ye5O4wRYJMYK555MgBuz7tfl83p+ xuYrQt6uokWdIsnyEJjTzxG1yAzH92EBXbs7zVl1xx0t5gdURTfQMb/dMpXNpHiFqpkl +sAYS6s963NJC3kJcNMCtETOwAHNk164fJvl6NkJ4o9NKvPfhpGsru+klXjcGqFfRAue 57E/GTmAotcqtaBPAMlhz26J/eVz96MNpDyhLiwJ5PHKOcXe7hgM5SHPsbIWqTGHASbn 4kTmfwg4vaDtYCrgZq8vnhWZILnc8bTjKsq4OWUXVQCOJzEuwigYAdP4UbSIF5U54Tf0 s50Q== X-Gm-Message-State: APt69E3r4wfcKPjlLpUngS/WDUviKK54VP381klPp/GQflw6XVE5Nv5h yOYLHX3voej7SdNR0z7MROq63L8tjtkaQAK+nSfOYA== X-Google-Smtp-Source: ADUXVKK6XbjnWFwax0NwrI/K15cppRA/3unysjKncozVFqZ5uGYX/pkygBZLm9wiuVP93at4CPSfqnth/UJ74IYZnhk= X-Received: by 2002:a6b:b48b:: with SMTP id d133-v6mr9551268iof.26.1529325932813; Mon, 18 Jun 2018 05:45:32 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:8d5c:0:0:0:0:0 with HTTP; Mon, 18 Jun 2018 05:45:31 -0700 (PDT) In-Reply-To: References: <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> From: Adam Date: Mon, 18 Jun 2018 07:45:31 -0500 Message-ID: Subject: Re: lightly loaded system eats swap space To: tech-lists Cc: "freebsd-stable@freebsd.org" , FreeBSD Questions Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 12:45:34 -0000 On Mon, Jun 18, 2018 at 7:27 AM, tech-lists wrote: > On 18/06/2018 09:08, Erich Dollansky wrote: > >> Hi, >> >> On Sun, 17 Jun 2018 23:19:02 +0100 >> tech-lists wrote: >> >> freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, >>> Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse >>> >> >> this might not be related but I noticed that your swap space is small >> compared to RAM size. I noticed on a much smaller Raspberry Pi, that it >> runs into trouble when there is no swap even there is enough RAM >> available. Is it easily possible for you to add some GB of swap space >> and let the machine run then? >> >> How much swap do the other machines have? >> > > Hi, > > Yes, the machine with the problem uses the default 4GB swap. That's all > the swap it has. The machine without issue has a swapfile installed on a > SSD in addition to the default 4GB swap. > > problematic machine: > Device 512-blocks Used Avail Capacity > /dev/ada0p3 8388608 3.3G 714M 83% > > machine without a problem, it has swapfile installed: > Device 512-blocks Used Avail Capacity > /dev/ada0s1b 8262248 1.7G 2.2G 44% > /dev/md0 65536000 1.9G 29G 6% > Total 73798248 3.7G 32G 10% > > I added the swapfile a long time ago on this machine due to the same issue. > > But my problem isn't so much an out of swapspace problem; all this is, is > a symptom. My problem is "why is it swapping out at all on a 128GB system > and why is what's swapped out not being swapped back in again". > What is the output of sysctl vm.overcommit? If this system is intended on being a VM host, then why don't you limit ARC to something reasonable like Total Mem - Projected VM Mem - Overhead = Ideal ARC . -- Adam From owner-freebsd-stable@freebsd.org Mon Jun 18 12:59:39 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8825A1005A67 for ; Mon, 18 Jun 2018 12:59:39 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 25F157D920 for ; Mon, 18 Jun 2018 12:59:39 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 826E621FA6 for ; Mon, 18 Jun 2018 08:59:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 18 Jun 2018 08:59:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=NX5R7mYPtrm3+3dvbOxwfKfPG2Xl/ GEUG4tPkwZYdaA=; b=AZVuo4QaClZ8lw9+P85d5eHLNJDQ4wY+qHH5O3sRZibwa fmZ6NBRz4GVmyi+nfNhDzRXYCRYw+poguU+gEf7nQ9JT36Dl7t6hCdwD1PefiXT2 2KCZbihDyuXobAOotK6mTHIriMuFWtOQb3oDXoHHkUM6pIsMT/RqvR2484rx/2ZR ws2dbgbx2ov7cImmT4/av59uKUziFSFXOO3836b/sbepzunVTYmNJ/UvjuxqOBTI E3p0gTJqYjqK0+1au3m4kcTzVWdTHwIa7pzuYT9q38x2/xdTISZZoUk9S9fCnLMB 7WAi4c3eLcsZ/OTkbajrEzL2+qCx2VraUMpinw0xw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=NX5R7m YPtrm3+3dvbOxwfKfPG2Xl/GEUG4tPkwZYdaA=; b=Xw/ezxrT6BLiThgDCqqEbO O1HgMI60Od8S2r+xYpAGgA2j7vrOyF/1iKKsuRAkY/ulnoMN/mBpF+26HChl2XMg 3Ixdeg4W+7jZxoCY91Vx5xXESQfabgMvUiMMQRb1qXVyT5hRLk89daAXG0lH1apu KY83fpgjg25NyGXtv7eYTpaL3v/yJ6NYhE7XzWnIA2hhKtK7nicu8Rs6wfeJgE7G +hhijnjoacQ5gcj8PYf4IPEDMwrTuSXwhcivOlxHiXQVHmwVQHWNjoHtqjtisAvF +eXPEX/Ymm/42Bv7l1h+C3WDJanVsNCMm3oilENGGcDDTsjvtXqMmV1Up4EREaSg == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 23221E4329 for ; Mon, 18 Jun 2018 08:59:38 -0400 (EDT) Subject: Re: lightly loaded system eats swap space To: freebsd-stable@freebsd.org References: <1529324601.427299.1411679552.7868D498@webmail.messagingengine.com> From: tech-lists Organization: none Message-ID: Date: Mon, 18 Jun 2018 13:59:37 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <1529324601.427299.1411679552.7868D498@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 12:59:39 -0000 On 18/06/2018 13:23, David Fullard wrote: > I've noticed you've got a rather large ZFS ARC. You could try > limiting the ZFS max ARC size by setting the vfs.zfs.arc_max sysctl. I'll try this as soon as I can. thanks, -- J. From owner-freebsd-stable@freebsd.org Mon Jun 18 13:10:33 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D516A100671A for ; Mon, 18 Jun 2018 13:10:33 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 793FF7E2D5 for ; Mon, 18 Jun 2018 13:10:33 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DCEF3220D0 for ; Mon, 18 Jun 2018 09:10:32 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 18 Jun 2018 09:10:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=x+Z8qeSJy9OcEIH7iOVgWSlq0icyD Q0B5GIP4IpS3r4=; b=RoRO1eJ6xzaP44Psweni28Swby/XyRugkLeSDwJziSwrE 9BgFKMgDpwVSFFLtB3moLesdKGvWkE+Zb1a0BBkyoYUNd2dz6xS+xQC5zmPI9fqI QyZSOZ1ERWaMQgaZGwxOxUOONelQf2QNZGjpSJVpekMqaJRB8b4BA/vDlsxU6R4n ZkAdwaP0kCEzCANhEuCqJdKzYRs0YCCeMEaz+s5YMfduwZUUYFlQYlSsG9rqIWSo AM4YRKXPOpxDHroTZVenpbUDzBlQ1txXE/viZhbIaOPRFnD5+0MsefxkUDislr1B UsMkBAWfpeV+ClSTsio1gew/HB+UOm1U/yUH3xSvw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=x+Z8qe SJy9OcEIH7iOVgWSlq0icyDQ0B5GIP4IpS3r4=; b=GtT/IU6a2G4JJaDcDnA4Dt 86WGlzg/S/YMDo57RZxvwb0rhdKJrf3O77LTzs33+lGsJa4TZcGui0+te12+GbkQ G2qF7vsjWwULLH20TBERDdY6/sTOb/QbLzZV7ixA4M3WfPD/+bkUQUiH3lFx9Cyn DlbujL9vo/OYSM7hKfDm9aaEnYLNhDNlMfHsaXCZrAunmqmSE3yfOZLNAtpaW+t/ zWJnaKak8JC6A+0sjOHq24hPfV2QTDH2H7Cf4lzzul66qbMNWZxshSTcZv4CkmjN PEF7VO5f04Gujn9STO5rgRCtl95andLvBLfUNrBU6fIgJXzG6i20hp7d2Q7LxBrQ == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 1B679E465F for ; Mon, 18 Jun 2018 09:10:32 -0400 (EDT) Subject: Re: lightly loaded system eats swap space References: <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> To: freebsd-stable@freebsd.org From: tech-lists Organization: none Message-ID: Date: Mon, 18 Jun 2018 14:10:31 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 13:10:34 -0000 On 18/06/2018 13:45, Adam wrote: > What is the output of sysctl vm.overcommit? That's a sysctl I've not heard of. It's 0 on both machines > If this system is intended on being a VM host, then why don't you > limit ARC to something reasonable like Total Mem - Projected VM Mem - > Overhead = Ideal ARC . I'll try doing that when I can take the machine out of service. thanks, -- J. From owner-freebsd-stable@freebsd.org Mon Jun 18 13:59:37 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF83510094F1 for ; Mon, 18 Jun 2018 13:59:36 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F62E80410; Mon, 18 Jun 2018 13:59:36 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w5IDxZ6J003622 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 18 Jun 2018 09:59:35 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w5IDxXHx052260; Mon, 18 Jun 2018 09:59:34 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French , truckman@FreeBSD.org Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com References: From: Mike Tancsa Openpgp: preference=signencrypt Autocrypt: addr=mike@sentex.net; prefer-encrypt=mutual; keydata= xsBNBEzcA24BCACpwI/iqOrs0GfQSfhA1v6Z8AcXVeGsRyKEKUpxoOYxXWc2z3vndbYlIP6E YJeifzKhS/9E+VjhhICaepLHfw865TDTUPr5D0Ed+edSsKjlnDtb6hfNJC00P7eoiuvi85TW F/gAxRY269A5d856bYrzLbkWp2lKUR3Bg6NnORtflGzx9ZWAltZbjYjjRqegPv0EQNYcHqWo eRpXilEo1ahT6nmOU8V7yEvT2j4wlLcQ6qg7w+N/vcBvyd/weiwHU+vTQ9mT61x5/wUrQhdw 2gJHeQXeDGMJV49RT2EEz+QVxaf477eyWsdQzPVjAKRMT3BVdK8WvpYAEfBAbXmkboOxABEB AAHNHG1pa2UgdGFuY3NhIDxtaWtlQHNlbnRleC5jYT7CwHgEEwECACIFAkzcA24CGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEJXHwM2kc8rX+sMH/2V6pTBKsQ5mpWWLgs6wVP2k BC+6r/YKNXv9Rw/PrC6+9hTbgA+sSjJ+8gxsCbJsOQXZrxF0x3l9oYdYfuKcwdwXFX1/FS8p HfBeDkmlH+dI709xT9wgrR4dS5aMmKp0scPrXPIAKiYVOHjOlNItcLYTEEWEFBepheEVsgmk GrNbcrHwOx/u4igUQ8vcpyXPyUki+BsftPw8ZQvBU887igh0OxaCR8AurJppQ5UQd63r81cX E1ZjoFoWCaGK/SjPb/OhpYpu5swoZIhOxQbn7OtakYPsDd5t2A5KhvjI8BMTnd5Go+2xsCmr jlIEq8Bi29gCcfQUvNiClevi13ifmnnOwE0ETNwDbgEIALWGNJHRAhpd0A4vtd3G0oRqMBcM FGThQr3qORmEBTPPEomTdBaHcn+Xl+3YUvTBD/67/mutWBwgp2R5gQOSqcM7axvgMSHbKqBL 9sd1LsLw0UT2O5AYxv3EwzhG84pwRg3XcUqvWA4lA8tIj/1q4Jzi5qOkg1zxq4W9qr9oiYK5 bBR638JUvr3eHMaz/Nz+sDVFgwHmXZj3M6aE5Ce9reCGbvrae7H5D5PPvtT3r22X8SqfVAiO TFKedCf/6jbSOedPN931FJQYopj9P6b3m0nI3ZiCDVSqeyOAIBLzm+RBUIU3brzoxDhYR8pz CJc2sK8l6YjqivPakrD86bFDff8AEQEAAcLAXwQYAQIACQUCTNwDbgIbDAAKCRCVx8DNpHPK 1+iQB/99aqNtez9ZTBWELj269La8ntuRx6gCpzfPXfn6SDIfTItDxTh1hrdRVP5QNGGF5wus N4EMwXouskva1hbFX3Pv72csYSxxEJXjW16oV8WK4KjKXoskLg2RyRP4uXqL7Mp2ezNtVY5F 9nu3fj4ydpHCSaqKy5xd70A8D50PfZsFgkrsa5gdQhPiGGEdxhq/XSeAAnZ4uVLJKarH+mj5 MEhgZPEBWkGrbDZpezl9qbFcUem/uT9x8FYT/JIztMVh9qDcdP5tzANW5J7nvgXjska+VFGY ryZK4SPDczh74mn6GI/+RBi7OUzXXPgpPBrhS5FByjwCqjjsSpTjTds+NGIY Organization: Sentex Communications Message-ID: Date: Mon, 18 Jun 2018 09:59:34 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 13:59:37 -0000 On 6/14/2018 6:30 AM, Pete French wrote: >> Check out this thread on current. I re-ran the tests I did in Feb to >> lockup the Ryzen box, and they are ok now with the latest micro code >> updates from AMD. I will let the tests run a good 48hrs, but in the >> past it would only take 5-10 min to cause a hard lockup >> >> https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > > Ah, excellent, tanksf for the pinter. I was already running the latest > microcode, but have also now flashed my BIOS and applied the shell > script fixes from that thread. Will try running with SMT re-enabled > next week, as I need the machine not to lockup the next few days > when I am not in the office, but it looks very promising. FYI, both my Epyc and Ryzen system have been running 2+ days with the tests that would normally hard lock the system in 5-60 min. The combo of Microcode updates and system settings https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html seem to have fixed the last issue I was seeing ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-stable@freebsd.org Mon Jun 18 14:34:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D19C100B5D4 for ; Mon, 18 Jun 2018 14:34:52 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (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 BE53981F3F; Mon, 18 Jun 2018 14:34:51 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fUvF1-000IoT-FI; Mon, 18 Jun 2018 14:34:47 +0000 Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Mike Tancsa , truckman@FreeBSD.org Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com References: From: Pete French Message-ID: <69049a4c-cfb0-9a4f-9cdf-86e138301543@ingresso.co.uk> Date: Mon, 18 Jun 2018 15:34:47 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 14:34:52 -0000 On 18/06/2018 14:59, Mike Tancsa wrote: > FYI, both my Epyc and Ryzen system have been running 2+ days with the > tests that would normally hard lock the system in 5-60 min. The combo of > Microcode updates and system settings Thats for the update - I turned all the default motherboard settings back on when I got into work this morning, and it has been running fine so far. WIll run like this all week. > https://lists.freebsd.org/pipermail/freebsd-current/2018-June/069799.html > > seem to have fixed the last issue I was seeing Yes, those are the chnages I have applied. I went through that list over the weekend cross-referncing them to the errata document, and there are a couple of things in there which made me think 'aha!' - particularly the MWWAIT causing lockups on SMT, as it was disbling SMT that made it stable for me. I also have access to a cpuple of (virtualised) Epyc machines which I am going to run up later in the week and try the workarounds there. But it does look very much like its fixed, which is excellent. Preseumably in the slightly longer term these workarounds go into the actual kernel if it detects Ryzen ? -pete. From owner-freebsd-stable@freebsd.org Mon Jun 18 16:08:16 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C9D11010616; Mon, 18 Jun 2018 16:08:16 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x242.google.com (mail-vk0-x242.google.com [IPv6:2607:f8b0:400c:c05::242]) (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 2417785DAF; Mon, 18 Jun 2018 16:08:16 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x242.google.com with SMTP id o71-v6so9873790vke.7; Mon, 18 Jun 2018 09:08:16 -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=pxCo33lm8wFiDXrtJUjAZYo6oCpfP6fBb9BnYU/EtuE=; b=tPG0+p0Mi9OLF3EwmpQp3ptjfV/qESdNmVS1oELqTXedG0n58B7hC3D57LevM36KPC iNFZQ7kek2N94ujWfJI+NkNnyYedtRs0otXrI8H4Fv/gKhRVzIWXsys2DrYfpKvY+8Nk /bjFmaJqqfbWRc5tcXXAn9oD5TQ2d2QBZa3XfZr3ADG291VnxqT+fpoYz5Lvw52lbS91 Dh20Z8xl6ExGx7njB0d5oKguQHrJ1pxCPIvvoYquW5ZWZ6n/cnIEWTf3Ujok6Rwr13VQ QpZiBSrDeumvMM1w5AIc4f0Gn6uCNEf7mwtanV+gMsRKGSeTK/vZzN12Pm/AtPb5greP F4zg== 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=pxCo33lm8wFiDXrtJUjAZYo6oCpfP6fBb9BnYU/EtuE=; b=bpje0qVxzoEwQXAnjRbuEp848YDt/YW48aYdC5GsSV8R1Ej2nUdc++8PXoG3VnxVee iT4TNwc/GYeho0NRoGquTFOtsTJhfQabp1c6sis1rBriPM6glVD+mqqmoThc8/xHyruz vT8E6EMaDxzg5YCfQ+XVRjgTsMkII11DQsOAiGAts0vVcJuveJYuqgxLc62BqGOxWHKs 17X4z27F+lrpHoS59Nvd26EjAbokMxO73rWs/t6W9c7oEeEuYSTgvGc9Z3nL89k02BWQ VW+vAGf5STFdJbMWTE97kgen/Zf3GB4Ps934nphub+nmr7rzDqWZ9R7bHTHAy5SdEe+5 v9HA== X-Gm-Message-State: APt69E0y+DUlTo8esS7VnHd6crwTALi8rgGe3nZNPFqQRQ8kmextRo/v Zt48+SgYH4dIJ7vFF0wEsZetGrzSF+pAWYP8RhEQotoJ X-Google-Smtp-Source: ADUXVKJG7xl7vzs7NK0xS/t4FT5bTa9d9iShyfNgVgg0E0qyjktXKw357lge3BMcipsj31Ic9HBafuycFoYAJ7L0nvs= X-Received: by 2002:a1f:5fc1:: with SMTP id t184-v6mr7398762vkb.140.1529338095424; Mon, 18 Jun 2018 09:08:15 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 2002:a67:8f05:0:0:0:0:0 with HTTP; Mon, 18 Jun 2018 09:08:14 -0700 (PDT) In-Reply-To: References: <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> From: Kevin Oberman Date: Mon, 18 Jun 2018 09:08:14 -0700 X-Google-Sender-Auth: a9IT67Z68sR0VOyrINCi-XLNw0M Message-ID: Subject: Re: lightly loaded system eats swap space To: tech-lists Cc: FreeBSD-STABLE Mailing List , Mailinglists FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 16:08:16 -0000 On Mon, Jun 18, 2018 at 5:27 AM, tech-lists wrote: > On 18/06/2018 09:08, Erich Dollansky wrote: > >> Hi, >> >> On Sun, 17 Jun 2018 23:19:02 +0100 >> tech-lists wrote: >> >> freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, >>> Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse >>> >> >> this might not be related but I noticed that your swap space is small >> compared to RAM size. I noticed on a much smaller Raspberry Pi, that it >> runs into trouble when there is no swap even there is enough RAM >> available. Is it easily possible for you to add some GB of swap space >> and let the machine run then? >> >> How much swap do the other machines have? >> > > Hi, > > Yes, the machine with the problem uses the default 4GB swap. That's all > the swap it has. The machine without issue has a swapfile installed on a > SSD in addition to the default 4GB swap. > > problematic machine: > Device 512-blocks Used Avail Capacity > /dev/ada0p3 8388608 3.3G 714M 83% > > machine without a problem, it has swapfile installed: > Device 512-blocks Used Avail Capacity > /dev/ada0s1b 8262248 1.7G 2.2G 44% > /dev/md0 65536000 1.9G 29G 6% > Total 73798248 3.7G 32G 10% > > I added the swapfile a long time ago on this machine due to the same issue. > > But my problem isn't so much an out of swapspace problem; all this is, is > a symptom. My problem is "why is it swapping out at all on a 128GB system > and why is what's swapped out not being swapped back in again". > > thanks, > -- > J. Small correction. Your problem is "why is it swapping out at all on a 128GB system ." Once pages are swapped out, they are never swapped back in until/unless they are needed. There is no reason to waste time/disk activity to swap pages back into memory unless they are required. RAM is always more valuable than swap. Ir is easy to write a process that eats up a large amount of memory, then goes idle without freeing it. The memory will get pages out, fill swap, and, unless the process terminates or becomes active, will consume up a great deal of swap space "forever". Firefox is a good example of this. I have to restart it every day or two and occasionally will run out of swap which results in a nearly deadlocked system. It can take many minutes to just kill firefox. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-stable@freebsd.org Mon Jun 18 19:50:30 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21CFF101D7A3 for ; Mon, 18 Jun 2018 19:50:30 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [IPv6:2607:fc50:1000:7400:216:3eff:fe72:314f]) (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 BD6CF6F3A1; Mon, 18 Jun 2018 19:50:29 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from sweettea.beer.town (unknown [76.164.8.130]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 583A65646E; Mon, 18 Jun 2018 14:50:28 -0500 (CDT) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French , Mike Tancsa , truckman@FreeBSD.org Cc: freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org References: <69049a4c-cfb0-9a4f-9cdf-86e138301543@ingresso.co.uk> From: Eric van Gyzen Openpgp: preference=signencrypt Message-ID: <9233bded-3ea2-dc46-19bf-f9a7eef7fa6b@vangyzen.net> Date: Mon, 18 Jun 2018 14:50:27 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <69049a4c-cfb0-9a4f-9cdf-86e138301543@ingresso.co.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 18 Jun 2018 19:50:30 -0000 On 06/18/2018 09:34, Pete French wrote: > Preseumably in the slightly longer term these workarounds go into the > actual kernel if it detects Ryzen ? Yes, Kostik said he would code this into the kernel after he gets enough feedback. Eric From owner-freebsd-stable@freebsd.org Tue Jun 19 01:48:46 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 398FC1010B1B for ; Tue, 19 Jun 2018 01:48:46 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from out3-6.antispamcloud.com (out3-6.antispamcloud.com [185.201.18.6]) (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 AD76181313 for ; Tue, 19 Jun 2018 01:48:45 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from [153.92.8.106] (helo=srv31.niagahoster.com) by mx63.antispamcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1fV5l6-0000Rk-OL; Tue, 19 Jun 2018 03:48:37 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sumeritec.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ubBK4tT6cPsmA0LT6ZjzW8O8R+hEgmmN0kXMOu2pRd0=; b=E6a6h0qxjcmP6koztbQUU/M796 JVhbJKbYkn7SpR+EX1C0yjIe6iLQ1C+v8WrBzDSzRliJRgHggMqWkbuoBLchRPr4SgNpMLHh6gEnN ry8h3Tgf7FKMPLDCtkGsZAIG2EB4PTIBjUy3LAyOjHA5AQrBI9Cy8B24mF2Hk/UcHQZOBeXrDcsAQ RI61L+d9XdRTnotIh08VbvpPeVk9SWxWpN4xS3JE91LHwzsa6LANgkkggSGFbwGoSxijY0XOuS5eD Dx3CBdOKzk/RuBZ7JplOGJtEfeicY4R40LQainIKzXVpqKiiMOAqDAAx+QiWHjBX8hAmmk2Kp0lc0 qK/3XG/g==; Received: from [182.1.110.123] (port=36627 helo=X220.sumeritec.com) by srv31.niagahoster.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1fV5ky-0000Ef-UT; Tue, 19 Jun 2018 08:48:32 +0700 Date: Tue, 19 Jun 2018 09:48:26 +0800 From: Erich Dollansky To: tech-lists Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: lightly loaded system eats swap space Message-ID: <20180619094826.75c0c735.freebsd.ed.lists@sumeritec.com> In-Reply-To: References: <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AuthUser: freebsd.ed.lists@sumeritec.com X-Originating-IP: 153.92.8.106 X-AntiSpamCloud-Domain: out.niagahoster.com X-AntiSpamCloud-Username: niaga Authentication-Results: antispamcloud.com; auth=pass (login) smtp.auth=niaga@out.niagahoster.com X-AntiSpamCloud-Outgoing-Class: ham X-AntiSpamCloud-Outgoing-Evidence: Combined (0.02) X-Recommended-Action: accept X-Filter-ID: EX5BVjFpneJeBchSMxfU5qs8ngPXEcjbWoVCgxeBz4V602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvOxaIwtUujoNIbErZzpBhdLdEykimEPJz4vxqAiX1/2grEjPCm4qLXWOIcJ1SaAOv+NWZ i5bIIYa9S0h67ZH5SXvI51WoVTst3UDc3Tc+zpnW4pWx7WxWFZpsjT/483ewgu5JfusABNhIyJPP 5Nt4ch9eUI1m44Bh4Rt/sb3dHEDQFHMPEyA05gafMZGwGiJNAwhEWvaIoDww+4QxfNN9HkkKLOus WKhOnst3qnCSa+ooImPP2dXZx92akKoN7fUg0kzXIlHX7eANWlCO2XGJyGU9oLDEz6cVLClJUS8A nGbz/BzL47xk+Q/uswILf2rDgM3sodCXd6Deqt8UbbiaEBtNhHbVMNVriwqiLfyjMaD0IGWzi/ZW VMCjfK76uXDcS+4b68bcfEUhGoUaMRLIrO7BePDP4/9QmYCRIF7Nfcc0IJ4wPZcRWc/x8B0Dq8iD 18tKpQZNCQ9fWNhdgLpZZMKumy7dSDdzT+FZaJbsZl2hXe9eBr/BlppHuPTdSOqbCq0jiD6XqsJZ tjQxlyCdsey6n3SPEHq5iliCZ8XofdvQPwUimsNGvJJilSn4u6QSZEpPc4+a4hAzgiKwXNZGYkTt cEEdFUtlBcd/cggQO2/Ly6uSlRfEHXv0FyPlUsc0FfdjzQ6YC7Heg3Xf7O1TOd70JEGZ4rWzGZ4/ zlyCC3H22azh0b/+k6ecX4jDrOoapV08UP4oHHmdSx2A1A1s+7ugyQaenMmH18/Q/rqh6KyCRQQx LY/+29TRohSqJrULEmYVBRym1GTL+3N3DlP9FRLpAXnrGA4CDNa5JkRTD9kWJR/YdqcpiEfVkaxc IKMqsCjBRB0t/r7fzY7HnTQ5j8Py3deP8vNnmz84mDUvZqxnB1hYVULyg3fWh5tbcz2mAWZJTLdd dmSmgUp4oA9rqJlne1u2s7aPHmvkjwmFXvRv X-Report-Abuse-To: spam@quarantine1.antispamcloud.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 01:48:46 -0000 Hi, On Mon, 18 Jun 2018 13:27:23 +0100 tech-lists wrote: > On 18/06/2018 09:08, Erich Dollansky wrote: > > > > On Sun, 17 Jun 2018 23:19:02 +0100 > > tech-lists wrote: > > > >> freebsd-11-stable r333874, ZFS raidz1-0 (3x4TB disks), 128GB RAM, > >> Swap: 4096M Total, 3502M Used, 594M Free, 85% Inuse > > > > this might not be related but I noticed that your swap space is > > small compared to RAM size. I noticed on a much smaller Raspberry > > Pi, that it runs into trouble when there is no swap even there is > > enough RAM available. Is it easily possible for you to add some GB > > of swap space and let the machine run then? > > > > How much swap do the other machines have? > > Yes, the machine with the problem uses the default 4GB swap. That's > all the swap it has. The machine without issue has a swapfile > installed on a SSD in addition to the default 4GB swap. > > problematic machine: > Device 512-blocks Used Avail Capacity > /dev/ada0p3 8388608 3.3G 714M 83% > > machine without a problem, it has swapfile installed: > Device 512-blocks Used Avail Capacity > /dev/ada0s1b 8262248 1.7G 2.2G 44% > /dev/md0 65536000 1.9G 29G 6% > Total 73798248 3.7G 32G 10% > > I added the swapfile a long time ago on this machine due to the same > issue. so, the same effect as on a small Raspberry. It seems that you also use a memory disk for swap. Mine is backed by a file via NFS. > > But my problem isn't so much an out of swapspace problem; all this > is, is a symptom. My problem is "why is it swapping out at all on a > 128GB system and why is what's swapped out not being swapped back in > again". > I wondered even on the small Raspberry about this. The Raspberries come with 1GB of RAM. Running just a compilation should never be the problem but sometimes it is. A very long time ago - and not on FreeBSD but maybe on a real BSD - I worked with a system that swapped pages out just to bring it back as one contiguous block. This made a difference those days. I do not know if the code made it out of the university I was working at. I just imagine now that the code made it out and is still in use with the opposite effect. Erich From owner-freebsd-stable@freebsd.org Tue Jun 19 07:06:56 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EE4F100144C; Tue, 19 Jun 2018 07:06:56 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout05.t-online.de (mailout05.t-online.de [194.25.134.82]) (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 95EDB6F3A5; Tue, 19 Jun 2018 07:06:55 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd30.aul.t-online.de (fwd30.aul.t-online.de [172.20.26.135]) by mailout05.t-online.de (Postfix) with SMTP id 5DAB44256FCE; Tue, 19 Jun 2018 09:06:46 +0200 (CEST) Received: from Stefans-MBP-204.fritz.box (SgFFUiZSoh9b2PMResQ++ZEnoJEgc3zwxFYShBgE4hc3DftoLsm3fveh5t-MzR1ZB1@[84.154.98.138]) by fwd30.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1fVAix-1m0w9A0; Tue, 19 Jun 2018 09:06:43 +0200 Subject: Re: lightly loaded system eats swap space To: Erich Dollansky , tech-lists Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org References: <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> <20180619094826.75c0c735.freebsd.ed.lists@sumeritec.com> From: Stefan Esser Openpgp: preference=signencrypt Autocrypt: addr=se@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFVxiRIBCADOLNOZBsqlplHUQ3tG782FNtVT33rQli9EjNt2fhFERHIo4NxHlWBpHLnU b0s4L/eItx7au0i7Gegv01A9LUMwOnAc9EFAm4EW3Wmoa6MYrcP7xDClohg/Y69f7SNpEs3x YATBy+L6NzWZbJjZXD4vqPgZSDuMcLU7BEdJf0f+6h1BJPnGuwHpsSdnnMrZeIM8xQ8PPUVQ L0GZkVojHgNUngJH6e21qDrud0BkdiBcij0M3TCP4GQrJ/YMdurfc8mhueLpwGR2U1W8TYB7 4UY+NLw0McThOCLCxXflIeF/Y7jSB0zxzvb/H3LWkodUTkV57yX9IbUAGA5RKRg9zsUtABEB AAHNKVN0ZWZhbiBFw59lciAoWWFob28hKSA8c3QuZXNzZXJAeWFob28uZGU+wsCWBBMBCgBA AhsDBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AWIQSjceplnAvsyCtxUxNH67XvWv31RAUC WvLvqwUJCyUBEwAKCRBH67XvWv31REySCACc6vqcSFQCRyBRc2CV5ZBjbbnTy7VBoXbUS3/c 4Hn8I0YQ39q7//2z8vYsgLeM1mMXL4PUIU/0f0dBAFBLpxV7bntGzyCJls6SeGS/qcQKhqaI 6I7NcWg8OkIJIhUL6q238cS1ql9pU65fyHe0PP8JS08m81PDpX2/4wTE6h2jgYUy55eXRzoF MEjr1S8SSnidsBem27o7iWu9ltJsUtE86071iZlLzbuHv2nvucrjAV9cK9tHrxYT/YiY8QhT L48iWj2xIjLjg1ebmgIFZ2k881we/KTIoUugqOOR1gDSc4qwM8CA388cN3frjtl98CwhAT5T UV8tIDqri+/Z1AKwzsBNBFVxiRIBCACxI/aglzGVbnI6XHd0MTP05VK/fJub4hHdc+LQpz1M kVnCAhFbY9oecTB/togdKtfiloavjbFrb0nJhJnx57K+3SdSuu+znaQ4SlWiZOtXnkbpRWNU eMm+gtTDMSvloGAfr76RtFHskdDOLgXsHD70bKuMhlBxUCrSwGzHaD00q8iQPhJZ5itb3WPq z3B4IjiDAWTO2obD1wtAvSuHuUj/XJRsiKDKW3x13cfavkad81bZW4cpNwUv8XHLv/vaZPSA ly+hkY7NrDZydMMXVNQ7AJQufWuTJ0q7sImRcEZ5EIa98esJPey4O7C0vY405wjeyxpVZkpq ThDMurqtQFn1ABEBAAHCwHwEGAEKACYCGwwWIQSjceplnAvsyCtxUxNH67XvWv31RAUCWvLv qwUJCyUBGQAKCRBH67XvWv31RLnrB/9gzcRlpx71sDMosoZULWn7wysBJ/8AIEfIByRaHQe3 pn/KwE57pB+zFbbQqB7YzeZb7/UUgR4zU2ZbOcEfwDZcHUbj0B3fGRsS3t0uiLlAd8w0sBZb SxrqzjdpDjIbOZkxssqUmvrsN67UG1AFWH9aD24keBS7YjPBS8hLxPeYV+Xz6vUL8fRZje/Z JgiBMIwyj6g2lH/zkdnxBdC0iG1xxJOLTaghMMeQyCdH6ef8+VMyAlAJsMckbOTvx63tY8z7 DFcrnTJfbe1EziRilVsEaK8tTzJzhcTfos+f3eBYWEilxe5HzIhYKJeC7lmsSUcGwa6+9VRg a0ctmi9Z8OgX Message-ID: <7fdc922c-ba19-c822-6f6e-d768533a2876@freebsd.org> Date: Tue, 19 Jun 2018 09:06:42 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180619094826.75c0c735.freebsd.ed.lists@sumeritec.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-ID: SgFFUiZSoh9b2PMResQ++ZEnoJEgc3zwxFYShBgE4hc3DftoLsm3fveh5t-MzR1ZB1 X-TOI-MSGID: 08e39055-2f77-4810-a074-8ce5ef090910 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 07:06:56 -0000 Am 19.06.18 um 03:48 schrieb Erich Dollansky: > A very long time ago - and not on FreeBSD but maybe on a real BSD - I > worked with a system that swapped pages out just to bring it back as > one contiguous block. This made a difference those days. I do not know > if the code made it out of the university I was working at. I just > imagine now that the code made it out and is still in use with the > opposite effect. If this was on a VAX, then it was due to a short-coming of the MMU of the VAX, which used one linear array (in system virtual memory) to hold physical addresses of user pages of all programs. Each user program had 2 slices in this array (1 growing up, 1 growing down for the stack) and whenever a program allocated a new page, this slice needed to grow. That leads to fragmentation (same a problem as with realloc() for an ever growing array), and when there was no contiguous free space in the array for a grown slice, then all process where swapped out (resulting in this whole page table array being cleared and thus without fragmentation, since swapped-out processes needed no space in this array). This was a solution that worked without the table walk used in todays VM systems. System pages were mapped by a linear page table in physical memory, while user programs used the above described linear page table in system virtual memory. Nothing of the above applies to any other architecture than the VAX and thus the swap-out of all user processes serves no purpose on any other system. It was an implementation detail of the VAX VM code, not a BSD Unix feature. Regards, STefan From owner-freebsd-stable@freebsd.org Tue Jun 19 08:09:25 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEE741005360; Tue, 19 Jun 2018 08:09:24 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from mx18-out13.antispamcloud.com (mx18-out13.antispamcloud.com [207.244.64.182]) (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 B6F1D7216B; Tue, 19 Jun 2018 08:09:23 +0000 (UTC) (envelope-from freebsd.ed.lists@sumeritec.com) Received: from [153.92.8.106] (helo=srv31.niagahoster.com) by mx18.antispamcloud.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1fVBhU-0000ZD-Q8; Tue, 19 Jun 2018 10:09:22 +0200 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sumeritec.com; s=default; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=2B1+zNULM2tQykPwu1VeBunT1oW50i8mGz9y1LVHPbA=; b=WIM4iBnzc1Hp38OUAEYCAGVjgi W+uzuQtexV9H/yW42gaa/jm4OXv6g8tq1rPzdpMjw0Sxv3jV22FTz8NnMrOgSZ74PHMXVatpAsw1o A2nsRV0MsI/r7Eia2Tl2R0uFDMb7P5JSXuW8n6WbNFOuzpr1n+QkbsgWG3+xgF7DvKoCjoyUBiDlr ixGTHDPXk0Rqj8kXwqv761ih2w2Q38+2IDTMqUcGw4iHnPKkGS+h2CVhZc/MM8GA4q2OJvgUX8krP 3YKz1004qv8OsOWTfOjxbeBcH/AaDgYptfW+fNpNqzYnJWYkwyF7UEHUuMApu93/EwBrwOf5xkj1B kO3kreHA==; Received: from [114.125.71.15] (port=62491 helo=X220.sumeritec.com) by srv31.niagahoster.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1fVBge-0009WC-Qf; Tue, 19 Jun 2018 15:08:27 +0700 Date: Tue, 19 Jun 2018 16:08:22 +0800 From: Erich Dollansky To: Stefan Esser Cc: tech-lists , freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: lightly loaded system eats swap space Message-ID: <20180619160822.028aedd5.freebsd.ed.lists@sumeritec.com> In-Reply-To: <7fdc922c-ba19-c822-6f6e-d768533a2876@freebsd.org> References: <20180618160855.44d9a0c2.freebsd.ed.lists@sumeritec.com> <20180619094826.75c0c735.freebsd.ed.lists@sumeritec.com> <7fdc922c-ba19-c822-6f6e-d768533a2876@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OutGoing-Spam-Status: No, score=-1.0 X-AuthUser: freebsd.ed.lists@sumeritec.com X-Originating-IP: 153.92.8.106 X-AntiSpamCloud-Domain: out.niagahoster.com X-AntiSpamCloud-Username: niaga Authentication-Results: antispamcloud.com; auth=pass (login) smtp.auth=niaga@out.niagahoster.com X-AntiSpamCloud-Outgoing-Class: unsure X-AntiSpamCloud-Outgoing-Evidence: Combined (0.16) X-Recommended-Action: accept X-Filter-ID: EX5BVjFpneJeBchSMxfU5usdY7E8KpTqno+Z301XEgF602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO4N5oQrZbCLfV7hJyljfOmfn6HaatznLU8a/oEUKfeIg/I6Frex1icm8Z5xovxYmeLlr qv8bccGjjcGuRJYc3CsRb3caiKydq8Z8Xbc5Vf6x2koUe6H4EgsR4KI2aZpsc6BPex1XXjYLerSq l+GM0oyqNgIHQ5dF9dtv8nnICvNYsOZUZ3LpX5sVKofsd4Ljn0SITl3F8isfnMI2tq4ALYmhFfT8 SX4c9CyvMRbQCZoBVgW9/bktU41htiJ8fk7NkEYjFo+uebo6mh5wy9P2cSKVjS1iAWRHBDDqjVRq rxKNcbyOkcjQN+Nad0B5PTkOY6yMT6yKWg7axbe8p2uiBYKlk6iLOvzJGCYfseu8gWUSAhrohMZt WSIoElgwDHfdIIkB1/R4ar1CYVgFKOoJD16tNj2rE+TJPq42zd+nDKsqKvWTUIuwAP+Be6QqMx/O K6S8tu2KVBI79Uufvsp4JVu/xPrargplL/tPsMC2s+w8vKhXliG78w9pKdlOmjaruM9jtS6Zuw56 NzJ4HoAbKeEtjEbRrFHvESnMqzLGulVo1Bnfpi+LPGsUlkOs7d49CmiH1Wgh6RAenBR+licROGZz MdrUQXpciqnq9qOjh4etVCt6wkGNBO7fECYEaHetw/Vz0MrRTeKdVDNlYSch1/L5XH68VhUGuWyN oOWkK0Uio9orsOc0u3VU19a+ctSrw6ntKr6+crm+rffkaQ6ZgOiaWu8ipdKNsU8IFBbqK4pIIhsw sD/LeXoEtIo9KOeLwYoK0XEeLExv6RoSf29nwNyXAHQFv25JRzDZU4hg3424zkzvfc03RW0sZulU a+392X6m+UeFXprlCOm3BAEbJtDc4+l+WWuYiTAZMJQK5ses+d5GWWc/u6JOjtOJBa9uhxminqBI 3nGd34AYLmTpVeFbLPp9n350Mbemie5JWWm/Mwqvvyz63pRF7yCn+1yLJJE4hKzEl0g6eZTimdco TomlgJLhZDkE6UMGbRwzU4S8 X-Report-Abuse-To: spam@quarantine1.antispamcloud.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 08:09:25 -0000 Hi, On Tue, 19 Jun 2018 09:06:42 +0200 Stefan Esser wrote: > Am 19.06.18 um 03:48 schrieb Erich Dollansky: > > A very long time ago - and not on FreeBSD but maybe on a real BSD - > > I worked with a system that swapped pages out just to bring it back > > as one contiguous block. This made a difference those days. I do > > not know if the code made it out of the university I was working > > at. I just imagine now that the code made it out and is still in > > use with the opposite effect. > > If this was on a VAX, then it was due to a short-coming of the > MMU of the VAX, which used one linear array (in system virtual this could have been the case as they have had many DEC systems. > Nothing of the above applies to any other architecture than the > VAX and thus the swap-out of all user processes serves no purpose > on any other system. It was an implementation detail of the VAX > VM code, not a BSD Unix feature. I know how an MMU works, but I also know how caches work. It still could give a tiny advantage if it is in one piece, even if it is not a requirement to function. Any way, I do not work in this area anymore. Erich From owner-freebsd-stable@freebsd.org Tue Jun 19 15:00:16 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90DCF101F8AF for ; Tue, 19 Jun 2018 15:00:16 +0000 (UTC) (envelope-from bounce@ims11.isendservice.com.br) Received: from ims11.isendservice.com.br (ims11.isendservice.com.br [54.232.115.234]) by mx1.freebsd.org (Postfix) with ESMTP id 0D64B85228 for ; Tue, 19 Jun 2018 15:00:15 +0000 (UTC) (envelope-from bounce@ims11.isendservice.com.br) Received: from localhost (localhost [127.0.0.1]) by ims11.isendservice.com.br (Postfix) with ESMTP id 5DDC748A83 for ; Tue, 19 Jun 2018 11:36:56 -0300 (BRT) Date: Tue, 19 Jun 2018 11:36:56 -0300 (BRT) From: SENAI | FATEC - Faculdade SENAI Reply-To: posgraduacao@senairs.org.br To: freebsd-stable@freebsd.org Message-ID: <950159343.38333.1529419016062.JavaMail.root@ims11> Subject: =?ISO-8859-1?Q?P=F3s-Gradua=E7=E3o_SENAI_|_FATEC?= =?ISO-8859-1?Q?_-_MBA_em_Gest=E3o_de_Projetos?= bounce-key: <2420-22522874-2174888> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 15:00:16 -0000 From owner-freebsd-stable@freebsd.org Tue Jun 19 17:29:39 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D10E7100228C for ; Tue, 19 Jun 2018 17:29:39 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from resqmta-po-09v.sys.comcast.net (resqmta-po-09v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:168]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "resqmta-po-01v.sys.comcast.net", Issuer "COMODO RSA Organization Validation Secure Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 717EB6C499 for ; Tue, 19 Jun 2018 17:29:39 +0000 (UTC) (envelope-from jdc@koitsu.org) Received: from resomta-po-01v.sys.comcast.net ([96.114.154.225]) by resqmta-po-09v.sys.comcast.net with ESMTP id VKKSfoxj3EEmzVKRlf1x8L; Tue, 19 Jun 2018 17:29:37 +0000 Received: from koitsu.org ([71.198.44.84]) by resomta-po-01v.sys.comcast.net with ESMTPA id VKRkf7i1WVGSOVKRlf3Klk; Tue, 19 Jun 2018 17:29:37 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 4193F1581FA9; Tue, 19 Jun 2018 10:29:36 -0700 (PDT) Date: Tue, 19 Jun 2018 10:29:36 -0700 From: Jeremy Chadwick To: freebsd-stable@freebsd.org Subject: Re: lightly loaded system eats swap space Message-ID: <20180619172936.GA24967@icarus.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.0 (2018-05-17) X-CMAE-Envelope: MS4wfB6vY8/+jSMm74JIDhszizUnlu5cxTDgAnYTCODC6YRbLLqJ6A0JAqgBxQ42Ic8cqDsz20v4Wnv0CAbPZfE1d1YkEg6AFfE4A3a8iQ9uWyCrFs83cOhM tl7x7qyrKahEemszm3gcc1inCiFffr46kJXGDXVg55fRy5CAukNPVJp6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 17:29:40 -0000 (I am not subscribed to -stable, so please CC me, though I doubt I can help in any way/shape/form past this Email) Not the first time this has come up -- and every time it has, all that's heard is crickets in the threads. Recent proof: https://lists.freebsd.org/pipermail/freebsd-stable/2018-April/088727.html https://lists.freebsd.org/pipermail/freebsd-stable/2018-April/088728.html https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089094.html I sent private mail to Peter Jeremy about his issue. I will not disclose that Email here. However, I will disclose the commits I included in said Email that have touched ZFS ARC-related code: http://www.freshbsd.org/commit/freebsd/r332785 http://www.freshbsd.org/commit/freebsd/r332552 http://www.freshbsd.org/commit/freebsd/r332540 (may help give insights) http://www.freshbsd.org/commit/freebsd/r330061 http://www.freshbsd.org/commit/freebsd/r328235 http://www.freshbsd.org/commit/freebsd/r327491 http://www.freshbsd.org/commit/freebsd/r326619 http://www.freshbsd.org/commit/freebsd/r326427 (quota-related, maybe irrelevant) http://www.freshbsd.org/commit/freebsd/r323667 In short (and nebulous as hell; sorry, I cannot be more specific given the nature of the problem): there have been changes about ZFS's memory allocation/releasing decision-making scheme compared to ZFS on "older" FreeBSD (i.e. earlier 11.x, and definitely 10.x and 9.x). Recommendations like "limit your ARC" are nothing new in FreeBSD, but are still ridiculous kludges: tech-lists' system clearly has 105GB MRU (MRU = most recently used) in ARC, meaning there is memory that can be released back to the rest of the OS for general use (re: memory contention/pressure situation), but the OS is choosing to use swap instead, eventually exhausting it. That logic sounds broken, IMO. (And yes I did notice the size of bhyve process) ZFS-related kernel folks need to be involved in this conversation. For whatever reason, in the past several years, related committers are no longer participating in these type of discussions. The opposite was true back in the 7.x to 9.x days. The answers have to come from them. I don't know, today, a) how they prefer these problems get reported to them, or b) what exact information they want that can help narrow it down (tech-lists' provided data is, IMO, good and par for the course). -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | From owner-freebsd-stable@freebsd.org Tue Jun 19 17:58:01 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D46831004050 for ; Tue, 19 Jun 2018 17:58:00 +0000 (UTC) (envelope-from peixotocassiano@gmail.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 6E2E96DBC0 for ; Tue, 19 Jun 2018 17:58:00 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x232.google.com with SMTP id o2-v6so144349qkc.13 for ; Tue, 19 Jun 2018 10:58:00 -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=qle7RfghUygJL+BPljsVEWWOfTb1AvTNttLxfhFj85k=; b=ir5NsLaJ4FFJKhueeNGXV0WPkG+05Asqfk6dj2swqOAduaiLP0L4FqW906W3+6Cub3 ij6Gma8VZBlXCv87gYb6cRcXGKjmBMEHtO+ES5GkWOI+fdnVZga1tp4nOSQQsNnLC7Rf ojpxI7OXWlwxs4F+NYzLA+9RW7x1R4O7tXsVcnTznsgGf5am/XSsSGs2plzYujB8YUaY MvczJiKdwWz58fv8gPtDUDnsDNrwsIsefbWBRZ/yfTMJCurUQYZhrPhvEfjSKagiX22l T375r8aK8TNwHwnAfIo+LUfHQw2Obkk5oeqv5eV+cZceghT5cLrRfTBifXquQGMfJiaR 9MMQ== 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=qle7RfghUygJL+BPljsVEWWOfTb1AvTNttLxfhFj85k=; b=n1JYpwT556cfitxu1M08NPGGAc/EmO3YVrkMBjeGrHfgqdyS8YRfAx34MTn7d74Z64 I8DwA8KpfR3LDakBZarRJ3LkVjQ1u5N4I6Ya9oVr+GDNkH5DybEp4qC97qUyTpal26eh lp0HuzAE2xC/lPhNoq75/LZGqRyild+4ppQgGhBcNEs8pgmKqBDIFw9g/IPTUuQyEFLj QX3vCh/Q5vFZ/E2AGHixwTeEOI4sa41D+U1aH+r4a1DXGt3fhH6htm46+0IK9vASvY/a qobQ3w6EBbnPOxjoI89e97SXlYdI8lG5naVSB69DRe4WMiiGMH//y3e2Qc/Is1yY4tZa rs8Q== X-Gm-Message-State: APt69E2tdzlO9XwIVcX/4z33QLmRoPiltHg/kdLny3buoBXyf6FQSNTx iMPUmrA2E1ZEI413afo3KiK0TkpT/OwkR1wmLPSL7A== X-Google-Smtp-Source: ADUXVKJ6z2D+1E1hkTKrSpHXCxb6Aiq9l2OYBUBJ/jplb8WGWoWPNn0qh8/iIGSf6DIx6WOVLevRGXThrcmlPybOiU4= X-Received: by 2002:a37:88c2:: with SMTP id k185-v6mr14934771qkd.102.1529431080077; Tue, 19 Jun 2018 10:58:00 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:5399:0:0:0:0:0 with HTTP; Tue, 19 Jun 2018 10:57:59 -0700 (PDT) In-Reply-To: <20180619172936.GA24967@icarus.home.lan> References: <20180619172936.GA24967@icarus.home.lan> From: Cassiano Peixoto Date: Tue, 19 Jun 2018 14:57:59 -0300 Message-ID: Subject: Re: lightly loaded system eats swap space To: Jeremy Chadwick Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 17:58:01 -0000 Hi, I have the very same issue on many servers. Mainly on mail servers running qmail+spamassassin+clamav. I've tuned some variables on loader.conf: vfs.zfs.vdev.cache.size="2G" vfs.zfs.arc_min="614400000" vfs.zfs.arc_max="4915200000" But after some days, it begins eating swap and the system comes very very slow then I need to reboot it. My system config is: FreeBSD 11.1-STABLE #5 r321625M: Thu Sep 21 16:01:56 -03 2017 root@mail.com:/usr/obj/usr/src/sys/MAIL amd64 FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) VT(vga): resolution 640x480 CPU: Intel(R) Atom(TM) CPU C2518 @ 1.74GHz (1750.04-MHz K8-class CPU) Origin="GenuineIntel" Id=0x406d8 Family=0x6 Model=0x4d Stepping=8 Features=0xbfebfbff Features2=0x43d8e3bf AMD Features=0x28100800 AMD Features2=0x101 Structured Extended Features=0x2282 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8213245952 (7832 MB) It's configured with 4GB of swap. Let me know if I can help with any other information. Thanks. On Tue, Jun 19, 2018 at 2:29 PM, Jeremy Chadwick wrote: > (I am not subscribed to -stable, so please CC me, though I doubt I can > help in any way/shape/form past this Email) > > Not the first time this has come up -- and every time it has, all that's > heard is crickets in the threads. Recent proof: > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-April/088727.html > https://lists.freebsd.org/pipermail/freebsd-stable/2018-April/088728.html > https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089094.html > > I sent private mail to Peter Jeremy about his issue. I will not > disclose that Email here. However, I will disclose the commits I > included in said Email that have touched ZFS ARC-related code: > > http://www.freshbsd.org/commit/freebsd/r332785 > http://www.freshbsd.org/commit/freebsd/r332552 > http://www.freshbsd.org/commit/freebsd/r332540 (may help give insights) > http://www.freshbsd.org/commit/freebsd/r330061 > http://www.freshbsd.org/commit/freebsd/r328235 > http://www.freshbsd.org/commit/freebsd/r327491 > http://www.freshbsd.org/commit/freebsd/r326619 > http://www.freshbsd.org/commit/freebsd/r326427 (quota-related, maybe > irrelevant) > http://www.freshbsd.org/commit/freebsd/r323667 > > In short (and nebulous as hell; sorry, I cannot be more specific given > the nature of the problem): there have been changes about ZFS's memory > allocation/releasing decision-making scheme compared to ZFS on "older" > FreeBSD (i.e. earlier 11.x, and definitely 10.x and 9.x). > > Recommendations like "limit your ARC" are nothing new in FreeBSD, but > are still ridiculous kludges: tech-lists' system clearly has 105GB MRU > (MRU = most recently used) in ARC, meaning there is memory that can be > released back to the rest of the OS for general use (re: memory > contention/pressure situation), but the OS is choosing to use swap > instead, eventually exhausting it. That logic sounds broken, IMO. (And > yes I did notice the size of bhyve process) > > ZFS-related kernel folks need to be involved in this conversation. For > whatever reason, in the past several years, related committers are no > longer participating in these type of discussions. The opposite was > true back in the 7.x to 9.x days. The answers have to come from them. > I don't know, today, a) how they prefer these problems get reported to > them, or b) what exact information they want that can help narrow it > down (tech-lists' provided data is, IMO, good and par for the course). > > -- > | Jeremy Chadwick jdc@koitsu.org | > | UNIX Systems Administrator http://jdc.koitsu.org/ | > | Making life hard for others since 1977. PGP 4BD6C0CB | > > _______________________________________________ > 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 Jun 19 18:30:59 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F4BA100686E for ; Tue, 19 Jun 2018 18:30:59 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A78A06FA72 for ; Tue, 19 Jun 2018 18:30:58 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id w5JIUu7s065031 for ; Tue, 19 Jun 2018 20:30:56 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 25B71965 for ; Tue, 19 Jun 2018 20:30:56 +0200 (CEST) Subject: Re: Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2? From: Harry Schmalzbauer To: freebsd-stable@freebsd.org References: <79e621cc-9c0a-c0c8-decd-5789241a633f@omnilan.de> Organization: OmniLAN Message-ID: <81edd070-0666-c39c-bb8f-5f0591c74f9d@omnilan.de> Date: Tue, 19 Jun 2018 20:30:55 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <79e621cc-9c0a-c0c8-decd-5789241a633f@omnilan.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: ACL 130 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Tue, 19 Jun 2018 20:30:56 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 18:30:59 -0000 Am 16.06.2018 um 21:42 schrieb Harry Schmalzbauer: … > To rule out a known vboxnetflt(4) limitation/failure, I'd like to know > if somebody successfully uses vboxnetflt(4) from > virtualbox-ose-kmod-5.2.12 on stable/11|11.2. Really nobody out there who has VirtualBox sucessfully running under stable/11 or 11.x with bridged network? Anyone who tried, but also observed similar problems like I have on -current? Thanks, -harry From owner-freebsd-stable@freebsd.org Tue Jun 19 19:29:46 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB5301009BB7 for ; Tue, 19 Jun 2018 19:29:45 +0000 (UTC) (envelope-from paulz@vanderzwan.org) Received: from mail.paztec.nl (mail.paztec.nl [81.171.19.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.paztec.nl", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 27E6072609 for ; Tue, 19 Jun 2018 19:29:43 +0000 (UTC) (envelope-from paulz@vanderzwan.org) Received: from gaspode.vanderzwan.org (static-145.133.145.71.ip.telfort.nl [145.133.145.71]) (authenticated bits=0) by mail.paztec.nl (8.15.2/8.15.2) with ESMTPSA id w5JJGBc5088307 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Jun 2018 21:16:12 +0200 (CEST) (envelope-from paulz@vanderzwan.org) X-Authentication-Warning: vps3.vanderzwan.org: Host static-145.133.145.71.ip.telfort.nl [145.133.145.71] claimed to be gaspode.vanderzwan.org From: Paul van der Zwan Message-Id: <822A9582-3C11-46AE-B492-F663E35CD10D@vanderzwan.org> Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: lightly loaded system eats swap space Date: Tue, 19 Jun 2018 21:16:10 +0200 In-Reply-To: Cc: Jeremy Chadwick , freebsd-stable@freebsd.org To: Cassiano Peixoto References: <20180619172936.GA24967@icarus.home.lan> X-Mailer: Apple Mail (2.3445.8.2) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.paztec.nl [81.171.19.13]); Tue, 19 Jun 2018 21:16:12 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 19:29:46 -0000 Hi I had something similar on FreeNAS 11.1 ( based on FreeBSD 11.1). Swap was allocated and never released until it ran out. Some time ago I set the following sysctl: vm.disable_swapspace_pageouts: 1 That completely stopped swap allocation and I have not rebooted since, = except for OS patching. =46rom what I found using google this sysctl may have some nasty side = effects when system runs out of memory, but that has not happened on my system. Paul > On 19 Jun 2018, at 19:57, Cassiano Peixoto = wrote: >=20 > Hi, >=20 > I have the very same issue on many servers. Mainly on mail servers = running > qmail+spamassassin+clamav. I've tuned some variables on loader.conf: >=20 > vfs.zfs.vdev.cache.size=3D"2G" > vfs.zfs.arc_min=3D"614400000" > vfs.zfs.arc_max=3D"4915200000" >=20 > But after some days, it begins eating swap and the system comes very = very > slow then I need to reboot it. >=20 > My system config is: >=20 > FreeBSD 11.1-STABLE #5 r321625M: Thu Sep 21 16:01:56 -03 2017 > root@mail.com:/usr/obj/usr/src/sys/MAIL amd64 > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on = LLVM > 4.0.0) > VT(vga): resolution 640x480 > CPU: Intel(R) Atom(TM) CPU C2518 @ 1.74GHz (1750.04-MHz K8-class = CPU) > Origin=3D"GenuineIntel" Id=3D0x406d8 Family=3D0x6 Model=3D0x4d = Stepping=3D8 >=20 > = Features=3D0xbfebfbff >=20 > = Features2=3D0x43d8e3bf > AMD Features=3D0x28100800 > AMD Features2=3D0x101 > Structured Extended Features=3D0x2282 > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > TSC: P-state invariant, performance statistics > real memory =3D 8589934592 (8192 MB) > avail memory =3D 8213245952 (7832 MB) >=20 > It's configured with 4GB of swap. Let me know if I can help with any = other > information. >=20 > Thanks. >=20 >=20 > On Tue, Jun 19, 2018 at 2:29 PM, Jeremy Chadwick = wrote: >=20 >> (I am not subscribed to -stable, so please CC me, though I doubt I = can >> help in any way/shape/form past this Email) >>=20 >> Not the first time this has come up -- and every time it has, all = that's >> heard is crickets in the threads. Recent proof: >>=20 >> = https://lists.freebsd.org/pipermail/freebsd-stable/2018-April/088727.html >> = https://lists.freebsd.org/pipermail/freebsd-stable/2018-April/088728.html >> = https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089094.html >>=20 >> I sent private mail to Peter Jeremy about his issue. I will not >> disclose that Email here. However, I will disclose the commits I >> included in said Email that have touched ZFS ARC-related code: >>=20 >> http://www.freshbsd.org/commit/freebsd/r332785 >> http://www.freshbsd.org/commit/freebsd/r332552 >> http://www.freshbsd.org/commit/freebsd/r332540 (may help give = insights) >> http://www.freshbsd.org/commit/freebsd/r330061 >> http://www.freshbsd.org/commit/freebsd/r328235 >> http://www.freshbsd.org/commit/freebsd/r327491 >> http://www.freshbsd.org/commit/freebsd/r326619 >> http://www.freshbsd.org/commit/freebsd/r326427 (quota-related, maybe >> irrelevant) >> http://www.freshbsd.org/commit/freebsd/r323667 >>=20 >> In short (and nebulous as hell; sorry, I cannot be more specific = given >> the nature of the problem): there have been changes about ZFS's = memory >> allocation/releasing decision-making scheme compared to ZFS on = "older" >> FreeBSD (i.e. earlier 11.x, and definitely 10.x and 9.x). >>=20 >> Recommendations like "limit your ARC" are nothing new in FreeBSD, but >> are still ridiculous kludges: tech-lists' system clearly has 105GB = MRU >> (MRU =3D most recently used) in ARC, meaning there is memory that can = be >> released back to the rest of the OS for general use (re: memory >> contention/pressure situation), but the OS is choosing to use swap >> instead, eventually exhausting it. That logic sounds broken, IMO. = (And >> yes I did notice the size of bhyve process) >>=20 >> ZFS-related kernel folks need to be involved in this conversation. = For >> whatever reason, in the past several years, related committers are no >> longer participating in these type of discussions. The opposite was >> true back in the 7.x to 9.x days. The answers have to come from = them. >> I don't know, today, a) how they prefer these problems get reported = to >> them, or b) what exact information they want that can help narrow it >> down (tech-lists' provided data is, IMO, good and par for the = course). >>=20 >> -- >> | Jeremy Chadwick jdc@koitsu.org | >> | UNIX Systems Administrator http://jdc.koitsu.org/ | >> | Making life hard for others since 1977. PGP 4BD6C0CB | >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >>=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >=20 From owner-freebsd-stable@freebsd.org Tue Jun 19 19:38:20 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 748B5100A3C3 for ; Tue, 19 Jun 2018 19:38:20 +0000 (UTC) (envelope-from philnorm@gmail.com) Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::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 01AEB72B35 for ; Tue, 19 Jun 2018 19:38:19 +0000 (UTC) (envelope-from philnorm@gmail.com) Received: by mail-wr0-x236.google.com with SMTP id f16-v6so829816wrm.3 for ; Tue, 19 Jun 2018 12:38:19 -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=oYKkrMhIdfCL1liytVj8Qwv5rVKU257wlmR7583Bq6A=; b=KHXoxT8aqBqvh9EEwTHt2niMy8v8J4RloyYJmfLL9vlugvyew6nquV5nQFzvU6bM3j ThJm+jCnVvmNy0QoVRhtdwFdmkwI4XjPCnpD+rqSzTuxbmR6E+QrT7rcemAWjSwwSSqD vMYbk7NOCOpn18KbRclB28AC72lbt2P2IzqXhyRxwHj5WHJxb74iTcPfmaY4JZKv5nNC nm0uEObDjF5MBztpYj1nzW5wFpQM1ZD2KrT7dfLBpxOBWjeWOvtcRBRgf/hxS1CW5tKo 9pJi/Ttm6w4kVWcqJBiaioIm1G64OYGUyVuv0h++1p6rTKP98h7TKcweXRI6eU4ITjNx mrfQ== 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=oYKkrMhIdfCL1liytVj8Qwv5rVKU257wlmR7583Bq6A=; b=mHw3Buh0Al1TpoaSsfsx+Vu0JdOma+RhqbcRt/hszwdqqXKtOpEMbWDAtYWaW71EgM shPY40onrm3B4Ev9UpWt9oo7nF0cNe0FI0HyJ5obsPuGUSrtXyBNUlD5yYT7iP8j7lhx 0Jl4F5yQYWJRyZTTNO+kZA+2tv2d8ag8ku8vSvA+o66LL4rPBTKCZ86GT/htPm6VyvLZ znXwNuaK/6qyIjiZOpA4QIcKFObLB4utQ7yCKMyDhlow+2xHA5gKRCog5ZZkFDMzma3k ateTg8M9H0T00q+o3N3ZRja5jCtsgVQBbdHUQKTdgE0RANm3RK7qW/8/UtZMO8AOFrPh mexw== X-Gm-Message-State: APt69E0pBWAPIVfXMEJvGdYXoIFgEmLR+bRIkpm28APUAhe5X+X5o4l5 Fx7UbCgF74bU9oxn763lOloVDyx4u25j24J7v5MSYzf5 X-Google-Smtp-Source: ADUXVKLPu5KPjcOB5RSMzDBKplIxH+FP7oECpqkBkjV89QXP9cBnqEYOwVtAEG14IwtqR2JhU30N3Fyrurqm81vhTv8= X-Received: by 2002:adf:dc52:: with SMTP id m18-v6mr16049666wrj.84.1529437098387; Tue, 19 Jun 2018 12:38:18 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1c:7e87:0:0:0:0:0 with HTTP; Tue, 19 Jun 2018 12:38:17 -0700 (PDT) From: Phil Norman Date: Tue, 19 Jun 2018 21:38:17 +0200 Message-ID: Subject: USB trouble on Ryzen 3/AsRock mobo. To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 19:38:20 -0000 Hi. I've recently converted to FreeBSD, fleeing the Windowsification of Ubuntu. I've been having some trouble with the USB system, which seems strange as FreeBSD's USB stack is, according to a friend, rock solid. I'd like to narrow down if this is a hardware (CPU or mobo) or software issue. I'm running a Ryzen 3 1200, plugged into a "Fatal1ty X370 Gaming-ITX/ac" motherboard (chosen because it supports ECC RAM and fits in an ITX case). On a cold boot (ie starting by flipping the physical PSU power switch), BSD boots up nice and quickly, without errors, and then runs for days without a single USB-related error on dmesg. However, any other kind of reboot which doesn't interrupt the electricity supply yields a large number of USB errors (USB_ERR_TIMEOUTs every few seconds or so) and frequent resets of the xhci0 controller. On occasion, I also get problems with my keyboard randomly stopping working (but then, if the USB subsystem is continuously resetting, that's only to be expected). I also seem to get slow USB storage device read throughput (2MB/s from a USB3 SSD), although I can't rule out that being caused by the fuse ext4fs driver. Here's what I see in dmesg when the USB system's in spam mode: ---------------- xhci0: Resetting controller usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored) usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT igb0: link state changed to UP usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT uhid0 on uhub3 uhid0: on usbus1 uhid1 on uhub3 uhid1: on usbus1 ums0 on uhub2 ums0: on usbus1 ums0: 3 buttons and [XYZ] coordinates ID=0 usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT, ignored) usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT ugen0.2: at usbus0 (disconnected) uhub_reattach_port: could not allocate new device uhub1: at usbus0, port 1, addr 1 (disconnected) uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 uhub1: 22 ports with 22 removable, self powered xhci0: Resetting controller ----------------- Here's the start of dmesg: ----------------- Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.2-PRERELEASE #0 r335198: Fri Jun 15 20:55:02 CEST 2018 phil@bob:/usr/obj/usr/src/sys/BOB amd64 FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) VT(efifb): resolution 1024x768 CPU: AMD Ryzen 3 1200 Quad-Core Processor (3094.26-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 Features=0x178bfbff Features2=0x7ed8320b AMD Features=0x2e500800 AMD Features2=0x35c233ff Structured Extended Features=0x209c01a9 XSAVE Features=0xf AMD Extended Feature Extensions ID EBX=0x1007 SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16519221248 (15753 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) random: unblocking device. Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20171214/tbfadt-796) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-55 on motherboard SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! Timecounter "TSC-low" frequency 1547130097 Hz quality 1000 random: entropy device external interface kbd0 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff80a3bd40, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.59 Wed May 9 21:54:48 PDT 2018 nexus0 cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.000000s Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 450 Event timer "HPET1" frequency 14318180 Hz quality 450 Event timer "HPET2" frequency 14318180 Hz quality 450 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pcib0: _OSC returned error 0x10 pci0: on pcib0 amdsmn0: on hostb0 amdtemp0: on hostb0 pci0: at device 0.2 (no driver attached) pcib1: at device 1.3 on pci0 pci1: on pcib1 xhci0: mem 0xf77a0000-0xf77a7fff irq 32 at device 0.0 on pci1 xhci0: 32 bytes context size, 64-bit DMA usbus0 on xhci0 ----------------- I don't remember if I had similar USB trouble on Linux, but I definitely did during my brief excursion into NetBSD. If anyone knows whether this is likely to be a CPU, mother board or software problem, or knows of something I can try to get more information or try to debug the thing, please let me know. Thanks, Phil From owner-freebsd-stable@freebsd.org Tue Jun 19 20:20:33 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7DF3100C454 for ; Tue, 19 Jun 2018 20:20:32 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from limbo.b1t.name (limbo.b1t.name [78.25.32.206]) (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 6CA8A74252 for ; Tue, 19 Jun 2018 20:20:32 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from [172.29.1.147] (probe.42.lan [172.29.1.147]) by limbo.b1t.name (Postfix) with ESMTPSA id CA417B3; Tue, 19 Jun 2018 23:20:21 +0300 (EEST) Subject: Re: lightly loaded system eats swap space To: Jeremy Chadwick , freebsd-stable@freebsd.org References: <20180619172936.GA24967@icarus.home.lan> From: Volodymyr Kostyrko Message-ID: Date: Tue, 19 Jun 2018 23:20:20 +0300 User-Agent: Mozilla/5.0 (X11; DragonFly x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180619172936.GA24967@icarus.home.lan> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=b1t.name; s=dkim; t=1529439623; bh=a/7zMlbqtpX0WkxRyx1KRGn+m3FCT2qyseHt7s0FgRw=; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=EUgmSNE+b1DUZpcP0aLBlAyRKsVPxRD2Rfr0pP92Dn3SRg0Ul1lStWHsAqWakXeBLNayxrjf1pKy26rydvVWms98vRUQxGQskbY50++ZAHrdo4ZRl+qUvdwbHFiuWXWr/odHdUUOmPfqy5AQbUiWZFgGT1+bwiHRAjuZlU8GC08= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 20:20:33 -0000 19.06.18 20:29, Jeremy Chadwick wrote: > (I am not subscribed to -stable, so please CC me, though I doubt I can > help in any way/shape/form past this Email) > > Not the first time this has come up -- and every time it has, all that's > heard is crickets in the threads. Recent proof: … I may sound lame but I also faced this issues a few month ago. After a few days of load system was trying to push more and more data into the swap up to the point that active window becomes too small to handle all programs so they should be get back from swap and while they are not running something pinches ARC and ARC claims the memory and so on… I wasn't ever a fan of limiting things. If something requires limits it can be easily exploited. Should I switch from normal limits to other limits when I, say, need to test something on 4 VMs? So while paging through documentation I found a rather old memo in tuning(7) about vm.swap_idle_enabled. I played a little with thresholds but that was only making things worse. I left swap_idle_enable on and let machine live. That was near January I suppose. To my amusement swap problems were gone. This doesn't mean swap wasn't used, instead system survived weeks under irregular load without issues. The only other change that I did was bumping up vfs.zfs.arc_free_target a little bit higher then default to make some space between ARC and VM so they wouldn't clash on memory so often. Since then all of my problems with swap was forgotten. I'm not sure what setting fixed that, neither I'm sure that wasn't some recent patches. I'm running 11-STABLE and rebuilding system at least once per month. Hope that can help someone. WBR. -- Sphinx of black quartz judge my vow. From owner-freebsd-stable@freebsd.org Tue Jun 19 21:23:14 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5BE2100F8B7 for ; Tue, 19 Jun 2018 21:23:14 +0000 (UTC) (envelope-from vince@hightek.org) Received: from mail.ngtek.org (ngtek.org [IPv6:2001:19f0:6400:8963:5400:ff:fe09:9585]) (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 4B57476ABD for ; Tue, 19 Jun 2018 21:23:14 +0000 (UTC) (envelope-from vince@hightek.org) Received: from ip68-227-103-24.ok.ok.cox.net ([68.227.103.24] helo=hightek.org) by mail.ngtek.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fVO5p-000BjW-3J for freebsd-stable@FreeBSD.ORG; Tue, 19 Jun 2018 16:23:13 -0500 Received: from localhost ([127.0.0.1] helo=quark.hightek.org) by hightek.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fVO5n-0009Ur-DG for freebsd-stable@FreeBSD.ORG; Tue, 19 Jun 2018 16:23:11 -0500 Received: (from vince@localhost) by quark.hightek.org (8.15.2/8.15.2/Submit) id w5JLNBOl036508 for freebsd-stable@FreeBSD.ORG; Tue, 19 Jun 2018 16:23:11 -0500 (CDT) (envelope-from vince) Date: Tue, 19 Jun 2018 16:23:11 -0500 From: Vincent Stemen To: freebsd-stable@FreeBSD.ORG Subject: ATI video problem - extremely slow desktop - 100% cpu load Message-ID: <20180619212311.GA36401@quark.hightek.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 21:23:14 -0000 Hi. FreeBSD 11.1-RELEASE Motherboard: gigabyte GA-78LMT-USB3 R2 Video: Integrated ATI Radeon HD 3000 graphics System runs fine with a simple stand alone window manager such as jwm, openbox, etc. But anytime I run a desktop environment that has a panel and/or desktop icons, the X desktop takes a very long time to start up and runs extremely slow and unresponsive, the pointer jumps instead of moving smoothly, and the main Xorg process runs at 100% load on one core. I have tried several different desktops, such as xfce, enlightenment, lumina, etc. Similar problem on all of them. It appears to be any environment that is using DBUS. That could just be a coincidence. The weird thing is that it does not always do it. Once in a while, when I launch X, it comes up quick and runs fine. Shut down X and re-run it and it's back doing it again. Sometimes it will come up running fine several times in a row. Once it comes up working correctly, it stays working until I restart X. Even after a reboot, it is inconsistent about doing it the first time X is run. I have tried re-installing all the ports from X11 and the desktop environments from FreeBSD 11 release_1, release_2, quarterly, and latest. Same problem with all of them. Does anybody have any idea what could be causing this? I don't know if for sure if this is a FreeBSD or a port problem. There are radeon modules running. # kldstat 5 1 0xffffffff82431000 12b4a0 radeonkms.ko ... 10 1 0xffffffff825b9000 103e radeonkmsfw_RS780_pfp.ko 11 1 0xffffffff825bb000 5b3f radeonkmsfw_RS780_me.ko 12 1 0xffffffff825c1000 1338 radeonkmsfw_R600_rlc.ko X is using the ati driver from the xf86-video-ati-7.9.0_1,1 package. The evidence seems to be pointing toward the xf86-video-ati package being the problem. If I edit /etc/X11/xorg.conf to use the "vesa" driver rather than the "radeon" driver the problem goes away. But, of course, the vesa driver is low resolution and does not re-initialize the console when I exit X. From owner-freebsd-stable@freebsd.org Tue Jun 19 22:19:14 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AC0C1012617 for ; Tue, 19 Jun 2018 22:19:14 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FD9978A21 for ; Tue, 19 Jun 2018 22:19:14 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x22a.google.com with SMTP id o17-v6so795869vka.2 for ; Tue, 19 Jun 2018 15:19:14 -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=lbJOg9huNHwAYCJQJr9SikVS2l/AaZIb+qkn7GkdyL0=; b=Dp+dEN0Bdsk8mZ7jmXGZxxd/JHAlPUfvovJOz+HbkD3p0wClBtjDJIw1L+/FFlY/xH 9vmSLV1YOH5iBsHPhSWFy7nxoqf0W13BHCgnbLlheeQgPp4jROfikrOkBh1yjmBpC1sO x4vYzB4rjyE+6p0bQfznLTRlJCrGdeBRbbRzdXYmmGu8Di6Uc7SH7GsjpvFORPD0Aahj shVUU0BK0ovHX9T1txakicPAsW4JMH+A/mX/PghyRuhsFbpHKS+6wSv8HEnNXkt4pUre EvqV5LmubhQT8UpXCMjKWL/1U47QAaMvsFKWEMKo+ggAv0pXao8LEIdz750f1W74hu8g Jc1g== 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=lbJOg9huNHwAYCJQJr9SikVS2l/AaZIb+qkn7GkdyL0=; b=BCL4/qhyTUk1KYXkqcr9RPSNDFRY0TG5FmlQv7yBo13BVBi25A4sfyhATIMP5Yk/4S JD7OUobWNEvsoyIulhA3jqCdNrU2Z1aQDwsAlHqbAh2+Zopbe2zp15tgPAwW0OmhIfax 0wjNw8dkrzEihTd0r4kbgh8jG89Oxr37SdgiOGHant2O+AmJw3Wz/y4++/aeX+V6PoxH KKSgKVKTtNnlBLLrImotIUWlc34mlNCcTCo1wedjhgYKtz37aYTW44Z3sApnkmigsHRE DdgwP8Eb8uKYosc41PTUpXg9aK2nOKwePvJygDJCSo6HEVbETATYlw1d3whPMwIQPyT3 2VNw== X-Gm-Message-State: APt69E1Y/C5EO/C2DrxcNncDLJAJ1X2yQZEPJtJLjyKydQZ+6r8htRhg piTm3nf5ffAmn3wc5HSUrWC1ADGIuTPvCbBBfNJek/Kk X-Google-Smtp-Source: ADUXVKIMqQBHb0aUmR1I+e2sSvqmM6HP9lmGWo4hugnUn3iBLDAUZMt2bYj83A4CvL+g/fSy6sEq51upZJjP15/bdhU= X-Received: by 2002:a1f:44cc:: with SMTP id r195-v6mr11546210vka.78.1529446753519; Tue, 19 Jun 2018 15:19:13 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 2002:a67:8f05:0:0:0:0:0 with HTTP; Tue, 19 Jun 2018 15:19:12 -0700 (PDT) In-Reply-To: <81edd070-0666-c39c-bb8f-5f0591c74f9d@omnilan.de> References: <79e621cc-9c0a-c0c8-decd-5789241a633f@omnilan.de> <81edd070-0666-c39c-bb8f-5f0591c74f9d@omnilan.de> From: Kevin Oberman Date: Tue, 19 Jun 2018 15:19:12 -0700 X-Google-Sender-Auth: jYRdlps9SVzXLCv1nHHr0JUxqEo Message-ID: Subject: Re: Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2? To: Harry Schmalzbauer Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 19 Jun 2018 22:19:14 -0000 On Tue, Jun 19, 2018 at 11:30 AM, Harry Schmalzbauer wrote: > Am 16.06.2018 um 21:42 schrieb Harry Schmalzbauer: > =E2=80=A6 > >> To rule out a known vboxnetflt(4) limitation/failure, I'd like to know i= f >> somebody successfully uses vboxnetflt(4) from virtualbox-ose-kmod-5.2.12= on >> stable/11|11.2. >> > > Really nobody out there who has VirtualBox sucessfully running under > stable/11 or 11.x with bridged network? > > Anyone who tried, but also observed similar problems like I have on > -current? > > Thanks, > > -harry > I suspect you would have gotten better response if you had asked for someone using a bridged network (as opposed to NATed) on VirtualBox 5.2.12 ib FreeBSD-11. I had to check on just what vboxnetflt was to realize that, yes, I use it and it works fine on my 11-STABLE system system. Worked on 11 from the time 5.12 was placed in ports ubtil now on several different revisions of STABLE. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-stable@freebsd.org Wed Jun 20 05:08:56 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB6F71025F7F for ; Wed, 20 Jun 2018 05:08:56 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id D8E688747A for ; Wed, 20 Jun 2018 05:08:55 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ppp118-210-86-172.bras2.adl4.internode.on.net (HELO leader.local) ([118.210.86.172]) by ipmail06.adl6.internode.on.net with ESMTP; 20 Jun 2018 14:38:47 +0930 Subject: Re: lightly loaded system eats swap space To: Jeremy Chadwick , freebsd-stable@freebsd.org References: <20180619172936.GA24967@icarus.home.lan> From: Shane Ambler Message-ID: <95c74868-7ba6-9077-4e24-6d685078aee6@ShaneWare.Biz> Date: Wed, 20 Jun 2018 14:38:45 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180619172936.GA24967@icarus.home.lan> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 05:08:56 -0000 On 20/06/2018 02:59, Jeremy Chadwick wrote: > In short (and nebulous as hell; sorry, I cannot be more specific given > the nature of the problem): there have been changes about ZFS's memory > allocation/releasing decision-making scheme compared to ZFS on "older" > FreeBSD (i.e. earlier 11.x, and definitely 10.x and 9.x). I would say the issues started with 10.x, I never had memory issues using 9.x with ZFS. I first had all ram marked wired when testing 10.1. > Recommendations like "limit your ARC" are nothing new in FreeBSD, but > are still ridiculous kludges: tech-lists' system clearly has 105GB MRU > (MRU = most recently used) in ARC, meaning there is memory that can be > released back to the rest of the OS for general use (re: memory > contention/pressure situation), but the OS is choosing to use swap > instead, eventually exhausting it. That logic sounds broken, IMO. (And > yes I did notice the size of bhyve process) This review is aiming to fix this - https://reviews.freebsd.org/D7538 I have been running the patch on stable/11 and after eight days uptime I still have zero swap in use, I can't recall a time in the last few years that I have had no swap usage past the first hour or two uptime. As I have commented in that review, the issue I am seeing is that arc_max is not counted when testing max_wired, the two together can add up to more than the physical ram and wiring all physical ram can push ram used by processes out to swap. I know with 8G physical ram having over 7G wired is not recoverable. max_wired seems to default to 30% ram (5G with 16G ram) I have never seen this mentioned in any zfs tuning, it should be subtracted from physical ram when calculating arc_max. arc_max should never be greater than (kmem_size - max_wired - padding) -- FreeBSD - the place to B...Storing Data Shane Ambler From owner-freebsd-stable@freebsd.org Wed Jun 20 09:07:11 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE654100CA73 for ; Wed, 20 Jun 2018 09:07:11 +0000 (UTC) (envelope-from graham@menhennitt.com.au) Received: from homiemail-a120.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6E3F571D89 for ; Wed, 20 Jun 2018 09:07:11 +0000 (UTC) (envelope-from graham@menhennitt.com.au) Received: from homiemail-a120.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a120.g.dreamhost.com (Postfix) with ESMTP id 3169C6000BD50 for ; Wed, 20 Jun 2018 02:07:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=menhennitt.com.au; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s= menhennitt.com.au; bh=I3cug2Mu+/U5bBk5OH+LtR8arXA=; b=pcpQOjZ0lQ grnp0q9GelIvddeXULFfcc3ZwhXBUECtgFjHqyQuJtucB/FgAlFIEdtjGBXL0Djo fY5DcNQ4PwmXYXmeow1ErWxYHOLS2u2pSa1Iqb2z+foLn0MLKBJ/KMDH3hQ0UxOH GkEpu+kh2B8LvnfbjGCUvtAYxzsJbI8ME= Received: from [203.2.73.68] (c220-239-210-241.mckinn3.vic.optusnet.com.au [220.239.210.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: graham@menhennitt.com.au) by homiemail-a120.g.dreamhost.com (Postfix) with ESMTPSA id C93AE6000BD4F for ; Wed, 20 Jun 2018 02:07:02 -0700 (PDT) Subject: Re: Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2? To: freebsd-stable@freebsd.org References: <79e621cc-9c0a-c0c8-decd-5789241a633f@omnilan.de> <81edd070-0666-c39c-bb8f-5f0591c74f9d@omnilan.de> From: Graham Menhennitt Message-ID: Date: Wed, 20 Jun 2018 19:07:00 +1000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <81edd070-0666-c39c-bb8f-5f0591c74f9d@omnilan.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 09:07:12 -0000 I'm on 11-Stable as of about a month ago. Works or me (although I don't=20 stress it very much). Graham On 20/06/2018 04:30, Harry Schmalzbauer wrote: > Am 16.06.2018 um 21:42 schrieb Harry Schmalzbauer: > =E2=80=A6 >> To rule out a known vboxnetflt(4) limitation/failure, I'd like to=20 >> know if somebody successfully uses vboxnetflt(4) from=20 >> virtualbox-ose-kmod-5.2.12 on stable/11|11.2. > > Really nobody out there who has VirtualBox sucessfully running under=20 > stable/11 or 11.x with bridged network? > > Anyone who tried, but also observed similar problems like I have on=20 > -current?=20 From owner-freebsd-stable@freebsd.org Wed Jun 20 10:04:27 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED6BD100F83F for ; Wed, 20 Jun 2018 10:04:26 +0000 (UTC) (envelope-from admin@npo-lencor.ru) Received: from forward100p.mail.yandex.net (forward100p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84F60742CE for ; Wed, 20 Jun 2018 10:04:26 +0000 (UTC) (envelope-from admin@npo-lencor.ru) Received: from mxback8j.mail.yandex.net (mxback8j.mail.yandex.net [IPv6:2a02:6b8:0:1619::111]) by forward100p.mail.yandex.net (Yandex) with ESMTP id 4B8C55106EB1 for ; Wed, 20 Jun 2018 13:04:24 +0300 (MSK) Received: from smtp1p.mail.yandex.net (smtp1p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:6]) by mxback8j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id twtJzHU6TK-4IZOtDAJ; Wed, 20 Jun 2018 13:04:18 +0300 Received: by smtp1p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id MkWEIzpXJr-4B8u44rs; Wed, 20 Jun 2018 13:04:11 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Subject: Re: ATI video problem - extremely slow desktop - 100% cpu load To: freebsd-stable@freebsd.org References: <20180619212311.GA36401@quark.hightek.org> From: Nikita Druba Message-ID: <90a377a2-4267-afb5-a36e-78cc0999a158@npo-lencor.ru> Date: Wed, 20 Jun 2018 13:04:11 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180619212311.GA36401@quark.hightek.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 10:04:27 -0000 Hello! I was have the same problem with my HD 4870x2 at FreeBSD 11.1 and kde5 some time ago. As a result I was change video card to Nvidia. But I don't try vesa drivers. Good luck! 20.06.2018 00:23, Vincent Stemen пишет: > Hi. > > FreeBSD 11.1-RELEASE > Motherboard: gigabyte GA-78LMT-USB3 R2 > Video: Integrated ATI Radeon HD 3000 graphics > > System runs fine with a simple stand alone window manager such as jwm, > openbox, etc. But anytime I run a desktop environment that has a panel and/or > desktop icons, the X desktop takes a very long time to start up and runs > extremely slow and unresponsive, the pointer jumps instead of moving smoothly, > and the main Xorg process runs at 100% load on one core. I have tried several > different desktops, such as xfce, enlightenment, lumina, etc. Similar problem > on all of them. > > It appears to be any environment that is using DBUS. That could just be > a coincidence. > > The weird thing is that it does not always do it. Once in a while, when > I launch X, it comes up quick and runs fine. Shut down X and re-run it and > it's back doing it again. Sometimes it will come up running fine several > times in a row. Once it comes up working correctly, it stays working until > I restart X. Even after a reboot, it is inconsistent about doing it the first > time X is run. > > I have tried re-installing all the ports from X11 and the desktop environments > from FreeBSD 11 release_1, release_2, quarterly, and latest. Same problem > with all of them. > > Does anybody have any idea what could be causing this? > > I don't know if for sure if this is a FreeBSD or a port problem. There are > radeon modules running. > > # kldstat > > 5 1 0xffffffff82431000 12b4a0 radeonkms.ko > ... > 10 1 0xffffffff825b9000 103e radeonkmsfw_RS780_pfp.ko > 11 1 0xffffffff825bb000 5b3f radeonkmsfw_RS780_me.ko > 12 1 0xffffffff825c1000 1338 radeonkmsfw_R600_rlc.ko > > X is using the ati driver from the xf86-video-ati-7.9.0_1,1 package. > > The evidence seems to be pointing toward the xf86-video-ati package being the > problem. If I edit /etc/X11/xorg.conf to use the "vesa" driver rather than > the "radeon" driver the problem goes away. > > But, of course, the vesa driver is low resolution and does not re-initialize the > console when I exit X. > > _______________________________________________ > 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 Wed Jun 20 10:48:08 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 546521011681 for ; Wed, 20 Jun 2018 10:48:08 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (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 DEE3E75820 for ; Wed, 20 Jun 2018 10:48:07 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [82.47.240.30] (helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fVaei-0009R8-6x for freebsd-stable@freebsd.org; Wed, 20 Jun 2018 10:48:04 +0000 Subject: Re: Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2? To: freebsd-stable@freebsd.org References: <79e621cc-9c0a-c0c8-decd-5789241a633f@omnilan.de> <81edd070-0666-c39c-bb8f-5f0591c74f9d@omnilan.de> From: Pete French Message-ID: Date: Wed, 20 Jun 2018 11:48:03 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 10:48:08 -0000 I use VirtualBox all the time on 11-STABLE. I do make sure I recompile the ernel module every time I rebuild the OS, but its pretty solid for me. You need the AIO tunings though. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298 -pete. From owner-freebsd-stable@freebsd.org Wed Jun 20 15:06:02 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A8CA101DC50 for ; Wed, 20 Jun 2018 15:06:02 +0000 (UTC) (envelope-from SRS0=2bF4=JG=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0C5E37E384 for ; Wed, 20 Jun 2018 15:06:01 +0000 (UTC) (envelope-from SRS0=2bF4=JG=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E5C4C2847C for ; Wed, 20 Jun 2018 17:05:53 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 06CE02849E for ; Wed, 20 Jun 2018 16:55:29 +0200 (CEST) To: freebsd-stable@freebsd.org From: Miroslav Lachman <000.fbsd@quip.cz> Subject: iostat busy value calculation Message-ID: <98c4156c-d2f0-f0c6-b859-9cea8ec29a42@quip.cz> Date: Wed, 20 Jun 2018 16:55:28 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 15:06:02 -0000 I would like to know how the value of disk "busy" is calculated? I want to use values from iostat in the monitoring (zabbix). iostat shows averages by default and the last column is "busy %", but the first output contains averages from the system boot til now. # iostat -x -t da extended device statistics device r/s w/s kr/s kw/s qlen svc_t %b ada0 2.5 13.8 49.0 287.9 0 45.7 2 ada1 2.6 13.8 51.7 287.9 0 39.6 2 I don't want to use "iostat -x -t da -w 20" to get averages of the last 20 seconds because it means monitoring needs to wait 20 seconds on each run. I can use absolute values from iostat. This output is without any delay and the monitoring SW can calculate averages between two runs. But the last column is no busy %, it is sb/i. # iostat -I -x -t da extended device statistics device r/i w/i kr/i kw/i qlen tsvc_t/i sb/i ada0 7403218.0 40825749.0 144647824.0 849655694.0 0 2204904.2 73121.8 ada1 7537423.0 40825749.0 152643874.5 849655694.0 0 1914301.0 69996.5 So the question is - If I want to plot "busy %" in the graph - how the "busy" value in the first example is calculated? Is it possible to calculate it from the numbers that I have from "iostat -I -x" and the know time interval between two runs? Miroslav Lachman From owner-freebsd-stable@freebsd.org Wed Jun 20 15:37:26 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A88E5101FBBF for ; Wed, 20 Jun 2018 15:37:26 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-am5eur03on0728.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe08::728]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 04202804A3 for ; Wed, 20 Jun 2018 15:37:25 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alogis.onmicrosoft.com; s=selector1-alogis-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bZYLbatGELwv/d1Zq2CmCenFFOiiM5uR+iDIYuW+cU4=; b=Ja4ecEHaSmRTpTK3i4/Amk75XCZznjZkTY3jU7YyDBlMaMq/EoY3bm+oVqxw7J+4he1BVLn2aDcZF4QlkZf2KXeUiI850GQ7x8TWEbGGp9XaZvFlqqndbNSbnXTkOT60jzkaEWU6CAN3yM6l8UUln0oVpXUNMRMTAPOsRZYVMy4= Received: from AM6P192MB0503.EURP192.PROD.OUTLOOK.COM (52.134.121.25) by AM6P192MB0360.EURP192.PROD.OUTLOOK.COM (52.134.120.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.863.16; Wed, 20 Jun 2018 15:37:24 +0000 Received: from AM6P192MB0503.EURP192.PROD.OUTLOOK.COM ([fe80::44d2:66f4:2156:d2d1]) by AM6P192MB0503.EURP192.PROD.OUTLOOK.COM ([fe80::44d2:66f4:2156:d2d1%13]) with mapi id 15.20.0863.016; Wed, 20 Jun 2018 15:37:23 +0000 From: Holger Kipp To: Miroslav Lachman <000.fbsd@quip.cz> CC: "freebsd-stable@freebsd.org" Subject: Re: iostat busy value calculation Thread-Topic: iostat busy value calculation Thread-Index: AQHUCKh/spwao2z+mkSo3Caw3YLCbqRpR9mA Date: Wed, 20 Jun 2018 15:37:23 +0000 Message-ID: <5765F5AE-131A-4F2F-8C46-9E362611CDA1@alogis.com> References: <98c4156c-d2f0-f0c6-b859-9cea8ec29a42@quip.cz> In-Reply-To: <98c4156c-d2f0-f0c6-b859-9cea8ec29a42@quip.cz> Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Holger.Kipp@alogis.com; x-originating-ip: [212.184.102.1] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; AM6P192MB0360; 7:cyXTy+/QlUyehJ1QWHt6md8tG6ApFeWMcgEk+GF2NzXoqefQm7GRr/PvBElTcmRCOxHg1xFuWpcAbAzBRlCpPvnH5A+MpQvgthBN2JtpyQDm/+h5JGuZf1dU1Y4hEtFuPlCZXTNvxSB8SnwT69kgHtASKTL55abEhQeFHrCiYYti3c3KDa8NAgCf/Sh0xj7EHFOLV2OeCf+z4X9UJVIRpLpZBI6v/fmSWiYgjfxyMEN1XnjLN5fVTGyBMvNv3mUY x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 2981fb67-fef1-401e-261e-08d5d6c3b7ef x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(711020)(2017052603328)(7153060)(7193020); SRVR:AM6P192MB0360; x-ms-traffictypediagnostic: AM6P192MB0360: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(72170088055959); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123558120)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:AM6P192MB0360; BCL:0; PCL:0; RULEID:; SRVR:AM6P192MB0360; x-forefront-prvs: 070912876F x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39840400004)(396003)(376002)(366004)(346002)(39380400002)(199004)(189003)(33656002)(36756003)(5660300001)(106356001)(236005)(8936002)(6116002)(6512007)(54896002)(99286004)(2616005)(14454004)(229853002)(76176011)(5250100002)(102836004)(486006)(6436002)(82746002)(6486002)(476003)(25786009)(11346002)(3480700004)(8676002)(7736002)(413944005)(53936002)(4326008)(3846002)(2900100001)(6506007)(6916009)(83716003)(316002)(81166006)(81156014)(72206003)(186003)(26005)(3660700001)(478600001)(3280700002)(2906002)(66066001)(6246003)(86362001)(105586002)(68736007)(446003)(97736004); DIR:OUT; SFP:1102; SCL:1; SRVR:AM6P192MB0360; H:AM6P192MB0503.EURP192.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: alogis.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: F1CmRgNMYSG/tYNpcxP20BZP2QlW+AkDQH0YIGvhaZUEfA0bwMJGmp+ZiQHUcMMiDno8HacK8C3enbFi8tbnTqJtjOLwgdJraDlhW7CEnPFwbK86E0c8v/fcGcWLNBIAp00DOIIH06HaTDYzNgzCz/6G5Xe8p5elx92JSA2m1utLnGiMdGYoL6NVZ7p89+94lAKjBWWFzVHZdVHgdRUADFWHH44KqIJz6BboVS9kVoCpPsOcmISAL2KvzeN+ZnHSdpPvUH4uHJBPurE4mheZe8GlafzZDnfFw/t89Ffmctej27hRFmghuDghVqKGFBSD spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: alogis.com X-MS-Exchange-CrossTenant-Network-Message-Id: 2981fb67-fef1-401e-261e-08d5d6c3b7ef X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Jun 2018 15:37:23.4725 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 15828ba7-fd50-4285-ae4d-078568595b48 X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6P192MB0360 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 15:37:27 -0000 Dear Miroslav, looking at the manpage for iostat I see: %b % of time the device had one or more outstanding transac= tions tsvc_t/i total duration of transactions per time period, in secon= ds sb/i total time the device had one or more outstanding transa= c- tions per time period, in seconds So calculating the percentage using sb/i should be fairly easy. Best regards, Holger Am 20.06.2018 um 16:55 schrieb Miroslav Lachman <000.fbsd@quip.cz>: I would like to know how the value of disk "busy" is calculated? I want to use values from iostat in the monitoring (zabbix). iostat shows averages by default and the last column is "busy %", but the f= irst output contains averages from the system boot til now. # iostat -x -t da extended device statistics device r/s w/s kr/s kw/s qlen svc_t %b ada0 2.5 13.8 49.0 287.9 0 45.7 2 ada1 2.6 13.8 51.7 287.9 0 39.6 2 I don't want to use "iostat -x -t da -w 20" to get averages of the last 20 = seconds because it means monitoring needs to wait 20 seconds on each run. I can use absolute values from iostat. This output is without any delay and= the monitoring SW can calculate averages between two runs. But the last co= lumn is no busy %, it is sb/i. # iostat -I -x -t da extended device statistics device r/i w/i kr/i kw/i qlen tsvc_t/i = sb/i ada0 7403218.0 40825749.0 144647824.0 849655694.0 0 2204904.2 = 73121.8 ada1 7537423.0 40825749.0 152643874.5 849655694.0 0 1914301.0 = 69996.5 So the question is - If I want to plot "busy %" in the graph - how the "bus= y" value in the first example is calculated? Is it possible to calculate it from the numbers that I have from "iostat -I= -x" and the know time interval between two runs? Miroslav Lachman From owner-freebsd-stable@freebsd.org Wed Jun 20 16:13:42 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F6941021EFA for ; Wed, 20 Jun 2018 16:13:42 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::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 CE8C982C57 for ; Wed, 20 Jun 2018 16:13:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id t6-v6so239496iob.10 for ; Wed, 20 Jun 2018 09:13:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6AdGx5ajBHn1yls/qsxrTd0blzTW7PZnujD9oDvx8Ps=; b=TMM0PsjFI7sVYnE2kACiqPQbI2ta0yoE7WgEwYkKwGNStlKba9slleXsg8aNMVS+/8 olXyWws40eld0YNnSbSz2u5Hs1vzSrYa4TfLAlqC4iDeqYFfxHhAcAxHn1+9EpItxUWZ mjncrmkHO/TqFRiChCA4x05pqOfqYP4pypB5NDe16fBF7E+vhvrBQQ7ZsUVMqmHEfX3r tbD6O7TFLvcIPqpwS04gEE19gFe3ukJmvh+qyN8vwjqrx6gQr7ujQ6taCtFMl05Ex8jy 4eqwFxdOZ6E3Vl/EsGKLQSzGp/Em+tO0k6lIp8sbd1lAnkUkSWbWtnDFUcHeX5+uN9d0 QjZg== 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=6AdGx5ajBHn1yls/qsxrTd0blzTW7PZnujD9oDvx8Ps=; b=nXDB843EVj3Flpc6uHu6quUzMpzO33Tw+L0Gb2p+EzQR1eoxo6bXz996GIMKM/kw2P 4O7ohiWP7ox6MaeErhgcNZwSsQMRAjQ+G2UzGLOY85OsNaeaFo/fUf0V4mNSBE2soS60 o9dft55yPanc8woXa9ymHsgXJQaH1shhurxFniesb31KmvK5Q+h7y5VdbfqP8F6blFJo inUWlDpCm+WK8eQgd+ABkebsQxWcOP6HTqUnyAlfHO0RVXPvo/aqhhXAcuxtn9afwC/O 9AUHeKHJUh6UOc7s+uwLSDepBSg6z26YTl74gJCT1xjEYEeuK8NZWoa2sVN8GtQgZWkY NUrw== X-Gm-Message-State: APt69E12kJ75eBKiMo6aFOHsYtvI0ltgbW/YNN3eRkDA/Mff8ruIWog1 X/0xumzpyZ6Lg7OssStke6RfjUDj1z3jXnjU3VXkWw== X-Google-Smtp-Source: ADUXVKKPBw2P780F3U5sxesgOu2rWZDhp0g6W3L39jO+iL/QytxP8VnTpfg2Vgrwp8ZucV65CDotN5JPMSxQLVB8FU8= X-Received: by 2002:a6b:29c4:: with SMTP id p187-v6mr17152163iop.299.1529511221035; Wed, 20 Jun 2018 09:13:41 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:5945:0:0:0:0:0 with HTTP; Wed, 20 Jun 2018 09:13:40 -0700 (PDT) X-Originating-IP: [50.227.106.226] In-Reply-To: <98c4156c-d2f0-f0c6-b859-9cea8ec29a42@quip.cz> References: <98c4156c-d2f0-f0c6-b859-9cea8ec29a42@quip.cz> From: Warner Losh Date: Wed, 20 Jun 2018 10:13:40 -0600 X-Google-Sender-Auth: qEEqObKqdW54Ov12qqUE1GnNgok Message-ID: Subject: Re: iostat busy value calculation To: Miroslav Lachman <000.fbsd@quip.cz> Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 16:13:42 -0000 On Wed, Jun 20, 2018 at 8:55 AM, Miroslav Lachman <000.fbsd@quip.cz> wrote: > I would like to know how the value of disk "busy" is calculated? > > I want to use values from iostat in the monitoring (zabbix). > iostat shows averages by default and the last column is "busy %", but the > first output contains averages from the system boot til now. > %busy comes from the devstat layer. It's defined as the percent of the time over the polling interval in which at least one transaction was awaiting completion by the lower layers. It's an imperfect measure of how busy the drives are (in ye-olden days, before tagged queuing and NCQ, it was OK because you had THE transaction pending and it was a good measure of how utilized things were. Now with concurrent I/O in flash devices, it's only an imperfect approximation). Warner From owner-freebsd-stable@freebsd.org Wed Jun 20 17:35:12 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 904E91025DAD for ; Wed, 20 Jun 2018 17:35:12 +0000 (UTC) (envelope-from SRS0=2bF4=JG=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 16BFD86D9C for ; Wed, 20 Jun 2018 17:35:11 +0000 (UTC) (envelope-from SRS0=2bF4=JG=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7DA7928416; Wed, 20 Jun 2018 19:35:10 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id EC39A2840C; Wed, 20 Jun 2018 19:35:08 +0200 (CEST) Subject: Re: iostat busy value calculation To: Holger Kipp Cc: "freebsd-stable@freebsd.org" References: <98c4156c-d2f0-f0c6-b859-9cea8ec29a42@quip.cz> <5765F5AE-131A-4F2F-8C46-9E362611CDA1@alogis.com> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Wed, 20 Jun 2018 19:35:08 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <5765F5AE-131A-4F2F-8C46-9E362611CDA1@alogis.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 17:35:12 -0000 Holger Kipp wrote on 2018/06/20 17:37: > Dear Miroslav, > > looking at the manpage for iostat I see: > > %b % of time the device had one or more outstanding transactions > tsvc_t/i > total duration of transactions per time period, in seconds > sb/i total time the device had one or more outstanding transac- > tions per time period, in seconds > > So calculating the percentage using sb/i should be fairly easy. If I understand it correctly, then it cannot be calculated from numbers between two independent runs of "iostat -I -x" because it gives me sb/i average from the boot time, so the calculated %b will be overall average instead of average between two runs after 60 seconds. The only possible way to calculated is to run "iostat -I -x -c 2 -w 60" where the sb/i value of the second line will be average of these last 60 seconds. But it also means monitoring probe will wait 60 seconds to get this value (each time) so it is the same problem as I described in my original post with "iostat -x". Miroslav Lachman > Am 20.06.2018 um 16:55 schrieb Miroslav Lachman <000.fbsd@quip.cz>: > > I would like to know how the value of disk "busy" is calculated? > > I want to use values from iostat in the monitoring (zabbix). > iostat shows averages by default and the last column is "busy %", but the first output contains averages from the system boot til now. > > # iostat -x -t da > extended device statistics > device r/s w/s kr/s kw/s qlen svc_t %b > ada0 2.5 13.8 49.0 287.9 0 45.7 2 > ada1 2.6 13.8 51.7 287.9 0 39.6 2 > > I don't want to use "iostat -x -t da -w 20" to get averages of the last 20 seconds because it means monitoring needs to wait 20 seconds on each run. > > I can use absolute values from iostat. This output is without any delay and the monitoring SW can calculate averages between two runs. But the last column is no busy %, it is sb/i. > > # iostat -I -x -t da > extended device statistics > device r/i w/i kr/i kw/i qlen tsvc_t/i sb/i > ada0 7403218.0 40825749.0 144647824.0 849655694.0 0 2204904.2 73121.8 > ada1 7537423.0 40825749.0 152643874.5 849655694.0 0 1914301.0 69996.5 > > So the question is - If I want to plot "busy %" in the graph - how the "busy" value in the first example is calculated? > Is it possible to calculate it from the numbers that I have from "iostat -I -x" and the know time interval between two runs? From owner-freebsd-stable@freebsd.org Wed Jun 20 17:37:28 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AF8D1025F4C for ; Wed, 20 Jun 2018 17:37:28 +0000 (UTC) (envelope-from SRS0=2bF4=JG=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E959086EC9 for ; Wed, 20 Jun 2018 17:37:27 +0000 (UTC) (envelope-from SRS0=2bF4=JG=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id C1B252840C; Wed, 20 Jun 2018 19:37:21 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id AD81B28416; Wed, 20 Jun 2018 19:37:20 +0200 (CEST) Subject: Re: iostat busy value calculation To: Warner Losh Cc: FreeBSD-STABLE Mailing List References: <98c4156c-d2f0-f0c6-b859-9cea8ec29a42@quip.cz> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <55731ed7-c9f5-1e39-9c09-b522e58b97a1@quip.cz> Date: Wed, 20 Jun 2018 19:37:20 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 17:37:28 -0000 Warner Losh wrote on 2018/06/20 18:13: > > > On Wed, Jun 20, 2018 at 8:55 AM, Miroslav Lachman <000.fbsd@quip.cz > > wrote: > > I would like to know how the value of disk "busy" is calculated? > > I want to use values from iostat in the monitoring (zabbix). > iostat shows averages by default and the last column is "busy %", > but the first output contains averages from the system boot til now. > > > %busy comes from the devstat layer. It's defined as the percent of the > time over the polling interval in which at least one transaction was > awaiting completion by the lower layers. It's an imperfect measure of > how busy the drives are (in ye-olden days, before tagged queuing and > NCQ, it was OK because you had THE transaction pending and it was a good > measure of how utilized things were. Now with concurrent I/O in flash > devices, it's only an imperfect approximation). Yes, I am aware of this issue. This percentage is just "is it slightly loaded or heavily loaded" indicator. Miroslav Lachman From owner-freebsd-stable@freebsd.org Wed Jun 20 19:43:50 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF42D10072D8 for ; Wed, 20 Jun 2018 19:43:50 +0000 (UTC) (envelope-from vince@hightek.org) Received: from mail.ngtek.org (ngtek.org [IPv6:2001:19f0:6400:8963:5400:ff:fe09:9585]) (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 56770718A4 for ; Wed, 20 Jun 2018 19:43:50 +0000 (UTC) (envelope-from vince@hightek.org) Received: from ip68-227-103-24.ok.ok.cox.net ([68.227.103.24] helo=hightek.org) by mail.ngtek.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fVj1B-000EWf-10 for freebsd-stable@FreeBSD.ORG; Wed, 20 Jun 2018 14:43:49 -0500 Received: from localhost ([127.0.0.1] helo=quark.hightek.org) by hightek.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fVj1A-000Mot-5a for freebsd-stable@FreeBSD.ORG; Wed, 20 Jun 2018 14:43:48 -0500 Received: (from vince@localhost) by quark.hightek.org (8.15.2/8.15.2/Submit) id w5KJhmVo087722 for freebsd-stable@FreeBSD.ORG; Wed, 20 Jun 2018 14:43:48 -0500 (CDT) (envelope-from vince) Date: Wed, 20 Jun 2018 14:43:48 -0500 From: Vincent Stemen To: freebsd-stable@FreeBSD.ORG Subject: Re: ATI video problem - extremely slow desktop - 100% cpu load Message-ID: <20180620194347.GA87224@quark.hightek.org> References: <20180619212311.GA36401@quark.hightek.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180619212311.GA36401@quark.hightek.org> User-Agent: Mutt/1.8.3 (2017-05-23) Reply-To: vince-2018062714@hightek.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 19:43:50 -0000 I have now tested with two additional ATI cards. A Radeon HD 5450 and and older card that shows as "RV370 [Radeon X300 SE]" in the PCI info. Same problem on all of them. Before, it would come up and run correctly once in a while. It doesn't seem to at all now. This seems to be some kind of core radeon driver bug. From owner-freebsd-stable@freebsd.org Wed Jun 20 21:13:20 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B3B4100C826 for ; Wed, 20 Jun 2018 21:13:20 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 94F33753C1 for ; Wed, 20 Jun 2018 21:13:19 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-wm0-x231.google.com with SMTP id o13-v6so1676731wmf.4 for ; Wed, 20 Jun 2018 14:13:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7nr1jFcOSlMTR18rRAS7qINAZzSkwYReoso0zOY8j2E=; b=cV8GIJSeBeRiuXPHisTG/dMjIPZjT6WHrnTCLQfmo8wVPZuNXyMT5jc6s36hinoD5u AHN+tXcIwZzolac+R/EILyGRHbnpm1GyuPM2ZnBtptJYKARcAfK8ElcCCGkeacgi6fwn myuCtKCC65m3jN179Nuntw6CVSUPtXBpryLSWgeAA5yAbX+KFOSU2RsmGn5MJZGBxO3m pMfRRlLEywV/eSnudtbfjnFaCqX+YIxp2fnTKCJzIrVYOp3aU3swVks1snK7l1gQTcOW vkiAQcbXMJmJ1EMIs4Ygwr3435qm+dRDfBK1qC0wy1TJGVMFBmjTOYMQI87p3n4WiEW+ hm5w== 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=7nr1jFcOSlMTR18rRAS7qINAZzSkwYReoso0zOY8j2E=; b=kvulfgY8wfzvW6rr64DYQbGHfS52cYig3piLCOScUuwV4uDxutp5ZnyTAfxFSBGkyx otPv47c+amJFsfS947xICok5yr8onmXFmfalu/KDj4btKypL+ePJVVrs0dFnG7/b5DeJ 88zHFP8qy7uhTE6U8BEYyFSoQ1OrSML2ghuKOypqV2QbAzgaNQt+1rCiTUKob7B3w3gM cbD4Gzl+FBulFJue9IpgOgmJqWQpyn9o7DFxbzVNVJk0uaVP5Mgt4yK60SAhlqEv/fQJ QS5ZQPeS1dyoJnQzeuB3VuCT35xdVVaK2l6vPDpURgCPXnVimzsGTbT82az3f5XIFVv8 0OmA== X-Gm-Message-State: APt69E1TBxvPXnR+kxqJFPML455WIG1P2A3g9FWU0FrC6djeB1gCdvnx LXMjh6tCZRsIePbQxZmHMBLGO+rP8Ytu9/XybL/zUd+2 X-Google-Smtp-Source: ADUXVKL02WCbe6FbVmwe9tfsUfZa4yxYdfwo6ASdgI501XWwOSHkEjIx2PFbgDMgGJPHscF6k7XBd9x+hVkDLzuLmro= X-Received: by 2002:a50:fc88:: with SMTP id f8-v6mr19932912edq.166.1529529198241; Wed, 20 Jun 2018 14:13:18 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:b53c:0:0:0:0:0 with HTTP; Wed, 20 Jun 2018 14:13:17 -0700 (PDT) X-Originating-IP: [38.104.68.66] In-Reply-To: <20180620194347.GA87224@quark.hightek.org> References: <20180619212311.GA36401@quark.hightek.org> <20180620194347.GA87224@quark.hightek.org> From: Mark Saad Date: Wed, 20 Jun 2018 17:13:17 -0400 Message-ID: Subject: Re: ATI video problem - extremely slow desktop - 100% cpu load To: vince-2018062714@hightek.org Cc: FreeBSD-Stable ML Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 20 Jun 2018 21:13:20 -0000 On Wed, Jun 20, 2018 at 3:43 PM, Vincent Stemen wrote: > I have now tested with two additional ATI cards. > A Radeon HD 5450 and and older card that shows as > "RV370 [Radeon X300 SE]" in the PCI info. > > Same problem on all of them. Before, it would come up and run correctly > once in a while. It doesn't seem to at all now. This seems to be some > kind of core radeon driver bug. > Vincent I am running 11.2-PRERELEASE with a Cedar PRO [Radeon HD 5450/6350] and I dont have any issues like that here is what I do to get it working for me; and I have used more or less the same setup since 10.3-RELEASE In my loader.conf I have radeonkms_load="YES" radeonkmsfw_CEDAR_pfp_load="YES" radeonkmsfw_CEDAR_rlc_load="YES" radeonkmsfw_CEDAR_me_load="YES" I use a static xorg.conf as well In there I have the following bits 1 Section "ServerLayout" 2 Identifier "X.org Configured" 3 Screen 0 "Screen0" 0 0 4 InputDevice "Mouse0" "CorePointer" 5 InputDevice "Keyboard0" "CoreKeyboard" 6 Option "AIGLX" "true" 7 EndSection ... 19 Section "Module" 20 Load "dbe" 21 Load "dri" 22 Load "dri2" 23 Load "extmod" 24 Load "record" 25 Load "freetype" 26 Load "bitmap" 27 Load "type1" 28 Load "glx" 29 EndSection ... 50 Section "Device" 51 Option "AccelMethod" "EXA" 52 Option "DRI" "true" 53 Identifier "Card0" 54 Driver "radeon" 55 BusID "PCI:3:0:0" 56 EndSection 57 ... Also if the redeon driver is not working for you try scfb . It works better the vesa it some cases msaad@ostrich:~ % pkg info xf86-video-scfb-0.0.4_5 xf86-video-scfb-0.0.4_5 Name : xf86-video-scfb Version : 0.0.4_5 Installed on : Mon Sep 25 10:52:09 2017 EDT Origin : x11-drivers/xf86-video-scfb Architecture : FreeBSD:11:amd64 Prefix : /usr/local Categories : x11-drivers Licenses : Maintainer : x11@FreeBSD.org WWW : UNKNOWN Comment : X.Org syscons display driver Annotations : repo_type : binary repository : FreeBSD Flat size : 21.4KiB Description : This package contains the X.Org xf86-video-scfb driver. Framebuffer access via FreeBSD syscons. > _______________________________________________ > 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" -- mark saad | nonesuch@longcount.org From owner-freebsd-stable@freebsd.org Thu Jun 21 01:38:59 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E409101A859 for ; Thu, 21 Jun 2018 01:38:59 +0000 (UTC) (envelope-from info@ys-kyoto.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3D51C7F0D5 for ; Thu, 21 Jun 2018 01:38:59 +0000 (UTC) (envelope-from info@ys-kyoto.com) Received: by mailman.ysv.freebsd.org (Postfix) id EBACF101A858; Thu, 21 Jun 2018 01:38:58 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D95A3101A857 for ; Thu, 21 Jun 2018 01:38:58 +0000 (UTC) (envelope-from info@ys-kyoto.com) Received: from www237b.sakura.ne.jp (www237b.sakura.ne.jp [219.94.155.97]) (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 18E597F0CF for ; Thu, 21 Jun 2018 01:38:57 +0000 (UTC) (envelope-from info@ys-kyoto.com) Received: from INT-VM (vps149830.trouble-free.net [66.45.231.187] (may be forged)) (authenticated bits=0) by www237b.sakura.ne.jp (8.15.2/8.15.2) with ESMTPA id w5L1ZO4Q092577 for ; Thu, 21 Jun 2018 10:38:55 +0900 (JST) (envelope-from info@ys-kyoto.com) Message-Id: <201806210138.w5L1ZO4Q092577@www237b.sakura.ne.jp> From: "Valodzka Anatoli. " Subject: Waiting for your Response. To: stable@FreeBSD.org MIME-Version: 1.0 Reply-To: valodzka.anatoli76@gmail.com Date: Wed, 20 Jun 2018 21:38:56 -0400 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 21 Jun 2018 01:38:59 -0000 Hello, I sent you an email earlier 4 days ago regarding a business proposal, = but did not get a reply from you up till this moment. I do not know i= f you receive it or not. Meanwhile, I am a Banker here in Bahrain. I = sent you a business proposition that will benefit the two of us and it= is important that we discuss it. Kindly get back to confirm receipt m= y email, so we can talk in details about it. Waiting your urgent resp= onse. Thanks. Anatoli. From owner-freebsd-stable@freebsd.org Thu Jun 21 09:32:43 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47CD21017C52 for ; Thu, 21 Jun 2018 09:32:43 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0095.outbound.protection.outlook.com [104.47.0.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 869B07511B for ; Thu, 21 Jun 2018 09:32:42 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alogis.onmicrosoft.com; s=selector1-alogis-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FrUIHDToHBurV9YBmiLElJK2kPBGMn4R7ztKvIGPsgU=; b=Pbd2ybI9uogvKaMpJ7On79vm4oo7Nlr4Yc39RLQqLrX5bLd8NgzEwXkJ6Au6nviHkIMoxJg6gwvwHO8FeGirFTw6mPjIPIb1+2PREcX7Gloq39WO7RQW/o3D8wF8Zuq3uT/bP0qlS8cWWDAinMDrnJXmfMT8Dndlv9i3qLig1lI= Received: from AM6P192MB0503.EURP192.PROD.OUTLOOK.COM (52.134.121.25) by AM6P192MB0277.EURP192.PROD.OUTLOOK.COM (52.134.120.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.884.20; Thu, 21 Jun 2018 09:32:39 +0000 Received: from AM6P192MB0503.EURP192.PROD.OUTLOOK.COM ([fe80::44d2:66f4:2156:d2d1]) by AM6P192MB0503.EURP192.PROD.OUTLOOK.COM ([fe80::44d2:66f4:2156:d2d1%13]) with mapi id 15.20.0863.021; Thu, 21 Jun 2018 09:32:39 +0000 From: Holger Kipp To: Miroslav Lachman <000.fbsd@quip.cz> CC: "freebsd-stable@freebsd.org" Subject: Re: iostat busy value calculation Thread-Topic: iostat busy value calculation Thread-Index: AQHUCKh/spwao2z+mkSo3Caw3YLCbqRpR9mAgAAg5gCAAQuGAA== Date: Thu, 21 Jun 2018 09:32:39 +0000 Message-ID: <0E9BBDF0-C46B-4BAF-A059-D9C8F635393A@alogis.com> References: <98c4156c-d2f0-f0c6-b859-9cea8ec29a42@quip.cz> <5765F5AE-131A-4F2F-8C46-9E362611CDA1@alogis.com> In-Reply-To: Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Holger.Kipp@alogis.com; x-originating-ip: [212.184.102.1] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; AM6P192MB0277; 7:E7x2FBzA/txI+Bfe7OWcU6Exrz8Uk4uTCxwCHK63kvPsRSzdj4AJEejY7aLSJ2VBbQEih8MC1L84RvOmdeJfC2BxyhTM8Vbk+x8j7tEti1n+Xrf7LwPlEMGED9n/yG14I/Bh/BoCNWlazk4CSpTmmoqEd/EvTCj1o+c6RqnaPhaD4EF+ROi6z2KN9rCBIFi6fLMHy0Q6v+RTIgUfGd8P5939alPzMOrnv4lrg0Frc77xNgcXz7uUpC0dwtU6XjsH x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 26f1e032-fc2b-4bcb-daa2-08d5d759ee4a x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(711020)(2017052603328)(7153060)(7193020); SRVR:AM6P192MB0277; x-ms-traffictypediagnostic: AM6P192MB0277: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(72170088055959); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231254)(944501410)(52105095)(3002001)(10201501046)(149027)(150027)(6041310)(20161123562045)(20161123558120)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:AM6P192MB0277; BCL:0; PCL:0; RULEID:; SRVR:AM6P192MB0277; x-forefront-prvs: 07106EF9B9 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(39380400002)(396003)(366004)(39830400003)(189003)(199004)(81166006)(478600001)(82746002)(53936002)(413944005)(8936002)(72206003)(97736004)(2616005)(476003)(8676002)(14454004)(99286004)(6512007)(486006)(446003)(106356001)(68736007)(11346002)(81156014)(6246003)(5660300001)(6916009)(33656002)(102836004)(6506007)(26005)(6436002)(3280700002)(76176011)(83716003)(2900100001)(3660700001)(3480700004)(5250100002)(186003)(6486002)(305945005)(25786009)(66066001)(2906002)(7736002)(4326008)(229853002)(86362001)(36756003)(3846002)(6116002)(316002)(105586002); DIR:OUT; SFP:1102; SCL:1; SRVR:AM6P192MB0277; H:AM6P192MB0503.EURP192.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: alogis.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: bQxAJLl8d9PhTkR63mYmCxYPdZ9+imzqwhaQ+6D5I67OLclIUkPq9lsJvQE1UUCHyBlpPfLSCjosgn5f9KFQaFN+ByLYDZgBtIgp8sg/oiidnbFWle4yKxBgTtzPxxL8NzavShanxLnTg2s+GvYnq4jnqyMn7rhOUO4gUn+9vvON7KRb6F7wQKcU02WfCjeTABDYm4nMgyIBUbUNBSmP4yfWMyusmvCBYmTf+M2pWrC/ea4M/ttYXv4qb6CJISMaLKsRtEiPUoO1DVlLHsytAG+lPgeYz/LxDyV6799IyfJnvoyiXaBVCVHtzHJBsLvyUZ/N4IarSAxpQJUwCubngg== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: <5AACA124061BA44E8B90129D988D968A@EURP192.PROD.OUTLOOK.COM> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: alogis.com X-MS-Exchange-CrossTenant-Network-Message-Id: 26f1e032-fc2b-4bcb-daa2-08d5d759ee4a X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jun 2018 09:32:39.1956 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 15828ba7-fd50-4285-ae4d-078568595b48 X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6P192MB0277 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 21 Jun 2018 09:32:43 -0000 RGVhciBNaXJvc2xhdiwNCg0KPiBBbSAyMC4wNi4yMDE4IHVtIDE5OjM1IHNjaHJpZWIgTWlyb3Ns YXYgTGFjaG1hbiA8MDAwLmZic2RAcXVpcC5jej46DQo+IA0KPiBIb2xnZXIgS2lwcCB3cm90ZSBv biAyMDE4LzA2LzIwIDE3OjM3Og0KPj4gRGVhciBNaXJvc2xhdiwNCj4+IGxvb2tpbmcgYXQgdGhl IG1hbnBhZ2UgZm9yIGlvc3RhdCBJIHNlZToNCj4+ICAgICAgICAgICAgJWIgICAgICAlIG9mIHRp bWUgdGhlIGRldmljZSBoYWQgb25lIG9yIG1vcmUgb3V0c3RhbmRpbmcgdHJhbnNhY3Rpb25zDQo+ PiAgICAgICAgICAgIHRzdmNfdC9pDQo+PiAgICAgICAgICAgICAgICAgICAgdG90YWwgZHVyYXRp b24gb2YgdHJhbnNhY3Rpb25zIHBlciB0aW1lIHBlcmlvZCwgaW4gc2Vjb25kcw0KPj4gICAgICAg ICAgICBzYi9pICAgIHRvdGFsIHRpbWUgdGhlIGRldmljZSBoYWQgb25lIG9yIG1vcmUgb3V0c3Rh bmRpbmcgdHJhbnNhYy0NCj4+ICAgICAgICAgICAgICAgICAgICB0aW9ucyBwZXIgdGltZSBwZXJp b2QsIGluIHNlY29uZHMNCj4+IFNvIGNhbGN1bGF0aW5nIHRoZSBwZXJjZW50YWdlIHVzaW5nIHNi L2kgc2hvdWxkIGJlIGZhaXJseSBlYXN5Lg0KPiANCj4gSWYgSSB1bmRlcnN0YW5kIGl0IGNvcnJl Y3RseSwgdGhlbiBpdCBjYW5ub3QgYmUgY2FsY3VsYXRlZCBmcm9tIG51bWJlcnMgYmV0d2VlbiB0 d28gaW5kZXBlbmRlbnQgcnVucyBvZiAiaW9zdGF0IC1JIC14IiBiZWNhdXNlIGl0IGdpdmVzIG1l IHNiL2kgYXZlcmFnZSBmcm9tIHRoZSBib290IHRpbWUsIHNvIHRoZSBjYWxjdWxhdGVkICViIHdp bGwgYmUgb3ZlcmFsbCBhdmVyYWdlIGluc3RlYWQgb2YgYXZlcmFnZSBiZXR3ZWVuIHR3byBydW5z IGFmdGVyIDYwIHNlY29uZHMuDQo+IFRoZSBvbmx5IHBvc3NpYmxlIHdheSB0byBjYWxjdWxhdGVk IGlzIHRvIHJ1biAiaW9zdGF0IC1JIC14IC1jIDIgLXcgNjAiIHdoZXJlIHRoZSBzYi9pIHZhbHVl IG9mIHRoZSBzZWNvbmQgbGluZSB3aWxsIGJlIGF2ZXJhZ2Ugb2YgdGhlc2UgbGFzdCA2MCBzZWNv bmRzLiBCdXQgaXQgYWxzbyBtZWFucyBtb25pdG9yaW5nIHByb2JlIHdpbGwgd2FpdCA2MCBzZWNv bmRzIHRvIGdldCB0aGlzIHZhbHVlIChlYWNoIHRpbWUpIHNvIGl0IGlzIHRoZSBzYW1lIHByb2Js ZW0gYXMgSSBkZXNjcmliZWQgaW4gbXkgb3JpZ2luYWwgcG9zdCB3aXRoICJpb3N0YXQgLXjigJwN Cg0KDQpJIGhhdmVu4oCZdCB0aG9yb3VnaGx5IGNoZWNrZWQgdGhpcyBteXNlbGYgKG9ubHkgYSBx dWljayBjaGVjayksIGJ1dCB3aXRoIC1JIHlvdSBzaG91bGQgZ2V0IHRoZSB0b3RhbCB2YWx1ZXMg c2luY2UgYm9vdC4gVGhlIG1hbi1wYWdlIGZvciBPcGVuQlNEIHN0YXRlcyAiVGhlIC1JIG9wdGlv biBjYXVzZXMgaW9zdGF0IHRvIHByaW50IHJhdywgdW5hdmVyYWdlZCB2YWx1ZXMu4oCcIA0KDQpF Zy4geW91IGhhdmUgYWJvdXQgNzAuMDAwIHNlY29uZHMgd2hlcmUgdGhlIGRldmljZXMgYWRhMCBh bmQgYWRhMSB3ZXJlIGJ1c3ksIHdoaWNoIGVxdWFscyAyJSwgc28geW91ciBzeXN0ZW0gaGFzIGFu IHVwdGltZSBvZiBhYm91dCA0MiBkYXlzLg0KDQpNYXliZSB5b3UganVzdCBjaGVjayBieSBnZXR0 aW5nIHZhbHVlcyBldmVyeSAxMCBzZWNvbmRzLCBsb29raW5nIGF0IHNiL2kgYW5kIGNhbGN1bGF0 ZSB0aGUgZGlmZmVyZW5jZSBvZiB0d28gY29uc2VjdXRpdmUgdmFsdWVzLCBkaXZpZGUgYnkgdGhl IHRpbWUgcGVyaW9kIGluIHNlY29uZHMsIG11bHRpcGx5IGJ5IDEwMCBhbmQgaGF2ZSBhIHBlcmNl bnRhZ2UgLSB3aXRoIHRoZSBkb3duc2lkZSBvZiBub3QgYmVpbmcgdGhhdCBhY2N1cmF0ZSAoYXMg V2FybmVyIExvc2ggcG9pbnRlZCBvdXQpLg0KDQpCZXN0IHJlZ2FyZHMsDQpIb2xnZXINCg0KPiBN aXJvc2xhdiBMYWNobWFuDQo+IA0KPiANCj4+IEFtIDIwLjA2LjIwMTggdW0gMTY6NTUgc2Nocmll YiBNaXJvc2xhdiBMYWNobWFuIDwwMDAuZmJzZEBxdWlwLmN6PG1haWx0bzowMDAuZmJzZEBxdWlw LmN6Pj46DQo+PiBJIHdvdWxkIGxpa2UgdG8ga25vdyBob3cgdGhlIHZhbHVlIG9mIGRpc2sgImJ1 c3kiIGlzIGNhbGN1bGF0ZWQ/DQo+PiBJIHdhbnQgdG8gdXNlIHZhbHVlcyBmcm9tIGlvc3RhdCBp biB0aGUgbW9uaXRvcmluZyAoemFiYml4KS4NCj4+IGlvc3RhdCBzaG93cyBhdmVyYWdlcyBieSBk ZWZhdWx0IGFuZCB0aGUgbGFzdCBjb2x1bW4gaXMgImJ1c3kgJSIsIGJ1dCB0aGUgZmlyc3Qgb3V0 cHV0IGNvbnRhaW5zIGF2ZXJhZ2VzIGZyb20gdGhlIHN5c3RlbSBib290IHRpbCBub3cuDQo+PiAj IGlvc3RhdCAteCAtdCBkYQ0KPj4gICAgICAgICAgICAgICAgICAgICAgICBleHRlbmRlZCBkZXZp Y2Ugc3RhdGlzdGljcw0KPj4gZGV2aWNlICAgICByL3MgICB3L3MgICAga3IvcyAgICBrdy9zIHFs ZW4gc3ZjX3QgICViDQo+PiBhZGEwICAgICAgIDIuNSAgMTMuOCAgICA0OS4wICAgMjg3LjkgICAg MCAgNDUuNyAgIDINCj4+IGFkYTEgICAgICAgMi42ICAxMy44ICAgIDUxLjcgICAyODcuOSAgICAw ICAzOS42ICAgMg0KPj4gSSBkb24ndCB3YW50IHRvIHVzZSAiaW9zdGF0IC14IC10IGRhIC13IDIw IiB0byBnZXQgYXZlcmFnZXMgb2YgdGhlIGxhc3QgMjAgc2Vjb25kcyBiZWNhdXNlIGl0IG1lYW5z IG1vbml0b3JpbmcgbmVlZHMgdG8gd2FpdCAyMCBzZWNvbmRzIG9uIGVhY2ggcnVuLg0KPj4gSSBj YW4gdXNlIGFic29sdXRlIHZhbHVlcyBmcm9tIGlvc3RhdC4gVGhpcyBvdXRwdXQgaXMgd2l0aG91 dCBhbnkgZGVsYXkgYW5kIHRoZSBtb25pdG9yaW5nIFNXIGNhbiBjYWxjdWxhdGUgYXZlcmFnZXMg YmV0d2VlbiB0d28gcnVucy4gQnV0IHRoZSBsYXN0IGNvbHVtbiBpcyBubyBidXN5ICUsIGl0IGlz IHNiL2kuDQo+PiAjIGlvc3RhdCAtSSAteCAtdCBkYQ0KPj4gICAgICAgICAgICAgICAgICAgICAg ICBleHRlbmRlZCBkZXZpY2Ugc3RhdGlzdGljcw0KPj4gZGV2aWNlICAgICAgICAgICByL2kgICAg ICAgICB3L2kgICAgICAgICBrci9pICAgICAgICAga3cvaSBxbGVuIHRzdmNfdC9pICAgICAgc2Iv aQ0KPj4gYWRhMCAgICAgICA3NDAzMjE4LjAgIDQwODI1NzQ5LjAgIDE0NDY0NzgyNC4wICA4NDk2 NTU2OTQuMCAgICAwIDIyMDQ5MDQuMiAgIDczMTIxLjgNCj4+IGFkYTEgICAgICAgNzUzNzQyMy4w ICA0MDgyNTc0OS4wICAxNTI2NDM4NzQuNSAgODQ5NjU1Njk0LjAgICAgMCAxOTE0MzAxLjAgICA2 OTk5Ni41DQo+PiBTbyB0aGUgcXVlc3Rpb24gaXMgLSBJZiBJIHdhbnQgdG8gcGxvdCAiYnVzeSAl IiBpbiB0aGUgZ3JhcGggLSBob3cgdGhlICJidXN5IiB2YWx1ZSBpbiB0aGUgZmlyc3QgZXhhbXBs ZSBpcyBjYWxjdWxhdGVkPw0KPj4gSXMgaXQgcG9zc2libGUgdG8gY2FsY3VsYXRlIGl0IGZyb20g dGhlIG51bWJlcnMgdGhhdCBJIGhhdmUgZnJvbSAiaW9zdGF0IC1JIC14IiBhbmQgdGhlIGtub3cg dGltZSBpbnRlcnZhbCBiZXR3ZWVuIHR3byBydW5zPw0KPiANCj4gDQoNCg== From owner-freebsd-stable@freebsd.org Thu Jun 21 16:15:10 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 308871022CDE for ; Thu, 21 Jun 2018 16:15:10 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A823283327 for ; Thu, 21 Jun 2018 16:15:08 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-wm0-x234.google.com with SMTP id j15-v6so7274579wme.0 for ; Thu, 21 Jun 2018 09:15:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FvDtS2NTWrI7csBMnl5zkAxGUQi5RvesUdM+uz/6LpA=; b=QiN8oXcb5O6QVQICj4YfFdOGfy0Z5BE3AYV7KE2oknSPvfCsetTpzD9hOwhgOCq8+h rPO01jVxBn6bb1kOTclPtcK7CuuBtF/+RXw6aRBKjHCPJLSkyNwqqAkL6eGPgSqVkUGp 3C3h1NJ+RElYY1sVQGKfwffTWbD01JlQNM8zPeHqxkXogY9qIY4KW/mARlOZWna6jvui KXaMeqKEOKdMfypLdATKQE6/zcxA8NQbVROZW4xxUBmtosP/0sNUf2RLGXjKiw4KPI4J AbbCXYDsDZr9lrLfF3GFLXqOCuTmqj+T8XMiHAqoZNsRQivQoondjDkbA8AhW3dup+QA 5Csw== 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=FvDtS2NTWrI7csBMnl5zkAxGUQi5RvesUdM+uz/6LpA=; b=dpAXtdJca2aI+46yia6bmgP6Y6zd1htPKoJNn74UJGTd9Mj52F5a4PQP55xqXZjcZG OQW28u8UwxC/fuuUDioHpJM1j0LmZj2pY9xBkwOkUQGjxtZyVAXe2YxD6kURD5UDA18K Xx2te7rRXWJfY4oDlTvmLc9wUN4Uh96Sn5ynLsNUjetswgQ210pPawom/BsDcN58+DmL cCELgP7vwghN2x/f1tv0V5bM0oj4zQuDEW8wZIPOM+83ZYA9wXrT6TM5stUR7F1uLpBC JELfjTBcjUc7ER+JldPwwviY6bI6cavONgOrLMSl77Rl4ClLDozPQc5OsBraRyzYc+KM ZCLA== X-Gm-Message-State: APt69E2m23ZCWcZt4WeR9MXbJSmXCsQ2UXktvugFnbA2j+Phb8YptPRH U+mpaxk9qCk1xKjucsS01jHd9GMceIULhafBSf6ybw== X-Google-Smtp-Source: ADUXVKIiZ7kcln3p1AUNoa0MvcqLwRu7wk2WewfkQS9T4glUBatI44/2XE6Y+3XfAccOwQUv88706eQRqTLFB2dScE0= X-Received: by 2002:a50:863d:: with SMTP id o58-v6mr22403310edo.243.1529597707809; Thu, 21 Jun 2018 09:15:07 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:8e0d:0:0:0:0:0 with HTTP; Thu, 21 Jun 2018 09:14:37 -0700 (PDT) In-Reply-To: References: From: Ed Schouten Date: Thu, 21 Jun 2018 18:14:37 +0200 Message-ID: Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 To: Michael Grimm Cc: "ed@FreeBSD.org" , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 21 Jun 2018 16:15:10 -0000 2018-06-18 8:02 GMT+02:00 Ed Schouten : > I've just committed the patch (r335314) and > will MFC it to 11-STABLE before the end of the week. Done, in r335492. Thanks again for reporting this issue! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands From owner-freebsd-stable@freebsd.org Fri Jun 22 01:58:02 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27036100A19C for ; Fri, 22 Jun 2018 01:58:02 +0000 (UTC) (envelope-from vince@hightek.org) Received: from mail.ngtek.org (ngtek.org [IPv6:2001:19f0:6400:8963:5400:ff:fe09:9585]) (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 BEC3579211 for ; Fri, 22 Jun 2018 01:58:01 +0000 (UTC) (envelope-from vince@hightek.org) Received: from ip68-227-103-24.ok.ok.cox.net ([68.227.103.24] helo=hightek.org) by mail.ngtek.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fWBKp-000IMo-TV; Thu, 21 Jun 2018 20:57:59 -0500 Received: from localhost ([127.0.0.1] helo=quark.hightek.org) by hightek.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fWBKn-000E70-Vn; Thu, 21 Jun 2018 20:57:58 -0500 Received: (from vince@localhost) by quark.hightek.org (8.15.2/8.15.2/Submit) id w5M1vvOY054248; Thu, 21 Jun 2018 20:57:57 -0500 (CDT) (envelope-from vince) Date: Thu, 21 Jun 2018 20:57:57 -0500 From: Vincent Stemen To: Mark Saad Cc: FreeBSD-Stable ML Subject: Re: ATI video problem - slow desktop - 100% cpu load [semi-solved] Message-ID: <20180622015757.GA52468@quark.hightek.org> References: <20180619212311.GA36401@quark.hightek.org> <20180620194347.GA87224@quark.hightek.org> 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-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 01:58:02 -0000 On Wed, Jun 20, 2018 at 05:13:17PM -0400, Mark Saad wrote: > Vincent > I am running 11.2-PRERELEASE with a Cedar PRO [Radeon HD 5450/6350] > and I dont have any issues like that > > here is what I do to get it working for me; and I have used more or > less the same setup since 10.3-RELEASE > > In my loader.conf I have > > radeonkms_load="YES" > radeonkmsfw_CEDAR_pfp_load="YES" > radeonkmsfw_CEDAR_rlc_load="YES" > radeonkmsfw_CEDAR_me_load="YES" > > I use a static xorg.conf as well In there I have the following bits > > > Also if the redeon driver is not working for you try scfb . It works > better the vesa it some cases Thank you very much Mark! The scfb driver works! I didn't know what the scfb driver was for or that it will use the radeon kernel modules. This seems to confirm that the problem lies in the radeon X server driver that's in the xf86-video-ati package. I tagged this as semi-solved in the subject because it solves our immediate problem and gets us working, but it seems to be a work around to fixing the ati driver problem. Unless FreeBSD is going in the direction of using the scfb driver and not needing the ati driver at all, but I have found no documentation indicating this. The man page for scfb says it is a non-accelerated driver. So far as I can tell, that is not necessarily the case. It is using the radeon kernel modules and I seem to have full desktop features, resolution, and performance, including transparencies. I even tested moving windows around that are playing high def videos. I am curious how you discovered the use of this driver for ATI cards since I have not found docs that say anything about it. BTW, I did test with all three ATI Radeon card models that I mentioned, and it works fine with all of them. Anyway, there are some caveats to getting it working. Since I spent the last few days working on this issue, I am posting my notes below to help others who might be experiencing the same issue. Solution to getting ATI Radeon graphics cards working ===================================================== Use the "scfb" driver from the xf86-video-scfb package rather than the "radeon" driver from the xf86-video-ati package. /etc/X11/xorg.conf Section "Device" ... Driver "scfb" ... EndSection This driver also requires the radeon kernel modules to be loaded, but does not automatically load them like the radeon driver does. I tried loading them in /boot/loader.conf, /boot/loader.conf radeonkms_load = yes radeonkmsfw_RS780_pfp_load = yes radeonkmsfw_RS780_me_load = yes radeonkmsfw_R600_rlc = yes This did not work. The radeonkmsfw_R600_rlc.ko module does not get loaded and the console does not get initialized. Apparently it has something to do with loader loading the modules first, when the kernel is not running yet to have detected the PCIe devices. Even if you manually load radeonkmsfw_R600_rlc after booting, using kldload, it still does not initialize the console. You must load radeonkms.ko after the system is fully booted. # kldload radeonkms That automatically loads the other 3 modules and initializes the console where the console text goes into higher resolution mode. Then X and the desktop environments work and seem to be fully functional, including transparency, etc. So I can either put it in /etc/rc.local, to be run at boot time, or put it in an X startup script wrapper. Note that it must be run prior to startx because it must be loaded before launching the X server. So it cannot be put in ~/.xinitrc. From owner-freebsd-stable@freebsd.org Fri Jun 22 03:41:34 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99B1E100C373 for ; Fri, 22 Jun 2018 03:41:34 +0000 (UTC) (envelope-from carlj@peak.org) Received: from filter01.peak.org (filter01.peak.org [207.55.16.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.peak.org", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C60A7C110 for ; Fri, 22 Jun 2018 03:41:33 +0000 (UTC) (envelope-from carlj@peak.org) Received: from zmail-mta02.peak.org ([207.55.16.112]) by filter01.peak.org ({e1c81c21-e4c4-4528-aa90-7a27869c545a}) via TCP (outbound) with ESMTPS id 20180622034124514_0000 for ; Thu, 21 Jun 2018 20:41:24 -0700 X-RC-FROM: X-RC-RCPT: Received: from zmail-mta02.peak.org (localhost [127.0.0.1]) by zmail-mta02.peak.org (Postfix) with ESMTPS id B39154DE14 for ; Thu, 21 Jun 2018 20:41:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zmail-mta02.peak.org (Postfix) with ESMTP id 91D204DE46 for ; Thu, 21 Jun 2018 20:41:23 -0700 (PDT) Received: from zmail-mta02.peak.org ([127.0.0.1]) by localhost (zmail-mta02.peak.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id RvALpJjnvgpa for ; Thu, 21 Jun 2018 20:41:23 -0700 (PDT) Received: from mailproxy-lb-06.peak.org (mailproxy-lb-06.peak.org [207.55.17.96]) by zmail-mta02.peak.org (Postfix) with ESMTP id 598CA4DE14 for ; Thu, 21 Jun 2018 20:41:23 -0700 (PDT) Received: from carlj by elm.localnet with local (Exim 4.90_1 (FreeBSD)) (envelope-from ) id 1fWCwr-000EoG-Sj for freebsd-stable@freebsd.org; Thu, 21 Jun 2018 20:41:21 -0700 From: Carl Johnson To: freebsd-stable@freebsd.org Subject: Re: ATI video problem - slow desktop - 100% cpu load [semi-solved] References: <20180619212311.GA36401@quark.hightek.org> <20180620194347.GA87224@quark.hightek.org> <20180622015757.GA52468@quark.hightek.org> X-Clacks-Overhead: GNU Terry Pratchett Date: Thu, 21 Jun 2018 20:41:21 -0700 In-Reply-To: <20180622015757.GA52468@quark.hightek.org> (Vincent Stemen's message of "Thu, 21 Jun 2018 20:57:57 -0500") Message-ID: <86zhznbi8u.fsf@elm.localnet> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-MAG-OUTBOUND: peakinternet.redcondor.net@207.55.16/22 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 03:41:34 -0000 Vincent Stemen writes: > You must load radeonkms.ko after the system is fully booted. > > # kldload radeonkms > > That automatically loads the other 3 modules and initializes the console where > the console text goes into higher resolution mode. Then X and the desktop > environments work and seem to be fully functional, including transparency, etc. > > So I can either put it in /etc/rc.local, to be run at boot time, or put it in > an X startup script wrapper. Note that it must be run prior to startx because > it must be loaded before launching the X server. So it cannot be put in > ~/.xinitrc. Have you tried loading it with kld_list in /etc/rc.conf? Those get loaded during boot, but it might be late enough to work. That would be automated, so it might be a little more convenient. -- Carl Johnson carlj@peak.org From owner-freebsd-stable@freebsd.org Fri Jun 22 08:07:36 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F15810125A4 for ; Fri, 22 Jun 2018 08:07:36 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id A61A583A4E for ; Fri, 22 Jun 2018 08:07:34 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 027D01806C; Fri, 22 Jun 2018 17:07:26 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id BE6D5107C4; Fri, 22 Jun 2018 17:07:25 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 9DFF1107C3; Fri, 22 Jun 2018 17:07:25 +0900 (JST) Date: Fri, 22 Jun 2018 17:07:20 +0900 (JST) Message-Id: <20180622.170720.1809136341323718366.yasu@utahime.org> To: freebsd-stable@FreeBSD.org Subject: Console is broken after updating to 11.2-RELEASE From: Yasuhiro KIMURA X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 08:07:36 -0000 Hello. With the commit of r335510 releng/11.2 switched to -RELEASE. So I updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. But when I rebooted I found OS boot messages are not displayed on console while OS itself has booted successfully. To be exact, 1. BIOS message are displayed. 2. Boot menu of FreeBSD is displayed. 3. Kernel boot starts but after 'Booting...' no following messages are displayed. 4. After OS has booted console stays unusable. Kernel configuration is as follwing. ---------------------------------------------------------------------- yasu@maybe[2006]% uname -a ~ FreeBSD maybe.home.utahime.org 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335513: Fri Jun 22 16:12:12 JST 2018 rootz@maybe.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/releng/11.2/sys/MAYBE amd64 yasu@maybe[2007]% cat /usr/src/sys/amd64/conf/MAYBE ~ # # MAYBE -- Local kernel configuration file of maybe for FreeBSD/amd64 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD$ include GENERIC ident MAYBE # ZFS support options ZFS # PF support device pf #PF OpenBSD packet-filter firewall device pflog #logging support interface for PF # # Temperature sensors: # # coretemp: on-die sensor on Intel Core and newer CPUs # device coretemp yasu@maybe[2008]% ---------------------------------------------------------------------- I tried GENERIC kernel but the problem still happened. HWs are, M/B: ASUS N3150I-C (https://www.asus.com/us/Motherboards/N3150IC/) Display: EIZO FlexScan L565 (http://www.eizoglobal.com/support/db/products/model/L565) M/B and display are connected with analog VGA. Does anyone experiences same problem? Are there any solution or workaound? Best Regards. --- Yasuhiro KIMURA From owner-freebsd-stable@freebsd.org Fri Jun 22 08:50:44 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D15A81013133 for ; Fri, 22 Jun 2018 08:50:43 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 433CD84F7F for ; Fri, 22 Jun 2018 08:50:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback16j.mail.yandex.net (mxback16j.mail.yandex.net [IPv6:2a02:6b8:0:1619::92]) by forward100j.mail.yandex.net (Yandex) with ESMTP id 6A4A95D84A8A; Fri, 22 Jun 2018 11:50:27 +0300 (MSK) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [2a02:6b8:0:1402::15:6]) by mxback16j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id P06YLQMZBu-oQ3eVEWt; Fri, 22 Jun 2018 11:50:27 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1529657427; bh=h/4sGsP1kpOYDRMJ+8Qj8uKmIhned5v6fNI1ViJfs7Y=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=elPjQeKBeOjgX03RCGyJZwqvt1Qxc+HZY7lrwyJN+f61DHq1ju5AlYOJc3bC0K6BQ 6hYIXaBHwhldddEcbXiwZmocz/9MLpsg+bpl9lelse0V5QPnYfXpt6xN7R6X6NmzOn WhZjAzzuyRURwwONqfw431u0QPhAEtYK7H6Hg/jQ= Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ANBSMjzwqt-oQvO96bH; Fri, 22 Jun 2018 11:50:26 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1529657426; bh=h/4sGsP1kpOYDRMJ+8Qj8uKmIhned5v6fNI1ViJfs7Y=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=Xu4vjkIGnTO+z81HwiY7nVTkCCU0CaBOxFtelEXxhm1xy6ETdmoA0iJn1ZV+4nRxx wRUP4NdsddZSEpRdmDREgnAUsWSbGkcccJRP69aEDd6EbzAZT6REm1BYD+B1an3BXW Itv8wbo4u3i58aRh8pu6wqvZHKTDa+VbmpbPHh9k= Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: Console is broken after updating to 11.2-RELEASE To: Yasuhiro KIMURA , freebsd-stable@FreeBSD.org References: <20180622.170720.1809136341323718366.yasu@utahime.org> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Autocrypt: addr=bu7cher@yandex.ru; prefer-encrypt=mutual; keydata= xsBNBEwBF1kBCADB9sXFhBEUy8qQ4X63Y8eBatYMHGEFWN9ypS5lI3RE6qQW2EYbxNk7qUC5 21YIIS1mMFVBEfvR7J9uc7yaYgFCEb6Sce1RSO4ULN2mRKGHP3/Sl0ijZEjWHV91hY1YTHEF ZW/0GYinDf56sYpDDehaBF5wkWIo1+QK5nmj3vl0DIDCMNd7QEiWpyLVwECgLX2eOAXByT8B bCqVhJGcG6iFP7/B9Ll6uX5gb8thM9LM+ibwErDBVDGiOgvfxqidab7fdkh893IBCXa82H9N CNwnEtcgzh+BSKK5BgvPohFMgRwjti37TSxwLu63QejRGbZWSz3OK3jMOoF63tCgn7FvABEB AAHNIkFuZHJleSBWLiBFbHN1a292IDxhZUBmcmVlYnNkLm9yZz7CwHsEEwECACUCGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheABQJMB/ruAhkBAAoJEAHF6gQQyKF6MLwH/3Ri/TZl9uo0 SepYWXOnxL6EaDVXDA+dLb1eLKC4PRBBjX29ttQ0KaWapiE6y5/AfzOPmRtHLrHYHjd/aiHX GMLHcYRXD+5GvdkK8iMALrZ28X0JXyuuZa8rAxWIWmCbYHNSBy2unqWgTI04Erodk90IALgM 9JeHN9sFqTM6zalrMnTzlcmel4kcjT3lyYw3vOKgoYLtsLhKZSbJoVVVlvRlGBpHFJI5AoYJ SyfXoN0rcX6k9X7Isp2K50YjqxV4v78xluh1puhwZyC0p8IShPrmrp9Oy9JkMX90o6UAXdGU KfdExJuGJfUZOFBTtNIMNIAKfMTjhpRhxONIr0emxxDOwE0ETAEXWQEIAJ2p6l9LBoqdH/0J PEFDY2t2gTvAuzz+8zs3R03dFuHcNbOwjvWCG0aOmVpAzkRa8egn5JB4sZaFUtKPYJEQ1Iu+ LUBwgvtXf4vWpzC67zs2dDuiW4LamH5p6xkTD61aHR7mCB3bg2TUjrDWn2Jt44cvoYxj3dz4 S49U1rc9ZPgD5axCNv45j72tggWlZvpefThP7xT1OlNTUqye2gAwQravXpZkl5JG4eOqJVIU X316iE3qso0iXRUtO7OseBf0PiVmk+wCahdreHOeOxK5jMhYkPKVn7z1sZiB7W2H2TojbmcK HZC22sz7Z/H36Lhg1+/RCnGzdEcjGc8oFHXHCxUAEQEAAcLAXwQYAQIACQUCTAEXWQIbDAAK CRABxeoEEMihegkYCAC3ivGYNe2taNm/4Nx5GPdzuaAJGKWksV+w9mo7dQvU+NmI2az5w8vw 98OmX7G0OV9snxMW+6cyNqBrVFTu33VVNzz9pnqNCHxGvj5dL5ltP160JV2zw2bUwJBYsgYQ WfyJJIM7l3gv5ZS3DGqaGIm9gOK1ANxfrR5PgPzvI9VxDhlr2juEVMZYAqPLEJe+SSxbwLoz BcFCNdDAyXcaAzXsx/E02YWm1hIWNRxanAe7Vlg7OL+gvLpdtrYCMg28PNqKNyrQ87LQ49O9 50IIZDOtNFeR0FGucjcLPdS9PiEqCoH7/waJxWp6ydJ+g4OYRBYNM0EmMgy1N85JJrV1mi5i Message-ID: <1e6913a0-c5e7-5d7b-9b6b-d2c8dfe03efa@yandex.ru> Date: Fri, 22 Jun 2018 11:47:24 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180622.170720.1809136341323718366.yasu@utahime.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nOpSAV2b6xpKGBpTFbz7uf3q8FzJoi9uu" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 08:50:44 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --nOpSAV2b6xpKGBpTFbz7uf3q8FzJoi9uu Content-Type: multipart/mixed; boundary="XHuzYY4qZZJEYncyKUClI56Yfjii8IIYQ"; protected-headers="v1" From: "Andrey V. Elsukov" To: Yasuhiro KIMURA , freebsd-stable@FreeBSD.org Message-ID: <1e6913a0-c5e7-5d7b-9b6b-d2c8dfe03efa@yandex.ru> Subject: Re: Console is broken after updating to 11.2-RELEASE References: <20180622.170720.1809136341323718366.yasu@utahime.org> In-Reply-To: <20180622.170720.1809136341323718366.yasu@utahime.org> --XHuzYY4qZZJEYncyKUClI56Yfjii8IIYQ Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 22.06.2018 11:07, Yasuhiro KIMURA wrote: > Hello. >=20 > With the commit of r335510 releng/11.2 switched to -RELEASE. So I > updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. >=20 > But when I rebooted I found OS boot messages are not displayed on > console while OS itself has booted successfully. To be exact, >=20 > 1. BIOS message are displayed. > 2. Boot menu of FreeBSD is displayed. > 3. Kernel boot starts but after 'Booting...' no following messages > are displayed. > 4. After OS has booted console stays unusable. Do you have some tweaks for serial console in your loader.conf? --=20 WBR, Andrey V. Elsukov --XHuzYY4qZZJEYncyKUClI56Yfjii8IIYQ-- --nOpSAV2b6xpKGBpTFbz7uf3q8FzJoi9uu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlsst6AACgkQAcXqBBDI oXqTMwgAlACFJse1QWmXx0bij9oXp5cSRsSnK5tmrB2ENwh3I11xkeRkiRU++/W6 TqgYeK1be1OQ/lq/X968tobd66a1PWgq89drfOoY3K2Mfnlswxm42vkXmKsCr4iz DVNmuMus3A9tRFCk8DG1DvqWvn9E6wxpPzJqKtWItt3FbRVHq0irMzn06WIsfi6J 6mnG9XnwrNDsTfrolAwbQnFgc1xJERcfDGnRB0ePaDZBqLkE+iEXW+6q0esOoMAD wG8FwescbBxY5KqOCsfA8rvGDmoJgiJ9lDiZsVLzOPhDrvUUn/LBFiU2kHz5558l R5j7XNlQxBZ9C2Wzh4qdyQ45A9ymbw== =Z6eh -----END PGP SIGNATURE----- --nOpSAV2b6xpKGBpTFbz7uf3q8FzJoi9uu-- From owner-freebsd-stable@freebsd.org Fri Jun 22 09:02:15 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 294521013A26 for ; Fri, 22 Jun 2018 09:02:15 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id A3E02858A4 for ; Fri, 22 Jun 2018 09:02:14 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 8B72318086; Fri, 22 Jun 2018 18:02:12 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 16D5D1610C; Fri, 22 Jun 2018 18:02:12 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id D55FC1610B; Fri, 22 Jun 2018 18:02:11 +0900 (JST) Date: Fri, 22 Jun 2018 18:02:02 +0900 (JST) Message-Id: <20180622.180202.1191714635067561401.yasu@utahime.org> To: freebsd-stable@FreeBSD.org Subject: Re: Console is broken after updating to 11.2-RELEASE,Re: Console is broken after updating to 11.2-RELEASE From: Yasuhiro KIMURA In-Reply-To: <1e6913a0-c5e7-5d7b-9b6b-d2c8dfe03efa@yandex.ru> References: <20180622.170720.1809136341323718366.yasu@utahime.org> <20180622.170720.1809136341323718366.yasu@utahime.org> <1e6913a0-c5e7-5d7b-9b6b-d2c8dfe03efa@yandex.ru> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 09:02:15 -0000 From: "Andrey V. Elsukov" Subject: Re: Console is broken after updating to 11.2-RELEASE,Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 11:47:24 +0300 > Do you have some tweaks for serial console in your loader.conf? No. I don't use serial console at all. Folloging is loader.conf of my home server in question. yasu@maybe[2019]% cat /boot/loader.conf kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0" #zfs_load="YES" yasu@maybe[2020]% --- Yasuhiro KIMURA From owner-freebsd-stable@freebsd.org Fri Jun 22 10:42:58 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98D251016B3A for ; Fri, 22 Jun 2018 10:42:58 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 1F2788AC3D for ; Fri, 22 Jun 2018 10:42:57 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id E0BEE180C2; Fri, 22 Jun 2018 19:42:54 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id AAD661625F; Fri, 22 Jun 2018 19:42:54 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 8A17E1625E; Fri, 22 Jun 2018 19:42:54 +0900 (JST) Date: Fri, 22 Jun 2018 19:42:36 +0900 (JST) Message-Id: <20180622.194236.1452402689514462600.yasu@utahime.org> To: freebsd-stable@FreeBSD.org Subject: Re: Console is broken after updating to 11.2-RELEASE From: Yasuhiro KIMURA In-Reply-To: <20180622.170720.1809136341323718366.yasu@utahime.org> References: <20180622.170720.1809136341323718366.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 10:42:58 -0000 From: Yasuhiro KIMURA Subject: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 17:07:20 +0900 (JST) > With the commit of r335510 releng/11.2 switched to -RELEASE. So I > updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. > > But when I rebooted I found OS boot messages are not displayed on > console while OS itself has booted successfully. To be exact, > > 1. BIOS message are displayed. > 2. Boot menu of FreeBSD is displayed. > 3. Kernel boot starts but after 'Booting...' no following messages > are displayed. > 4. After OS has booted console stays unusable. I have another 11.1-RELEASE-p11 amd64 environment working as guest of VirtualBox whose host is 64bit Windows 10. So I updated it to 11.2-RELEASE like my home server in question. But in this case console worked fine just as it was 11.1-RELEASE-p11. So the problem seems to be hardwear dependent. --- Yasuhiro KIMURA From owner-freebsd-stable@freebsd.org Fri Jun 22 10:44:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B752F1016BEE for ; Fri, 22 Jun 2018 10:44:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 5F78C8AD0A for ; Fri, 22 Jun 2018 10:44:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 4279322355; Fri, 22 Jun 2018 06:44:31 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 22 Jun 2018 06:44:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=eYpimuUX4nFFiR8uRAFnIYaMaHE6g n9L41vQP4aRSs0=; b=bL8jamf+e/LDoyi529/W4HPB5wPfpWkAvAD3AQnV6aHue bY4eekC9Pru/fHlZ6hyWHVG5H3bvBGCOjMNCgp/QqpB6gAz9IwhBqFScTu4NJhK7 Y2TDax7otjREoMKT4DgjEH3nS7V9YpNwM24lHR2BruvIAGD7Pj7rjcWnOMnQDEZJ wEhPAz57HH+t+xAlzHjEWMtIY1EE4vc9m41FihhH37O5N+GuqRtOrJt/Jd32yE+6 FGyZTNjLbE1V5TemzM3uWSrI/q/bMi9RJKjWOhjVkTuj4HZObyD33GHOWKQql/aJ jjtSJwn1o1+e0cktz9PHl4XBVo2CGBKdvnhQUEJhw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=eYpimu UX4nFFiR8uRAFnIYaMaHE6gn9L41vQP4aRSs0=; b=BoyrgOt/ayLBB8dsS6QQzq lGp5+CDAJfzX1FU+b/vS0TkzNWdfhhm0n/9/AcmNezxpalx8SP2M6SIIrDg402Hd +kyCwzvuM1DFgxg4e00m7WUKKIWkMlSz8OqIxa9Lkak71lHS55dzQ778p4+WsgTp SYdaAKPHZ6hFdiEh+AZWK5+TDB0STQmu5PbnB/ThLniQ7uaQATXsAikBYOCNr+8e YPN9KBvdSZfiuc3WRMOl/9C61Uz4Dao+dhvGmtBW0+cyK7X3n/u7fENnP79igA0x mvDrTDrFPs3zYL/N3a+VsqdvmYlzQdqme/DNQfNKJ1WQ1wE/lRFJqK43dlgewdIQ == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 8414F10387; Fri, 22 Jun 2018 06:44:30 -0400 (EDT) From: tech-lists Subject: Re: Console is broken after updating to 11.2-RELEASE To: Yasuhiro KIMURA , freebsd-stable@FreeBSD.org References: <20180622.170720.1809136341323718366.yasu@utahime.org> Organization: none Message-ID: Date: Fri, 22 Jun 2018 11:44:29 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180622.170720.1809136341323718366.yasu@utahime.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 10:44:38 -0000 Hi, On 22/06/2018 09:07, Yasuhiro KIMURA wrote: > 1. BIOS message are displayed. > 2. Boot menu of FreeBSD is displayed. > 3. Kernel boot starts but after 'Booting...' no following messages > are displayed. > 4. After OS has booted console stays unusable. I've seen this effect elsewhere. Not exactly the same, but it's been happening with me on some systems since 11.1. The context I see it is when spinning up a bhyve instance in screen. I see a bit more than just booting, something like "unreferenced ps/2 interrupt" after "Booting...". The bhyve instance itself is fully functional. Logging into the bhyve instance through ssh I can see its dmesg and it all looks OK. However, if in syslogd.conf I enable console logging via console.log and reboot, *nothing gets written to it*. Have had this issue for about a year now, not been able to fix it. Frustratingly, it doesn't happen with all VMs. I've not seen it happen with a 12-current VM, just 11-stable. And even then, not *all* 11-stable VMs. -- J. From owner-freebsd-stable@freebsd.org Fri Jun 22 11:03:56 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 948B91017486 for ; Fri, 22 Jun 2018 11:03:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::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 2232D8BBB4 for ; Fri, 22 Jun 2018 11:03:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x233.google.com with SMTP id k16-v6so3009057ioa.8 for ; Fri, 22 Jun 2018 04:03:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RhhskBtoXNnOO+mNlg8GwZSp0JDBam0IXS/qj/3YBN8=; b=nAhxKfCOu6z1AJFLkeSfbLydTb3XWCKOcc4BjDHPZ3FATeazucmCPn5dpXSzKCLR/g hrotcK17JQZHUy0UG5CXRdLTK48Rx9a3/s9BzVba1rk33MqwzWcKXqnf90EAvZlItmGs 1C8N1XXtCu6qgRZcgAyd90WHFMLDB+8SUn+EpB3fEZt/Puxc3DEdCD3MXxi3sKNhO3Xq /qAoA5bSOkRxakr7CDRpDW73erYB8Xig7AEvXLxTNstQnVGgIo7H8KzfG+9ot0fBz4lY Gj1eDsO90JjpG46G7iP1vnyHGoJ0AIt1/MvM2QpKosXI3ZzwHgEpI6MB2Bcn3EzrD0vu hFnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RhhskBtoXNnOO+mNlg8GwZSp0JDBam0IXS/qj/3YBN8=; b=sq8VFekJ1Eilvb7GxOFGLliuDmK48/wjDNkF6F9+KpsEXJebFok618nYTufLzEVmz9 I+G9vu8GX6QkBgx2Qpq7qg7CKYJtqml6d/FmYln2K6VpWA+Im55++g225EbyygUPnl0T qtyzf/ZYWVVL7TFzmSFUDRp7Fzh0RCZ4C+nE2YgBqVNAd6d4K5jc2fqn8zJ8d/oWixi9 wSsnsrWNHNHn7N4m7GBbhCF2plMQudxRZYC2VtuhHiPAoga7tuOvURvRTDzdSdYf6xp3 jrX24QwO0YQUctwZkMfOwNOSysNmQsMf9EFzdW9LPY+hC6ZsrWJgsiM9H7+gvRNJjE0A C3Vw== X-Gm-Message-State: APt69E3SI90IotWZM7MNc8P4rgccw9+oY7pZn2WD4NbfRBI4bO/OL7hQ LwzD6OmtQLlMXoK42a5m8rJeUF/xdOZlN+PLi0PY8w== X-Google-Smtp-Source: ADUXVKJMJxFgQvYqfQH3UhRNJHrevAQSkj6F9Twq7ubov3Vn70b/4CrX09uTL+RyUDfny9GZDA3WsL5zbZjtZzmNYAw= X-Received: by 2002:a6b:284b:: with SMTP id o72-v6mr861376ioo.168.1529665435442; Fri, 22 Jun 2018 04:03:55 -0700 (PDT) MIME-Version: 1.0 References: <20180622.170720.1809136341323718366.yasu@utahime.org> In-Reply-To: <20180622.170720.1809136341323718366.yasu@utahime.org> From: Warner Losh Date: Fri, 22 Jun 2018 05:03:43 -0600 Message-ID: Subject: Re: Console is broken after updating to 11.2-RELEASE To: Yasuhiro KIMURA Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 11:03:56 -0000 UEFI or legacy boot? Is a BMC involved? Warner On Fri, Jun 22, 2018, 2:09 AM Yasuhiro KIMURA wrote: > Hello. > > With the commit of r335510 releng/11.2 switched to -RELEASE. So I > updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE. > > But when I rebooted I found OS boot messages are not displayed on > console while OS itself has booted successfully. To be exact, > > 1. BIOS message are displayed. > 2. Boot menu of FreeBSD is displayed. > 3. Kernel boot starts but after 'Booting...' no following messages > are displayed. > 4. After OS has booted console stays unusable. > > Kernel configuration is as follwing. > > ---------------------------------------------------------------------- > yasu@maybe[2006]% uname -a > ~ > FreeBSD maybe.home.utahime.org 11.2-RELEASE FreeBSD 11.2-RELEASE #0 > r335513: Fri Jun 22 16:12:12 JST 2018 rootz@maybe.home.utahime.org:/usr0/freebsd/base/obj/usr0/freebsd/base/releng/11.2/sys/MAYBE > amd64 > yasu@maybe[2007]% cat /usr/src/sys/amd64/conf/MAYBE > ~ > # > # MAYBE -- Local kernel configuration file of maybe for FreeBSD/amd64 > # > # For more information on this file, please read the config(5) manual page, > # and/or the handbook section on Kernel Configuration Files: > # > # > http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html > # > # The handbook is also available locally in /usr/share/doc/handbook > # if you've installed the doc distribution, otherwise always see the > # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the > # latest information. > # > # An exhaustive list of options and more detailed explanations of the > # device lines is also present in the ../../conf/NOTES and NOTES files. > # If you are in doubt as to the purpose or necessity of a line, check first > # in NOTES. > # > # $FreeBSD$ > > include GENERIC > > ident MAYBE > > # ZFS support > options ZFS > > # PF support > device pf #PF OpenBSD packet-filter firewall > device pflog #logging support interface for PF > > # > # Temperature sensors: > # > # coretemp: on-die sensor on Intel Core and newer CPUs > # > device coretemp > yasu@maybe[2008]% > ---------------------------------------------------------------------- > > I tried GENERIC kernel but the problem still happened. > > HWs are, > > M/B: ASUS N3150I-C > (https://www.asus.com/us/Motherboards/N3150IC/) > Display: EIZO FlexScan L565 > (http://www.eizoglobal.com/support/db/products/model/L565) > > M/B and display are connected with analog VGA. > > Does anyone experiences same problem? Are there any solution or > workaound? > > Best Regards. > > --- > Yasuhiro KIMURA > _______________________________________________ > 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 Jun 22 11:43:51 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 857E11018491 for ; Fri, 22 Jun 2018 11:43:51 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 049128CEF5 for ; Fri, 22 Jun 2018 11:43:50 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id DAB0818042; Fri, 22 Jun 2018 20:43:46 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 85104162B1; Fri, 22 Jun 2018 20:43:46 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 484B8162B0; Fri, 22 Jun 2018 20:43:46 +0900 (JST) Date: Fri, 22 Jun 2018 20:42:18 +0900 (JST) Message-Id: <20180622.204218.2024776012115160106.yasu@utahime.org> To: freebsd-stable@freebsd.org Subject: Re: Console is broken after updating to 11.2-RELEASE From: Yasuhiro KIMURA In-Reply-To: References: <20180622.170720.1809136341323718366.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 11:43:51 -0000 From: Warner Losh Subject: Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 05:03:43 -0600 > UEFI or legacy boot? Is a BMC involved? Legacy boot. And BMC is not involved. --- Yasuhiro KIMURA From owner-freebsd-stable@freebsd.org Fri Jun 22 11:43:51 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82C961018490 for ; Fri, 22 Jun 2018 11:43:51 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 049CC8CEF6 for ; Fri, 22 Jun 2018 11:43:50 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id F3DCC18043; Fri, 22 Jun 2018 20:43:46 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id CB1C7162B6; Fri, 22 Jun 2018 20:43:46 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id AB7ED162B5; Fri, 22 Jun 2018 20:43:46 +0900 (JST) Date: Fri, 22 Jun 2018 20:43:28 +0900 (JST) Message-Id: <20180622.204328.2245607503460205311.yasu@utahime.org> To: freebsd-stable@FreeBSD.org Subject: Re: Console is broken after updating to 11.2-RELEASE From: Yasuhiro KIMURA In-Reply-To: References: <20180622.170720.1809136341323718366.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 11:43:51 -0000 From: tech-lists Subject: Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 11:44:29 +0100 > I've seen this effect elsewhere. Not exactly the same, but it's been > happening with me on some systems since 11.1. The context I see it is > when spinning up a bhyve instance in screen. I see a bit more than > just booting, something like "unreferenced ps/2 interrupt" after > "Booting...". > > The bhyve instance itself is fully functional. Logging into the bhyve > instance through ssh I can see its dmesg and it all looks OK. However, > if in syslogd.conf I enable console logging via console.log and > reboot, *nothing gets written to it*. Thank you for information. I created /etc/syslog.d/console.log.conf as below and rebooted system. yasu@maybe[2012]% cat /etc/syslog.d/console.log.conf ~ # Log all writes to /dev/console to a separate file. !* console.* /var/log/console.log !* yasu@maybe[2013]% Then boot messages are written in /var/log/console.log yasu@maybe[2016]% LANG=C ls -l /var/log/console.log ~ -rw-r--r-- 1 root wheel 9568 Jun 22 20:29 /var/log/console.log yasu@maybe[2016]% So my case seems to be different from yours. --- Yasuhiro KIMURA From owner-freebsd-stable@freebsd.org Fri Jun 22 13:12:21 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E567101B27C; Fri, 22 Jun 2018 13:12:21 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:401:2100::5:8a0e]) (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 2B2FD8FC19; Fri, 22 Jun 2018 13:12:17 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f1b:7801:4570:b981:3c60:950f] (p200300E97F1B78014570B9813C60950F.dip0.t-ipconnect.de [IPv6:2003:e9:7f1b:7801:4570:b981:3c60:950f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 41BzVw2YDJzkH; Fri, 22 Jun 2018 15:12:08 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net From: Michael Grimm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Message-Id: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> Date: Fri, 22 Jun 2018 15:12:05 +0200 To: Mailing List FreeBSD Ports , FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.kaan-bock.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 13:12:21 -0000 Hi, this is 11.2-STABLE (r335532), and I am referring to the recent MFC of = syslogd modifications [1].=20 Because I cannot judge whether fail2ban lacks support for the renewed = syslogd or syslogd has an issue in receiving fail2ban messages I do = crosspost this mail to ports and stable. I do have fail2ban configured to report to SYSLOG: logtarget =3D SYSLOG syslogsocket =3D auto But now, after upgrading to the new syslogd fail2ban refuses to report = to syslogd; no single message gets recorded [2]. I did try to modify the syslogsocket setting to /var/run/log without = success. Pointing logtarget to a regular files tells me that fail2ban is = running as expected, it only lacks reporting to SYSLOG. #) Does anyone else has running py-fail2ban at >=3D r335059 and can = confirm my observations?=20 #) Any ideas how to debug this issue? Thank you in advance and regards, Michael [1] = https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?revisi= on=3D335059&view=3Dmarkup&sortby=3Dfile [2] both syslogd and fail2ban are running at the host, thus another = issue with syslogd fixed in=20 = https://svnweb.freebsd.org/base?view=3Drevision&sortby=3Dfile&revision=3D3= 35314 does not apply From owner-freebsd-stable@freebsd.org Fri Jun 22 13:13:47 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BF40101B34A for ; Fri, 22 Jun 2018 13:13:47 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9D9338FE92 for ; Fri, 22 Jun 2018 13:13:46 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w5MDDXZM044590; Fri, 22 Jun 2018 06:13:39 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: In-Reply-To: <20180622.204218.2024776012115160106.yasu@utahime.org> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Yasuhiro KIMURA" Subject: Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 06:13:39 -0700 Message-Id: <5412681415d73751e981585076fb4922@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 13:13:47 -0000 On Fri, 22 Jun 2018 20:42:18 +0900 (JST) "Yasuhiro KIMURA" said > From: Warner Losh > Subject: Re: Console is broken after updating to 11=2E2-RELEASE > Date: Fri, 22 Jun 2018 05:03:43 -0600 >=20 > > UEFI or legacy boot? Is a BMC involved? >=20 > Legacy boot=2E And BMC is not involved=2E Try adding the following to your loader=2Econf(5) file (/boot/loader=2Econf): # Load SysCons driver kern=2Evty=3Dsc # noisy boot boot_verbose=3D"YES" Hope this helps! --Chris >=20 > --- > Yasuhiro KIMURA > _______________________________________________ > freebsd-stable@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd=2Eorg" From owner-freebsd-stable@freebsd.org Fri Jun 22 15:38:03 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C3A8101EEC1 for ; Fri, 22 Jun 2018 15:38:03 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 B7FC7748D2 for ; Fri, 22 Jun 2018 15:38:02 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fWO8F-000KRo-0U; Fri, 22 Jun 2018 18:37:51 +0300 Date: Fri, 22 Jun 2018 18:37:50 +0300 From: Slawa Olhovchenkov To: Miroslav Lachman <000.fbsd@quip.cz> Cc: Warner Losh , FreeBSD-STABLE Mailing List Subject: Re: iostat busy value calculation Message-ID: <20180622153750.GA2488@zxy.spb.ru> References: <98c4156c-d2f0-f0c6-b859-9cea8ec29a42@quip.cz> <55731ed7-c9f5-1e39-9c09-b522e58b97a1@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55731ed7-c9f5-1e39-9c09-b522e58b97a1@quip.cz> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 15:38:03 -0000 On Wed, Jun 20, 2018 at 07:37:20PM +0200, Miroslav Lachman wrote: > > %busy comes from the devstat layer. It's defined as the percent of the > > time over the polling interval in which at least one transaction was > > awaiting completion by the lower layers. It's an imperfect measure of > > how busy the drives are (in ye-olden days, before tagged queuing and > > NCQ, it was OK because you had THE transaction pending and it was a good > > measure of how utilized things were. Now with concurrent I/O in flash > > devices, it's only an imperfect approximation). > > Yes, I am aware of this issue. This percentage is just "is it slightly > loaded or heavily loaded" indicator. for "heavily loaded" use average transaction time and average queue length From owner-freebsd-stable@freebsd.org Fri Jun 22 15:59:30 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38E7D101F9D8 for ; Fri, 22 Jun 2018 15:59:30 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC9567562F for ; Fri, 22 Jun 2018 15:59:29 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (zarychtam@localhost [127.0.0.1]) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPS id w5MFxNJB061498 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 22 Jun 2018 17:59:23 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1529683163; bh=aAwADTtQixt7Gx1leXxkyEeW4vmHQa1dDebNGnh/mzM=; h=Date:From:To:Subject:References:In-Reply-To; b=iosp8iJRdMGkbrxUTJ7Ajd45hzYc1eaZywB3PagOAEQLDVq5CXhtNHsTsQ2SmMtYV bTCQVAIG3zPm5vN9JUo/V+Syhs3Y2mS4FNNZ17SVFc1kOm2goWyHyQr0HboIlK0uoi ohi3BmYadYyWd7UEqduem9xuDMe0VN56eIC+u/b3DuektRbmdMwwPSIsrSwd/CHIKC Q7e+3KBqR1bTYJb3pELMMLJalQCwHAaMyyb1wiZsjv8Q9jWpEhxN3iI/p+cLUksIP3 uVoEW3dWYjEMOSXNJ3vZIJE2QMhhPgSOGHextWSwO1RxdNBdIRFswCT0U0TNrB8Pa/ BdM4ZQftEUT0g== Received: (from zarychtam@localhost) by plan-b.pwste.edu.pl (8.15.2/8.15.2/Submit) id w5MFxMp2061497 for freebsd-stable@freebsd.org; Fri, 22 Jun 2018 17:59:22 +0200 (CEST) (envelope-from zarychtam) Date: Fri, 22 Jun 2018 17:59:22 +0200 From: Marek Zarychta To: freebsd-stable@freebsd.org Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Message-ID: <20180622155922.GA61217@plan-b.pwste.edu.pl> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 15:59:30 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 22, 2018 at 03:12:05PM +0200, Michael Grimm wrote: > Hi, >=20 > this is 11.2-STABLE (r335532), and I am referring to the recent MFC of sy= slogd modifications [1].=20 >=20 > Because I cannot judge whether fail2ban lacks support for the renewed sys= logd or syslogd has an issue in receiving fail2ban messages I do crosspost = this mail to ports and stable. >=20 > I do have fail2ban configured to report to SYSLOG: >=20 > logtarget =3D SYSLOG > syslogsocket =3D auto >=20 > But now, after upgrading to the new syslogd fail2ban refuses to report to= syslogd; no single message gets recorded [2]. >=20 > I did try to modify the syslogsocket setting to /var/run/log without succ= ess. Pointing logtarget to a regular files tells me that fail2ban is runnin= g as expected, it only lacks reporting to SYSLOG. >=20 > #) Does anyone else has running py-fail2ban at >=3D r335059 and can confi= rm my observations?=20 > #) Any ideas how to debug this issue? >=20 > Thank you in advance and regards, > Michael >=20 >=20 > [1] https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?r= evision=3D335059&view=3Dmarkup&sortby=3Dfile > [2] both syslogd and fail2ban are running at the host, thus another issue= with syslogd fixed in=20 > https://svnweb.freebsd.org/base?view=3Drevision&sortby=3Dfile&revisio= n=3D335314 does not apply >=20 This is probably connected with the lack of handling of non-RFC compliant timestamps.=20 My syslog server also suffers from this issue. It stopped logging messages from old Cisco equipment and some newer Netgear switches. Running it in debug mode gives some clue: Failed to parse TIMESTAMP from x.x.x.x: 12403: Jun 22 17:31:38 CEST: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, changed state to down Could you please give any advice or workaround for this issue? --=20 Marek Zarychta --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlstHNgACgkQdZ/s//1S jSyUkAf5Ae7lSkVMSxq9jeZAeG1CAyBRzbW65JFKWfiwB9onS7SrFE0fbRWO/U95 DRUpg8cQCv9fXWLF0BKjVzGh06LFxuulQVNQxzXPqyPiuVqrVYcyFYN2PFXgIDEl En1m1VjkHwRAGwuzfJNqQHDpNBvwbNEROTyvNTK4UTxC3XRaUv2P3/5Pcruym6fX 54nBVsmePnTpWhA3AaOv68GpQ8kcqMIN2CbL5/hDaNDVxjI0YG/q93Y7Qs5zyfqF lAI5U3GXoLzz+M0WGjhD8G/ZseykoLopbHzsNZah83vvf4H9Q3w24Vqs9wsC1Nng ZPzlFn51LWWIWyWLooVx4ElEfo6nqQ== =YTva -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-stable@freebsd.org Fri Jun 22 16:54:34 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B85671020C86; Fri, 22 Jun 2018 16:54:34 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [IPv6:2001:41d0:302:1100::7:9a96]) (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 4D05C7714F; Fri, 22 Jun 2018 16:54:34 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f1b:7801:dd22:e1f2:698:8f0d] (p200300E97F1B7801DD22E1F206988F0D.dip0.t-ipconnect.de [IPv6:2003:e9:7f1b:7801:dd22:e1f2:698:8f0d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 41C4RW0b7Sz23k; Fri, 22 Jun 2018 18:54:31 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) From: Michael Grimm In-Reply-To: <20180622155922.GA61217@plan-b.pwste.edu.pl> Date: Fri, 22 Jun 2018 18:54:30 +0200 Cc: ed@freebsd.org, theis@gmx.at Content-Transfer-Encoding: quoted-printable Message-Id: <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> To: FreeBSD-STABLE Mailing List , Mailing List FreeBSD Ports X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=1.3 required=5.0 tests=RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.mer-waases.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 16:54:35 -0000 Marek Zarychta wrote: > On Fri, Jun 22, 2018 at 03:12:05PM +0200, Michael Grimm wrote: >> Hi, >>=20 >> this is 11.2-STABLE (r335532), and I am referring to the recent MFC = of syslogd modifications [1].=20 >>=20 >> Because I cannot judge whether fail2ban lacks support for the renewed = syslogd or syslogd has an issue in receiving fail2ban messages I do = crosspost this mail to ports and stable. >>=20 >> I do have fail2ban configured to report to SYSLOG: >>=20 >> logtarget =3D SYSLOG >> syslogsocket =3D auto >>=20 >> But now, after upgrading to the new syslogd fail2ban refuses to = report to syslogd; no single message gets recorded [2]. >>=20 >> I did try to modify the syslogsocket setting to /var/run/log without = success. Pointing logtarget to a regular files tells me that fail2ban is = running as expected, it only lacks reporting to SYSLOG. >>=20 >> #) Does anyone else has running py-fail2ban at >=3D r335059 and can = confirm my observations?=20 >> #) Any ideas how to debug this issue? >>=20 >> Thank you in advance and regards, >> Michael >>=20 >>=20 >> [1] = https://svnweb.freebsd.org/base/stable/11/usr.sbin/syslogd/Makefile?revisi= on=3D335059&view=3Dmarkup&sortby=3Dfile >> [2] both syslogd and fail2ban are running at the host, thus another = issue with syslogd fixed in=20 >> = https://svnweb.freebsd.org/base?view=3Drevision&sortby=3Dfile&revision=3D3= 35314 does not apply >>=20 >=20 > This is probably connected with the lack of handling of non-RFC > compliant timestamps.=20 >=20 > My syslog server also suffers from this issue. It stopped logging > messages from old Cisco equipment and some newer Netgear switches. > Running it in debug mode gives some clue: >=20 > Failed to parse TIMESTAMP from x.x.x.x: 12403: Jun 22 17:31:38 CEST: > %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, > changed state to down Ah, yes! Haven't thought about running syslogd in debugging mode: Failed to parse TIMESTAMP from x.x.x.x: fail2ban.filter [79598]: = INFO [=E2=80=A6] > Could you please give any advice or workaround for this issue? I cannot answer whether it might be possible to either tell syslogd to = accept legacy timestamps [1] or configure fail2ban (or your = applications) to switch to using RFC5424 compliant timestamps. [1] I did try to set '-O rfc3164' starting syslogd to no avail Anyone? Regards, Michael From owner-freebsd-stable@freebsd.org Fri Jun 22 17:14:57 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA483102160F; Fri, 22 Jun 2018 17:14:57 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net [91.121.41.56]) (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 61E0777C71; Fri, 22 Jun 2018 17:14:57 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f1b:7801:dd22:e1f2:698:8f0d] (p200300E97F1B7801DD22E1F206988F0D.dip0.t-ipconnect.de [IPv6:2003:e9:7f1b:7801:dd22:e1f2:698:8f0d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 41C4tw23G8z29Q; Fri, 22 Jun 2018 19:14:48 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net From: Michael Grimm Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Date: Fri, 22 Jun 2018 19:14:47 +0200 References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> To: FreeBSD-STABLE Mailing List , Mailing List FreeBSD Ports In-Reply-To: <20180622155922.GA61217@plan-b.pwste.edu.pl> Message-Id: <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org> X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=1.3 required=5.0 tests=RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.mer-waases.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 17:14:58 -0000 On 22. Jun 2018, at 17:59, Marek Zarychta = wrote: > Could you please give any advice or workaround for this issue? I switched to a workaround for the time being which you might use as = well in a similar way: #) configure fail2ban to use /var/log/faillog #) run something like that in the background: nohup tail -q -F /var/log/fail2ban.log | logger -t = fail2ban.filter -p daemon.notice & #) to let this workaround survive a reboot you need to use a script = fired up from /etc/rc.d Regards, Michael From owner-freebsd-stable@freebsd.org Fri Jun 22 17:57:25 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B4AB1022948 for ; Fri, 22 Jun 2018 17:57:25 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id D81B679919 for ; Fri, 22 Jun 2018 17:57:24 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 475F018045; Sat, 23 Jun 2018 02:57:21 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id C8FC916107; Sat, 23 Jun 2018 02:57:20 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id 8C45E16106; Sat, 23 Jun 2018 02:57:20 +0900 (JST) Date: Sat, 23 Jun 2018 02:56:35 +0900 (JST) Message-Id: <20180623.025635.943064292669730543.yasu@utahime.org> To: freebsd-stable@freebsd.org Subject: Re: Console is broken after updating to 11.2-RELEASE From: Yasuhiro KIMURA In-Reply-To: <5412681415d73751e981585076fb4922@udns.ultimatedns.net> References: <20180622.204218.2024776012115160106.yasu@utahime.org> <5412681415d73751e981585076fb4922@udns.ultimatedns.net> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 17:57:25 -0000 From: "Chris H" Subject: Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 06:13:39 -0700 > Try adding the following to your loader.conf(5) file > (/boot/loader.conf): > > # Load SysCons driver > kern.vty=sc > # noisy boot > boot_verbose="YES" > > Hope this helps! Thank you for information. I added above lines to /boot/loader.conf and rebooted system. Then all boot messages are displayed and console works fine! --- Yasuhiro KIMURA From owner-freebsd-stable@freebsd.org Fri Jun 22 18:02:37 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE0301022D7A for ; Fri, 22 Jun 2018 18:02:37 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AA847A169; Fri, 22 Jun 2018 18:02:36 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from hplaptop.potoki.eu ([IPv6:2001:678:618:c0:2:0:0:1]) (authenticated bits=0) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPSA id w5MI2Woh063137 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 22 Jun 2018 20:02:33 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1529690553; bh=Akp9MTYONuUSWSpcZeVQdRlsPK8g3NUzbLhuahgaNj8=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=ACUDpj1+TYLF6f3ahKuAc71qqV3WxE7NfuFP2o79UIdK8hkDuWt1LkypiEHAQZ+L4 RJwbKsoFdB1Rlpd+phs3yTH0cfjB7wze6f5RHJvC4TDpY3NfIWeRFXP8bCJ5fupB/k SLNSMfsssR1xeu7X9eLPPKDanycfssX3QHWebS6e4qh64JUUZgAv8G3fV8NKJonWQP Ji04yR5zbT8bNIF9DfO11gm+8Q/0xKy8ilGTwCTcurgC9KOQQ3b5FrD06r++GM8jYW PAq6Ssg7ScuyEwkgiP+HIDZnGDesLb/CbpPfa+Enl4TQD4ZLK92kS8puANdsy4dp+V BK/6Y7WHiNHiw== X-Authentication-Warning: plan-b.pwste.edu.pl: Host [IPv6:2001:678:618:c0:2:0:0:1] claimed to be hplaptop.potoki.eu Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) To: freebsd-stable@freebsd.org References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org> Cc: ed@freebsd.org From: Marek Zarychta Openpgp: preference=signencrypt Autocrypt: addr=zarychtam@plan-b.pwste.edu.pl; prefer-encrypt=mutual; keydata= xsBNBFfi3cMBCADLecMTFXad4uDXqv3eRuB4qJJ8G9tzzFezeRnnwxOsPdytW5ES2z1ibSrR IsiImx6+PTqrAmXpTInxAi7yiZGdSiONRI4CCxKY9d1YFiNYT/2WyNXCekm9x29YeIU7x0JB Llbz0f/9HC+styBIu2H+PY/X98Clzm110CS+n/b9l1AtiGxTiVFj7/uavYAKxH6LNWnbkuc5 v8EVNc7NkEcl5h7Z9X5NEtzDxTOiBIFQ/kOT7LAtkYUPo1lqLeOM2DtWSXTXQgXl0zJI4iP1 OAu4qQYm2nXwq4b2AH9peknelvnt1mpfgDCGSKnhc26q6ibTfMwydp+tvUtQIQYpA6b9ABEB AAHNLk1hcmVrIFphcnljaHRhIChQV1NURSkgPHphcnljaHRhQHB3c3RlLmVkdS5wbD7CwHoE EwEIACQCGwMFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AFAlfi61cCGQEACgkQHZW8vIFppoKb Qgf+IlZ71gjdVsvBykXUyxF6tZvpdPS0jnPqZBG/+WKIv6D2YfQ1wAQCkApv1CGz3XPdWDhh 0vGmF8ZCN/fKDpMGT4pIJkn5ZZxSmediy44BGUqFBqWSsZaFb6Ub6EbRHDvfBssRQZT9TMB9 abZtF5ZZOXmxlTuDDGL1PMp5XYVSMXfBH6qU8DSv5mBQr3v1IYJyxc6ylyE6lhg52eZ73NAl uxZelDIZX+uTK2GhpP1YWDucTUBUCpquhQjpNd6jw2uhmeF1ZgbS1WiTyK4j1VqT+j1HqiLB zOq9dC52g/wEGZet82Of5EFIpp1+o3PXkAVf9CpSsm3aavp9463QlksxA87ATQRX4t3DAQgA 10h6RCXuBLMHxq5B8X/ZIlj9sgLoeyfRdDZEc9rT2KUeUJVHDsbvOFf4/7F1ovWYhJbA6GK/ LUZeHHTjnbZcH1uDYQeHly4UOLxeEvhGoz4JhS2C7JzN/uRnwbdOAUbJr8rUj/IYa7gk906r ktsc/Ldrxrxh7O6WO0JCh2XO/p4pDfEwwB37g4xHprSab28ECYJ9JMbtA8Sy4M55g3+GQ28F vSlGnx48OoGXU2BZdc1vZKSQmNOlikB+9/hDX8zdYWVfDaX1TLQ8Ib4+xTUmapzamV/bxIsa ZRBw+jFjLQHhTbIMfPEU+4mxFDvTdbKPruKPqVf1ydgMnPZWngowdwARAQABwsBfBBgBCAAJ BQJX4t3DAhsMAAoJEB2VvLyBaaaC6qkIAJs9sDPqrqW0bYoRfzY6XjDWQ59p9tJiv8aogxac QNCfAu+WkJ8PNVUtC1dlVcG5NnZ80gXzd1rc8ueIvXlvdanUt/jZd8jbb3gaDbK3wh1yMCGB l/1fOJTyEGYv1CRojv97KK89KP5+r8x1P1iHcSrunlDNqGxTMydNCwBH23QcOM+mu4spKnJ/ s0VRBkw3xoKBZfZza6fTQ4gTpAipjyk7ldOGBV+PvkKATdhK2yLwuWXhKbg/GRlD1r5P0gxz SqfV4My+KJuc2EDcrqp1y0wOpE1m9iZqCcd0fup5f7HDsYlLWshr7NQl28f6+fQbsylq/j67 2BHXsdeqf/Ip9V4= Message-ID: Date: Fri, 22 Jun 2018 20:02:32 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3qMdLa7GfpIAPA00Y45LZdxZhBukuhP63" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 18:02:37 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3qMdLa7GfpIAPA00Y45LZdxZhBukuhP63 Content-Type: multipart/mixed; boundary="64NVWbA0zD6k5ZNzZd7k2dpXPAI8msZZb"; protected-headers="v1" From: Marek Zarychta To: freebsd-stable@freebsd.org Cc: ed@freebsd.org Message-ID: Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org> In-Reply-To: <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org> --64NVWbA0zD6k5ZNzZd7k2dpXPAI8msZZb Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US W dniu 2018.06.22 o=C2=A019:14, Michael Grimm pisze: > On 22. Jun 2018, at 17:59, Marek Zarychta wrote: > >> Could you please give any advice or workaround for this issue? > I switched to a workaround for the time being which you might use as we= ll in a similar way: > > #) configure fail2ban to use /var/log/faillog > #) run something like that in the background: > > nohup tail -q -F /var/log/fail2ban.log | logger -t fail2ban.filter -p = daemon.notice & > > #) to let this workaround survive a reboot you need to use a script fir= ed up from /etc/rc.d > > I have rolled back to r334835. The issue has gone. Should a PR be created about this regression ? BTW a few decent syslog daemons are available in /usr/ports/sysutils. --=20 Marek Zarychta --64NVWbA0zD6k5ZNzZd7k2dpXPAI8msZZb-- --3qMdLa7GfpIAPA00Y45LZdxZhBukuhP63 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlstOb4ACgkQdZ/s//1S jSx9bwf+P8u3O48VJYCWns1oL0mW9PzpihuBD7KKaspVhv73pEV9V+fFVcwO+YlK FWtKSK6BLiiZC+6Bl2VpkC/ZBRjnRVGf1rYIY30NQEIaEwYDqnmCBHV/DlFkA1JD jfbjHWtLpjxx0mKzJoNWbxKrY4pciGmLGFEfYdhB9tTkVlbQfCXthzsHxk4DBKSB UqENxHTotRu02o4mpPVcMIMx0myRgWvD7youfuHMyUh8eDPvADvysG3xnIG2SweN JJ8DphyVPrGyE49CfCtUnSIVOtXHNnHoTNlgWBdVoaumwubEM9sMsf+iymReg2FQ pQBSjM/Asc3G6PEk1mw4kjUaWxDzPQ== =6dDZ -----END PGP SIGNATURE----- --3qMdLa7GfpIAPA00Y45LZdxZhBukuhP63-- From owner-freebsd-stable@freebsd.org Fri Jun 22 18:13:59 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 181851023409 for ; Fri, 22 Jun 2018 18:13:59 +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 9BF597A96A; Fri, 22 Jun 2018 18:13:58 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fWQZM-000GX3-0i; Fri, 22 Jun 2018 20:14:00 +0200 Date: Fri, 22 Jun 2018 20:13:59 +0200 From: Kurt Jaeger To: Marek Zarychta Cc: freebsd-stable@freebsd.org, ed@freebsd.org Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Message-ID: <20180622181359.GQ4028@home.opsec.eu> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 18:13:59 -0000 Hi! > >> Could you please give any advice or workaround for this issue? > > I switched to a workaround for the time being which you might use as well in a similar way: > > > > #) configure fail2ban to use /var/log/faillog > > #) run something like that in the background: > > > > nohup tail -q -F /var/log/fail2ban.log | logger -t fail2ban.filter -p daemon.notice & > > > > #) to let this workaround survive a reboot you need to use a script fired up from /etc/rc.d > > > > > > I have rolled back to r334835. The issue has gone. Should a PR be > created about this regression ? Yes, please. > BTW a few decent syslog daemons are available in /usr/ports/sysutils. -- pi@opsec.eu +49 171 3101372 2 years to go ! From owner-freebsd-stable@freebsd.org Fri Jun 22 18:23:47 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 704871023952 for ; Fri, 22 Jun 2018 18:23:47 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id EBB677B11F for ; Fri, 22 Jun 2018 18:23:46 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id 33BB718069; Sat, 23 Jun 2018 03:23:45 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id F2443161E5; Sat, 23 Jun 2018 03:23:44 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id CF0F0161E4; Sat, 23 Jun 2018 03:23:44 +0900 (JST) Date: Sat, 23 Jun 2018 03:23:13 +0900 (JST) Message-Id: <20180623.032313.1789870000601589163.yasu@utahime.org> To: freebsd-stable@FreeBSD.org Subject: Re: Console is broken after updating to 11.2-RELEASE From: Yasuhiro KIMURA In-Reply-To: <20180622.170720.1809136341323718366.yasu@utahime.org> References: <20180622.170720.1809136341323718366.yasu@utahime.org> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 18:23:47 -0000 I submitted this problem as following bug report. Bug 229235 - vt(4) of 11.2-RELEASE is broken with hardware dependent problem. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229235 Just FYI. --- Yasuhiro KIMURA From owner-freebsd-stable@freebsd.org Fri Jun 22 18:34:26 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69E601023FF8 for ; Fri, 22 Jun 2018 18:34:26 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE4E67BD80 for ; Fri, 22 Jun 2018 18:34:25 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (zarychtam@localhost [127.0.0.1]) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPS id w5MIYLlP063582 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Fri, 22 Jun 2018 20:34:21 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1529692461; bh=uuC3/9p1hi6zoA73cPDqRPcDq+c47Qp5e5aNS3t1dkU=; h=Date:From:To:Subject:References:In-Reply-To; b=gkpOLM1a99Ch8DFggA0m60Qz3wBimSbrSpK3dXk06znIpEckquf4cTE6yO/8ns4/H lRbt+7KCtTRXz83Pcas82Y13GUITREDl9PNqTcZDh5AsrFBTgEXO6KgEn8f5zW291u +7TL770snTbxkhXjpPdoHBYhBcWWflCdAE6U/NLMKYlLbT3ifrV3AbJh3CxnARpbZ6 D7YpxeQ13pwCPglAE9RHYKvskjXW75kCCym7nzQkQQMeND4DUetsm6FVuaBQb/TyI6 gUau5J5aDBgWmX2rqMIL7vpPbz1Xeemb6Bii9lBI4T9/2XDDLSoAtCCBDu/Tkb+7a9 JJVaIx1AgC/tA== Received: (from zarychtam@localhost) by plan-b.pwste.edu.pl (8.15.2/8.15.2/Submit) id w5MIYLNW063581 for freebsd-stable@freebsd.org; Fri, 22 Jun 2018 20:34:21 +0200 (CEST) (envelope-from zarychtam) Date: Fri, 22 Jun 2018 20:34:21 +0200 From: Marek Zarychta To: freebsd-stable@freebsd.org Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Message-ID: <20180622183421.GA63556@plan-b.pwste.edu.pl> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <8103A181-1C50-4EA5-9851-8092861177D8@ellael.org> <20180622181359.GQ4028@home.opsec.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline In-Reply-To: <20180622181359.GQ4028@home.opsec.eu> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 18:34:26 -0000 --ibTvN161/egqYuK8 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 22, 2018 at 08:13:59PM +0200, Kurt Jaeger wrote: > > I have rolled back to r334835. The issue has gone. Should a PR be > > created about this regression ? >=20 > Yes, please. >=20 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229236 --=20 Marek Zarychta --ibTvN161/egqYuK8 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlstQSoACgkQdZ/s//1S jSytoQgAh/9BThucx6Py1w485Bf7akVmNbH6X+OjP7SMkO/83hKTo1L3ZqV1Z/RM FmZx0Rt/GdXa96wxoLMQiVamlap6E1fDhC3lTpFpu3fuBZC2o71+c+AnE2ovj2kf FxnzwG7AA21O95gnPRUl0LkYYYZSpcACoQoWqHyn4/8wCadHAse8IbLScS1bU5by 7DcYO+xNg4FyAFqlQt6Sn0YcZ4yY/GwxWeH/4/HYsnvXycSwLoue1P57PzFscDdV rBBW4Lm8y0Jz7o4GUrnH+MgYIQs6xDpfbYPIxhqVbESpc3+k53615QJMrwhQVVEI LnNB94Gm2Q4krgCtDP+OUHxuQdtXVQ== =cira -----END PGP SIGNATURE----- --ibTvN161/egqYuK8-- From owner-freebsd-stable@freebsd.org Fri Jun 22 19:11:39 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E1291024B7F for ; Fri, 22 Jun 2018 19:11:39 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 92D207CFC2 for ; Fri, 22 Jun 2018 19:11:38 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-ed1-x533.google.com with SMTP id x4-v6so1802663edq.7 for ; Fri, 22 Jun 2018 12:11:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xT8j5LHw12Yh7KnbHktmtPvtaYT0YV7a6AySIqfrSq0=; b=x/IwSwG3BKyD2umkJtpAX5A0MNSgGrITOFnkZYfbXh4Oa9zlc5a5GI9QHUXWxd7weV lNB5LRWi6qY/06D5tq1OdXxqgMeAXztFOkm48QdgEA/kqigueJPUMaHH+tdO0mb6qu2L wXhJYXk+WMnb2Ld/piMkpXWql+2SKb9UA8L8F9VK6AXsfLzgF3BdMhb1yp41le00sig4 1aC5OS9BAjjvA3rSYq2QlwplZOj0Tq8WHs9KYIWsUccETMsEpyh6X768hVsLl7kEfXV+ QAr/dpNs03l6EWbgeLUZFoxkjM482yTEvBapUj/wBHU4RGybDd3E/wltjARe+mlrPqAK QrJA== 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=xT8j5LHw12Yh7KnbHktmtPvtaYT0YV7a6AySIqfrSq0=; b=ecGlPuHPo5G45SDOZgT9Uzd89ZpwFMu2onc9A7Vmbmkt/db86ioe8QSOz6/2hGFKTy uWOKjgDet8Ndf6SFxvbnmoc0UpSdetvAVPfvGY4i4PSyZ6moMUA6oj+4J2sfNZ5BfuVw Osd6ZU9xoFZPTx8NPdkbspyxlmorfcsmWAIWLyxFqFCn9VQL+afZVzF+19uDRrb9hwgO I/XJ0udou9qFxknkOtQsNEpzRmX1oC9BRZ4f+nKD1CfKSA+JHJiHq+eg4CpZkeiI70ts SJ4EbUf3UODsuFVm5VpMBstR2FnTXEJ6ZShvXgpahZIJF8DoZQJfXCYjDtwn/w12uRle XnBw== X-Gm-Message-State: APt69E2EmBFPsZmYTdCOY8jkPuT350dylP1vpqxwKrJkDAwDINRMBdDO y16sZQGdkv/q9cCE4wWtDl2dtdlJmxI/pHqZAbrbOA== X-Google-Smtp-Source: ADUXVKJJ5vEudlpb4UTjoAlyZHQBwUBGZTDKVtg0Uc7HIwWP+ANMvyNP9o8Q3h5QuRGBtEE2zDWLdWWowIQpiwNLIy0= X-Received: by 2002:aa7:c588:: with SMTP id g8-v6mr2741466edq.200.1529694697218; Fri, 22 Jun 2018 12:11:37 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:8e0d:0:0:0:0:0 with HTTP; Fri, 22 Jun 2018 12:11:06 -0700 (PDT) In-Reply-To: <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> From: Ed Schouten Date: Fri, 22 Jun 2018 21:11:06 +0200 Message-ID: Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) To: Michael Grimm Cc: FreeBSD-STABLE Mailing List , Mailing List FreeBSD Ports , "ed@FreeBSD.org" , theis@gmx.at, Gleb Smirnoff Content-Type: multipart/mixed; boundary="0000000000000b106f056f3fcd51" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 19:11:39 -0000 --0000000000000b106f056f3fcd51 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Marek, [ +glebius ] Thanks for reporting this! 2018-06-22 18:54 GMT+02:00 Michael Grimm : >> Failed to parse TIMESTAMP from x.x.x.x: 12403: Jun 22 17:31:38 CEST: >> %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, >> changed state to down > > Ah, yes! Haven't thought about running syslogd in debugging mode: > > Failed to parse TIMESTAMP from x.x.x.x: fail2ban.filter [79598]: = INFO [=E2=80=A6] This is interesting. As fail2ban uses Python's logging framework, I managed to reproduce this with the following script: #!/usr/bin/env python3 import logging.handlers logging.basicConfig(handlers=3D[ logging.handlers.SysLogHandler( '/var/run/log', facility=3Dlogging.handlers.SysLogHandler.LOG_LOCAL= 7) ]) logging.warning('Hi') This will write the following message to syslogd: sendto(3,"<188>WARNING:root:Hi\0",21,0,NULL,0) =3D 21 (0x15) This message gets rejected by syslogd, due to the change made in r326573, which later got adjusted by me and subsequently MFCed: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D326573 Gleb, what are your thoughts on the attached patch? It alters syslogd to let the 'legacy' RFC 3164 parser also accept messages without a timestamp. The time on the syslogd server will be used instead. Michael, Marek, could you please give this patch a try? Thanks! --=20 Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands --0000000000000b106f056f3fcd51 Content-Type: text/x-patch; charset="US-ASCII"; name="syslogd-optional-timestamp.diff" Content-Disposition: attachment; filename="syslogd-optional-timestamp.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_jiqcpgzp0 SW5kZXg6IHVzci5zYmluL3N5c2xvZ2Qvc3lzbG9nZC5jCj09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIHVzci5zYmlu L3N5c2xvZ2Qvc3lzbG9nZC5jCShyZXZpc2lvbiAzMzUzMTQpCisrKyB1c3Iuc2Jpbi9zeXNsb2dk L3N5c2xvZ2QuYwkod29ya2luZyBjb3B5KQpAQCAtMTE3Miw0NSArMTE3Miw0MyBAQAogCXNpemVf dCBpLCBtc2dsZW47CiAJY2hhciBsaW5lW01BWExJTkUgKyAxXTsKIAotCS8qIFBhcnNlIHRoZSB0 aW1lc3RhbXAgcHJvdmlkZWQgYnkgdGhlIHJlbW90ZSBzaWRlLiAqLwotCWlmIChzdHJwdGltZSht c2csIFJGQzMxNjRfREFURUZNVCwgJnRtX3BhcnNlZCkgIT0KLQkgICAgbXNnICsgUkZDMzE2NF9E QVRFTEVOIHx8IG1zZ1tSRkMzMTY0X0RBVEVMRU5dICE9ICcgJykgewotCQlkcHJpbnRmKCJGYWls ZWQgdG8gcGFyc2UgVElNRVNUQU1QIGZyb20gJXM6ICVzXG4iLCBmcm9tLCBtc2cpOwotCQlyZXR1 cm47Ci0JfQotCW1zZyArPSBSRkMzMTY0X0RBVEVMRU4gKyAxOworCS8qIFBhcnNlIHRoZSB0aW1l c3RhbXAgcHJvdmlkZWQgYnkgdGhlIHJlbW90ZSBzaWRlLCBpZiBhbnkuICovCisJdGltZXN0YW1w ID0gTlVMTDsKKwlpZiAoc3RycHRpbWUobXNnLCBSRkMzMTY0X0RBVEVGTVQsICZ0bV9wYXJzZWQp ID09CisJICAgIG1zZyArIFJGQzMxNjRfREFURUxFTiAmJiBtc2dbUkZDMzE2NF9EQVRFTEVOXSA9 PSAnICcpIHsKKwkJbXNnICs9IFJGQzMxNjRfREFURUxFTiArIDE7CisJCWlmICghUmVtb3RlQWRk RGF0ZSkgeworCQkJc3RydWN0IHRtIHRtX25vdzsKKwkJCXRpbWVfdCB0X25vdzsKKwkJCWludCB5 ZWFyOwogCi0JaWYgKCFSZW1vdGVBZGREYXRlKSB7Ci0JCXN0cnVjdCB0bSB0bV9ub3c7Ci0JCXRp bWVfdCB0X25vdzsKLQkJaW50IHllYXI7Ci0KLQkJLyoKLQkJICogQXMgdGhlIHRpbWVzdGFtcCBk b2VzIG5vdCBjb250YWluIHRoZSB5ZWFyIG51bWJlciwKLQkJICogZGF5bGlnaHQgc2F2aW5nIHRp bWUgaW5mb3JtYXRpb24sIG5vciBhIHRpbWUgem9uZSwKLQkJICogYXR0ZW1wdCB0byBpbmZlciBp dC4gRHVlIHRvIGNsb2NrIHNrZXdzLCB0aGUKLQkJICogdGltZXN0YW1wIG1heSBldmVuIGJlIHBh cnQgb2YgdGhlIG5leHQgeWVhci4gVXNlIHRoZQotCQkgKiBsYXN0IHllYXIgZm9yIHdoaWNoIHRo ZSB0aW1lc3RhbXAgaXMgYXQgbW9zdCBvbmUgd2VlawotCQkgKiBpbiB0aGUgZnV0dXJlLgotCQkg KgotCQkgKiBUaGlzIGxvb3AgY2FuIG9ubHkgcnVuIGZvciBhdCBtb3N0IHRocmVlIGl0ZXJhdGlv bnMKLQkJICogYmVmb3JlIHRlcm1pbmF0aW5nLgotCQkgKi8KLQkJdF9ub3cgPSB0aW1lKE5VTEwp OwotCQlsb2NhbHRpbWVfcigmdF9ub3csICZ0bV9ub3cpOwotCQlmb3IgKHllYXIgPSB0bV9ub3cu dG1feWVhciArIDE7OyAtLXllYXIpIHsKLQkJCWFzc2VydCh5ZWFyID49IHRtX25vdy50bV95ZWFy IC0gMSk7Ci0JCQl0aW1lc3RhbXBfcmVtb3RlLnRtID0gdG1fcGFyc2VkOwotCQkJdGltZXN0YW1w X3JlbW90ZS50bS50bV95ZWFyID0geWVhcjsKLQkJCXRpbWVzdGFtcF9yZW1vdGUudG0udG1faXNk c3QgPSAtMTsKLQkJCXRpbWVzdGFtcF9yZW1vdGUudXNlYyA9IDA7Ci0JCQlpZiAobWt0aW1lKCZ0 aW1lc3RhbXBfcmVtb3RlLnRtKSA8Ci0JCQkgICAgdF9ub3cgKyA3ICogMjQgKiA2MCAqIDYwKQot CQkJCWJyZWFrOworCQkJLyoKKwkJCSAqIEFzIHRoZSB0aW1lc3RhbXAgZG9lcyBub3QgY29udGFp biB0aGUgeWVhcgorCQkJICogbnVtYmVyLCBkYXlsaWdodCBzYXZpbmcgdGltZSBpbmZvcm1hdGlv biwgbm9yCisJCQkgKiBhIHRpbWUgem9uZSwgYXR0ZW1wdCB0byBpbmZlciBpdC4gRHVlIHRvCisJ CQkgKiBjbG9jayBza2V3cywgdGhlIHRpbWVzdGFtcCBtYXkgZXZlbiBiZSBwYXJ0CisJCQkgKiBv ZiB0aGUgbmV4dCB5ZWFyLiBVc2UgdGhlIGxhc3QgeWVhciBmb3Igd2hpY2gKKwkJCSAqIHRoZSB0 aW1lc3RhbXAgaXMgYXQgbW9zdCBvbmUgd2VlayBpbiB0aGUKKwkJCSAqIGZ1dHVyZS4KKwkJCSAq CisJCQkgKiBUaGlzIGxvb3AgY2FuIG9ubHkgcnVuIGZvciBhdCBtb3N0IHRocmVlCisJCQkgKiBp dGVyYXRpb25zIGJlZm9yZSB0ZXJtaW5hdGluZy4KKwkJCSAqLworCQkJdF9ub3cgPSB0aW1lKE5V TEwpOworCQkJbG9jYWx0aW1lX3IoJnRfbm93LCAmdG1fbm93KTsKKwkJCWZvciAoeWVhciA9IHRt X25vdy50bV95ZWFyICsgMTs7IC0teWVhcikgeworCQkJCWFzc2VydCh5ZWFyID49IHRtX25vdy50 bV95ZWFyIC0gMSk7CisJCQkJdGltZXN0YW1wX3JlbW90ZS50bSA9IHRtX3BhcnNlZDsKKwkJCQl0 aW1lc3RhbXBfcmVtb3RlLnRtLnRtX3llYXIgPSB5ZWFyOworCQkJCXRpbWVzdGFtcF9yZW1vdGUu dG0udG1faXNkc3QgPSAtMTsKKwkJCQl0aW1lc3RhbXBfcmVtb3RlLnVzZWMgPSAwOworCQkJCWlm IChta3RpbWUoJnRpbWVzdGFtcF9yZW1vdGUudG0pIDwKKwkJCQkgICAgdF9ub3cgKyA3ICogMjQg KiA2MCAqIDYwKQorCQkJCQlicmVhazsKKwkJCX0KKwkJCXRpbWVzdGFtcCA9ICZ0aW1lc3RhbXBf cmVtb3RlOwogCQl9Ci0JCXRpbWVzdGFtcCA9ICZ0aW1lc3RhbXBfcmVtb3RlOwotCX0gZWxzZQot CQl0aW1lc3RhbXAgPSBOVUxMOworCX0KIAogCS8qCiAJICogQSBzaW5nbGUgc3BhY2UgY2hhcmFj dGVyIE1VU1QgYWxzbyBmb2xsb3cgdGhlIEhPU1ROQU1FIGZpZWxkLgo= --0000000000000b106f056f3fcd51-- From owner-freebsd-stable@freebsd.org Fri Jun 22 19:26:51 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C18110251C2; Fri, 22 Jun 2018 19:26:51 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:401:2100::5:8a0e]) (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 F0D337D892; Fri, 22 Jun 2018 19:26:50 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f1b:7801:54b7:5afc:c9f5:e023] (p200300E97F1B780154B75AFCC9F5E023.dip0.t-ipconnect.de [IPv6:2003:e9:7f1b:7801:54b7:5afc:c9f5:e023]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 41C7q33hQgz4NL; Fri, 22 Jun 2018 21:26:39 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) From: Michael Grimm In-Reply-To: Date: Fri, 22 Jun 2018 21:26:36 +0200 Cc: "ed@FreeBSD.org" , theis@gmx.at, Gleb Smirnoff , FreeBSD-STABLE Mailing List , Mailing List FreeBSD Ports Content-Transfer-Encoding: quoted-printable Message-Id: <851C065F-0E02-425C-B4AF-8FCE0E405F8E@ellael.org> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> To: Ed Schouten X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.kaan-bock.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 19:26:51 -0000 On 22. Jun 2018, at 21:11, Ed Schouten wrote: > Gleb, what are your thoughts on the attached patch? It alters syslogd > to let the 'legacy' RFC 3164 parser also accept messages without a > timestamp. The time on the syslogd server will be used instead. >=20 > Michael, Marek, could you please give this patch a try? Thanks! Recompiled world (FreeBSD 11.2-STABLE r335532), substituted syslogd with = the re-compiled one, and: Thank you! Your patch is working w.r.t. fail2ban logging to SYSLOG. = Perfect! Thank you very much for this fast fix, and regards, Michael From owner-freebsd-stable@freebsd.org Fri Jun 22 20:06:42 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B0741025B0E; Fri, 22 Jun 2018 20:06:42 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [87.98.149.189]) (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 08D1D7F046; Fri, 22 Jun 2018 20:06:41 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f1b:7801:54b7:5afc:c9f5:e023] (p200300E97F1B780154B75AFCC9F5E023.dip0.t-ipconnect.de [IPv6:2003:e9:7f1b:7801:54b7:5afc:c9f5:e023]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 41C8jB2xnwz4gH; Fri, 22 Jun 2018 22:06:38 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) From: Michael Grimm In-Reply-To: <851C065F-0E02-425C-B4AF-8FCE0E405F8E@ellael.org> Date: Fri, 22 Jun 2018 22:06:36 +0200 Cc: FreeBSD-STABLE Mailing List , theis@gmx.at, Gleb Smirnoff , "ed@FreeBSD.org" , Mailing List FreeBSD Ports Content-Transfer-Encoding: quoted-printable Message-Id: <1A5B44D8-28B0-49C9-B88D-EE6EBEE8788D@ellael.org> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> <851C065F-0E02-425C-B4AF-8FCE0E405F8E@ellael.org> To: Ed Schouten X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.kaan-bock.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 20:06:42 -0000 On 22. Jun 2018, at 21:26, Michael Grimm wrote: > On 22. Jun 2018, at 21:11, Ed Schouten wrote: >> Michael, Marek, could you please give this patch a try? Thanks! >=20 > Recompiled world (FreeBSD 11.2-STABLE r335532), substituted syslogd = with the re-compiled one, and: >=20 > Thank you! Your patch is working w.r.t. fail2ban logging to SYSLOG. = Perfect! Now I realised that there is a minor glitch: logfile+logger: Jun 22 19:01:48 HOSTNAME fail2ban.filter: = 2018-06-22 19:01:48,637 fail2ban.actions [85544]: NOTICE = [JAILNAME] Unban x.x.x.x Old syslogd before MFC: May 30 15:39:41 HOSTNAME fail2ban.actions [929]: = NOTICE [JAILNAME] Unban x.x.x.x After applying your patch: Jun 22 21:22:01 HOSTNAME [31033]: NOTICE = [JAILNAME] Unban x.x.x.x Watch: 'fail2ban.actions' -the service- is missing. Regards, Michael From owner-freebsd-stable@freebsd.org Fri Jun 22 20:09:34 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B9531025C33; Fri, 22 Jun 2018 20:09:34 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from cell.glebi.us (glebi.us [198.45.61.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 850EB7F20D; Fri, 22 Jun 2018 20:09:33 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id w5MK7p4P056142 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 22 Jun 2018 13:07:51 -0700 (PDT) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id w5MK7ple056141; Fri, 22 Jun 2018 13:07:51 -0700 (PDT) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@freebsd.org using -f Date: Fri, 22 Jun 2018 13:07:51 -0700 From: Gleb Smirnoff To: Ed Schouten Cc: Michael Grimm , FreeBSD-STABLE Mailing List , Mailing List FreeBSD Ports , "ed@FreeBSD.org" , theis@gmx.at Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Message-ID: <20180622200751.GD1103@cell.glebi.us> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 20:09:34 -0000 Hi Ed, On Fri, Jun 22, 2018 at 09:11:06PM +0200, Ed Schouten wrote: E> > Ah, yes! Haven't thought about running syslogd in debugging mode: E> > E> > Failed to parse TIMESTAMP from x.x.x.x: fail2ban.filter [79598]: INFO […] E> E> This is interesting. As fail2ban uses Python's logging framework, I E> managed to reproduce this with the following script: E> E> #!/usr/bin/env python3 E> import logging.handlers E> logging.basicConfig(handlers=[ E> logging.handlers.SysLogHandler( E> '/var/run/log', facility=logging.handlers.SysLogHandler.LOG_LOCAL7) E> ]) E> logging.warning('Hi') E> E> This will write the following message to syslogd: E> E> sendto(3,"<188>WARNING:root:Hi\0",21,0,NULL,0) = 21 (0x15) E> E> This message gets rejected by syslogd, due to the change made in E> r326573, which later got adjusted by me and subsequently MFCed: E> E> https://svnweb.freebsd.org/base?view=revision&revision=326573 E> E> Gleb, what are your thoughts on the attached patch? It alters syslogd E> to let the 'legacy' RFC 3164 parser also accept messages without a E> timestamp. The time on the syslogd server will be used instead. E> E> Michael, Marek, could you please give this patch a try? Thanks! I didn't examine the patch thoroughly, but I agree that looks like we have no other choice as to support the legacy and normal messages at the same time. -- Gleb Smirnoff From owner-freebsd-stable@freebsd.org Fri Jun 22 20:29:28 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 506A71026380 for ; Fri, 22 Jun 2018 20:29:28 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 9E15B800F3 for ; Fri, 22 Jun 2018 20:29:27 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-ed1-x535.google.com with SMTP id i16-v6so1907735eds.12 for ; Fri, 22 Jun 2018 13:29:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QtnPZ3X6nGbe2UhV46Z/WhGoIX/OsBi9qSJILCFSCvw=; b=vsosKbGzjwjMfPzKSndXe+zNGH07aBmqgYHHTBx52pUWW52zUKpcVZZM68Z21j7Yjz Wsqj4YiYHzUuthpy/blgDqCTdo6Sl3uMF61XW5jVpS7Snie9sxwe8L5H089u/eSiS8Hc EKN66LBWCbyi4hB5CbZ5T2rcxPKTDinpiiT4HgPCMiVsAGguIUrQJDIFRjAY0L2sPdKS PrSJbtZfn5J3ah5yblJBaxnN5MCh4+mGe0jRFEx06siczpTVp7nIw9ikpohK0CS7wBIS TtyEbprFVNA9MAE5jQwtzSdGwkxz35E1SQ9MsteoF8j4TxmDfPQR2MTK7RBYkNA9sh52 rRFA== 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=QtnPZ3X6nGbe2UhV46Z/WhGoIX/OsBi9qSJILCFSCvw=; b=RLHrAGN43fUEf18RtbcUlkTByc12Mpf8/3aedTS3nUE/FxJnGz/izNBtxU/AdlylBf mTLIO2UwFEGh3ZE9bSOIET04RVpEAMd2AOeJp+VnFNJyCLSCTVP2g05pfL0XSNQ7ypcl Qw8wfaq3+8cIybCyZSS8r337RX6IqOpRwKjh/8M5FpOmaUr2MG7l7VuDHgE9Vq+Suzmx NDOXH4z6uIvYNWZdLUNc2KIHJ1A7sSuE18me4z3yOQGDFxkH0DoNwxdzueYjxcw1YNtz ZdojpFEkPuEo032Se++Uq/bRVsKOmdU9tic007AiWdqoag3vdf57oeW+on+9jUN7T+rh xdVg== X-Gm-Message-State: APt69E3kR5go61GYBWET1eQHrtQX+8a8YlPiEO4dIFgC4nHiPgC3+s/p DhhY/X5ILgVNkLGf80H52knqsbUDFKekNDAZDhAmNw== X-Google-Smtp-Source: ADUXVKK2BfSHjPfSIvoxhVKTO3VXfjtB408jZv+lQJNfHuIWyzS3vfz/NKbPMQrFknApjsQ1EEzIFmB4+zQn/EM0/Io= X-Received: by 2002:a50:aba5:: with SMTP id u34-v6mr3003745edc.252.1529699366486; Fri, 22 Jun 2018 13:29:26 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:8e0d:0:0:0:0:0 with HTTP; Fri, 22 Jun 2018 13:28:55 -0700 (PDT) In-Reply-To: <1A5B44D8-28B0-49C9-B88D-EE6EBEE8788D@ellael.org> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> <851C065F-0E02-425C-B4AF-8FCE0E405F8E@ellael.org> <1A5B44D8-28B0-49C9-B88D-EE6EBEE8788D@ellael.org> From: Ed Schouten Date: Fri, 22 Jun 2018 22:28:55 +0200 Message-ID: Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) To: Michael Grimm Cc: FreeBSD-STABLE Mailing List , theis@gmx.at, Gleb Smirnoff , "ed@FreeBSD.org" , Mailing List FreeBSD Ports Content-Type: multipart/mixed; boundary="0000000000005a72e8056f40e3c2" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 20:29:28 -0000 --0000000000005a72e8056f40e3c2 Content-Type: text/plain; charset="UTF-8" Hi Michael, 2018-06-22 22:06 GMT+02:00 Michael Grimm : > After applying your patch: > Jun 22 21:22:01 HOSTNAME [31033]: NOTICE [JAILNAME] Unban x.x.x.x > > Watch: 'fail2ban.actions' -the service- is missing. That's likely due to the fact that it now interprets the first word in the message as the remote hostname, which gets discarded. Attached is a somewhat refined patch that only tries to parse the hostname in remote messages if they are preceded by a timestamp. If the timestamp is missing, it assumes the entire payload is the message. Can you give this one a try? Thanks! -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands --0000000000005a72e8056f40e3c2 Content-Type: application/octet-stream; name="syslogd-optional-timestamp-v2.diff" Content-Disposition: attachment; filename="syslogd-optional-timestamp-v2.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_jiqfgkxv0 SW5kZXg6IHVzci5zYmluL3N5c2xvZ2Qvc3lzbG9nZC5jCj09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIHVzci5zYmlu L3N5c2xvZ2Qvc3lzbG9nZC5jCShyZXZpc2lvbiAzMzUzMTQpCisrKyB1c3Iuc2Jpbi9zeXNsb2dk L3N5c2xvZ2QuYwkod29ya2luZyBjb3B5KQpAQCAtMTE3Miw2OSArMTE3Miw3MSBAQAogCXNpemVf dCBpLCBtc2dsZW47CiAJY2hhciBsaW5lW01BWExJTkUgKyAxXTsKIAotCS8qIFBhcnNlIHRoZSB0 aW1lc3RhbXAgcHJvdmlkZWQgYnkgdGhlIHJlbW90ZSBzaWRlLiAqLwotCWlmIChzdHJwdGltZSht c2csIFJGQzMxNjRfREFURUZNVCwgJnRtX3BhcnNlZCkgIT0KLQkgICAgbXNnICsgUkZDMzE2NF9E QVRFTEVOIHx8IG1zZ1tSRkMzMTY0X0RBVEVMRU5dICE9ICcgJykgewotCQlkcHJpbnRmKCJGYWls ZWQgdG8gcGFyc2UgVElNRVNUQU1QIGZyb20gJXM6ICVzXG4iLCBmcm9tLCBtc2cpOwotCQlyZXR1 cm47Ci0JfQotCW1zZyArPSBSRkMzMTY0X0RBVEVMRU4gKyAxOworCS8qCisJICogUGFyc2UgdGhl IFRJTUVTVEFNUCBwcm92aWRlZCBieSB0aGUgcmVtb3RlIHNpZGUuIElmIG5vbmUgaXMKKwkgKiBm b3VuZCwgYXNzdW1lIHRoaXMgaXMgbm90IGFuIFJGQyAzMTY0IGZvcm1hdHRlZCBtZXNzYWdlLAor CSAqIG9ubHkgY29udGFpbmluZyBhIFRBRyBhbmQgYSBNU0cuCisJICovCisJdGltZXN0YW1wID0g TlVMTDsKKwlpZiAoc3RycHRpbWUobXNnLCBSRkMzMTY0X0RBVEVGTVQsICZ0bV9wYXJzZWQpID09 CisJICAgIG1zZyArIFJGQzMxNjRfREFURUxFTiAmJiBtc2dbUkZDMzE2NF9EQVRFTEVOXSA9PSAn ICcpIHsKKwkJbXNnICs9IFJGQzMxNjRfREFURUxFTiArIDE7CisJCWlmICghUmVtb3RlQWRkRGF0 ZSkgeworCQkJc3RydWN0IHRtIHRtX25vdzsKKwkJCXRpbWVfdCB0X25vdzsKKwkJCWludCB5ZWFy OwogCi0JaWYgKCFSZW1vdGVBZGREYXRlKSB7Ci0JCXN0cnVjdCB0bSB0bV9ub3c7Ci0JCXRpbWVf dCB0X25vdzsKLQkJaW50IHllYXI7CisJCQkvKgorCQkJICogQXMgdGhlIHRpbWVzdGFtcCBkb2Vz IG5vdCBjb250YWluIHRoZSB5ZWFyCisJCQkgKiBudW1iZXIsIGRheWxpZ2h0IHNhdmluZyB0aW1l IGluZm9ybWF0aW9uLCBub3IKKwkJCSAqIGEgdGltZSB6b25lLCBhdHRlbXB0IHRvIGluZmVyIGl0 LiBEdWUgdG8KKwkJCSAqIGNsb2NrIHNrZXdzLCB0aGUgdGltZXN0YW1wIG1heSBldmVuIGJlIHBh cnQKKwkJCSAqIG9mIHRoZSBuZXh0IHllYXIuIFVzZSB0aGUgbGFzdCB5ZWFyIGZvciB3aGljaAor CQkJICogdGhlIHRpbWVzdGFtcCBpcyBhdCBtb3N0IG9uZSB3ZWVrIGluIHRoZQorCQkJICogZnV0 dXJlLgorCQkJICoKKwkJCSAqIFRoaXMgbG9vcCBjYW4gb25seSBydW4gZm9yIGF0IG1vc3QgdGhy ZWUKKwkJCSAqIGl0ZXJhdGlvbnMgYmVmb3JlIHRlcm1pbmF0aW5nLgorCQkJICovCisJCQl0X25v dyA9IHRpbWUoTlVMTCk7CisJCQlsb2NhbHRpbWVfcigmdF9ub3csICZ0bV9ub3cpOworCQkJZm9y ICh5ZWFyID0gdG1fbm93LnRtX3llYXIgKyAxOzsgLS15ZWFyKSB7CisJCQkJYXNzZXJ0KHllYXIg Pj0gdG1fbm93LnRtX3llYXIgLSAxKTsKKwkJCQl0aW1lc3RhbXBfcmVtb3RlLnRtID0gdG1fcGFy c2VkOworCQkJCXRpbWVzdGFtcF9yZW1vdGUudG0udG1feWVhciA9IHllYXI7CisJCQkJdGltZXN0 YW1wX3JlbW90ZS50bS50bV9pc2RzdCA9IC0xOworCQkJCXRpbWVzdGFtcF9yZW1vdGUudXNlYyA9 IDA7CisJCQkJaWYgKG1rdGltZSgmdGltZXN0YW1wX3JlbW90ZS50bSkgPAorCQkJCSAgICB0X25v dyArIDcgKiAyNCAqIDYwICogNjApCisJCQkJCWJyZWFrOworCQkJfQorCQkJdGltZXN0YW1wID0g JnRpbWVzdGFtcF9yZW1vdGU7CisJCX0KIAogCQkvKgotCQkgKiBBcyB0aGUgdGltZXN0YW1wIGRv ZXMgbm90IGNvbnRhaW4gdGhlIHllYXIgbnVtYmVyLAotCQkgKiBkYXlsaWdodCBzYXZpbmcgdGlt ZSBpbmZvcm1hdGlvbiwgbm9yIGEgdGltZSB6b25lLAotCQkgKiBhdHRlbXB0IHRvIGluZmVyIGl0 LiBEdWUgdG8gY2xvY2sgc2tld3MsIHRoZQotCQkgKiB0aW1lc3RhbXAgbWF5IGV2ZW4gYmUgcGFy dCBvZiB0aGUgbmV4dCB5ZWFyLiBVc2UgdGhlCi0JCSAqIGxhc3QgeWVhciBmb3Igd2hpY2ggdGhl IHRpbWVzdGFtcCBpcyBhdCBtb3N0IG9uZSB3ZWVrCi0JCSAqIGluIHRoZSBmdXR1cmUuCi0JCSAq Ci0JCSAqIFRoaXMgbG9vcCBjYW4gb25seSBydW4gZm9yIGF0IG1vc3QgdGhyZWUgaXRlcmF0aW9u cwotCQkgKiBiZWZvcmUgdGVybWluYXRpbmcuCisJCSAqIEEgc2luZ2xlIHNwYWNlIGNoYXJhY3Rl ciBNVVNUIGFsc28gZm9sbG93IHRoZSBIT1NUTkFNRSBmaWVsZC4KIAkJICovCi0JCXRfbm93ID0g dGltZShOVUxMKTsKLQkJbG9jYWx0aW1lX3IoJnRfbm93LCAmdG1fbm93KTsKLQkJZm9yICh5ZWFy ID0gdG1fbm93LnRtX3llYXIgKyAxOzsgLS15ZWFyKSB7Ci0JCQlhc3NlcnQoeWVhciA+PSB0bV9u b3cudG1feWVhciAtIDEpOwotCQkJdGltZXN0YW1wX3JlbW90ZS50bSA9IHRtX3BhcnNlZDsKLQkJ CXRpbWVzdGFtcF9yZW1vdGUudG0udG1feWVhciA9IHllYXI7Ci0JCQl0aW1lc3RhbXBfcmVtb3Rl LnRtLnRtX2lzZHN0ID0gLTE7Ci0JCQl0aW1lc3RhbXBfcmVtb3RlLnVzZWMgPSAwOwotCQkJaWYg KG1rdGltZSgmdGltZXN0YW1wX3JlbW90ZS50bSkgPAotCQkJICAgIHRfbm93ICsgNyAqIDI0ICog NjAgKiA2MCkKKwkJbXNnbGVuID0gc3RybGVuKG1zZyk7CisJCWZvciAoaSA9IDA7IGkgPCBNSU4o TUFYSE9TVE5BTUVMRU4sIG1zZ2xlbik7IGkrKykgeworCQkJaWYgKG1zZ1tpXSA9PSAnICcpIHsK KwkJCQlpZiAoUmVtb3RlSG9zdG5hbWUpIHsKKwkJCQkJbXNnW2ldID0gJ1wwJzsKKwkJCQkJZnJv bSA9IG1zZzsKKwkJCQl9CisJCQkJbXNnICs9IGkgKyAxOwogCQkJCWJyZWFrOwotCQl9Ci0JCXRp bWVzdGFtcCA9ICZ0aW1lc3RhbXBfcmVtb3RlOwotCX0gZWxzZQotCQl0aW1lc3RhbXAgPSBOVUxM OwotCi0JLyoKLQkgKiBBIHNpbmdsZSBzcGFjZSBjaGFyYWN0ZXIgTVVTVCBhbHNvIGZvbGxvdyB0 aGUgSE9TVE5BTUUgZmllbGQuCi0JICovCi0JbXNnbGVuID0gc3RybGVuKG1zZyk7Ci0JZm9yIChp ID0gMDsgaSA8IE1JTihNQVhIT1NUTkFNRUxFTiwgbXNnbGVuKTsgaSsrKSB7Ci0JCWlmIChtc2db aV0gPT0gJyAnKSB7Ci0JCQlpZiAoUmVtb3RlSG9zdG5hbWUpIHsKLQkJCQltc2dbaV0gPSAnXDAn OwotCQkJCWZyb20gPSBtc2c7CiAJCQl9Ci0JCQltc2cgKz0gaSArIDE7Ci0JCQlicmVhazsKKwkJ CS8qCisJCQkgKiBTdXBwb3J0IG5vbiBSRkMgY29tcGxpYW50IG1lc3NhZ2VzLCB3aXRob3V0IGhv c3RuYW1lLgorCQkJICovCisJCQlpZiAobXNnW2ldID09ICc6JykKKwkJCQlicmVhazsKIAkJfQot CQkvKgotCQkgKiBTdXBwb3J0IG5vbiBSRkMgY29tcGxpYW50IG1lc3NhZ2VzLCB3aXRob3V0IGhv c3RuYW1lLgotCQkgKi8KLQkJaWYgKG1zZ1tpXSA9PSAnOicpCi0JCQlicmVhazsKKwkJaWYgKGkg PT0gTUlOKE1BWEhPU1ROQU1FTEVOLCBtc2dsZW4pKSB7CisJCQlkcHJpbnRmKCJJbnZhbGlkIEhP U1ROQU1FIGZyb20gJXM6ICVzXG4iLCBmcm9tLCBtc2cpOworCQkJcmV0dXJuOworCQl9CiAJfQot CWlmIChpID09IE1JTihNQVhIT1NUTkFNRUxFTiwgbXNnbGVuKSkgewotCQlkcHJpbnRmKCJJbnZh bGlkIEhPU1ROQU1FIGZyb20gJXM6ICVzXG4iLCBmcm9tLCBtc2cpOwotCQlyZXR1cm47Ci0JfQog CiAJLyogUmVtb3ZlIHRoZSBUQUcsIGlmIHByZXNlbnQuICovCiAJcGFyc2Vtc2dfcmZjMzE2NF9h cHBfbmFtZV9wcm9jaWQoJm1zZywgJmFwcF9uYW1lLCAmcHJvY2lkKTsK --0000000000005a72e8056f40e3c2-- From owner-freebsd-stable@freebsd.org Fri Jun 22 20:42:23 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D07151026BAE for ; Fri, 22 Jun 2018 20:42:23 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5A08E80DD4 for ; Fri, 22 Jun 2018 20:42:23 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w5MKgHen008615; Fri, 22 Jun 2018 13:42:24 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: In-Reply-To: <20180623.025635.943064292669730543.yasu@utahime.org> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Yasuhiro KIMURA" Subject: Re: Console is broken after updating to 11.2-RELEASE Date: Fri, 22 Jun 2018 13:42:23 -0700 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 20:42:24 -0000 On Sat, 23 Jun 2018 02:56:35 +0900 (JST) "Yasuhiro KIMURA" said > From: "Chris H" > Subject: Re: Console is broken after updating to 11=2E2-RELEASE > Date: Fri, 22 Jun 2018 06:13:39 -0700 >=20 > > Try adding the following to your loader=2Econf(5) file > > (/boot/loader=2Econf): > >=20 > > # Load SysCons driver > > kern=2Evty=3Dsc > > # noisy boot > > boot_verbose=3D"YES" > >=20 > > Hope this helps! >=20 > Thank you for information=2E I added above lines to /boot/loader=2Econf > and rebooted system=2E Then all boot messages are displayed and console > works fine! WooHoo! :-) I could make further observations based on *why* that worked=2E But several are likely, and I don't have enough info on your hardware=2E But now that you are no longer "blind"=2E You should have little trouble sorting out the cause=2E --Chris >=20 > --- > Yasuhiro KIMURA > _______________________________________________ > freebsd-stable@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd=2Eorg" From owner-freebsd-stable@freebsd.org Fri Jun 22 20:43:30 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D16361026BF0; Fri, 22 Jun 2018 20:43:30 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from mx2.enfer-du-nord.net (mx2.enfer-du-nord.net [IPv6:2001:41d0:401:2100::5:8a0e]) (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 5AABD80E88; Fri, 22 Jun 2018 20:43:30 +0000 (UTC) (envelope-from trashcan@ellael.org) Received: from [IPv6:2003:e9:7f1b:7801:54b7:5afc:c9f5:e023] (p200300E97F1B780154B75AFCC9F5E023.dip0.t-ipconnect.de [IPv6:2003:e9:7f1b:7801:54b7:5afc:c9f5:e023]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx2.enfer-du-nord.net (Postfix) with ESMTPSA id 41C9Wd4McDz4rV; Fri, 22 Jun 2018 22:43:25 +0200 (CEST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) From: Michael Grimm In-Reply-To: Date: Fri, 22 Jun 2018 22:43:24 +0200 Cc: "ed@FreeBSD.org" , theis@gmx.at, Gleb Smirnoff , FreeBSD-STABLE Mailing List , Mailing List FreeBSD Ports Content-Transfer-Encoding: quoted-printable Message-Id: <636B4CDC-CAF6-4AF8-B025-00C3CC9D826C@ellael.org> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> <851C065F-0E02-425C-B4AF-8FCE0E405F8E@ellael.org> <1A5B44D8-28B0-49C9-B88D-EE6EBEE8788D@ellael.org> To: Ed Schouten X-Mailer: Apple Mail (2.3445.8.2) X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.kaan-bock.lan X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 20:43:31 -0000 On 22. Jun 2018, at 22:28, Ed Schouten wrote: > 2018-06-22 22:06 GMT+02:00 Michael Grimm : >> After applying your patch: >> Jun 22 21:22:01 HOSTNAME [31033]: NOTICE = [JAILNAME] Unban x.x.x.x >>=20 >> Watch: 'fail2ban.actions' -the service- is missing. >=20 > That's likely due to the fact that it now interprets the first word in > the message as the remote hostname, which gets discarded. >=20 > Attached is a somewhat refined patch that only tries to parse the > hostname in remote messages if they are preceded by a timestamp. If > the timestamp is missing, it assumes the entire payload is the > message. Can you give this one a try? Thanks! Great, you fixed it again in very short time, and I really do appreciate = this! Now with patch v2: Jun 22 22:39:59 HOSTNAME fail2ban.actions = [72605]: NOTICE [JAILNAME] Restore Ban x.x.x.x Thank you very, very much, Michael From owner-freebsd-stable@freebsd.org Fri Jun 22 20:48:45 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C25731026E87; Fri, 22 Jun 2018 20:48:45 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (plan-b.pwste.edu.pl [IPv6:2001:678:618::40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4276D81299; Fri, 22 Jun 2018 20:48:44 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (zarychtam@localhost [127.0.0.1]) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPS id w5MKmg34065375 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 22 Jun 2018 22:48:42 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=plan-b.pwste.edu.pl; s=plan-b-mailer; t=1529700522; bh=RiAVHBADVEFsiEMzOtwKxy1FREkJHhB1noQALE2M7lU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=fqEj2BHCa4df3aP/sfTaTv8rx3I+LbWTnHsdNG41oqKu8TXH1U/DbcfVczHCLpOyk KLR6Uur5pwKAFLnXeZIDtrgIIgT0/tQabfCacRek3c+1Nq2xl0TQZb6AQJXRaroBch YMQnyJTThWsDNt8ZJk5Q88yIHSdWu1cpLuPlDNrKGOgDRgei/t0iy4VhZ0cB7C64gi mgjLAaAPtnywtMM55CHijTf4RNh5DPZTDdeJy3UfdUkZ+Tsh8frbCnlDntb2u2R+2t Ivn9DwaAiqRbBo8ttfqRpgfBrNHmI8mf1EFb5imG0cc75VZ7AsLNgmz+GBwDN3CG98 jqAYVUj2+FRiw== Received: (from zarychtam@localhost) by plan-b.pwste.edu.pl (8.15.2/8.15.2/Submit) id w5MKmftA065374; Fri, 22 Jun 2018 22:48:41 +0200 (CEST) (envelope-from zarychtam) Date: Fri, 22 Jun 2018 22:48:41 +0200 From: Marek Zarychta To: Ed Schouten Cc: Michael Grimm , "ed@FreeBSD.org" , theis@gmx.at, Gleb Smirnoff , FreeBSD-STABLE Mailing List , Mailing List FreeBSD Ports Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) Message-ID: <20180622204841.GA65261@plan-b.pwste.edu.pl> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 20:48:46 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 22, 2018 at 09:11:06PM +0200, Ed Schouten wrote: > Hi Marek, >=20 > [ +glebius ] >=20 > Thanks for reporting this! >=20 > 2018-06-22 18:54 GMT+02:00 Michael Grimm : > >> Failed to parse TIMESTAMP from x.x.x.x: 12403: Jun 22 17:31:38 CEST: > >> %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17, > >> changed state to down > > > > Ah, yes! Haven't thought about running syslogd in debugging mode: > > > > Failed to parse TIMESTAMP from x.x.x.x: fail2ban.filter [79598]= : INFO [=E2=80=A6] >=20 > This is interesting. As fail2ban uses Python's logging framework, I > managed to reproduce this with the following script: >=20 > #!/usr/bin/env python3 > import logging.handlers > logging.basicConfig(handlers=3D[ > logging.handlers.SysLogHandler( > '/var/run/log', facility=3Dlogging.handlers.SysLogHandler.LOG_LOC= AL7) > ]) > logging.warning('Hi') >=20 > This will write the following message to syslogd: >=20 > sendto(3,"<188>WARNING:root:Hi\0",21,0,NULL,0) =3D 21 (0x15) >=20 > This message gets rejected by syslogd, due to the change made in > r326573, which later got adjusted by me and subsequently MFCed: >=20 > https://svnweb.freebsd.org/base?view=3Drevision&revision=3D326573 >=20 > Gleb, what are your thoughts on the attached patch? It alters syslogd > to let the 'legacy' RFC 3164 parser also accept messages without a > timestamp. The time on the syslogd server will be used instead. >=20 > Michael, Marek, could you please give this patch a try? Thanks! >=20 Hi Ed, Thank you for expedited effort. Patch compiles fine and I can confirm, that it resolves the issue. --=20 Marek Zarychta --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEMOqvKm6wKvS1/ZeCdZ/s//1SjSwFAlstYKYACgkQdZ/s//1S jSyQSAf9EztYw09oXL1mifsFNQ+Zn909WsKbsP180+wGeilkmfDUhO2q9AeWr2ut cyNErFRUpQBIpAMwSONytP5Hv/FXliPX6QnGes/3/6TjvPvjK+v7ZxQo94+HUOnH sXZq857cN3D91riUcKXsijTxlcTrWCWtdxYiJXueQ41AQHI6fDdNM04scAPjo9X/ TMpppR7KL8hIvag22kXVM4flZZGx2m9Upf1QtiVHUjvmXNr7pYgvh1Wz69uTkjNJ OJh8QAXxA8ekVoC/J7ukwJmecFaHXq8UmUWTnyHwo+1JNyYPmD6pZhRIXbtLVYUP 1LliXczjGBdchXnjYiiD5Ux7NWWJsg== =YKxF -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- From owner-freebsd-stable@freebsd.org Fri Jun 22 20:52:55 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A355110271BE for ; Fri, 22 Jun 2018 20:52:55 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660058.outbound.protection.outlook.com [40.107.66.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2A260817DC for ; Fri, 22 Jun 2018 20:52:54 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM (52.132.44.24) by YTOPR0101MB1291.CANPRD01.PROD.OUTLOOK.COM (52.132.45.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.884.21; Fri, 22 Jun 2018 20:52:53 +0000 Received: from YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::d0eb:3783:7c99:2802]) by YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM ([fe80::d0eb:3783:7c99:2802%3]) with mapi id 15.20.0863.016; Fri, 22 Jun 2018 20:52:53 +0000 From: Rick Macklem To: Yasuhiro KIMURA , "bsd-lists@BSDforge.com" CC: "freebsd-stable@freebsd.org" Subject: Re: Console is broken after updating to 11.2-RELEASE Thread-Topic: Console is broken after updating to 11.2-RELEASE Thread-Index: AQHUCmmNE3eSGRsXEUSl8cq4SldFVKRsv7kJ Date: Fri, 22 Jun 2018 20:52:53 +0000 Message-ID: References: <20180623.025635.943064292669730543.yasu@utahime.org>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1291; 7:frZpQDbf3T7s2JNBo7X41hBvO0ev1nj6Na8ojVFV+dwP7AiK32DXtqiLUbr/sPfIxinFRcodCGiklehIDdkttH7SsI4HJ6Pt4nu0tHaP5yEr8L5NJYkQnXEh+Q1vltyJTAFhuiATysm0sqc8RIkX0ocFeP948nvTvzNSzLSSMsivGNBGYuUIN0CvKM/pDrUJ+tuLResOISxJasufjjP9CNoJ5t2NWSWFKzQ1lyzTNfmJ1ohbj8nPTkgLAUsy7gf7 x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: b19aeab9-967d-41cc-2cc3-08d5d8821fce x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600026)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB1291; x-ms-traffictypediagnostic: YTOPR0101MB1291: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123558120)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:YTOPR0101MB1291; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB1291; x-forefront-prvs: 071156160B x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(396003)(376002)(39860400002)(39380400002)(366004)(189003)(199004)(2906002)(7696005)(229853002)(4326008)(74482002)(55016002)(25786009)(9686003)(105586002)(6246003)(6436002)(106356001)(81166006)(68736007)(81156014)(14454004)(8676002)(305945005)(8936002)(99286004)(5250100002)(74316002)(2501003)(486006)(97736004)(478600001)(2900100001)(110136005)(446003)(316002)(786003)(11346002)(76176011)(53936002)(345774005)(26005)(476003)(5660300001)(186003)(33656002)(102836004)(3280700002)(86362001)(6506007)(3660700001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1291; H:YTOPR0101MB0953.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: ts5XAYbcqTZm8TzgWLkaaghhqRkeSCt8Ro4VqVcMN+UPUhA/tnRgXliGR6RUgqx1tj70O69WxsQkIqR83ys+koTIYP4/pXA16DnbkIlTIHGRiaknPwFwLD0je/GM9fq8tJQM2w9Re9WeIfXHWtLk8v29tbs6Pfgjhm9EgwBv2lUgICyFPfV9ffWQeReSTvEPG4HLN+eA67xiRoB4t6jwemgYG+i6jUcmB4FwKvohUqgmfnHLK0UDyE9PCODIB8HiqyOtSC3ZH8NH3UuTFWZnECsgTEg1X6bG6UXBW0S+gotqdCRyfnbLnpFnT421iH8bEpT1KvStsXuAuSZIX77ptkVhcZmjQZweYBsDiCTmMsg= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: b19aeab9-967d-41cc-2cc3-08d5d8821fce X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jun 2018 20:52:53.2809 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1291 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 20:52:55 -0000 Chris H wrote: [stuff snipped] >> >> Thank you for information. I added above lines to /boot/loader.conf >> and rebooted system. Then all boot messages are displayed and console >> works fine! > >WooHoo! :-) > >I could make further observations based on *why* that worked. But several >are likely, and I don't have enough info on your hardware. But now that >you are no longer "blind". You should have little trouble sorting out the >cause. I have no idea if this helps, but running a fairly recent head kernel, when= I would switch virtual consoles, the screen would go blank until I power cycled the= SVGA monitor. I switched to "sc" and the problem went away. (This is an old Pentium 4 with what dmesg calls a "Generic VGA display".) I don't see the same problem with a laptop of the same era. Just in case it gives you a hint w.r.t. the problem, rick From owner-freebsd-stable@freebsd.org Fri Jun 22 20:57:19 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4A451027398 for ; Fri, 22 Jun 2018 20:57:18 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 5D3D981B80 for ; Fri, 22 Jun 2018 20:57:18 +0000 (UTC) (envelope-from ed@nuxi.nl) Received: by mail-ed1-x52e.google.com with SMTP id c1-v6so1913602edt.2 for ; Fri, 22 Jun 2018 13:57:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nuxi-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=aSeKoHXXK+yp9ZUPdmyZU8+LYzQ7jlViYk6lFa0wMGE=; b=ByZip7B+y2k2k9usVHtNELJswkg/g5KOndTcH4ckzh2kgJYmsBa0I/dmj3BHssvLcB 4m4hdR7ed71dmmGH1ZUz+k0Ojy0sgtjknB7OtQl8bafniOFDCSQEyUQ0ZuNpf9vqu58o OdkSpYIJ0kIsZ1+An2rHA+pIaQU5wjEnayaxvinK18LpLOUi4d9AOJhdkk/LjIV+rFaY djllknRMnTyOluu1uQe9/OOzmaLClTIfJ3nnJ27b+Wv3STd4+isTZqSoU8yvRMFVTRNh SwaFqioM0oavDbdE0WuxDCsWKjIwd+shi5qNuTRrZwQiER/aeA8yfzjqNimTkZ8QLofo J8lg== 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=aSeKoHXXK+yp9ZUPdmyZU8+LYzQ7jlViYk6lFa0wMGE=; b=eo+vMU7eFIQ+8cX2VOgNm8swyG5pu9TJ7AC74dwznGM4oq3QLQovydbxlPdChaWWTW VYucSIf0wjmrwdSg0Jl8Cea7phOz6/Xjo/MLtVjkibaqFe/ZQi7pfwIkcrqhdDgxzGxN ATMVuLucgFCm7qeusjl3BrIUK9ZJY8/tzhvoCNncl2AWsa2Skux/FEYJBmakW1oBW8mr cmwan6/BCrrkLOm2AIA1kOG7ZQbCtZXTILJ2bhgAv1rd0IBno4irqiFDFgC94liWsBZn 1wxsnQfJBvOBZL2f8AmLDC4ny4D4wjS/7EUvNVukDDXpJvlOyfVAivYhtnS2yT80cjhl 8DBg== X-Gm-Message-State: APt69E0kEmPSLys3n9yGD3wKVkIJOj/iUlHlH6tyMzqrn6iqjNDQmyU+ 6ct+CHV1wRERkMhzSOKekGAQfQ4DZtyKGDfzxOwpfw== X-Google-Smtp-Source: ADUXVKJ/UfWlRFgzKmWrLPe39CBCI9Veqg5K1/C0gwiFv8MX+z/rW1U4162YXKxxRjJAn+kcs8mGSZhuogLerwkzoJc= X-Received: by 2002:a50:a4c6:: with SMTP id x6-v6mr2967679edb.247.1529701037312; Fri, 22 Jun 2018 13:57:17 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a50:8e0d:0:0:0:0:0 with HTTP; Fri, 22 Jun 2018 13:56:46 -0700 (PDT) In-Reply-To: <20180622204841.GA65261@plan-b.pwste.edu.pl> References: <590A1B87-464D-455C-A03D-9908EB7AF286@ellael.org> <20180622155922.GA61217@plan-b.pwste.edu.pl> <697FFEFE-6AFB-45CE-ADCD-4DB10286E68B@ellael.org> <20180622204841.GA65261@plan-b.pwste.edu.pl> From: Ed Schouten Date: Fri, 22 Jun 2018 22:56:46 +0200 Message-ID: Subject: Re: py-fail2ban turned silent after syslogd rollout (r335059, stable/11) To: Marek Zarychta Cc: Michael Grimm , "ed@FreeBSD.org" , theis@gmx.at, Gleb Smirnoff , FreeBSD-STABLE Mailing List , Mailing List FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 20:57:19 -0000 Hi Michael, Marek, 2018-06-22 22:48 GMT+02:00 Marek Zarychta : > Patch compiles fine and I can confirm, that it resolves the issue. Thanks for testing to both of you. Really appreciated. I've just committed this patch as r335565. As it is a bit more intrusive than the previous patch I wrote, let's give this a week to settle in HEAD before merging it to 11-STABLE. I'll close PR 229236 once it's been merged. -- Ed Schouten Nuxi, 's-Hertogenbosch, the Netherlands From owner-freebsd-stable@freebsd.org Fri Jun 22 21:13:32 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB49C1027AEA; Fri, 22 Jun 2018 21:13:32 +0000 (UTC) (envelope-from SRS0=d2j5=JI=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 62BE98281B; Fri, 22 Jun 2018 21:13:32 +0000 (UTC) (envelope-from SRS0=d2j5=JI=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8734B28454; Fri, 22 Jun 2018 23:13:24 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id B9E3928451; Fri, 22 Jun 2018 23:13:17 +0200 (CEST) To: freebsd-jail@freebsd.org Cc: freebsd-stable Stable From: Miroslav Lachman <000.fbsd@quip.cz> Subject: jail related inconsistencies in FreeBSD tools parameters Message-ID: <8da11edc-7d3f-a410-23eb-4ea672c5d65c@quip.cz> Date: Fri, 22 Jun 2018 23:13:17 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 21:13:33 -0000 I don't know if it is better to discuss it in jail@ or stable@ list so a do cross-post. FreeBSD has many jail aware utilities but they are inconsistent in taking JID as parameter. For example "sockstat" takes -j JID "Show only sockets belonging to the specified jail ID" and it means numeric ID only. On the other hand "ps" takes -J JID "This may be either the jid or name of the jail. Use -J 0 to display only host processes." The same apply for "top", it understands jid as a number or name of the jail too. Then again "cpuset" takes only numerical ID of the jail... Shouldn't it be consistent across all FreeBSD base utilities so all of them can use numerical ID and name? Should I file a PR for it? Miroslav Lachman PS: I am on FreeBSD 10.4 so I don't know if something is different in newer branches From owner-freebsd-stable@freebsd.org Fri Jun 22 21:46:02 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BB291000B59; Fri, 22 Jun 2018 21:46:02 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8A928437C; Fri, 22 Jun 2018 21:46:01 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w5MLjuVB013785; Fri, 22 Jun 2018 14:46:02 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "freebsd-stable Stable" , In-Reply-To: <8da11edc-7d3f-a410-23eb-4ea672c5d65c@quip.cz> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Miroslav Lachman" <000.fbsd@quip.cz> Subject: Re: jail related inconsistencies in FreeBSD tools parameters Date: Fri, 22 Jun 2018 14:46:02 -0700 Message-Id: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 21:46:02 -0000 On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" <000=2Efbsd@quip=2Ecz> sa= id > I don't know if it is better to discuss it in jail@ or stable@ list so a= =20 > do cross-post=2E >=20 > FreeBSD has many jail aware utilities but they are inconsistent in=20 > taking JID as parameter=2E >=20 > For example "sockstat" takes -j JID "Show only sockets belonging to the= =20 > specified jail ID" and it means numeric ID only=2E > On the other hand "ps" takes -J JID "This may be either the jid or name= =20 > of the jail=2E Use -J 0 to display only host processes=2E" > The same apply for "top", it understands jid as a number or name of the= =20 > jail too=2E > Then again "cpuset" takes only numerical ID of the jail=2E=2E=2E >=20 > Shouldn't it be consistent across all FreeBSD base utilities so all of=20 > them can use numerical ID and name? Good idea! Are you offering to create a patch? ;-) It'd be my guess that given they weren't all created at the same time, nor the same individual; that (quite probably?) the "jail" additions were also added at different times, and by different people=2E So I'd imagine that unless someone with a commit bit decides one day they'd like to take that on=2E Someone(tm) maybe you? will need to propose a patch=2E :-) --Chris >=20 > Should I file a PR for it? >=20 > Miroslav Lachman >=20 > PS: I am on FreeBSD 10=2E4 so I don't know if something is different in=20 > newer branches > _______________________________________________ > freebsd-stable@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd=2Eorg" From owner-freebsd-stable@freebsd.org Fri Jun 22 22:03:53 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32FE210011EE; Fri, 22 Jun 2018 22:03:53 +0000 (UTC) (envelope-from SRS0=d2j5=JI=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B4B5084CCF; Fri, 22 Jun 2018 22:03:52 +0000 (UTC) (envelope-from SRS0=d2j5=JI=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 9152128422; Sat, 23 Jun 2018 00:03:50 +0200 (CEST) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 7BD1628411; Sat, 23 Jun 2018 00:03:48 +0200 (CEST) Subject: Re: jail related inconsistencies in FreeBSD tools parameters To: bsd-lists@BSDforge.com Cc: freebsd-stable Stable , freebsd-jail@freebsd.org References: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Sat, 23 Jun 2018 00:03:48 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.3 MIME-Version: 1.0 In-Reply-To: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 22:03:53 -0000 Chris H wrote on 2018/06/22 23:46: > On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" <000.fbsd@quip.cz> > said > >> I don't know if it is better to discuss it in jail@ or stable@ list so >> a do cross-post. >> >> FreeBSD has many jail aware utilities but they are inconsistent in >> taking JID as parameter. >> >> For example "sockstat" takes -j JID "Show only sockets belonging to >> the specified jail ID" and it means numeric ID only. >> On the other hand "ps" takes -J JID "This may be either the jid or >> name of the jail.  Use -J 0 to display only host processes." >> The same apply for "top", it understands jid as a number or name of >> the jail too. >> Then again "cpuset" takes only numerical ID of the jail... >> >> Shouldn't it be consistent across all FreeBSD base utilities so all of >> them can use numerical ID and name? > Good idea! Are you offering to create a patch? ;-) > It'd be my guess that given they weren't all created at the same time, nor > the same individual; that (quite probably?) the "jail" additions were also > added at different times, and by different people. So I'd imagine that > unless someone with a commit bit decides one day they'd like to take that > on. Someone(tm) maybe you? will need to propose a patch. :-) If I can understand C sources I will create the patch by myself instead of just posting here. Unfortunately I am able to code in sh, php and a bit of javascript and perl but no C. :) Miroslav Lachman From owner-freebsd-stable@freebsd.org Fri Jun 22 22:40:35 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E9C81001DEE for ; Fri, 22 Jun 2018 22:40:35 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qt0-x243.google.com (mail-qt0-x243.google.com [IPv6:2607:f8b0:400d:c0d::243]) (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 20AFB85FF5 for ; Fri, 22 Jun 2018 22:40:34 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-qt0-x243.google.com with SMTP id 92-v6so2891211qta.11 for ; Fri, 22 Jun 2018 15:40:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LjzGVZXi3sHXL7lqsW1PZqp2UK6bqmeOVc9l9uhRCSM=; b=OFIxIDEHkUGPMNqhE7aa1qzAn2jP8TjKEeIYA+zveWA14bw1k/J+P2t940JDVKWJxh +hKkdiqJeRIXlNhRgpzAL+wLUZJBk51TrOndm8rsGEtNZ78YfigiXM04A4NnRxP9wvpr DpXL/j2axrcMBbh1hfSQD/doS5I32w/K0fYfTwkujp3px4Qds49Zrzbz/Afv254+EgAk 87r0ZXiZGYtBCbmjRbmtce80R+Wk9RSiAcMzfW6CLedWdnqSQf4PsA6M4EwD2ZFWEFas yzemR9jGrJx7Laha7P3RLD3wNHADizAkVbzSldpRtwrVKmAdBCbWnRjtXWGzfTsIDMWZ rzTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LjzGVZXi3sHXL7lqsW1PZqp2UK6bqmeOVc9l9uhRCSM=; b=rBq9oZAsRsPlEkcy/BADr0wQafC/dB2QKSyWaTL0c28l9MCDqelC3mnvG6NY8h4UnM 6L/2eZ/j7eQUWp+7o++iLao2tKoEuLzzgoWT+2cSjFAjoAdMK4LdI9+pDjsc3CsXHJGT 0XlDiFW6JQlMRPobRkUr+8jSElG8RTQRwRfZzKjCvk/inKOiZV14Eprq57cxU795397y QnT7O0G5qhqso3qqNv/QWmFBT6amF4cxtvSeCSK9wWu5ba4jrha+SMg2hdG0kNQ6rJY2 E7t3KmlkJpwHkV4remCI9TKZ6MO3uBhVCg1S1FNrJqYh2HhqyOEQMofoP5X/kDy8O0ip mZSA== X-Gm-Message-State: APt69E0ldOYNy9WUhW3Ahd2Qqk1CVJMefCMsuPGz74CulH4NvuwVubPV rZcOPoxy8BDDReC10HaM/Pe0Bw== X-Google-Smtp-Source: AAOMgpcT/TcunUz2UxtEDdDhohG395tTS/MT1mliPuEZ3RfWqyRBjLFH37AckJ7Mka3TsKE28kvddg== X-Received: by 2002:a0c:e28a:: with SMTP id r10-v6mr3198005qvl.172.1529707234308; Fri, 22 Jun 2018 15:40:34 -0700 (PDT) Received: from ?IPv6:2600:1017:b808:4424:6d47:48e2:6d5b:f23c? ([2600:1017:b808:4424:6d47:48e2:6d5b:f23c]) by smtp.gmail.com with ESMTPSA id k30-v6sm7712103qtc.31.2018.06.22.15.40.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jun 2018 15:40:33 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: ATI video problem - slow desktop - 100% cpu load [semi-solved] From: Mark Saad X-Mailer: iPhone Mail (15F79) In-Reply-To: <86zhznbi8u.fsf@elm.localnet> Date: Fri, 22 Jun 2018 18:40:31 -0400 Cc: freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180619212311.GA36401@quark.hightek.org> <20180620194347.GA87224@quark.hightek.org> <20180622015757.GA52468@quark.hightek.org> <86zhznbi8u.fsf@elm.localnet> To: Carl Johnson X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 22:40:35 -0000 Vincent I used the scfb driver in openbsd land for a work project . Currently I am= using 11-STABLE with the Radeon driver but at one point I had a different c= ard under 11.0 that didn=E2=80=99t work unless I used the scfb driver .=20 --- Mark Saad | nonesuch@longcount.org > On Jun 21, 2018, at 11:41 PM, Carl Johnson wrote: >=20 > Vincent Stemen writes: >=20 >> You must load radeonkms.ko after the system is fully booted. >>=20 >> # kldload radeonkms >>=20 >> That automatically loads the other 3 modules and initializes the console w= here >> the console text goes into higher resolution mode. Then X and the deskto= p >> environments work and seem to be fully functional, including transparency= , etc. >>=20 >> So I can either put it in /etc/rc.local, to be run at boot time, or put i= t in >> an X startup script wrapper. Note that it must be run prior to startx be= cause >> it must be loaded before launching the X server. So it cannot be put in >> ~/.xinitrc. >=20 > Have you tried loading it with kld_list in /etc/rc.conf? Those get > loaded during boot, but it might be late enough to work. That would be > automated, so it might be a little more convenient. > --=20 > Carl Johnson carlj@peak.org >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Fri Jun 22 22:58:55 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C727A10027DB for ; Fri, 22 Jun 2018 22:58:55 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (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 4F58886BC2 for ; Fri, 22 Jun 2018 22:58:55 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-qk0-x241.google.com with SMTP id q70-v6so4595621qke.1 for ; Fri, 22 Jun 2018 15:58:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:date:subject:message-id :to; bh=zYs6xOZqxidQFRkc+Y0pxM/1Viux/s4U3mwmqsRI9es=; b=pW7meE1RmYnp6dm7Voq6jUQFqTVVyTD2fysb49E6QUwLaTr/K+ROz1cuOUT5whkafF Ms5EL3rRR/05W15y6vOUGc37z0YJUKUeZPCF+Y9u0ECYZiqbG3gAGaGSgYnhzubDcNxO mbcEkW5ZJ/ceQkZnQOtBTLqsbjRvR+bL2RDwSNftERttkvfTd2184KBr0BrmFybIihBF RFoJGFk27y58RIV++32XZAS7guaUg80C44cwQ84CMyuIK5a2qiBV9ml6aL6dkFto8KlY JYAjjfYL3/8oJmxUh27OezCYXjQ7F8RnxB/gH5OJB16G1ZtKn5mdjy8pU1ANuOlgPsYv RM0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:to; bh=zYs6xOZqxidQFRkc+Y0pxM/1Viux/s4U3mwmqsRI9es=; b=cjL8GXb3eB3MJtl1NNc8HWk4AN8g9g4l8OV2Lm5+DXRLM82IRp/Dh+I6d0T+rqxzmQ qU9BtnJ1ZlixvfMFsPPgsuFqguYk4aifvzsIIB5N27pAyIG9PR3/nycFBepOPUMIBbVV wW4Dk+xwcs36e/JKYllsAR5VrIld3+gGmVmjpRku/Jzqst9yfKUDKvyIr58gT1VV+I1J EJir4mq2dKcMKYbaK67ma6SDKe+uOKm6Ggc4rHCjhReB7IvKmc595RAsT4BFnub2uT81 4LxG59mTQZKTxBVgxGJiO+qbAG5enxjj7aS2oXxFxh7K3h2gxI766RdtmGmyqHMZ6yzW CbkA== X-Gm-Message-State: APt69E35ofbpkM5FAxUUZBngxsyX0qmwQYtj5J0OQdFLgKIK7OiGciE5 +F+B/vd5v91VIiAcrqZhUgZinhpxr1Y= X-Google-Smtp-Source: AAOMgpdUnORD7UTp5rg4+BjqZhL6XnHhkSF9GREv8gmSH1E9b6BCwS4seeztdBX8cm0BC22ZLatQug== X-Received: by 2002:a37:a38c:: with SMTP id m134-v6mr3215076qke.57.1529708334631; Fri, 22 Jun 2018 15:58:54 -0700 (PDT) Received: from ?IPv6:2600:1017:b808:4424:6d47:48e2:6d5b:f23c? ([2600:1017:b808:4424:6d47:48e2:6d5b:f23c]) by smtp.gmail.com with ESMTPSA id m128-v6sm6220590qkd.33.2018.06.22.15.58.53 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Jun 2018 15:58:53 -0700 (PDT) From: Mark Saad Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Fri, 22 Jun 2018 18:58:50 -0400 Subject: Anyone have a summary of what kernel option RSS does ? / netisr oddness . Message-Id: To: freebsd-stable@freebsd.org X-Mailer: iPhone Mail (15F79) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 22 Jun 2018 22:58:56 -0000 Hi all On a recount 11-STABLE I see that the interaction with netisr and rss has c= hanged. Forgive me if this is clumsy but I don=E2=80=99t quite get what chan= ges were. On 10-Stable when I have a solarflare or intel Ixgbe card I would get a kern= el thread per rss queue per card and a netirs queue:bucket thread per cpu ( o= r tuned to a value I define < ncpus ) . However on recent 11-STABLE about wh= en the RSS kernel option was imported or added; I now get one netisr queue:b= ucket for the whole system and no tuning effects how many threads are create= d. =20 Second part I started looking into the kernel rss option and I wanted the be= tter understand what it was doing ? Enabling it and the associate protocol b= lock ? Option gave me 64 queues and no clear way to tune them or constrain t= hem to the numa domain of the card companies consuming them I could not find= options_rss.h either . So is there a commit anyone can direct me to to for= more insight? Is there a write up on it somewhere?=20 Thanks again .=20 --- Mark Saad | nonesuch@longcount.org= From owner-freebsd-stable@freebsd.org Sat Jun 23 15:30:26 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC8D51025091; Sat, 23 Jun 2018 15:30:26 +0000 (UTC) (envelope-from jamie@freebsd.org) Received: from gritton.org (gritton.org [199.192.165.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gritton.org", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4399086E2F; Sat, 23 Jun 2018 15:30:26 +0000 (UTC) (envelope-from jamie@freebsd.org) Received: from gritton.org ([127.0.0.131]) by gritton.org (8.15.2/8.15.2) with ESMTP id w5NFUBRu095434; Sat, 23 Jun 2018 09:30:11 -0600 (MDT) (envelope-from jamie@freebsd.org) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Sat, 23 Jun 2018 09:30:11 -0600 From: James Gritton To: bsd-lists@bsdforge.com, freebsd-jail@freebsd.org, freebsd-stable Stable Cc: Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: jail related inconsistencies in FreeBSD tools parameters In-Reply-To: References: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> Message-ID: <18000a3b93085c91aeffbca937862786@freebsd.org> X-Sender: jamie@freebsd.org User-Agent: Roundcube Webmail/1.3.6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 23 Jun 2018 15:30:26 -0000 On 2018-06-22 16:03, Miroslav Lachman wrote: > Chris H wrote on 2018/06/22 23:46: >> On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" >> <000.fbsd@quip.cz> said >> >>> I don't know if it is better to discuss it in jail@ or stable@ list >>> so a do cross-post. >>> >>> FreeBSD has many jail aware utilities but they are inconsistent in >>> taking JID as parameter. >>> >>> For example "sockstat" takes -j JID "Show only sockets belonging to >>> the specified jail ID" and it means numeric ID only. >>> On the other hand "ps" takes -J JID "This may be either the jid or >>> name of the jail.  Use -J 0 to display only host processes." >>> The same apply for "top", it understands jid as a number or name of >>> the jail too. >>> Then again "cpuset" takes only numerical ID of the jail... >>> >>> Shouldn't it be consistent across all FreeBSD base utilities so all >>> of them can use numerical ID and name? >> Good idea! Are you offering to create a patch? ;-) >> It'd be my guess that given they weren't all created at the same time, >> nor >> the same individual; that (quite probably?) the "jail" additions were >> also >> added at different times, and by different people. So I'd imagine that >> unless someone with a commit bit decides one day they'd like to take >> that >> on. Someone(tm) maybe you? will need to propose a patch. :-) > > If I can understand C sources I will create the patch by myself > instead of just posting here. Unfortunately I am able to code in sh, > php and a bit of javascript and perl but no C. :) > > Miroslav Lachman Sure, a PR would be handy for this - it's a pretty simple thing to add, and consistency would indeed be a good move. - Jamie From owner-freebsd-stable@freebsd.org Sat Jun 23 15:45:40 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2E3010258DB for ; Sat, 23 Jun 2018 15:45:39 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x230.google.com (mail-yb0-x230.google.com [IPv6:2607:f8b0:4002:c09::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 5F4A388093 for ; Sat, 23 Jun 2018 15:45:39 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x230.google.com with SMTP id a2-v6so3053726ybe.11 for ; Sat, 23 Jun 2018 08:45:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=iO/EAh1E+Si6GTuZtbw5dHoVKJnewrMw2RKzBBsFli0=; b=FimD2RmNVpXpgL/D90IlwqdC+korx4PyoMjClHv5ITkiEBmxh4IDe+PchxQka9vmA1 6Ujs6TVqwHTbugtt9d2x1RH7lH0gdL5e/dHPwxAf/WX1aV38GaOiC+xjz4YGbS3ztu1c tzuL/BcnCa9jM5XOn+FjJZC5s+fnHqjUHu76Y= 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=iO/EAh1E+Si6GTuZtbw5dHoVKJnewrMw2RKzBBsFli0=; b=r8YLIbttbgzIP2lo4Gd6NGnLO/1xuFoxldP6uh7r8j+zmNXX2YA+n3ngNsAP1YwfRV 1F5wUm2JyCaY/1Zx3aI9qY69pigcB9R5Svfym31NA/maHCM1nU3F18YIdDuME3efJhHY avF50y5uFeKJ7QiKQ/cSFy93X8+Oznr+VVxE6+J8tJmFLNIPfVbQQ1iaXQ4+myXw6xy/ jENuxegciCHrpm1c2FH7LRbsxorpW8G3/fB4pGaueCRWZSKlAKjkEg86mYXpv6eZIwT0 S2d0tpz7SZZeWlYT1D5wijDf58bmMYY5w/LKVee5elNoQ5Dmba8jYrcqZGObMhRT6cKF 8LoQ== X-Gm-Message-State: APt69E0w2Ir8YYUCD1k1Vl6zYb9zymqff+XwC7BmFFVjcM3w7rfPVDaV KkcDIVl6DQk1hIjJdpDmWi2jo+F73nRU/yfUZZWhdg== X-Google-Smtp-Source: ADUXVKIMyT1lYPfkwEAkPvKytRbmD5uqQ239YSXvQDsbvN0zqQsA4UZg9D/PN6WFlEUwV1AukOWoR4nbW7o0up8IsOw= X-Received: by 2002:a5b:64c:: with SMTP id o12-v6mr2981316ybq.460.1529768738649; Sat, 23 Jun 2018 08:45:38 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Sat, 23 Jun 2018 08:45:08 -0700 (PDT) In-Reply-To: <18000a3b93085c91aeffbca937862786@freebsd.org> References: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> <18000a3b93085c91aeffbca937862786@freebsd.org> From: Eitan Adler Date: Sat, 23 Jun 2018 08:45:08 -0700 Message-ID: Subject: Re: jail related inconsistencies in FreeBSD tools parameters To: James Gritton Cc: bsd-lists@bsdforge.com, freebsd-jail@freebsd.org, freebsd-stable Stable Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 23 Jun 2018 15:45:40 -0000 On 23 June 2018 at 08:30, James Gritton wrote: > On 2018-06-22 16:03, Miroslav Lachman wrote: >> >> Chris H wrote on 2018/06/22 23:46: >>> >>> On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" <000.fbsd@quip.cz> >>> said >>> >>>> I don't know if it is better to discuss it in jail@ or stable@ list so a >>>> do cross-post. >>>> >>>> FreeBSD has many jail aware utilities but they are inconsistent in >>>> taking JID as parameter. >>>> >>>> For example "sockstat" takes -j JID "Show only sockets belonging to the >>>> specified jail ID" and it means numeric ID only. >>>> On the other hand "ps" takes -J JID "This may be either the jid or name >>>> of the jail. Use -J 0 to display only host processes." >>>> The same apply for "top", it understands jid as a number or name of the >>>> jail too. >>>> Then again "cpuset" takes only numerical ID of the jail... >>>> >>>> Shouldn't it be consistent across all FreeBSD base utilities so all of >>>> them can use numerical ID and name? >>> >>> Good idea! Are you offering to create a patch? ;-) >>> It'd be my guess that given they weren't all created at the same time, >>> nor >>> the same individual; that (quite probably?) the "jail" additions were >>> also >>> added at different times, and by different people. So I'd imagine that >>> unless someone with a commit bit decides one day they'd like to take that >>> on. Someone(tm) maybe you? will need to propose a patch. :-) >> >> >> If I can understand C sources I will create the patch by myself >> instead of just posting here. Unfortunately I am able to code in sh, >> php and a bit of javascript and perl but no C. :) >> >> Miroslav Lachman > > > Sure, a PR would be handy for this - it's a pretty simple thing to add, and > consistency would indeed be a good move. Agreed. I'll review and commit such patches. I'd like to see a single function for taking a "id or name". Ideally it would live in a library, perhaps libjail? -- Eitan Adler From owner-freebsd-stable@freebsd.org Sat Jun 23 15:50:10 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B0C11025B5C; Sat, 23 Jun 2018 15:50:10 +0000 (UTC) (envelope-from jamie@freebsd.org) Received: from gritton.org (gritton.org [199.192.165.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gritton.org", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C480188405; Sat, 23 Jun 2018 15:50:09 +0000 (UTC) (envelope-from jamie@freebsd.org) Received: from gritton.org ([127.0.0.131]) by gritton.org (8.15.2/8.15.2) with ESMTP id w5NFo0Rw096329; Sat, 23 Jun 2018 09:50:00 -0600 (MDT) (envelope-from jamie@freebsd.org) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 23 Jun 2018 09:50:00 -0600 From: James Gritton To: bsd-lists@bsdforge.com, freebsd-jail@freebsd.org, freebsd-stable Stable Cc: Eitan Adler Subject: Re: jail related inconsistencies in FreeBSD tools parameters In-Reply-To: References: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> <18000a3b93085c91aeffbca937862786@freebsd.org> Message-ID: <51718e96f63175e997cb8268381d1070@freebsd.org> X-Sender: jamie@freebsd.org User-Agent: Roundcube Webmail/1.3.6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 23 Jun 2018 15:50:10 -0000 On 2018-06-23 09:45, Eitan Adler wrote: > On 23 June 2018 at 08:30, James Gritton wrote: >> On 2018-06-22 16:03, Miroslav Lachman wrote: >>> >>> Chris H wrote on 2018/06/22 23:46: >>>> >>>> On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" >>>> <000.fbsd@quip.cz> >>>> said >>>> >>>>> I don't know if it is better to discuss it in jail@ or stable@ list >>>>> so a >>>>> do cross-post. >>>>> >>>>> FreeBSD has many jail aware utilities but they are inconsistent in >>>>> taking JID as parameter. >>>>> >>>>> For example "sockstat" takes -j JID "Show only sockets belonging to >>>>> the >>>>> specified jail ID" and it means numeric ID only. >>>>> On the other hand "ps" takes -J JID "This may be either the jid or >>>>> name >>>>> of the jail. Use -J 0 to display only host processes." >>>>> The same apply for "top", it understands jid as a number or name of >>>>> the >>>>> jail too. >>>>> Then again "cpuset" takes only numerical ID of the jail... >>>>> >>>>> Shouldn't it be consistent across all FreeBSD base utilities so all >>>>> of >>>>> them can use numerical ID and name? >>>> >>>> Good idea! Are you offering to create a patch? ;-) >>>> It'd be my guess that given they weren't all created at the same >>>> time, >>>> nor >>>> the same individual; that (quite probably?) the "jail" additions >>>> were >>>> also >>>> added at different times, and by different people. So I'd imagine >>>> that >>>> unless someone with a commit bit decides one day they'd like to take >>>> that >>>> on. Someone(tm) maybe you? will need to propose a patch. :-) >>> >>> >>> If I can understand C sources I will create the patch by myself >>> instead of just posting here. Unfortunately I am able to code in sh, >>> php and a bit of javascript and perl but no C. :) >>> >>> Miroslav Lachman >> >> >> Sure, a PR would be handy for this - it's a pretty simple thing to >> add, and >> consistency would indeed be a good move. > > Agreed. I'll review and commit such patches. I'd like to see a single > function for taking a "id or name". Ideally it would live in a > library, perhaps libjail? It already lives there: jail_getid(3) - Jamie From owner-freebsd-stable@freebsd.org Sat Jun 23 17:27:26 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE14F100010B for ; Sat, 23 Jun 2018 17:27:25 +0000 (UTC) (envelope-from 2yt@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 584058B797 for ; Sat, 23 Jun 2018 17:27:25 +0000 (UTC) (envelope-from 2yt@gmx.com) Received: from carbon.localdomain ([98.127.45.240]) by mail.gmx.com (mrgmx001 [212.227.17.184]) with ESMTPSA (Nemesis) id 0MOw4N-1fZp7D2bN1-006Pd4 for ; Sat, 23 Jun 2018 19:27:17 +0200 To: freebsd-stable@freebsd.org From: David Samms <2yt@gmx.com> Subject: 11.2-RC3 regression - networking igb driver Message-ID: <2b154303-35f8-df8e-5d2f-ea93b8fdad1d@gmx.com> Date: Sat, 23 Jun 2018 11:27:14 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:II3eOmEXUoI2ur4FmaqgZCQGBFg6FjqAP7UrUj14zCKdVkTsIm0 52Hs9kpQ9EIWY+J+snYf8zW2v88FqeVD/sDpCHKjCjAr9pOUmmXBTc9VLdsGFwRKMCSLYm5 qLUEv+kUS6e+1vIWRe0O61lqLAbd7V0Iuh4IKn09kWxR/ZZp9jpyiWRFwrdR1IyhWb/9l+d a1fUo7u7Emmx77DBuyBAA== X-UI-Out-Filterresults: notjunk:1;V01:K0:GCVBxG/ip7k=:GVwN4/NARshE0aLUtVGwMJ oZ4ijvex33cMWzBqWW/oaArp6VjHYAl96dgvQ5rvEio5W+8x/Mmtr5y/jD681ShBhqDs745Sl Q2SBuJhG4dyN8ZsdGqgpx6tR+BcVmnQCzNWz/COusYGrh53Bi+dVXBSUyncuDoQaXQ4IFhaCZ 9Fb5r6RZMi4tF0BJS0pSQ+wL3qs0ELfz/5ujp5iQOFWGJMKcVP0258Xfh9HFQavLQo47atN0s ZP0zKH5rl9EWUHAl/RBN3Nn3kK83/b5hB6XOT/mUvEiRzd1t3EfJQUSEKgE9EvL7KxAKtt3ap 5V42RT6N2FOd69GuBpXi0Lb4LDMK5uoQwNZVpvRtWMtR9kZ5OAtcdrZvZuvHx/5iWOSawlkHV oyuT9z3/kifl4ZJdA2wI1RZjsieG3Sue/9FcnMr4IMJM6x3QcagOnz3xO00+ZgMGAeZ/orExe 9BUswyp+nGHFvk9sLfA8vhZfRDRXPE60/gLqejAJPhzzhj6bMI+FxBCH0Q0onDHOrqJaukptS AMWSUUzVhjTERYZ5kqxY5TxAsZkpLjddvAxvl8O3uW2yR97QBGB+dRADbI6oJjjCmvMZROymk A3Qcu1ds2Eea+YkdX7RACKjYmaSax1GitnH0dMT3B6IW2UdgiYSv48HrNHkz2xIqx6ResVOII 0zh2phuYOA2boFq5PSkFLjM+nEtYqHtCOKcYFGA5n3Kwnoqx6Zk6RH5npkXXHxK4vt51FOxPa CmKbz7Ah/0KOHcFPQ95yy08MN0z6ZRQl2hfin/06mUxT1gYmo01/QefscDb7kIqdPjfqYzrvb odp4IsW X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 23 Jun 2018 17:27:26 -0000 There is a regression in 11.2-RC3 that effects the igb driver for Intels C2000 SoC I354 Quad GbE Controller Supermicro A1SRi-2558F http://www.supermicro.com/products/motherboard/Atom/X10/A1SRi-2558F.cfm This server has run 10.x and 11.x fine up till 11.2-RC3. PROBLEM: with 11.2-RC3 the server boots and gets a network connection to the cable modem, but the interface (igb0) resets every 4-8 second. The reset time appears to be related to network load, but reset withing 10s with next to no traffic. I did try swapping cables, but with no effect. With each reset the interface successfully obtains an IP address via DHCP, works for a few seconds and resets. Restoring the server to 11.1-RELEASE-p10 resolves the problem. Any suggestions? -- David Samms From owner-freebsd-stable@freebsd.org Sat Jun 23 18:59:31 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97309100278C for ; Sat, 23 Jun 2018 18:59:31 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::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 248188E425 for ; Sat, 23 Jun 2018 18:59:31 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x235.google.com with SMTP id z12-v6so3036148ybj.4 for ; Sat, 23 Jun 2018 11:59:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=k5idQu0415WccGq4dB8hDuls2JTA5mvjxum5FqR0xPU=; b=ApphqxmRgNutt527SGDb1YMXNmtRathFbtnodTejUCzBIJ+jxonAJB+6iP1TopXZy8 p/K/UPHnIzLbiaUZ9IVOaqvHocw0FNkAKm0ox/+CoAoLQ3DzD2ZNBkyYhMEwqTWRG6zQ yJySyCM2VVnZbx0bxsar9lPTFfiXIdWpAEyIk= 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=k5idQu0415WccGq4dB8hDuls2JTA5mvjxum5FqR0xPU=; b=capklz4EY8ZhM0tKVs9ryNus+ixCyzmkdHoBXpZueeMrpbWLO8gDaMQblAdlCoRe+X soa6RFmt0O31++KezIsetRinMrQiw8LOACE4B6mAlVW4L7Z0rQYa+LPWTHh5IdDZa9iJ xUTxZyY+LEXG62BtLMOYjoLuONKT/QHL1DgyeOwoBdBZxDWkx/3Jxo9iFk5p9aGzsIxp T5gcd1TVwHTNAYOreVmgxwLIe357bjMCQCGk5nW32lUMGREO4IScH1BAqeeGkkoCScmH Ap5emI3hCpYJOYrmjhjOg5j0R5N0ljcNwPTJQ9o9YQLRSPcTG5JDRqHJPtYGmobSWqbl MmYg== X-Gm-Message-State: APt69E21GiFqZK4rEJ5F6yUaoOjZW63S0H7qMph0oSc+crNHi670jYZ0 1u1r8uYqb89e9VTYb0a7mXqvFcrt6L+7WTU4F2Ls4Q== X-Google-Smtp-Source: ADUXVKLndiphHnmhCUH3iCsmdGqeCqPgLxaeZcQTzVxKpiKFOnNNChBwRpz9oe+XMx5ECIMDHKk+Yq9Vo5T7xi11HBc= X-Received: by 2002:a25:734f:: with SMTP id o76-v6mr3198890ybc.69.1529780370323; Sat, 23 Jun 2018 11:59:30 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:ef50:0:0:0:0:0 with HTTP; Sat, 23 Jun 2018 11:58:59 -0700 (PDT) In-Reply-To: <51718e96f63175e997cb8268381d1070@freebsd.org> References: <6dd9952452c73826a2f9c01612586bea@udns.ultimatedns.net> <18000a3b93085c91aeffbca937862786@freebsd.org> <51718e96f63175e997cb8268381d1070@freebsd.org> From: Eitan Adler Date: Sat, 23 Jun 2018 11:58:59 -0700 Message-ID: Subject: Re: jail related inconsistencies in FreeBSD tools parameters To: James Gritton Cc: bsd-lists@bsdforge.com, freebsd-jail@freebsd.org, freebsd-stable Stable Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.26 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, 23 Jun 2018 18:59:31 -0000 On 23 June 2018 at 08:50, James Gritton wrote: > On 2018-06-23 09:45, Eitan Adler wrote: >> >> On 23 June 2018 at 08:30, James Gritton wrote: >>> >>> On 2018-06-22 16:03, Miroslav Lachman wrote: >>>> >>>> >>>> Chris H wrote on 2018/06/22 23:46: >>>>> >>>>> >>>>> On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" >>>>> <000.fbsd@quip.cz> >>>>> said >>>>> >>>>>> I don't know if it is better to discuss it in jail@ or stable@ list so >>>>>> a >>>>>> do cross-post. >>>>>> >>>>>> FreeBSD has many jail aware utilities but they are inconsistent in >>>>>> taking JID as parameter. >>>>>> >>>>>> For example "sockstat" takes -j JID "Show only sockets belonging to >>>>>> the >>>>>> specified jail ID" and it means numeric ID only. >>>>>> On the other hand "ps" takes -J JID "This may be either the jid or >>>>>> name >>>>>> of the jail. Use -J 0 to display only host processes." >>>>>> The same apply for "top", it understands jid as a number or name of >>>>>> the >>>>>> jail too. >>>>>> Then again "cpuset" takes only numerical ID of the jail... >>>>>> >>>>>> Shouldn't it be consistent across all FreeBSD base utilities so all of >>>>>> them can use numerical ID and name? >>>>> >>>>> >>>>> Good idea! Are you offering to create a patch? ;-) >>>>> It'd be my guess that given they weren't all created at the same time, >>>>> nor >>>>> the same individual; that (quite probably?) the "jail" additions were >>>>> also >>>>> added at different times, and by different people. So I'd imagine that >>>>> unless someone with a commit bit decides one day they'd like to take >>>>> that >>>>> on. Someone(tm) maybe you? will need to propose a patch. :-) >>>> >>>> >>>> >>>> If I can understand C sources I will create the patch by myself >>>> instead of just posting here. Unfortunately I am able to code in sh, >>>> php and a bit of javascript and perl but no C. :) >>>> >>>> Miroslav Lachman >>> >>> >>> >>> Sure, a PR would be handy for this - it's a pretty simple thing to add, >>> and >>> consistency would indeed be a good move. >> >> >> Agreed. I'll review and commit such patches. I'd like to see a single >> function for taking a "id or name". Ideally it would live in a >> library, perhaps libjail? > > > It already lives there: jail_getid(3) I was thinking of a more generic one that does id or name. Now that I think about it a bit more, C makes this kind of thing impossible to do usefully. That said, I'll still review and commit any patches to existing tools to make them behave consistently. -- Eitan Adler