From owner-freebsd-hackers@freebsd.org Sun Nov 10 09:28:45 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 090D51AF9F7 for ; Sun, 10 Nov 2019 09:28:45 +0000 (UTC) (envelope-from joel.bertrand@systella.fr) Received: from rayleigh.systella.fr (newton-ipv6.systella.fr [IPv6:2001:7a8:a8ed:253::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "*.systella.fr", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 479pbb5DCCz3J0L for ; Sun, 10 Nov 2019 09:28:43 +0000 (UTC) (envelope-from joel.bertrand@systella.fr) Received: from [192.168.10.103] (hilbert.systella.fr [192.168.10.103]) (authenticated bits=0) by rayleigh.systella.fr (8.15.2/8.15.2/Debian-15) with ESMTPSA id xAA9SNtx010224 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sun, 10 Nov 2019 10:28:24 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=systella.fr; s=mail; t=1573378114; bh=NP7unbGP2ekZCoDIA5ETOGXKcrqHrSTzIaMNrz8lujM=; h=To:From:Subject:Date:From; b=F4RL4YcHzw6COc3qOjaXhB1RKwMGpd1RjVW7WCLUcJ/pDBek7kdt9N1GTAdW0wzwW ZZWo+esBmlcdLCVMqZMo9p6ZsAI7TuybUfgC2RiXL5rBnwT65x59Qbgxgtwgg935pC GKSv2hNRUI5BJz9Vz/0poY242h+h3dMnnG1yUZh/qxaGHolXmwn3Nwn2piGxx4WEMw wks7huniUfNUriuTAyph7cIPUD3RRYebU0okXEMayS5gyH4s7cn4bgtS3lnzxpce3A RTeCsOnCxJOmd3nz8TCJdJmXgUJkLyjYKDSo8xFDS09oIbBrrFj3kTPTjSZ7/icGnU h5gZcnxzH+/HA== To: freebsd-hackers@freebsd.org From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= Subject: Strange trouble with ntpd account Openpgp: preference=signencrypt Autocrypt: addr=joel.bertrand@systella.fr; prefer-encrypt=mutual; keydata= mQINBFphqV8BEAC+ye6YQBdlEn9p/mbZhiQLkZQjIbGL84M0XOd66AgWqJ3T2TiwEyiExQyM Of0VswmB1q6SaIyh0x4bzaRyKwJLWDJy+AMGLGT2cpmsrDgllUxiBv3xAoLpwR8yDuLs5+bT vPpu81Pm/nzO2NDl85+3WAQbW+bUDAUdBhkg7X07bjJePypRxoRh4LF/syalOjzPEFARFNBY VrXFCTS/F7ZwmUHLv2xWJpEyKHfsC4BSo4ZPjrKmPJBxBPxuR+KiSYG/TkjU6CzoFvdwRY33 GNrK+dUmt9/VnPC/l1rGWS3durgah4OEkxciesKiTvQBUzVfMY0dvzBQKJeNNMFLstnjq3NP qvo3g5DnhFYFSAjI7wzqLkcYO8qg01wrWYyY/NLfAY6CvK0VjlenlKu84ePQDu7zh9/DUzBs 75ZAP2vZv4o00B2A3ksbkXSIs9eSDDx19OS1EUkSqw1VtFRfupoMkK7I7zrGR+DBENl5oK09 SOYJw594XVAoPpZ5zVUlEBDpatBNICTTT17EHrVpEB222TVfChvoE0cwYGkS40nVRIhQ1Yo3 A8qeKb2EeeCtslgiNcb1ajeZOSGUSHnczWHTaX5jMB/evNxZpLJH1WX8PqZ/+7wVRYuZGZ/b r8V3wXjZVNzPSTONwq3w/VjizPcQqdwicoNtxvuB6hM1J1tLGQARAQABtCpCRVJUUkFORCBK b8OrbCA8am9lbC5iZXJ0cmFuZEBzeXN0ZWxsYS5mcj6JAlQEEwEKAD4WIQSrhgKgAkzAsSVl Vhc4B+jSUpDz5wUCWmGpXwIbIwUJCWYBgAULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRA4 B+jSUpDz5xwED/462ki+I97keYMSDPVjzx9MmcE/pznOqv8b4IbFbWzaSCx5J3BByBVU1IyP LdDCdZgvc7vM5l8Gc6mqxeABbgdyxBGMwoXBBADXt9dcAKW3xl6URMLoor8DwgnuluCdQT+K 7VW6ron23x7wI9iscuXV2M6xG2G84o5kDgW2NrkKBIwfWqS/XATNrC8e9j71h29cv1RvKN2a 3XQMI6kvBRirb9zM8jWaP1K/QCLZpvhuiXCJwJvl+MGTuOUTxvp44MjVaM++Wfljc9NAVyD8 s3UxBTjhei1zIHiLUMANzeFLnW21UnoCLLoqzD558VC2Gyqk9I9kaZ/jgQqEu6drbJG+6LbY zbiYt1OhURCrMh7zXjPbBCF1rjtjhEZx2EmT2U7KWQvgcW75JBEGCRveTXQga8ytBTcNoEC8 e7ZjM0ob769ZQ1HmeWAOJy6xKEnv1A2P3erQ3xTZEHFVesoruhMAzrf2fdWJ9vGvndMt7sV/ G0NabDwlI+eIZ77vEUCdFiCZuE8vk0BglwXHVH5zjgJNVLNgNFSs3uTSf5zOIqLXyQTOd0px 5jNe2mePxdMuI9MuQWXE8Z7InUaU1WZ+95eTMonTs+DRUJzQ+XWYbqllGudx230T/Y6cYxSW stw5bAQl1aNhNCZjHutNUigb8row2cH2kCVJexv4LYUx8vdc2bkCDQRaYalfARAA000pOiAt CMcbNPczj/sFU5UZ6zaEOPj08nNv48UZAfo8ZiWejSp7YbaU4HW0VxcT2ZQvhsHor2wjqI5K Ii7gmGyjMA6NJPhHVoJw8+j64m38mRcOzlSaQEZV+Pp+TAX8PyucZvNPXHy40UQfDqCoYxAw A0bSWwcSwH+N/eEijrEOf7k1QRjEodjGTxaE50XOWXz/NMVx7l9ORcd5r2oq2DLjqnnQzl6k XxmxSV5cm+HDIojLmQz1qxq7r2GhC5hGuR5KXrO/p4bNiqCTw+rwm4bO6YjTfaH+eNRwzg6L OpW7ZNw0pfWf4wO/h+ozZTY5q9EbZSmZyVoSyPu2J1+mX3gF2ZLSzZ7+XgV4z6EIAcF1sjGE hsqA9yF4NVHGlrP9dkhZFoBVtkJgjSfdSWGXp40X+pUROeVuexD6zDadB5rCv05o9/EPDFu0 W7mJ+l8h3rGI0E5ObmR6+HyFGqalByGFxYbia+x51Kj6WbHNMuddkPk0YbHs53zS9VGnRcnh xTGdga2rMzO9ZycKo7DPrdZVi7bZWKM/WM0IL5m6FTPSJteJ886NP9oc8U6o2GxZ1cMeZwnu AprT77mISL0Z1CCcoSDZEnD+EmOcKxYnkxJuhMY2kdMd2x47I2HFxTa1ix6UQ7OY6i0VQ4gG WZ3tgiHYIHbeAyZXn0P4nM5ofgEAEQEAAYkCPAQYAQoAJhYhBKuGAqACTMCxJWVWFzgH6NJS kPPnBQJaYalfAhsMBQkJZgGAAAoJEDgH6NJSkPPn9mEP/2mEFZGT0AaecRRXfpfrVnxxIwK8 YK3mmaa8jqSLXzDgubTO6PWojVt/SCrvhCtEf5vxATPbeFz5Ho0foI/iGys9SQkYmsIn13m0 z9oY8LBIyrPFud56RrIqYBno3qR6N7SWBWtZeUw+gc6HYbMyk2L7//wz4DkneJYLLcTfMxb/ +Ok0tNmWp6YfuyRBt5yHU6VfW4tZxF5qzg+9niW3VbB6BEZbM+ya7qBZD8su4e1EfUjaKb2z Egyw09laSgBW4NzGBwlhX3zeDsNTiReqa78e1pv52Ur3dI5GH4psLw4rH7ghh/aA/eVDMcKn LPNeTNl+Sz/1PK+oVNxz6tGBVsTVbZpwbanv6+qQP3yPvX0MS1x5QQPp/SAsjJv6lpFkoUGK n2clMYH8pSefR7jp0UPCrMBeFv5bom8tNMTHrIQrpnWo7vXUmeJ7OP/lHUtbBB26882pYbpa 05D79xUkBMYX2BGvtM687+CZaWwA4u/Tl7cu3PpIavPWgmmvIBJOwsDKxNgopLkix8AGFbfs wPcE7d03t9tdauheHA8pssNQmy3scoThC3DQc4eIEBUU5M9uIW2HARl3OgJP9h9OePsgaT8g zTlN3q6QmDWQwRmxF6J7Z9dtIDmXr+014XtK7UCzxkBIFS5jPGzL8dSKDu5jIx8cboy9QUeH Tr6FXnLg Message-ID: <35704598-f05d-d8bb-dca8-8c57ba746ea1@systella.fr> Date: Sun, 10 Nov 2019 10:28:23 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.5 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.101.4 at rayleigh X-Virus-Status: Clean X-Rspamd-Queue-Id: 479pbb5DCCz3J0L X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=systella.fr header.s=mail header.b=F4RL4YcH; dmarc=none; spf=pass (mx1.freebsd.org: domain of joel.bertrand@systella.fr designates 2001:7a8:a8ed:253::1 as permitted sender) smtp.mailfrom=joel.bertrand@systella.fr X-Spamd-Result: default: False [-2.48 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[systella.fr:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:7a8:a8ed:253::1/64]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; DMARC_NA(0.00)[systella.fr]; DKIM_TRACE(0.00)[systella.fr:+]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.02)[asn: 13193(0.11), country: FR(-0.00)]; ASN(0.00)[asn:13193, ipnet:2001:7a8::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2019 09:28:45 -0000 Hello, Yesterday, I have rebooted my diskless workstation running FreeBSD 12.0-RELEASE-p10. I have seen that ntpd refuses to start : root@pythagore:/etc # /etc/rc.d/ntpd start Starting ntpd. su: unknown login: ntpd /etc/rc.d/ntpd: WARNING: failed to start ntpd root@pythagore:/etc # indeed : root@pythagore:/var/db/ntp # ls -al total 16 drwxr-xr-x 2 123 ntpd 512 Mar 20 2019 . drwxr-xr-x 22 root wheel 1024 Oct 22 19:01 .. -rw-r--r-- 1 root wheel 8 Mar 20 2019 ntpd.drift -rw-r--r-- 1 root ntpd 4 Mar 20 2019 ntpd.pid Please note user 123 instead of user ntpd. I have tried to create a new file and change owner to ntpd without success : root@pythagore:/var/db/ntp # touch toto root@pythagore:/var/db/ntp # chown ntpd toto chown: ntpd: illegal user name I don't understand why ntpd user is illegal as this account exists in /etc/master.passwd : # $FreeBSD: releng/12.0/etc/master.passwd 337882 2018-08-15 23:18:34Z brd $ # root:$6$mNlwOa.XAsUQF0bo$RCxDWSK0Hc2HGWkT5f46R6zjRhfgKhiA8IGKbM9KkILUACC0fLnKf3jABGiHSxRLSJH/.SXXsjaZJi30.CGR21:0:0::0:0:Charlie &:/root:/bin/csh toor:*:0:0::0:0:Bourne-again Superuser:/root: daemon:*:1:1::0:0:Owner of many system processes:/root:/usr/sbin/nologin ... www:*:80:80::0:0:World Wide Web Owner:/nonexistent:/usr/sbin/nologin ntpd:*:123:123::0:0:NTP Daemon:/var/db/ntp:/usr/sbin/nologin _ypldap:*:160:160::0:0:YP LDAP unprivileged user:/var/empty:/usr/sbin/nologin cups:*:193:193::0:0:Cups Owner:/nonexistent:/usr/sbin/nologin ... webcamd:*:145:145::0:0:Webcamd user:/var/empty:/usr/sbin/nologin colord:*:970:970::0:0:colord color management daemon:/nonexistent:/usr/sbin/nologin +::::::::: polkit:*LOCKED**:1013:1001::0:0:User &:/var/polkit:/usr/sbin/nologin Of course, I have checked that, for example, I can create a new file and change owner to cups without error. My nsswitch.conf is : group: compat group_compat: nis hosts: files dns netgroup: compat networks: files passwd: compat passwd_compat: nis shells: files services: compat services_compat: nis protocols: files rpc: files and, of course, nis run as expected. Why is ntpd account disabled ? Best regards, JB From owner-freebsd-hackers@freebsd.org Sun Nov 10 11:40:25 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D95871B1E6C for ; Sun, 10 Nov 2019 11:40:25 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 479sWX20Vnz3PCC for ; Sun, 10 Nov 2019 11:40:23 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13:0:0:0:5]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id xAABeBPV005913 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 10 Nov 2019 11:40:14 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: joel.bertrand@systella.fr Received: from [10.58.0.4] (dadv@[10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id xAABe2eE038350 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 10 Nov 2019 18:40:03 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: Strange trouble with ntpd account To: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= , freebsd-hackers@freebsd.org References: <35704598-f05d-d8bb-dca8-8c57ba746ea1@systella.fr> From: Eugene Grosbein Message-ID: <9eae960b-ff99-1322-e557-ead488e3739f@grosbein.net> Date: Sun, 10 Nov 2019 18:39:56 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <35704598-f05d-d8bb-dca8-8c57ba746ea1@systella.fr> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record * -0.0 SPF_PASS SPF: sender matches SPF record * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on hz.grosbein.net X-Rspamd-Queue-Id: 479sWX20Vnz3PCC X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=permerror (mx1.freebsd.org: domain of eugen@grosbein.net uses mechanism not recognized by this client) smtp.mailfrom=eugen@grosbein.net X-Spamd-Result: default: False [-3.68 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[grosbein.net]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_PERMFAIL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-1.58)[ip: (-3.98), ipnet: 2a01:4f8::/29(-2.26), asn: 24940(-1.67), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2019 11:40:25 -0000 10.11.2019 16:28, BERTRAND Joël wrote: > Hello, > > Yesterday, I have rebooted my diskless workstation running FreeBSD > 12.0-RELEASE-p10. I have seen that ntpd refuses to start : > > root@pythagore:/etc # /etc/rc.d/ntpd start > Starting ntpd. > su: unknown login: ntpd > /etc/rc.d/ntpd: WARNING: failed to start ntpd > root@pythagore:/etc # > > indeed : > > root@pythagore:/var/db/ntp # ls -al > total 16 > drwxr-xr-x 2 123 ntpd 512 Mar 20 2019 . > drwxr-xr-x 22 root wheel 1024 Oct 22 19:01 .. > -rw-r--r-- 1 root wheel 8 Mar 20 2019 ntpd.drift > -rw-r--r-- 1 root ntpd 4 Mar 20 2019 ntpd.pid > > Please note user 123 instead of user ntpd. > I have tried to create a new file and change owner to ntpd without success : > > root@pythagore:/var/db/ntp # touch toto > root@pythagore:/var/db/ntp # chown ntpd toto > chown: ntpd: illegal user name > > I don't understand why ntpd user is illegal as this account exists in > /etc/master.passwd : > # $FreeBSD: releng/12.0/etc/master.passwd 337882 2018-08-15 23:18:34Z brd $ > # > root:$6$mNlwOa.XAsUQF0bo$RCxDWSK0Hc2HGWkT5f46R6zjRhfgKhiA8IGKbM9KkILUACC0fLnKf3jABGiHSxRLSJH/.SXXsjaZJi30.CGR21:0:0::0:0:Charlie > &:/root:/bin/csh > toor:*:0:0::0:0:Bourne-again Superuser:/root: > daemon:*:1:1::0:0:Owner of many system processes:/root:/usr/sbin/nologin > ... > www:*:80:80::0:0:World Wide Web Owner:/nonexistent:/usr/sbin/nologin > ntpd:*:123:123::0:0:NTP Daemon:/var/db/ntp:/usr/sbin/nologin The system does not use text file /etc/master.passwd but binary files /etc/pwd.db and /etc/swd.db and yours are out-of-sync with master.passwd for some reason. Just re-generate binary files from /etc/master.passwd and pwd_mkdb(8) manual page's EXAMPLE section suggests: /usr/sbin/pwd_mkdb -p /etc/master.passwd From owner-freebsd-hackers@freebsd.org Sun Nov 10 13:19:14 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7A1E61B4460 for ; Sun, 10 Nov 2019 13:19:14 +0000 (UTC) (envelope-from joel.bertrand@systella.fr) Received: from rayleigh.systella.fr (newton-ipv6.systella.fr [IPv6:2001:7a8:a8ed:253::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "*.systella.fr", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 479vjX74Syz3yHY for ; Sun, 10 Nov 2019 13:19:12 +0000 (UTC) (envelope-from joel.bertrand@systella.fr) Received: from [192.168.10.103] (hilbert.systella.fr [192.168.10.103]) (authenticated bits=0) by rayleigh.systella.fr (8.15.2/8.15.2/Debian-15) with ESMTPSA id xAADIvFr016876 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sun, 10 Nov 2019 14:18:58 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=systella.fr; s=mail; t=1573391948; bh=fqgcsStSzO6MLKWOfflnXeTPBkqdOpEYTtOhi0gyobI=; h=Subject:To:References:From:Date:In-Reply-To:From; b=LfzfKtQatoMqASYG4de9uw4/uNn8lNIpdNFKal3RumPECor1EXusXMbh2O/Qde9RV xRZRHvl0JdHicWNuhmzpf1rQuER/4AYutMs55XLCI0Clsx3BLl5oOej2mI5/0iSy4M 4QNYY6Ksv2HJGvi1DHKCjdcgG0RDKdbkx3wiUC4y1Dqmvf67jLHAB9kYN7JuFtj5Y4 yD+SUeeHljVw2mEeUUyqM4ZUfT9Qe274/EBQPzT6g8KSptRKVZ5PiTVwyTuo2BzSAt SJ9JBAUqrQPYKKA3fDeo61dPzKfOdYaDUVa9vq3E4Nw80LrlsaAQ+McKCZdmuhJHNR spBTqe1No5y1g== Subject: Re: Strange trouble with ntpd account To: freebsd-hackers@freebsd.org References: <35704598-f05d-d8bb-dca8-8c57ba746ea1@systella.fr> <9eae960b-ff99-1322-e557-ead488e3739f@grosbein.net> From: =?UTF-8?Q?BERTRAND_Jo=c3=abl?= Openpgp: preference=signencrypt Autocrypt: addr=joel.bertrand@systella.fr; prefer-encrypt=mutual; keydata= mQINBFphqV8BEAC+ye6YQBdlEn9p/mbZhiQLkZQjIbGL84M0XOd66AgWqJ3T2TiwEyiExQyM Of0VswmB1q6SaIyh0x4bzaRyKwJLWDJy+AMGLGT2cpmsrDgllUxiBv3xAoLpwR8yDuLs5+bT vPpu81Pm/nzO2NDl85+3WAQbW+bUDAUdBhkg7X07bjJePypRxoRh4LF/syalOjzPEFARFNBY VrXFCTS/F7ZwmUHLv2xWJpEyKHfsC4BSo4ZPjrKmPJBxBPxuR+KiSYG/TkjU6CzoFvdwRY33 GNrK+dUmt9/VnPC/l1rGWS3durgah4OEkxciesKiTvQBUzVfMY0dvzBQKJeNNMFLstnjq3NP qvo3g5DnhFYFSAjI7wzqLkcYO8qg01wrWYyY/NLfAY6CvK0VjlenlKu84ePQDu7zh9/DUzBs 75ZAP2vZv4o00B2A3ksbkXSIs9eSDDx19OS1EUkSqw1VtFRfupoMkK7I7zrGR+DBENl5oK09 SOYJw594XVAoPpZ5zVUlEBDpatBNICTTT17EHrVpEB222TVfChvoE0cwYGkS40nVRIhQ1Yo3 A8qeKb2EeeCtslgiNcb1ajeZOSGUSHnczWHTaX5jMB/evNxZpLJH1WX8PqZ/+7wVRYuZGZ/b r8V3wXjZVNzPSTONwq3w/VjizPcQqdwicoNtxvuB6hM1J1tLGQARAQABtCpCRVJUUkFORCBK b8OrbCA8am9lbC5iZXJ0cmFuZEBzeXN0ZWxsYS5mcj6JAlQEEwEKAD4WIQSrhgKgAkzAsSVl Vhc4B+jSUpDz5wUCWmGpXwIbIwUJCWYBgAULCQgHAgYVCgkICwIEFgIDAQIeAQIXgAAKCRA4 B+jSUpDz5xwED/462ki+I97keYMSDPVjzx9MmcE/pznOqv8b4IbFbWzaSCx5J3BByBVU1IyP LdDCdZgvc7vM5l8Gc6mqxeABbgdyxBGMwoXBBADXt9dcAKW3xl6URMLoor8DwgnuluCdQT+K 7VW6ron23x7wI9iscuXV2M6xG2G84o5kDgW2NrkKBIwfWqS/XATNrC8e9j71h29cv1RvKN2a 3XQMI6kvBRirb9zM8jWaP1K/QCLZpvhuiXCJwJvl+MGTuOUTxvp44MjVaM++Wfljc9NAVyD8 s3UxBTjhei1zIHiLUMANzeFLnW21UnoCLLoqzD558VC2Gyqk9I9kaZ/jgQqEu6drbJG+6LbY zbiYt1OhURCrMh7zXjPbBCF1rjtjhEZx2EmT2U7KWQvgcW75JBEGCRveTXQga8ytBTcNoEC8 e7ZjM0ob769ZQ1HmeWAOJy6xKEnv1A2P3erQ3xTZEHFVesoruhMAzrf2fdWJ9vGvndMt7sV/ G0NabDwlI+eIZ77vEUCdFiCZuE8vk0BglwXHVH5zjgJNVLNgNFSs3uTSf5zOIqLXyQTOd0px 5jNe2mePxdMuI9MuQWXE8Z7InUaU1WZ+95eTMonTs+DRUJzQ+XWYbqllGudx230T/Y6cYxSW stw5bAQl1aNhNCZjHutNUigb8row2cH2kCVJexv4LYUx8vdc2bkCDQRaYalfARAA000pOiAt CMcbNPczj/sFU5UZ6zaEOPj08nNv48UZAfo8ZiWejSp7YbaU4HW0VxcT2ZQvhsHor2wjqI5K Ii7gmGyjMA6NJPhHVoJw8+j64m38mRcOzlSaQEZV+Pp+TAX8PyucZvNPXHy40UQfDqCoYxAw A0bSWwcSwH+N/eEijrEOf7k1QRjEodjGTxaE50XOWXz/NMVx7l9ORcd5r2oq2DLjqnnQzl6k XxmxSV5cm+HDIojLmQz1qxq7r2GhC5hGuR5KXrO/p4bNiqCTw+rwm4bO6YjTfaH+eNRwzg6L OpW7ZNw0pfWf4wO/h+ozZTY5q9EbZSmZyVoSyPu2J1+mX3gF2ZLSzZ7+XgV4z6EIAcF1sjGE hsqA9yF4NVHGlrP9dkhZFoBVtkJgjSfdSWGXp40X+pUROeVuexD6zDadB5rCv05o9/EPDFu0 W7mJ+l8h3rGI0E5ObmR6+HyFGqalByGFxYbia+x51Kj6WbHNMuddkPk0YbHs53zS9VGnRcnh xTGdga2rMzO9ZycKo7DPrdZVi7bZWKM/WM0IL5m6FTPSJteJ886NP9oc8U6o2GxZ1cMeZwnu AprT77mISL0Z1CCcoSDZEnD+EmOcKxYnkxJuhMY2kdMd2x47I2HFxTa1ix6UQ7OY6i0VQ4gG WZ3tgiHYIHbeAyZXn0P4nM5ofgEAEQEAAYkCPAQYAQoAJhYhBKuGAqACTMCxJWVWFzgH6NJS kPPnBQJaYalfAhsMBQkJZgGAAAoJEDgH6NJSkPPn9mEP/2mEFZGT0AaecRRXfpfrVnxxIwK8 YK3mmaa8jqSLXzDgubTO6PWojVt/SCrvhCtEf5vxATPbeFz5Ho0foI/iGys9SQkYmsIn13m0 z9oY8LBIyrPFud56RrIqYBno3qR6N7SWBWtZeUw+gc6HYbMyk2L7//wz4DkneJYLLcTfMxb/ +Ok0tNmWp6YfuyRBt5yHU6VfW4tZxF5qzg+9niW3VbB6BEZbM+ya7qBZD8su4e1EfUjaKb2z Egyw09laSgBW4NzGBwlhX3zeDsNTiReqa78e1pv52Ur3dI5GH4psLw4rH7ghh/aA/eVDMcKn LPNeTNl+Sz/1PK+oVNxz6tGBVsTVbZpwbanv6+qQP3yPvX0MS1x5QQPp/SAsjJv6lpFkoUGK n2clMYH8pSefR7jp0UPCrMBeFv5bom8tNMTHrIQrpnWo7vXUmeJ7OP/lHUtbBB26882pYbpa 05D79xUkBMYX2BGvtM687+CZaWwA4u/Tl7cu3PpIavPWgmmvIBJOwsDKxNgopLkix8AGFbfs wPcE7d03t9tdauheHA8pssNQmy3scoThC3DQc4eIEBUU5M9uIW2HARl3OgJP9h9OePsgaT8g zTlN3q6QmDWQwRmxF6J7Z9dtIDmXr+014XtK7UCzxkBIFS5jPGzL8dSKDu5jIx8cboy9QUeH Tr6FXnLg Message-ID: <1e0644af-7e10-c57b-fccc-c9582b492443@systella.fr> Date: Sun, 10 Nov 2019 14:18:57 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.5 MIME-Version: 1.0 In-Reply-To: <9eae960b-ff99-1322-e557-ead488e3739f@grosbein.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Virus-Scanned: clamav-milter 0.101.4 at rayleigh X-Virus-Status: Clean X-Rspamd-Queue-Id: 479vjX74Syz3yHY X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=systella.fr header.s=mail header.b=LfzfKtQa; dmarc=none; spf=pass (mx1.freebsd.org: domain of joel.bertrand@systella.fr designates 2001:7a8:a8ed:253::1 as permitted sender) smtp.mailfrom=joel.bertrand@systella.fr X-Spamd-Result: default: False [-2.54 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[systella.fr:s=mail]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:7a8:a8ed:253::1/64]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DMARC_NA(0.00)[systella.fr]; DKIM_TRACE(0.00)[systella.fr:+]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.04)[asn: 13193(-0.20), country: FR(-0.00)]; ASN(0.00)[asn:13193, ipnet:2001:7a8::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2019 13:19:14 -0000 Eugene Grosbein a écrit : > /usr/sbin/pwd_mkdb -p /etc/master.passwd Thanks a lot, it runs now as expected. But I don't understand why files are out-of-sync... Best regards, JB From owner-freebsd-hackers@freebsd.org Sun Nov 10 17:33:10 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3763A1B9C33; Sun, 10 Nov 2019 17:33:10 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-il1-x12b.google.com (mail-il1-x12b.google.com [IPv6:2607:f8b0:4864:20::12b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47B1LY2plQz4Bsq; Sun, 10 Nov 2019 17:33:09 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by mail-il1-x12b.google.com with SMTP id d83so9750979ilk.7; Sun, 10 Nov 2019 09:33:09 -0800 (PST) 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=Golb5IpnQEKzSd8CA30ACHW5JTKLVkvoVOlNa+vhNQE=; b=korxSWLcjS7aUpsIlGbglrWX2SU/b5LQfkfcDQg2DdJv9wp7ysgN/BnwtQz8Ep947p EvfJjIrdA4wP05/rk8wTshqugWyffgVadglGSLHiKIfAJVwJJxt/jGfiIIufHropjl4z CD55DhKZcqtq1FckN7VtWD2Zf95JZpZ7O9HQclYKR4Oqa2toSEx7/i0Bc3kX3dFiIIWE ASbb9g1/NdI0qxgkGLGGftg43Nydppt/JdCOuSWrOVkEyu0FqcM1FHAalDKuaoF9G0rX owuQeBtMnbppmOLBvCP87LM05fT7XPcQi1hS4fS5Q571twiOBHFnFbySgrKwjAhZZi+8 k7zQ== 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=Golb5IpnQEKzSd8CA30ACHW5JTKLVkvoVOlNa+vhNQE=; b=JMXtWpjLgzJFidTxG/IH0s7tVRl1PU0skl1lQjpwGTQGchzrwWggIbHI+HGudvGJ7q k09pMcXSm5eq8U3iCL4kG6P0uBywDJbn0xgEPiT2VR7ZeAc8dlwMx06juBMXqQ5PYsQK h6TBuHNlJ+7of0YZu28p7oL+2LZvA1+vKf02e8+mV3ug6cZ6smY7TTR3x4P7mNJdzJ7R SbQ1JekgX2LwcdncMsgDSr75P3RjF8OIfNCeB+gwguxw+dYAyDYU76KGe43J7CtpkOmd IajG6lstzmYP6RJdX+637N5IhpRymRu7522zfyN5IZrCmvNw2XpMz0ONMqh5IBV4KaH3 /1JQ== X-Gm-Message-State: APjAAAVfMhYxsix7ywatHiD7h9cxS/q/vv+tUnwP5EtHHg85MKV5FuGk zFmWda3Vs8HeynkGoSomSeisEITnyJAnUEcPUabBCJRGiwI= X-Google-Smtp-Source: APXvYqw2ovndSonNfeoSwbUxPwdmx/kFwEr8cwNbh2LnjA8/xAuAIFdDhEwZubutEn7Ld6r8dZwtoUcybwlKpJ8zjVw= X-Received: by 2002:a92:c10f:: with SMTP id p15mr10723262ile.119.1573407188059; Sun, 10 Nov 2019 09:33:08 -0800 (PST) MIME-Version: 1.0 From: Aryeh Friedman Date: Sun, 10 Nov 2019 12:32:56 -0500 Message-ID: Subject: Telling svnlite to ignore specific dirs/ports To: FreeBSD Mailing List , FreeBSD Mailing List X-Rspamd-Queue-Id: 47B1LY2plQz4Bsq X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=korxSWLc; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of aryehfriedman@gmail.com designates 2607:f8b0:4864:20::12b as permitted sender) smtp.mailfrom=aryehfriedman@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_TWO(0.00)[2]; URI_COUNT_ODD(1.00)[3]; IP_SCORE_FREEMAIL(0.00)[]; IP_SCORE(0.00)[ip: (-7.93), ipnet: 2607:f8b0::/32(-2.34), asn: 15169(-2.00), country: US(-0.05)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[b.2.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2019 17:33:10 -0000 I am using a pre-release emulator/virtualbox-ose-* (the one in PR 234878) how do I prevent a svnlite update on /usr/port from clobbering some or all of the files in the effected port dirs? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-hackers@freebsd.org Sun Nov 10 18:52:50 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 85A091BBB9F; Sun, 10 Nov 2019 18:52:50 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47B36T0HlZz4Gyk; Sun, 10 Nov 2019 18:52:48 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x32d.google.com with SMTP id l17so10275572wmh.0; Sun, 10 Nov 2019 10:52:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=Bn4d6igN7pCtXXSMsZ+nrbyqiKK7Y2uKBfy3xMqYSsw=; b=kLQRGq27aRhhMBbwDbWyz5xuv+Zqfd1S0cvjloX4M2xkUqqLzOVB1Gp8TbvpEsDUZ5 KLTyBqFZ13jeVdN5Kzn8zJ5d8Beoe4Cykif1vTts2l7p4DmznlueZKlK69LLUr9xqWpX MSDSNpJTzBiRPTsCVii32SrK3FiBO0uAj5PK/2LUj+WY2PPSX+XivY9Ox8AnmxgnG37Z SVSw0j6c+MtEMzqYiSm1zuzTsSoNcc0wO5oi3ges7xCBrDhBauQIDBWvVZL1p0F9Zvw9 8hQ2Wm8Ynkw7VGgHJq6ZaBJT3vmMwUodMgG6wkCSu6FMhDnL8LiAGxELDcYTmALeEv+i j6pw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=Bn4d6igN7pCtXXSMsZ+nrbyqiKK7Y2uKBfy3xMqYSsw=; b=IwYzbPRCeQJXwhyMmNKQm6kBEDVvUQx6D0xWf/zAv1N/k6Vx5BkcWDYrgh31LDUYWV Y1/h1pFaKD24zBuYkVrYZwBaGXMWO4DDnHELapr47ZSf8KokUnfwMziITTtgi2lw5hGf t7z31vsX24fat29drr/53EZQUyNcxVmBTqZqIM/R8aL7BrHz55SpFn5FN4BvwMgstdio Umz7zVX3wRCnvqub9pOA/bQVGWW0shQyiTqolAV2CfVfM7hE8klfB6H6ebX1R5qXnT8z 7q+3eLyZ1yU4GSpjyFpvO9YoUPqEFvngvhhUu1cyXD0HtLrhIsQt1n+4Ez7oDtjC7D0o rqiw== X-Gm-Message-State: APjAAAU7213ybzCV/BbDaOdtgBDHnyMiRSsnp2AxZ7sSMtvUBFapn4tJ XsnvOgEwBOMs0BoUfBhHalA= X-Google-Smtp-Source: APXvYqwYqZHvqPuNaazIgkdPPlVB9iCMekdj4UqmldZkiXhN6xZEDom5zw86nHKuziNIOO4oAn8kvw== X-Received: by 2002:a1c:38c3:: with SMTP id f186mr17743419wma.58.1573411967594; Sun, 10 Nov 2019 10:52:47 -0800 (PST) Received: from ernst.home (p5B3BEBE5.dip0.t-ipconnect.de. [91.59.235.229]) by smtp.gmail.com with ESMTPSA id n23sm12721620wmc.18.2019.11.10.10.52.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 10 Nov 2019 10:52:47 -0800 (PST) Date: Sun, 10 Nov 2019 19:52:45 +0100 From: Gary Jennejohn To: Aryeh Friedman Cc: FreeBSD Mailing List , FreeBSD Mailing List Subject: Re: Telling svnlite to ignore specific dirs/ports Message-ID: <20191110195245.3a16bd86@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47B36T0HlZz4Gyk X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=kLQRGq27; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gljennjohn@gmail.com designates 2a00:1450:4864:20::32d as permitted sender) smtp.mailfrom=gljennjohn@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[gljennjohn@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; IP_SCORE(0.00)[ip: (-9.14), ipnet: 2a00:1450::/32(-2.75), asn: 15169(-2.00), country: US(-0.05)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[229.235.59.91.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[]; FREEMAIL_REPLYTO(0.00)[gmail.com]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[d.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Nov 2019 18:52:50 -0000 On Sun, 10 Nov 2019 12:32:56 -0500 Aryeh Friedman wrote: > I am using a pre-release emulator/virtualbox-ose-* (the one in PR 234878) > how do I prevent a svnlite update on /usr/port from clobbering some or all > of the files in the effected port dirs? > Simply make a new directory and copy everything into it. I did that with nvidia-driver version 430 before the main port was updated by creating nvidia-driver-430 and putting all the files into it. -- Gary Jennejohn From owner-freebsd-hackers@freebsd.org Mon Nov 11 16:25:51 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C17381B8FFE for ; Mon, 11 Nov 2019 16:25:51 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x341.google.com (mail-wm1-x341.google.com [IPv6:2a00:1450:4864:20::341]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47BbpQ5HNhz4Lsd for ; Mon, 11 Nov 2019 16:25:50 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x341.google.com with SMTP id b11so13955480wmb.5 for ; Mon, 11 Nov 2019 08:25:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=uRPPrLRXqZSYKsk5IInNDAIYLepMn4jw2qzfYv2qc3A=; b=Lh3e3VAboFOm15v2xNXoyptPkero8JMkbybeLYCopmhFpwFYa9SoXMjEA692hxx5FC AjKNia2VA79tAFSStoN7CUzKP1cYrFHeFLryShFAgecHV43gICMfiBLV9EktdgWW22Hk 4VJTDt1NHufv1hzTb9hdCsCacTLtV1f6HNINie65M31xy3qcADuL9k6qzHEZCzARMbKz 0qYchqXvUI0+jRy7qR9AcTkpPktmaXUVWi7cqtycr3c2175wxp0qkjIRsXzAuDosIKB5 XDR8bRtZ7m4lP2DQXUzErWFi2CH8te5/ZB6RRuM2pNQaTpql0Lfd+zj3J9M84TJH2dNX VYSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=uRPPrLRXqZSYKsk5IInNDAIYLepMn4jw2qzfYv2qc3A=; b=O9ac/Wa9VqPmwT9C2iMugztcmT825LdS4aRCsnbHy9qq3QS+Nj9hv9LsX2IMwsm/m9 dnUM8HHY0ACMrtNoBvLKtUbWQPrEhoy7j4l8X+Kq3bdlTanYxPYMzv/QCqkMVcJNPNEe W8TXdwK7AJ24/hgcTvaC2OO5+MpAXhX4Nox1qAC6XkdLgs5VLY6IQ+nR1z3L4facbOgN d5TFatMIPR8yaC2XoEhOmccf168Rdabg3aGJ1ywarW0lZftephA0TmsVRCcF5Rm5lc7B yz5T5FAI1d/SBAllHpvPKyZFRxKwZ4xq83wf3aVdYJQdMaSLi3Gx+a3+dsD/dRhlFANa mUZg== X-Gm-Message-State: APjAAAXWNingUlT3eQnO4qF5zeCRi0r3WY5RRiDd/PMx+fhJnZGlo+HC iHNvJM4yJUdohR9QzOR6Ca8l5F3/ X-Google-Smtp-Source: APXvYqwnz9ABDuDO8UK8TNLPvHkJ6LFo04n/+l6hyRtAvXyflXwsaa7dHwjsWtR8HqPVX85yt1I5VQ== X-Received: by 2002:a1c:410a:: with SMTP id o10mr21268088wma.117.1573489548258; Mon, 11 Nov 2019 08:25:48 -0800 (PST) Received: from ernst.home (pD9E23368.dip0.t-ipconnect.de. [217.226.51.104]) by smtp.gmail.com with ESMTPSA id p14sm18191146wrq.72.2019.11.11.08.25.47 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 11 Nov 2019 08:25:47 -0800 (PST) Date: Mon, 11 Nov 2019 17:25:43 +0100 From: Gary Jennejohn To: freebsd-hackers Subject: Re: A bounty of 450 (was $100) for rtsx SD card reader driver. Message-ID: <20191111172543.74f95d07@ernst.home> In-Reply-To: <20191102082641.52f64cc8@ernst.home> References: <9C97A802-A542-44B3-A295-79CCF70BF8D2@webweaving.org> <20191102082641.52f64cc8@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.4 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47BbpQ5HNhz4Lsd X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Lh3e3VAb; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gljennjohn@gmail.com designates 2a00:1450:4864:20::341 as permitted sender) smtp.mailfrom=gljennjohn@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; HAS_REPLYTO(0.00)[gljennjohn@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; SUBJECT_HAS_CURRENCY(1.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; IP_SCORE(0.00)[ip: (2.94), ipnet: 2a00:1450::/32(-2.75), asn: 15169(-2.00), country: US(-0.05)]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[104.51.226.217.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; FREEMAIL_REPLYTO(0.00)[gmail.com]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[1.4.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2019 16:25:51 -0000 On Sat, 2 Nov 2019 08:26:41 +0100 Gary Jennejohn wrote: > On Fri, 1 Nov 2019 12:00:01 +0100 > Dirk-Willem van Gulik wrote: > > > On 1 Nov 2019, at 11:48, Gleb Popov wrote: > > > On Wed, Jun 19, 2019 at 10:22 AM Gleb Popov wrote: > > > > >> I've posted a bounty for this bug: > > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 > > > > > > In case anyone is interested, the bounty is $375 already. > > > > It is 450$ now. > > > > This raises several questions: > 1) which version(s) of FreeBSD? > 2) how does a developer get his/her hands on a device which uses this > controller? It is not reasonable to expect a developer will to buy a > laptop or PCI card just to develop a driver. > 3) what is the target environment? Laptop? PCI card? Some other > device with an embedded controller? > So, thanks to the generosity of a FreeBSD user I now have a laptop on loan with one of the Realtek SD card reader controllers. I started working on porting the NetBSD code (basically the same as the OpenBSD code), but the FreeBSD bus and mmc code is radically different, so it will take quite a while to get a working driver. So far only the pci bus probe code works, but that's a start. -- Gary Jennejohn From owner-freebsd-hackers@freebsd.org Tue Nov 12 05:31:52 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4434B178EB9 for ; Tue, 12 Nov 2019 05:31:52 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from tor1-11.mx.scaleengine.net (tor1-11.mx.scaleengine.net [IPv6:2001:470:1:474::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47BxFM5kXgz46xk for ; Tue, 12 Nov 2019 05:31:51 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [192.168.86.56] (c-98-207-102-199.hsd1.ca.comcast.net [98.207.102.199]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by tor1-11.mx.scaleengine.net (Postfix) with ESMTPSA id 09C4B2CABD for ; Tue, 12 Nov 2019 05:31:44 +0000 (UTC) Subject: Re: Strange trouble with ntpd account To: freebsd-hackers@freebsd.org References: <35704598-f05d-d8bb-dca8-8c57ba746ea1@systella.fr> <9eae960b-ff99-1322-e557-ead488e3739f@grosbein.net> <1e0644af-7e10-c57b-fccc-c9582b492443@systella.fr> From: Allan Jude Message-ID: <0f8e8ad9-5b05-4e88-ae09-f575724b070e@freebsd.org> Date: Mon, 11 Nov 2019 21:31:43 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <1e0644af-7e10-c57b-fccc-c9582b492443@systella.fr> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 47BxFM5kXgz46xk X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.68 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.68)[-0.679,0]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2019 05:31:52 -0000 On 2019-11-10 5:18 a.m., BERTRAND Joël wrote: > Eugene Grosbein a écrit : >> /usr/sbin/pwd_mkdb -p /etc/master.passwd > > Thanks a lot, it runs now as expected. But I don't understand why files > are out-of-sync... > > Best regards, > > JB > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > If you edit the files manually instead of using vipw or the pw command, then the database will not be updated unless you run the pwd_mkdb command manually. -- Allan Jude From owner-freebsd-hackers@freebsd.org Tue Nov 12 12:17:46 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 57D331ABCA3 for ; Tue, 12 Nov 2019 12:17:46 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47C6Fj0Dwmz4TkP for ; Tue, 12 Nov 2019 12:17:44 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: by mail-wm1-x32c.google.com with SMTP id z19so2710479wmk.3 for ; Tue, 12 Nov 2019 04:17:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=uiB0T2XCBj4AsMnmGWvMZN5ppefIoz9SQCj74p3REwE=; b=Ka/tZrA+zsV04vkshAD/I9zrCOD0FSLtTXsgd11KLuexTfTyf1TRe+Uw1FGZnQ12zD GWAHI6si0v0Q75pG2QuVTUMfLTAIAZM+y3UNTq/w4sYGaDXXoUmfWiyM9KHuIZjzRdz0 IWEUFr1X6gw+UDvKWKg9Uj3VPVH6+tYcKiI8zdPAlNn8j53sQYXy9i2wCGJykUz5XEkQ +PB1D4An1kePb1DCrmknTAmha4oQODxm+qrOWy5McVjRgmILtuFBNMjYis6jaxoRhCBR ANvqhUeqd4tKrQ/EfNPkUhxfUoyeF7spR9x8k6HyCZ9niTbnjLpsionWZ0DNKgbaSxba 11BQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=uiB0T2XCBj4AsMnmGWvMZN5ppefIoz9SQCj74p3REwE=; b=ivm3P96BlNABWKYntx+rOHe6lnmhoB2Wu0P/i1ISyqw5tc59NES9t17cs1ittd+kJk uepet8xjMflniASC7H02wxfZbKxKJwMtCb1al+9fQzwq7WKeMstl0hreq6qYrrhWaeKl AXch+pakqzAPtc8VqKhLi1DLeoyGtDDAmFswC5z/hnveakt4NOzA/jKr6zvOlAzkKuRi Z+m342JCVRJcEPW+Zv0qY3RuZMSGEQuQu15zHZr+Mm+vbHVg5OMKR9h37hxI9u3ztiPt GFgtV2YmVrI8XUR5Lx1DAoljO7b6L8w8g/OH/Ht7c/eiTisjWlUkuAhD3XoaQjiqh+5P 3GuQ== X-Gm-Message-State: APjAAAXH1gqyeKih43wYfaDuPp31h47Wksq54NwlE89b47KR4COQJKdb RoMq8qK+OzEm4b5OEPeykHM8DXpw X-Google-Smtp-Source: APXvYqz7TEgI4xQv9/NivkA0fUrO2I8zNxTbNIf7LWbTFjrg8lGcIj7qSsrM3df0LH7ACglXfJztCw== X-Received: by 2002:a1c:9dd3:: with SMTP id g202mr3815564wme.43.1573561062218; Tue, 12 Nov 2019 04:17:42 -0800 (PST) Received: from localhost ([213.149.55.100]) by smtp.gmail.com with ESMTPSA id s11sm2187295wrr.43.2019.11.12.04.17.41 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Nov 2019 04:17:41 -0800 (PST) Date: Tue, 12 Nov 2019 13:16:20 +0100 From: Domagoj =?UTF-8?Q?Smol=C4=8Di=C4=87?= To: freebsd-hackers Subject: Re: Hang at stage 3 boot (Race condition?) loader Message-ID: <20191112131620.0000091f@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 47C6Fj0Dwmz4TkP X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=Ka/tZrA+; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of rank1seeker@gmail.com designates 2a00:1450:4864:20::32c as permitted sender) smtp.mailfrom=rank1seeker@gmail.com X-Spamd-Result: default: False [-2.00 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.37), ipnet: 2a00:1450::/32(-2.74), asn: 15169(-2.00), country: US(-0.05)]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; SUBJECT_HAS_QUESTION(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[c.2.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2019 12:17:46 -0000 So ... Things that didn't work: Reinstall of stage 2 /boot/boot Lowering ticks of BootEasy down to 1 tick Replacing BootEasy by installing /boot/mbr So, I thought to try to enable fast boot in BIOS ..., it already was. Just as a last shot, without too much optimism, I've disabled it ... It worked! ;) Domagoj Smol=C4=8Di=C4=87 From owner-freebsd-hackers@freebsd.org Wed Nov 13 19:56:12 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BD9111B9E04 for ; Wed, 13 Nov 2019 19:56:12 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47CwNC64s7z4hfP for ; Wed, 13 Nov 2019 19:56:11 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::26] (court.m5p.com [IPv6:2001:470:1f07:15ff:0:0:0:26]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id xADJu2tP007763 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 13 Nov 2019 14:56:09 -0500 (EST) (envelope-from george+freebsd@m5p.com) To: FreeBSD Hackers From: George Mitchell Subject: Correct SVN revision for latest security fix Autocrypt: addr=george+freebsd@m5p.com; prefer-encrypt=mutual; keydata= mQINBFgnLnwBEADAJDiBKQX77LFRz9wZW8mz3KvaQol2nIremcws0F1mz/zgFlk6uhQVtwnL wb4XL5LdFwcNE1+QZzPLcbYWoWQlz0lBw1bMuKAgr0S6V2e0+I0DqhKeslVFctcTwtvT6pnK VLZXO/7ZGAaLzG4K5vSPzgoevU+YI/pxNsVCH2UO/c3jQW63uEt25mIZbCF1Pu4jgp4RhIgF ujn877r/j6OwBwjzRUu3E6ADp+U825d+5YCuQMEH0wIPnn9GTpXvfdKdbwOIl2akqXqs4cnk iATWfK3r6D4mvDEj1OPHlTvJYcfic7aOIiAwmx1C1v78GjXOdOOA0SGffNix3C2/8oZUO1+V Aet4MKpUKkduWSvULhIkHNZ5Nu8SIJOqge8pmtHxuNXAMfMrAjMdjPwwBFLsYg3Xa2E2oJwg ehTauwd/EDJFcVCyDCyCAYOi/BH/+XQyxzgDlY9N9qj9tHqhVPI6XK7t8UVffGiZUq4rHp5J RdOToqiTNC6eCJBczhMIW+DuFvWU9e6W708T1dz0Accn6Lrgk4eRIn3GFPBG+TxnpjAqHsbW 607dcnD3YKAqY4e+khczL4EObhe7dC1v2fmZiAC6Ds3WHR11IfqoUgCkIwJ590Ej+ElygJFF XxI82wtEz9hkeLLvItpyEJNVjppViRW+Dgl/U7ypHB3qDgYjgwARAQABtChHZW9yZ2UgTWl0 Y2hlbGwgPGdlb3JnZStmcmVlYnNkQG01cC5jb20+iQJUBBMBCAA+FiEENdM4ZHktsJW5kKZX wRES3m+p4fkFAlhZcR0CGyMFCQlmAYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQwRES 3m+p4flqmw/9Emr/ydTG2n9o/IX1yVCNcHVFenVrcOY0L+DGQYZRO/XpLvsGYcuSIQId1w7h l4HZKI89ri2fF2ks6upMqBajLf8s7a8PnYrbw5bPaoOFyNTjv57GLZVsYw95kmMUpK6siuAA fXvHfKUpC/sThbwSv/1CLryVG74+5vdI8j7cQeDM436FThxlVfHKrILIiL34D4WThFB3hV/Y 2A+mQwXmdLcuQXXeAazqsFJL8sgEKSC7GMcExDkVpGc5Rh2hu97a4Sa7qWX9G/YdZOrcDacJ XxfvePn3m3WfRtXN/r0lUfiVXiqkFfbvqSaZQ0I4UvZXNGd/gH4jKHtX9RTH9G96UZeHNoMo tPw9U0fx8Ceh72nUL9qzqnmok/ryWm+6gt4Q1eRP7QAosOa1g/RgUdS1Z9IuCmbXMDp5kbNw L4ZoDMF5U3mmh8/IOKkhGopNLbNv0mwUgC59pnCptiOVx8DyckXWC4L2r6PKbWGrcGIzsUER 9smfL10gpp5H5agjwwPZI6/kzJ0R5nBzQWAlwqI73YAy6JI0HTD6lvxW7yWm2fGjEfmyaBOU 8OLUin7auoFSn+QmD5yNCUn5Ls77qHARkT1ZGocAnQkvZBGTwXpvyJixygXsm+vSUFDYBOSn cR54vdXOEMqrJk6SGau5YI9V7EhQVveE1BUp8ofWf2oo4RG5Ag0EWCcufAEQALuTOxmqMFE+ ieev/rcL3wVJrcuKS+pBbKCY9IIL0OwVf98HQJJcgdOsdDhruVd19nJNlwZ3Fc34wLw7y2GO 9WrpZiYKnI4n9urhLE5r1ydBInlI/1UKZWgM3/dPjJtcXMsC3vnqR9DmOxW4/SbqJDjP3XzO FleT4yip3AaNhPGwEPTZrubVp5hp/JojaZn690TLRwOFXg8NcjpOEs0Bq9M+OLpmsF0flrgs yDfS7y+SQ17R4Iq9T7RxZvZVAh510yGGIZIETYO/4Dh417VVm+gaksOVh2egetpUUvYYc0Ub KaP+5F/WGNrmRb1F6SKypvLlKkYAHCsUUSzsAGl9gbQhEEpuOMbUKp1979HoRMkW+8046kIo 8BZ6ph8izG/g4dZOaEqKGEhqdhYIB7UwMtFFuPtSs5Nl6JrZYni/nzFtTmtVCgcj9PNqrzqt fNFYhNznD6St6wxp3TOm9D3TQF0dzwBM1jZpb8WvmK3k6oy8hbpjiBzxn3kyRA9Vzy+PdbN/ G5a1k0rpZu/ivpBuLCDVGljUmgQigXg6xkk5UxBoHp7MPvG9prZ5jqdEa2r1KgnGjaq+VJsu Uqrw10dVgeG1NulDU1+sQl+/mwtflbkimhjDDjxsVgfrv7uvV/9be+gGm1KATuqdgCboSb1s QAo5ARfwFfChrnh+fTfPpPKHABEBAAGJAiQEGAEIAA8FAlgnLnwCGwwFCQlmAYAACgkQwRES 3m+p4fno9w/4m+swztkzxSWdutjgSv2mw+PdrKWVGFAUD2HoY1Qpi5LNLE6s9pP3qzwpQYwK viOufVJYWZ540ss6BImZBGJwyHouacqrpZjpRo5+ftj07rY1SNd8QjcHDggPfpgJ1D4Il3Xi vRg5/gzkXnRu8dXeVvMP1Ndk/F5wcoLZlQwFtPfu2xyRYIsveXMoyypAvAFSaAGXU0hRzuDJ fGI3LFvpI9UXU2C4MMzjfyZyD2NJEDKOACTo85QQzxgheTDQaDocXW00wknXFMwEItiXp8dO 2zEml/3Kj4efDfjqGpjNefjK0cnj02Byt7y6GozWXyIylrXu0SN9qWRzUVZH3+q+ijA4q3Gm 9uWzLdpjN4QWAiiaEvMhLPohp9DdLsy3kAWWrA3+pAfHSTZXrobMMbSeBkE9E4/WxdKl0nM7 TNslAWcxkTd/7Ly9cxwT8wFdHuQB1hgCmIQxDNXHL1N1ANTeUYum1w9nUg6e1M0UWu+nk3Cw qL7oL2KZe13mQnU/CFwlhbf+i//j3SXrQLlIVQv9Fn805bxIcVo9yqUZyoiV7EUpvOsxDCZh ej3mNYF5nRCf6trEJQVk0aLC26zJAYExykdUlRqc4I13XPhlt+aFSMMkoL/thYO6e9oNFK6Q aJEKXomzxxqpceJVmPH6zvqJbOboAdE/mOD0PoS1M6saIQ== Message-ID: <7d65fc8f-e9b9-6472-199e-41f5010a8714@m5p.com> Date: Wed, 13 Nov 2019 14:56:02 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="l4Gox306sYYg5PTChRor5ZiWMWvZbbWUn" X-Spam-Status: No, score=0.7 required=10.0 tests=HELO_MISC_IP,HELO_NO_DOMAIN autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mattapan.m5p.com X-Rspamd-Queue-Id: 47CwNC64s7z4hfP X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of george@m5p.com designates 74.104.188.4 as permitted sender) smtp.mailfrom=george@m5p.com X-Spamd-Result: default: False [-7.19 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DMARC_NA(0.00)[m5p.com]; TO_DN_ALL(0.00)[]; IP_SCORE(-2.79)[ip: (-9.85), ipnet: 74.104.0.0/16(-4.93), asn: 701(0.87), country: US(-0.05)]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:+,4:~,5:+,6:~]; ASN(0.00)[asn:701, ipnet:74.104.0.0/16, country:US]; TAGGED_FROM(0.00)[freebsd]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Nov 2019 19:56:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --l4Gox306sYYg5PTChRor5ZiWMWvZbbWUn Content-Type: multipart/mixed; boundary="fBCjldC9U5jFEP2jGBX2SkZABk2TMSEFx"; protected-headers="v1" From: George Mitchell To: FreeBSD Hackers Message-ID: <7d65fc8f-e9b9-6472-199e-41f5010a8714@m5p.com> Subject: Correct SVN revision for latest security fix --fBCjldC9U5jFEP2jGBX2SkZABk2TMSEFx Content-Type: multipart/mixed; boundary="------------CA8E5A7E7D40B3B73312FEAD" Content-Language: en-US This is a multi-part message in MIME format. --------------CA8E5A7E7D40B3B73312FEAD Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable The attached security-advisories message cites an incorrect SVN revision number for updating to fix CVE-2018-12207. The revision given is r354653, but it should be r354654 to include the UPDATING fix and the newvers.sh change to report the correct "p" level. I sent a note about this as a reply to the message (so it actually went to freebsd-security), but I suspect my reply is lost in the moderation queue. Can someone please fix this? -- George --------------CA8E5A7E7D40B3B73312FEAD Content-Type: message/rfc822; name="FreeBSD Security Advisory FreeBSD-SA-19:25.mcepsc.eml" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="FreeBSD Security Advisory FreeBSD-SA-19:25.mcepsc.eml" X-Envelope-From: owner-freebsd-security-notifications@freebsd.org Return-Path: Received: from mx2.freebsd.org (mx2.freebsd.org [96.47.72.81]) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPS id xACJDPp5052116 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK) for ; Tue, 12 Nov 2019 14:13:31 -0500 (EST) (envelope-from owner-freebsd-security-notifications@freebsd.org) Received: from mx1.freebsd.org (mx1.freebsd.org [96.47.72.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx2.freebsd.org (Postfix) with ESMTPS id 3371C7B33C; Tue, 12 Nov 2019 19:12:31 +0000 (UTC) (envelope-from owner-freebsd-security-notifications@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 47CHSG6s70z3x7b; Tue, 12 Nov 2019 19:12:30 +0000 (UTC) (envelope-from owner-freebsd-security-notifications@freebsd.org) Delivered-To: freebsd-security-notifications@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2E5491B6073 for ; Tue, 12 Nov 2019 19:12:06 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47CHRp0VPxz3wh5; Tue, 12 Nov 2019 19:12:06 +0000 (UTC) (envelope-from security-advisories@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 945) id 0A6751178; Tue, 12 Nov 2019 19:12:06 +0000 (UTC) From: FreeBSD Security Advisories To: FreeBSD Security Advisories Subject: FreeBSD Security Advisory FreeBSD-SA-19:25.mcepsc Precedence: bulk Message-Id: <20191112191206.0A6751178@freefall.freebsd.org> Date: Tue, 12 Nov 2019 19:12:06 +0000 (UTC) X-BeenThere: freebsd-security-notifications@freebsd.org X-Mailman-Version: 2.1.29 List-Id: "Moderated Security Notifications \[moderated, low volume\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: freebsd-security@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: owner-freebsd-security-notifications@freebsd.org Sender: owner-freebsd-security-notifications@freebsd.org X-Spam-Status: No, score=-6.0 required=10.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mattapan.m5p.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-19:25.mcepsc Security Advisory The FreeBSD Project Topic: Machine Check Exception on Page Size Change Category: core Module: kernel Announced: 2019-11-12 Credits: Intel Affects: All supported versions of FreeBSD. Corrected: 2019-11-12 18:03:26 UTC (stable/12, 12.1-STABLE) 2019-11-12 18:13:04 UTC (releng/12.1, 12.1-RELEASE-p1) 2019-11-12 18:13:04 UTC (releng/12.0, 12.0-RELEASE-p12) 2019-11-12 18:04:28 UTC (stable/11, 11.3-STABLE) 2019-11-12 18:13:04 UTC (releng/11.3, 11.3-RELEASE-p5) CVE Name: CVE-2018-12207 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background The Intel machine check architecture is a mechanism to detect and report hardware errors, such as system bus errors, ECC errors, parity errors, and others. This allows the processor to signal the detection of a machine check error to the operating system. II. Problem Description Intel discovered a previously published erratum on some Intel platforms can be exploited by malicious software to potentially cause a denial of service by triggering a machine check that will crash or hang the system. III. Impact Malicious guest operating systems may be able to crash the host. IV. Workaround No workaround is available. Systems not running untrusted guest virtual machines are not impacted. V. Solution Upgrade your vulnerable system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date, and reboot. Perform one of the following: 1) To update your vulnerable system via a binary patch: Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # shutdown -r +10min "Rebooting for a security update" 2) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. [FreeBSD 12.1] # fetch https://security.FreeBSD.org/patches/SA-19:25/mcepsc.12.1.patch # fetch https://security.FreeBSD.org/patches/SA-19:25/mcepsc.12.1.patch.asc # gpg --verify mcepsc.12.1.patch.asc [FreeBSD 12.0] # fetch https://security.FreeBSD.org/patches/SA-19:25/mcepsc.12.0.patch # fetch https://security.FreeBSD.org/patches/SA-19:25/mcepsc.12.0.patch.asc # gpg --verify mcepsc.12.0.patch.asc [FreeBSD 11.3] # fetch https://security.FreeBSD.org/patches/SA-19:25/mcepsc.11.patch # fetch https://security.FreeBSD.org/patches/SA-19:25/mcepsc.11.patch.asc # gpg --verify mcepsc.11.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch < /path/to/patch c) Recompile your kernel as described in and reboot the system. VI. Correction details The following list contains the correction revision numbers for each affected branch. Branch/path Revision - ------------------------------------------------------------------------- stable/12/ r354650 releng/12.1/ r354653 releng/12.0/ r354653 stable/11/ r354651 releng/11.3/ r354653 - ------------------------------------------------------------------------- To see which files were modified by a particular revision, run the following command, replacing NNNNNN with the revision number, on a machine with Subversion installed: # svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base Or visit the following URL, replacing NNNNNN with the revision number: VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAl3K+khfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n 5cIWdA//dTBwRIejd8vkgB/6wCLfXARU2Nw9je69JwfvpC/3BzkV+oD9rwoL7ltk NtOIu6otRmGnGHvC19WQ/JdlHUgtoxaxB26ROoU5BCYPJL7dU48T6l6RLbNXdMC4 MxU3mgbiDrVw9hhh42qKNVQ+ZzpMjgUPN1WRCyKQNlG7jNm5a8BvBaK0mFYkLdEw 9u+kNpXdaC9Ip45JI4QVS+jyK5JqFYWZw4SlB6AggcMO93QySzWWx4ZjXafw+0EK VoS8ByQ5nTlCVqq+hok+yVEz42mZ9AFSE1E1n3pe5TFZZmxF+NcDVMw324eLWUY3 pVX3S6Y0dCtKKvpyy2WIMrBV4Ro5BX3nQXJINdwCo2IlBRvJgK7u0wK3P0ionsJk Hc4x3sjZQm9Rhb8qqOh01wb7MjmGMWX/nlyishF6MAmnIV3dXctMaG00CSsIMbv9 jtx5v8uSGUHXb8bGYa6QLxaNN1gV6ZLMne1HLunkP7sCX9NYfibjkBXSIfNAkQTn MFrz9LLgy1K+8s2D1yFJZeyAZMWZ82yc14FSbux21pZS8MURpFt0OBYymAlzn0/J fhFEKg7rjKBuIBKjDycu9K8+s8h5TIGDROmgQojeqHm6wmlqyGVIPsREyBcCEvwM 16pasZC9s5C7aoSvzDExekR+LQOc8jVZ80KjNGmMga41tSANKTQ= =9nRn -----END PGP SIGNATURE----- _______________________________________________ freebsd-security-notifications@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-security-notifications To unsubscribe, send any mail to "freebsd-security-notifications-unsubscribe@freebsd.org" --------------CA8E5A7E7D40B3B73312FEAD-- --fBCjldC9U5jFEP2jGBX2SkZABk2TMSEFx-- --l4Gox306sYYg5PTChRor5ZiWMWvZbbWUn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAl3MX9IACgkQwRES3m+p 4flCnxAAnrUyA7lQnRYOVR4qd7T7BV0q44I0/nNgze2aRMo+niN6U2a2KyCcro1r lqA0HiSkRdMBAK1NZ/kJtMp52cEUK+d+BWaHOFYSDUrDEeznFvxEqYxQHCHWEXw8 sg5IpW6zb1fqZUeF5880hc9zHk5LPpxga1cJooM69+IsyTpTL65fxVL4nLcYLCV2 DpH3Ip7ou3yGdimEi+zqsY+hTJ1sYLk8nfsGRUvkB7uAG1dMdY2Kp5xiHy9dRvvv FPfLno6WszYQwZZiRi2EJ32a7CJJ3l1D6N3Y9Uwa3bNTiw8EYZ6DTdgBj/gN3fwd /vQ9g+egZjojtq2LnW8KZX21VLFjW/x5VSREBNYJ9N3ZHEYi8jsAph1qB15ehfFu EfQqcm94zWApDRw8P7Ib1pyBrcvf1gJFkXrbdPM2uBS/fr6Cj55Jvy8EJbaVzhYf 3qxa3VQ1GWWwfKSsvcxGp/RJDovrY9V6Aw+/s20iMGEwsOMLOCKTA7wV6wfQAXFk krMlOlfu2OABT2YKh8D8riQnbZ5/QxJh29axHMahsovLRC9HZDOUTst4SEjhEkH5 g/+iQ6BAlAYuajlHhXDtBIPcV/iNXiq5oRF0ucS2q0B5yd/6PlZ2ILbJiPlLygF7 6TiFlm+vz1xcNt71JuVOUnzTSiaHVjIstWg9dkVroPwin6cOyLw= =TKSy -----END PGP SIGNATURE----- --l4Gox306sYYg5PTChRor5ZiWMWvZbbWUn-- From owner-freebsd-hackers@freebsd.org Thu Nov 14 02:11:35 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 379A41C3CD6 for ; Thu, 14 Nov 2019 02:11:35 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic310-22.consmr.mail.gq1.yahoo.com (sonic310-22.consmr.mail.gq1.yahoo.com [98.137.69.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47D4jK47L3z3RJH for ; Thu, 14 Nov 2019 02:11:33 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: .W.QM.4VM1npFF_KbUwQzg1247RWzWuEhaS6n7ldxSxrPD7tcSaX9JchuFuYqkL UEpA_rwuNbZgP.wkNVdOiVUioSB_8Jjpjbm9YqvHhX5yYD01Wsj7Mvb9Gjmbg916r0CMnM1jwCb2 Ez3YDPV8IvA5e5Sv0wPPVjIVsDuCHX6JSG9JRO.Y3u1I9kLTVJITY29u3OeycB_07MeLgTWgU1W3 EL6Pjt..9KHZ2.sSA1ao4KiqWDZ6fMMpp3.ZoaUzkKoKaSf3Q5qzNv7b1Oqz8XwddnvhnQKbWQoC 8fnsS0Nixpo64JdiprFArQA1u4bbOSIDTuIO4toYFik5lh4HDiqGeIg7BzwQ.XTBEZBZN8.zpiV9 l7iaIXvUBRAJSGwbVpQ4Rpvl95guw6gS2WhNDfjwPa4GkCk.D8aO0rmmBZ50f1g0fGabCoL1whli uFKbQKezZiiFEuxLiCbHuSgrVq_W_1y4Olc4u14w1hWB9IqtkQ59p4g0ROmmam9Fwa2hZcGdzyyJ huTC1bK9G_13jxpw_FePlVppUjSGQrnXfEOfw6Q_Eb4pTF4JCHwmwXuhOCFlHNCmq492hrkeGN_8 Es0OsOt9exD50UZJ9wU73Gh31zrG100Oc1gkEaU.JMHPolyMYdFLCKP9WW52NTB.LeOOaMay2XPP rAL69aiYIIwiL_vSwK8KlIVQsp68XrDIifYX3c7TtbRIb.0WlpezQJ5N3kQ4wm5bTOsfW4koR_rN vSS3ThPyhoaynImKObkV1Nhvn2p53QFk8zZ3Qin_27TyVEkumPLptvY.rUL9IUP5EXJWfUZ5DeIa 1lV7y1bsfHIMRRo2UxiIxH3DnGS45EU3IEbe2oj7p_.24Q2gXgOuRKrdfn9KxG7wabUEJFCVDSMu MmyrRFAeav9jmykEKD0GR2Yc8NeHfQeeCkwS3wSXequZDlnn.bRFODy5b5k2spI5xRCpRVq_qTND ue1rsijJuwtUOYEOMNJm0pw3pFW8Jlkxk1H4Th3pm1.cNSBs6PnJqfrKU_ZT4YbcvyQvBoIF0fHJ QFWLe3ZxvTLRG4LgGXbcs5Wi127zhedQHfnT5CxNB1bnwfalZeEg7DfZnTGUY91BLCtb1wK775rO BTJaWMaasUO3ADcFMPYGvgVBnoNuUj6bJSNnJ8JTPa_nJP3lYyjp8UQDUllsjAWF4Vni29zTlaHN DrmIiwduy9criqjgutfgsVcMvV6gOlcY9WWRpJCv.iAwJyMI_nWmZZxFjvl6BTo7J.4FbgjH0rIb SrP6rBggjXhl1TLRDB7XUFkHXc9WT5oH4XhdHWDvNtQ1tBmqEDnzzzernYdUuqVhKgsgsa3HVl9U fafkjDbtvgoV2Uq4veo7Iqwwx8gNbo65FBQzpahOSWhjJDZGSUz_VBw.IMQaO2IypiWZdRXOgWWR BJH6NDTCA9gvnHw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Thu, 14 Nov 2019 02:11:31 +0000 Received: by smtp415.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 82d3de8299cad81fd615a2dff172740c; Thu, 14 Nov 2019 02:11:27 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: truss assertion failure report Message-Id: <4FE5E95E-8991-4049-A7A9-764477623BC2@yahoo.com> Date: Wed, 13 Nov 2019 18:11:26 -0800 To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.3601.0.10) References: <4FE5E95E-8991-4049-A7A9-764477623BC2.ref@yahoo.com> X-Rspamd-Queue-Id: 47D4jK47L3z3RJH X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.32 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.84)[-0.836,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.988,0]; RCVD_COUNT_TWO(0.00)[2]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE_FREEMAIL(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; RCVD_IN_DNSWL_NONE(0.00)[148.69.137.98.list.dnswl.org : 127.0.5.0]; MV_CASE(0.50)[]; IP_SCORE(0.00)[ip: (1.01), ipnet: 98.137.64.0/21(0.88), asn: 36647(0.70), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 02:11:35 -0000 After setting truss to watch a couple of processes from a poudriere session: # truss -o ~/arm-none-eabi-gcc-truss.log -p 56361 & # truss -o ~/ffmpeg-truss.log -p 37003 & and later using ^C to stop the poudriere session that was still running those processes, truss reported: Assertion failed: (LIST_NEXT(info->curthread, entries) =3D=3D NULL), = function find_exit_thread, file /usr/src/usr.bin/truss/setup.c, line = 416. Assertion failed: (LIST_NEXT(info->curthread, entries) =3D=3D NULL), = function find_exit_thread, file /usr/src/usr.bin/truss/setup.c, line = 416. and also: [2] Abort trap (core dumped) truss -o ~/arm-none-eabi-gcc-truss.log -p = 56361 [3] Abort trap (core dumped) truss -o ~/ffmpeg-truss.log -p 37003 FYI: The poudriere session was a amd64->armv7 cross-build session. # uname -apKU FreeBSD FBSDFHUGE 13.0-CURRENT FreeBSD 13.0-CURRENT #36 r352341M: Sat = Sep 14 15:54:55 PDT 2019 = markmi@FBSDFHUGE:/usr/obj/amd64_clang/amd64.amd64/usr/src/amd64.amd64/sys/= GENERIC-NODBG amd64 amd64 1300047 1300047 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-hackers@freebsd.org Thu Nov 14 14:53:04 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 661191AA0B7 for ; Thu, 14 Nov 2019 14:53:04 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 47DPby5M2Bz4Cjr for ; Thu, 14 Nov 2019 14:53:02 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=To:Date:Message-Id:Subject:Mime-Version:Content-Transfer-Encoding:Content-Type:From; bh=02OF62eTAA/XX2bF/3XjT0vFP51ijkeWkTVlqO6iDQ4=; b=mXaOjpQWf0Y6nYu3Ob7QIq119CwbnAPwjHLNTxwc4j4yoPUveLUgrSHPCiL7Rbv0GDUPdbShzwzrGKtNfrY9kS0amFtrL7Ssu2U6jbfVGjCsFSPIDzUKq2HBc45fIdXBpb/zXNH1WXJElNiJaySoub/jt4y81GXDJ+rwv8dOcf95Xf/qtiq6h0cIXL1a8iXcU6+d/5AjvLqPGY8L1/LtXD2Hy+T7CVh7FTwneREXqMdm/iFRo2y/djDwa3FJxCTKtD05B2Po/MZckpSFPn0BZ0zmjdXyRFWP9QsNiECtNUNo1KkkeNWzXVgqfSLgjxGFy/vI83B4qWazZBtRqyts5A==; Received: from macmini.bk.cs.huji.ac.il ([132.65.179.19]) by kabab.cs.huji.ac.il with esmtp id 1iVGUV-000B1A-46 for freebsd-hackers@freebsd.org; Thu, 14 Nov 2019 16:52:59 +0200 From: Daniel Braniss Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: can the hardware watchdog reboot a hung kernel? Message-Id: Date: Thu, 14 Nov 2019 16:52:57 +0200 To: freebsd-hackers X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47DPby5M2Bz4Cjr X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cs.huji.ac.il header.s=57791128 header.b=mXaOjpQW; dmarc=pass (policy=none) header.from=huji.ac.il; spf=none (mx1.freebsd.org: domain of danny@cs.huji.ac.il has no SPF policy when checking 132.65.116.210) smtp.mailfrom=danny@cs.huji.ac.il X-Spamd-Result: default: False [-1.99 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.994,0]; R_DKIM_ALLOW(-0.20)[cs.huji.ac.il:s=57791128]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-0.70)[ip: (-1.40), ipnet: 132.64.0.0/13(-1.20), asn: 378(-0.96), country: IL(0.05)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[cs.huji.ac.il:+]; DMARC_POLICY_ALLOW(-0.50)[huji.ac.il,none]; RCVD_IN_DNSWL_NONE(0.00)[210.116.65.132.list.dnswl.org : 127.0.10.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:378, ipnet:132.64.0.0/13, country:IL]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 14:53:04 -0000 hi, I have serveral hundred Nano-pi NEO running, and sometimes they hang, = since there is no console available, the only solution is to do a power cycle - not so easy since = they are distributed in three buildings :-) I am looking at the watchdog stuff, but it seems that what I want is not = supported, i.e. reboot the kernel when hung=20 wishful thinking? cheers, danny From owner-freebsd-hackers@freebsd.org Thu Nov 14 15:24:11 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AFF421AAD60 for ; Thu, 14 Nov 2019 15:24:11 +0000 (UTC) (envelope-from SRS0=11Vf=ZG=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 47DQHt4k1nz3M6V for ; Thu, 14 Nov 2019 15:24:10 +0000 (UTC) (envelope-from SRS0=11Vf=ZG=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 BD0D328416; Thu, 14 Nov 2019 16:24:07 +0100 (CET) Received: from illbsd.quip.test (ip-62-24-92-232.net.upcbroadband.cz [62.24.92.232]) (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 F0CCB28411; Thu, 14 Nov 2019 16:24:06 +0100 (CET) Subject: Re: can the hardware watchdog reboot a hung kernel? To: Daniel Braniss , freebsd-hackers References: From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: Date: Thu, 14 Nov 2019 16:24:06 +0100 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-Rspamd-Queue-Id: 47DQHt4k1nz3M6V X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of SRS0=11Vf=ZG=quip.cz=000.fbsd@elsa.codelab.cz has no SPF policy when checking 94.124.105.4) smtp.mailfrom=SRS0=11Vf=ZG=quip.cz=000.fbsd@elsa.codelab.cz X-Spamd-Result: default: False [5.08 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; IP_SCORE(0.89)[ip: (0.41), ipnet: 94.124.104.0/21(0.21), asn: 42000(3.76), country: CZ(0.09)]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[quip.cz]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.99)[0.986,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[4.105.124.94.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(1.00)[0.999,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[000.fbsd@quip.cz,SRS0=11Vf=ZG=quip.cz=000.fbsd@elsa.codelab.cz]; MIME_TRACE(0.00)[0:+]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:42000, ipnet:94.124.104.0/21, country:CZ]; SUBJECT_ENDS_QUESTION(1.00)[]; FROM_NEQ_ENVFROM(0.00)[000.fbsd@quip.cz, SRS0=11Vf=ZG=quip.cz=000.fbsd@elsa.codelab.cz] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 15:24:11 -0000 Daniel Braniss wrote on 2019/11/14 15:52: > hi, > I have serveral hundred Nano-pi NEO running, and sometimes they hang, since there is no console > available, the only solution is to do a power cycle - not so easy since they are distributed in three buildings :-) > > I am looking at the watchdog stuff, but it seems that what I want is not supported, i.e. > reboot the kernel when hung > > wishful thinking? There is watchdog and watchdogd in base. I never tried it but there are some solutions which need support in BIOS / board where watchdog is communicating with HW and if OS freezes, HW don't get reply from OS and issue reboot after timeout. I don't know if Nano-pi has this support or not. Miroslav Lachman From owner-freebsd-hackers@freebsd.org Thu Nov 14 15:29:20 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 12B901AB0DD for ; Thu, 14 Nov 2019 15:29:20 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47DQPq0QJDz3y83 for ; Thu, 14 Nov 2019 15:29:18 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13:0:0:0:5]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id xAEFSvYf005402 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 14 Nov 2019 15:28:57 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: danny@cs.huji.ac.il Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id xAEFSsXw025517 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 14 Nov 2019 22:28:54 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: can the hardware watchdog reboot a hung kernel? To: Daniel Braniss , freebsd-hackers References: From: Eugene Grosbein Message-ID: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> Date: Thu, 14 Nov 2019 22:28:49 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record * -0.0 SPF_PASS SPF: sender matches SPF record * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on hz.grosbein.net X-Rspamd-Queue-Id: 47DQPq0QJDz3y83 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=permerror (mx1.freebsd.org: domain of eugen@grosbein.net uses mechanism not recognized by this client) smtp.mailfrom=eugen@grosbein.net X-Spamd-Result: default: False [-2.69 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[grosbein.net]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; R_SPF_PERMFAIL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-1.59)[ip: (-4.00), ipnet: 2a01:4f8::/29(-2.29), asn: 24940(-1.65), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 15:29:20 -0000 14.11.2019 21:52, Daniel Braniss wrote: > hi, > I have serveral hundred Nano-pi NEO running, and sometimes they hang, since there is no console > available, the only solution is to do a power cycle - not so easy since they are distributed in three buildings :-) > > I am looking at the watchdog stuff, but it seems that what I want is not supported, i.e. > reboot the kernel when hung > > wishful thinking? It's possible if the hardware has such a watchdog and kernel subsystem watchdog(4) supports it. rc.conf(5) manual page describes watchdogd_enable option. From owner-freebsd-hackers@freebsd.org Thu Nov 14 15:30:24 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C9DA61AB23B for ; Thu, 14 Nov 2019 15:30:24 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 47DQR36xHQz40Y6 for ; Thu, 14 Nov 2019 15:30:23 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=SCS6bZwZKoicEVnUIe+fqfHAVsjW5ocoLt9Rjyp5hqM=; b=2R2kFcZrQal76zL0klMw6O1bcADXxOOxnt49oyRaC2dFBDCtS3ofwmmb+EFB75fMQG1XnpMnvDz0NcuDJDZR7QjVR3/4aIpDssM7bke+9F7NYytaCQys5cFYBO4/IgexbPzEc0DM1wcZL7tmf5I9R06+15N6H/Bmtn+Hs/ysz2PdzDOw/QFIggyxLa2mt//DFBR2WkZu7lEJPYsQ2sRdAHMx3VT9kSyV/aKlCgRO7f6uy8SG0SoaYC2n/3cVDRbdoYw3p3YQEM4vEo7dP2n+Gk+YtsViX0Mmp4xfE/QTRKb7VVZSfox7adHuyaBQN3ARxf7FfoHvfpkk7FB/xGwj4g==; Received: from macmini.bk.cs.huji.ac.il ([132.65.179.19]) by kabab.cs.huji.ac.il with esmtp id 1iVH4f-000D64-7l; Thu, 14 Nov 2019 17:30:21 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: can the hardware watchdog reboot a hung kernel? From: Daniel Braniss In-Reply-To: Date: Thu, 14 Nov 2019 17:30:20 +0200 Cc: freebsd-hackers Content-Transfer-Encoding: quoted-printable Message-Id: <33FF6A8A-C01A-4261-A35A-0E05C96FD04A@cs.huji.ac.il> References: To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47DQR36xHQz40Y6 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cs.huji.ac.il header.s=57791128 header.b=2R2kFcZr; dmarc=pass (policy=none) header.from=huji.ac.il; spf=none (mx1.freebsd.org: domain of danny@cs.huji.ac.il has no SPF policy when checking 132.65.116.210) smtp.mailfrom=danny@cs.huji.ac.il X-Spamd-Result: default: False [-1.99 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.994,0]; R_DKIM_ALLOW(-0.20)[cs.huji.ac.il:s=57791128]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[cs.huji.ac.il:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[210.116.65.132.list.dnswl.org : 127.0.10.0]; DMARC_POLICY_ALLOW(-0.50)[huji.ac.il,none]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:378, ipnet:132.64.0.0/13, country:IL]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.70)[ip: (-1.40), ipnet: 132.64.0.0/13(-1.20), asn: 378(-0.96), country: IL(0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 15:30:24 -0000 > On 14 Nov 2019, at 17:24, Miroslav Lachman <000.fbsd@quip.cz> wrote: >=20 > Daniel Braniss wrote on 2019/11/14 15:52: >> hi, >> I have serveral hundred Nano-pi NEO running, and sometimes they hang, = since there is no console >> available, the only solution is to do a power cycle - not so easy = since they are distributed in three buildings :-) >> I am looking at the watchdog stuff, but it seems that what I want is = not supported, i.e. >> reboot the kernel when hung >> wishful thinking? >=20 > There is watchdog and watchdogd in base. I never tried it but there = are some solutions which need support in BIOS / board where watchdog is = communicating with HW and if OS freezes, HW don't get reply from OS and = issue reboot after timeout. > I don't know if Nano-pi has this support or not. >=20 > Miroslav Lachman the nano reports: aw_wdog0: mem 0x1c20ca0-0x1c20cbf irq = 26 on simplebus0 so there is something there :-) From owner-freebsd-hackers@freebsd.org Thu Nov 14 15:35:10 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1487D1AB5F7 for ; Thu, 14 Nov 2019 15:35:10 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 47DQXY2GxMz46jD for ; Thu, 14 Nov 2019 15:35:08 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=LPfkPJXZ5SAYhzQ0NPHh9EYaKtvb4jK6I+dEyYbeOyU=; b=2AygW/a/Rgx5LeB03NFH3+MqbfgwR9gK9OC/bk3ic/H+FbsI6G0ROhdN18C8IZdI7eCxiroqXskC7S6fYhbOSS0YSOhDnYN5uSD4hqakm2dm48JClzwQrxE0NNIzUuYhH60h4FK7afVxPapmT+LBTZwwxDMTrQOMZPYSe3wzmPUgmgFX3NCWN7MtvAY3Tj0pjkDohQQvvWG/nQbJ8qnD6qdkbuZvwtOj7pY6Nt2JjOBX2YZKc9Bzx8CkSgvj9YtLL67bctk8cl4qnuxbkaKW4owTM7zPTL6cjR5WoUUf+cB9IelEAE02GZ5Sy/oMteX4oFtrgERKAGNbg3JyAa/QRQ==; Received: from macmini.bk.cs.huji.ac.il ([132.65.179.19]) by kabab.cs.huji.ac.il with esmtp id 1iVH9G-000Dhv-89; Thu, 14 Nov 2019 17:35:06 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: can the hardware watchdog reboot a hung kernel? From: Daniel Braniss In-Reply-To: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> Date: Thu, 14 Nov 2019 17:35:06 +0200 Cc: freebsd-hackers Content-Transfer-Encoding: quoted-printable Message-Id: <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> To: Eugene Grosbein X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47DQXY2GxMz46jD X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cs.huji.ac.il header.s=57791128 header.b=2AygW/a/; dmarc=pass (policy=none) header.from=huji.ac.il; spf=none (mx1.freebsd.org: domain of danny@cs.huji.ac.il has no SPF policy when checking 132.65.116.210) smtp.mailfrom=danny@cs.huji.ac.il X-Spamd-Result: default: False [-1.99 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.994,0]; R_DKIM_ALLOW(-0.20)[cs.huji.ac.il:s=57791128]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[cs.huji.ac.il:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[210.116.65.132.list.dnswl.org : 127.0.10.0]; DMARC_POLICY_ALLOW(-0.50)[huji.ac.il,none]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:378, ipnet:132.64.0.0/13, country:IL]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-0.70)[ip: (-1.40), ipnet: 132.64.0.0/13(-1.20), asn: 378(-0.96), country: IL(0.05)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 15:35:10 -0000 > On 14 Nov 2019, at 17:28, Eugene Grosbein wrote: >=20 > 14.11.2019 21:52, Daniel Braniss wrote: >=20 >> hi, >> I have serveral hundred Nano-pi NEO running, and sometimes they hang, = since there is no console >> available, the only solution is to do a power cycle - not so easy = since they are distributed in three buildings :-) >>=20 >> I am looking at the watchdog stuff, but it seems that what I want is = not supported, i.e. >> reboot the kernel when hung=20 >>=20 >> wishful thinking? >=20 > It's possible if the hardware has such a watchdog and kernel subsystem = watchdog(4) supports it. > rc.conf(5) manual page describes watchdogd_enable option. >=20 yes, but it relys on user land, what if the kernel is hung?=20 From owner-freebsd-hackers@freebsd.org Thu Nov 14 15:53:34 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2009C1ABB56 for ; Thu, 14 Nov 2019 15:53:34 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47DQxm5XvVz4Yll for ; Thu, 14 Nov 2019 15:53:32 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13:0:0:0:5]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id xAEFrBVv005488 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 14 Nov 2019 15:53:12 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: danny@cs.huji.ac.il Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id xAEFr9v9025817 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 14 Nov 2019 22:53:09 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: can the hardware watchdog reboot a hung kernel? To: Daniel Braniss References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> Cc: freebsd-hackers From: Eugene Grosbein Message-ID: Date: Thu, 14 Nov 2019 22:53:04 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record * -0.0 SPF_PASS SPF: sender matches SPF record * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on hz.grosbein.net X-Rspamd-Queue-Id: 47DQxm5XvVz4Yll X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=permerror (mx1.freebsd.org: domain of eugen@grosbein.net uses mechanism not recognized by this client) smtp.mailfrom=eugen@grosbein.net X-Spamd-Result: default: False [-2.69 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[grosbein.net]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; R_SPF_PERMFAIL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; IP_SCORE(-1.59)[ip: (-4.00), ipnet: 2a01:4f8::/29(-2.29), asn: 24940(-1.65), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 15:53:34 -0000 14.11.2019 22:35, Daniel Braniss wrote: >> It's possible if the hardware has such a watchdog and kernel subsystem watchdog(4) supports it. >> rc.conf(5) manual page describes watchdogd_enable option. >> > > yes, but it relys on user land, what if the kernel is hung? No, it does not relay on userland. Well, in part: userland daemon replies to hardware watchdog "host is alive" and if system hangs and watchdog stops getting replies, it resets the system. From owner-freebsd-hackers@freebsd.org Thu Nov 14 16:02:40 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C8A4F1AC09A for ; Thu, 14 Nov 2019 16:02:40 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound2m.ore.mailhop.org (outbound2m.ore.mailhop.org [54.149.155.156]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47DR8J0q5Qz3F3H for ; Thu, 14 Nov 2019 16:02:39 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1573747356; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=Olh67MR7OcRbzolpgogXCWF+sjn4kb0GFK7Z8GkeUbg72zJBVHVmQSA4SFldx6CbhnvJsH6y9fF+C SgFxqv9USDKiyWMB2xI8oNdq523cWlc+nyXVeY3RiXablRrPV1/jZ1Rfpq/9avcJG3mA8tUZT2Wrb9 Z8adbrjKaDk+mhCg0kN2/U0Q6poXrmAAeIEw3axKR3asM0lTd2AVXvwcmAvX9EHaoYNJQj8XxSJWAe stF+ibAeov1pK5vGhZ3Gdw+Ri0u5xhG3hobEQTGeGtiT1iuF10tlZuOkm8rhfpSm6ZLkniKuyAv08s d0W5o6FX8fPcnZEI8DpissJ0uWP8eiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=4+3wJLkBDJxWaW1NiXR+Qw0YsTXtWD1eAlhu0IH/Ny0=; b=UOiQ+X0/4nS+fg7LKsOzR2WnaoW07RgI8dP+soWmUGEdAkuXdmRR6tWyzyTPb76gKmZdgoGg4M6bs MPiy61PD+R5RPT7T+CNFx5ICyi98Uo5MDIv2Ha4pFqiL9bOewvsqvXRN24PM4QNhMxn/MvfwiM/sK8 0v8XjqcGHIVNifdhnFqVlAV0Lt6/jBvEQ6ISiIuzL7FpZeACZ8nmzbyP/3OG/7JzzqayhEJMM+hWjl 8+lOYn6/HqDLqMY3lTXVAhZ+UeKet2peu1mLUs28mWD1JS37N8jn0bevZbCt0YqmGt2J1bazLEXVDq yHrUjovVD3hQKBhFeM0BtS6AzEp6C8Q== ARC-Authentication-Results: i=1; outbound4.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=4+3wJLkBDJxWaW1NiXR+Qw0YsTXtWD1eAlhu0IH/Ny0=; b=Y30WDyVXqqktd/Itj0jfdB5f08VtRU2TSmYLgEnKPSrtpXdlBmYWLAvvSRiQr4vGFXGmJOGx9H08/ Uzd5xoz2d5CaExD/e+2x26eoNeS6q0BWmBH9vi3hdMRD73JpSx9c0Sq/qiaie0NhqWAiwRIdV+o2fT kH/BMQ/qpBdIG814RSAMnFPTlL4S1NRbPG7QcfMsH+Ht5G8AhST9oyDrPp+yo7tcFaufRP6VEZTC8z cI4jPNjKwkl2f4vHOc9mHIB7slXBNmzHvDlkrSI7PBIuO0ngVwoFJmfiQS7NQ9X/U6/h6lwXMY7jQm U5Cn+sbf3j+iGz1vh01EVJ2n2QPW8BQ== X-MHO-RoutePath: aGlwcGll X-MHO-User: 2a9baf79-06f8-11ea-829e-79a40d15cccd X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound4.ore.mailhop.org (Halon) with ESMTPSA id 2a9baf79-06f8-11ea-829e-79a40d15cccd; Thu, 14 Nov 2019 16:02:35 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id xAEG2WIT027870; Thu, 14 Nov 2019 09:02:32 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> Subject: Re: can the hardware watchdog reboot a hung kernel? From: Ian Lepore To: Daniel Braniss Cc: freebsd-hackers Date: Thu, 14 Nov 2019 09:02:32 -0700 In-Reply-To: <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47DR8J0q5Qz3F3H X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.92 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.92)[-0.916,0]; ASN(0.00)[asn:16509, ipnet:54.148.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 16:02:40 -0000 On Thu, 2019-11-14 at 17:35 +0200, Daniel Braniss wrote: > > On 14 Nov 2019, at 17:28, Eugene Grosbein > > wrote: > > > > 14.11.2019 21:52, Daniel Braniss wrote: > > > > > hi, > > > I have serveral hundred Nano-pi NEO running, and sometimes they > > > hang, since there is no console > > > available, the only solution is to do a power cycle - not so easy > > > since they are distributed in three buildings :-) > > > > > > I am looking at the watchdog stuff, but it seems that what I want > > > is not supported, i.e. > > > reboot the kernel when hung > > > > > > wishful thinking? > > > > It's possible if the hardware has such a watchdog and kernel > > subsystem watchdog(4) supports it. > > rc.conf(5) manual page describes watchdogd_enable option. > > > > yes, but it relys on user land, what if the kernel is hung? > It relies on the userland daemon to issue the ioctl() calls to pet the dog. If the kernel is hung, then userland code isn't going to run either, and the watchdog petting won't happen, and eventually the hardware reboots. We use this at $work specifically to reboot if the kernel hangs, using this config: watchdogd_enable=YES watchdogd_flags="-s 16 -t 64 -x 64" That says the daemon should pet the dog every 16 seconds, and the hardware is programmed to reboot if 64 seconds elapses without petting. In addition, when watchdogd is shutdown normally (like during a normal system reboot) it doesn't disable the watchdog hardware, it sets the timeout to 64s to protect against any kind of hang during the reboot. The -t and -x times can be different, 64s just happens to work well for us in both cases. -- Ian From owner-freebsd-hackers@freebsd.org Thu Nov 14 18:10:26 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 17B0C1AF433 for ; Thu, 14 Nov 2019 18:10:26 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 47DTzj6ZSlz46pK; Thu, 14 Nov 2019 18:10:25 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=ZBc4FA1XV8v3aX9IwabxsnNYH9WCSkU81dgR/BvOkg8=; b=Yv4VUEvwH67SPxtKrt8ZF3oE6n3Uwn3RpFvnJx1iw9hPI+ZEmmzzSitiKp2LblxARL0vAlWLPtM3nX7y/IYT7G3y+GpqZmVfGGk4QWuoGdW7YyoX4UwpMc9OUG8/op9VsWPvWUwhlF4Nm5kRy6+AzcesOY+J84lYafHeuS9pCJicoZgyvMVtMDmUTg2G/fk7Br/LuvnJsxLL5cLjK7aJu6xaziPeHnrHQ1lEBOauwWsg8vhAmSE5ExmqTEPT6iqfCo/IKevwSKijusM4SjdRQhM0KiR9n4FIAmeD9V4wNbGEUv85aVHjK4bND0DoM249TMEQnt0xUFmFkNbRO3rI9A==; Received: from macmini.bk.cs.huji.ac.il ([132.65.179.19]) by kabab.cs.huji.ac.il with esmtp id 1iVJZV-000NLO-7d; Thu, 14 Nov 2019 20:10:21 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: can the hardware watchdog reboot a hung kernel? From: Daniel Braniss In-Reply-To: <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> Date: Thu, 14 Nov 2019 20:10:20 +0200 Cc: freebsd-hackers Content-Transfer-Encoding: quoted-printable Message-Id: References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47DTzj6ZSlz46pK X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.98 / 15.00]; NEURAL_HAM_MEDIUM(-0.98)[-0.982,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 18:10:26 -0000 > On 14 Nov 2019, at 18:02, Ian Lepore wrote: >=20 > On Thu, 2019-11-14 at 17:35 +0200, Daniel Braniss wrote: >>> On 14 Nov 2019, at 17:28, Eugene Grosbein >>> wrote: >>>=20 >>> 14.11.2019 21:52, Daniel Braniss wrote: >>>=20 >>>> hi, >>>> I have serveral hundred Nano-pi NEO running, and sometimes they >>>> hang, since there is no console >>>> available, the only solution is to do a power cycle - not so easy >>>> since they are distributed in three buildings :-) >>>>=20 >>>> I am looking at the watchdog stuff, but it seems that what I want >>>> is not supported, i.e. >>>> reboot the kernel when hung=20 >>>>=20 >>>> wishful thinking? >>>=20 >>> It's possible if the hardware has such a watchdog and kernel >>> subsystem watchdog(4) supports it. >>> rc.conf(5) manual page describes watchdogd_enable option. >>>=20 >>=20 >> yes, but it relys on user land, what if the kernel is hung?=20 >>=20 >=20 > It relies on the userland daemon to issue the ioctl() calls to pet the > dog. If the kernel is hung, then userland code isn't going to run > either, and the watchdog petting won't happen, and eventually the > hardware reboots. >=20 > We use this at $work specifically to reboot if the kernel hangs, using > this config: >=20 > watchdogd_enable=3DYES > watchdogd_flags=3D"-s 16 -t 64 -x 64" >=20 > That says the daemon should pet the dog every 16 seconds, and the > hardware is programmed to reboot if 64 seconds elapses without = petting. > In addition, when watchdogd is shutdown normally (like during a normal > system reboot) it doesn't disable the watchdog hardware, it sets the > timeout to 64s to protect against any kind of hang during the reboot.=20= > The -t and -x times can be different, 64s just happens to work well = for > us in both cases. >=20 > -- Ian >=20 ok, that is very encouraging, now a last question how can i hang the kernel to test that the watchdog kicks in? apart from = writing a kernel module :-) =20 >=20 From owner-freebsd-hackers@freebsd.org Thu Nov 14 18:13:49 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DCCDD1AF6FD for ; Thu, 14 Nov 2019 18:13:49 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47DV3c3Z7Cz4C7K for ; Thu, 14 Nov 2019 18:13:48 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1573755226; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=hkltkIKhwA1J1QI5lnfe6F0nBosETdlEbnYmLu2652GElHVYC3er+fs1XJ9eA18fCl5RllAWHQkP9 RH5M18Mx+X+p1ter39bwbB9Wq17hTHZrGBQGwRRvg5XQzEGVx9EtLPxA11VUZhBkbxsp6W1pPnL0Tp rbextfJt45bXSaEhWWdZx1pPw/3jgEs81B6HEOFEhNUG757+KLqSzCcRAztKiW0q4b45VthoifSUXT 8H0ryePApVM7c7J/dJo3NvXjjIIalRBtaPgZobjAV0T4E8aoYyPVrkfwAW38BeROOuTc6JlMJc+kKk WwLuh2IGmcZjQHe5o6OONfL+fR7XLkA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=n73dx7dTF1kOC15Bh1uayku8lVO/FBEct8IbXAvrqpE=; b=rS3K0zesC5Hpv30ZXIO/4NbMFGDD5b/2pC6epr3VHag7Dakrx9f23clCAhy7cSP66+z90TjpktJY0 TX+jXj1gUwRJOglMunsDG7ozcxPP65/pqA4LlH0I1j/VXM64ZOKZy7WAGORn9RgQidZERvxAroVXbo L2HtPbY6EK1b3hAWieTjEJmQBShmY8xY6GsdQu+sEyX8g5t1PE9zgiJ8a+LtwCVLEKhdGp/9MHOoCQ I1j7XOtrjMXGW5ZeKWpYIUTVuPAeUvGoSiijouZEBjfqmcEHm9qck72RHeJAtikuZ5b4e7IBkRZUha IDlawmHf2Gs9jh8Qn+iGgnLId4Cy+tg== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=n73dx7dTF1kOC15Bh1uayku8lVO/FBEct8IbXAvrqpE=; b=nkflKJAbtn6dQwOHAR43RWygtz5ahmF1yga6r0CH48/Y6kUAeWC/oY9RTPK9CSjX+LCv52ltULrx7 /ut4AkueLlrOdTqihVD0fJw/NYZ/5H/Kdwau2+C/jEHpIaIJadVyRvFRhpWwKMhytQnGsM0DYlUdfT 1k5czkex3T0WyJy8te7frNaNuCj6MSsl7n5SpbRY7C1fZsYNkrs9gs9oo4UxNZkJ7V9dHOHc1pP4v6 AdCpq6SQweNns2ZT8jk7eT3DjOVQxQ5SnlLK4naSKl6M9ldAJ/ayby/DFxmVqZY2giYrWqVtBJ/dR2 n2svaHRlFbMZRIM5JvlmOAwCllvfiEg== X-MHO-RoutePath: aGlwcGll X-MHO-User: 7ceb28e0-070a-11ea-b80c-052b4a66b6b2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 7ceb28e0-070a-11ea-b80c-052b4a66b6b2; Thu, 14 Nov 2019 18:13:44 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id xAEIDftA028254; Thu, 14 Nov 2019 11:13:41 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <8814791e9634980810a41b9cc229612e225a40ee.camel@freebsd.org> Subject: Re: can the hardware watchdog reboot a hung kernel? From: Ian Lepore To: Daniel Braniss Cc: freebsd-hackers Date: Thu, 14 Nov 2019 11:13:41 -0700 In-Reply-To: References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47DV3c3Z7Cz4C7K X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.92 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.92)[-0.916,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 18:13:50 -0000 On Thu, 2019-11-14 at 20:10 +0200, Daniel Braniss wrote: > > On 14 Nov 2019, at 18:02, Ian Lepore wrote: > > > > On Thu, 2019-11-14 at 17:35 +0200, Daniel Braniss wrote: > > > > On 14 Nov 2019, at 17:28, Eugene Grosbein > > > > wrote: > > > > > > > > 14.11.2019 21:52, Daniel Braniss wrote: > > > > > > > > > hi, > > > > > I have serveral hundred Nano-pi NEO running, and sometimes > > > > > they > > > > > hang, since there is no console > > > > > available, the only solution is to do a power cycle - not so > > > > > easy > > > > > since they are distributed in three buildings :-) > > > > > > > > > > I am looking at the watchdog stuff, but it seems that what I > > > > > want > > > > > is not supported, i.e. > > > > > reboot the kernel when hung > > > > > > > > > > wishful thinking? > > > > > > > > It's possible if the hardware has such a watchdog and kernel > > > > subsystem watchdog(4) supports it. > > > > rc.conf(5) manual page describes watchdogd_enable option. > > > > > > > > > > yes, but it relys on user land, what if the kernel is hung? > > > > > > > It relies on the userland daemon to issue the ioctl() calls to pet > > the > > dog. If the kernel is hung, then userland code isn't going to run > > either, and the watchdog petting won't happen, and eventually the > > hardware reboots. > > > > We use this at $work specifically to reboot if the kernel hangs, > > using > > this config: > > > > watchdogd_enable=YES > > watchdogd_flags="-s 16 -t 64 -x 64" > > > > That says the daemon should pet the dog every 16 seconds, and the > > hardware is programmed to reboot if 64 seconds elapses without > > petting. > > In addition, when watchdogd is shutdown normally (like during a > > normal > > system reboot) it doesn't disable the watchdog hardware, it sets > > the > > timeout to 64s to protect against any kind of hang during the > > reboot. > > The -t and -x times can be different, 64s just happens to work well > > for > > us in both cases. > > > > -- Ian > > > > ok, that is very encouraging, now a last question > how can i hang the kernel to test that the watchdog kicks in? apart > from writing a kernel module :-) > Drop into the kernel debugger and just let it sit there until it reboots (or fails to, I guess). Do "sysctl debug.kdb.enter=1". -- Ian From owner-freebsd-hackers@freebsd.org Thu Nov 14 18:19:59 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 56B1B1AF99F for ; Thu, 14 Nov 2019 18:19:59 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47DVBl0Vq8z4KHj for ; Thu, 14 Nov 2019 18:19:58 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1573755598; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=ANJFWXooSFYKAh98KjEvideyHKTmhssDg6/eTKwiikvBFhuq73fRILk8uFUHb+UjEgLSlFrRDFmvP Wl85Exz8cdSX67DkuNc8jJ0wRWDVzWQ53dkhS2Xrm5fQqnWu90JmjXO3spPrnkDUOzkUqGbcxxscY0 vJACN1i76CvWqv4Qb3GdrVov9qZCi6vqX//r6arBOnX34u7ax6WaARARsb+I4xKHkNrqlgCzCJZESE 0jbOkYWQ99jc5cMJlVOuy4Hn2VsxFKiSkp90ZeKEGVFGjSLvuskQsflEAA5FceStZU72SOSke5F4uK ipF5sDdvekQnRcXI8b2H1pA1lXIKetw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=fYuAWyq8YPq0kYQJX88IirYwWf45UAwBCxIeEyAqtAI=; b=psI8n8rjOFozhdQwCSY+0F/drSurIz7ShplKbid6c0jP1KckBw4KLpec2fFBhBAmpJEX3GjdQNZYl z7QaFAMNR/CwfbknBK6PyTfP4hfBK7FZhq1TKRCB3MXEsgOWs31GquKjzuboBYVs53Grl2hb3qY+R+ ovCje33+x19y0kfcObkkPJsxMgVfPsxt64WgkiF/qz6Hl6Tu8ICIhc9k26uJvH4DTyMoEyFhyzJ4DZ wgCiBY1/y5nQKK1WQskNsSrArxZn7xByPLH8oFR3+qIdWDy4fRnLFKzUZYTrv9Jfv7+hqGlxmTcihx 8UsBjBv9Ua0ySaSuf2W4AvGzdSITztg== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=fYuAWyq8YPq0kYQJX88IirYwWf45UAwBCxIeEyAqtAI=; b=NdsxqVZEmD5D4jIiHpTJ0gZAK6m6tSSLOA1FFIkYryDvkrAYNwJPOhq6/5vGBBzfnvXwOohqLT2J9 1WXt/f6p3H5/vP09hVnIXZsYF2B7KDjQLu7aehbfev/G4ILRgTQnELX2ts6xbFFLa7PZlFmvvMLPHj k2x3syVGUEiYCd2CEZ2ULkO7fdKmdwpscmU2G5djduOzAbroe0Oj2Z99TCNvPh/Kl7QVfHLkpd6Mh+ KPvMjKFWb0s6ZQ03zFJU4fiPn0XAS60q2QkQEClx5oiGnlhLpohywlYc7r/7BgZTbpKWW602ascH25 20PByq/l4N0d3CSYwSJYwX3/Xwk7h3g== X-MHO-RoutePath: aGlwcGll X-MHO-User: 5a686a4a-070b-11ea-b80c-052b4a66b6b2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 5a686a4a-070b-11ea-b80c-052b4a66b6b2; Thu, 14 Nov 2019 18:19:56 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id xAEIJqug028268; Thu, 14 Nov 2019 11:19:52 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: can the hardware watchdog reboot a hung kernel? From: Ian Lepore To: Daniel Braniss Cc: freebsd-hackers Date: Thu, 14 Nov 2019 11:19:52 -0700 In-Reply-To: References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 47DVBl0Vq8z4KHj X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.92 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.92)[-0.917,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 18:19:59 -0000 On Thu, 2019-11-14 at 20:10 +0200, Daniel Braniss wrote: > > On 14 Nov 2019, at 18:02, Ian Lepore wrote: > > > > On Thu, 2019-11-14 at 17:35 +0200, Daniel Braniss wrote: > > > > On 14 Nov 2019, at 17:28, Eugene Grosbein > > > > wrote: > > > > > > > > 14.11.2019 21:52, Daniel Braniss wrote: > > > > > > > > > hi, > > > > > I have serveral hundred Nano-pi NEO running, and sometimes they > > > > > hang, since there is no console > > > > > available, the only solution is to do a power cycle - not so easy > > > > > since they are distributed in three buildings :-) > > > > > > > > > > I am looking at the watchdog stuff, but it seems that what I want > > > > > is not supported, i.e. > > > > > reboot the kernel when hung > > > > > > > > > > wishful thinking? > > > > > > > > It's possible if the hardware has such a watchdog and kernel > > > > subsystem watchdog(4) supports it. > > > > rc.conf(5) manual page describes watchdogd_enable option. > > > > > > > > > > yes, but it relys on user land, what if the kernel is hung? > > > > > > > It relies on the userland daemon to issue the ioctl() calls to pet the > > dog. If the kernel is hung, then userland code isn't going to run > > either, and the watchdog petting won't happen, and eventually the > > hardware reboots. > > > > We use this at $work specifically to reboot if the kernel hangs, using > > this config: > > > > watchdogd_enable=YES > > watchdogd_flags="-s 16 -t 64 -x 64" > > > > That says the daemon should pet the dog every 16 seconds, and the > > hardware is programmed to reboot if 64 seconds elapses without petting. > > In addition, when watchdogd is shutdown normally (like during a normal > > system reboot) it doesn't disable the watchdog hardware, it sets the > > timeout to 64s to protect against any kind of hang during the reboot. > > The -t and -x times can be different, 64s just happens to work well for > > us in both cases. > > > > -- Ian > > > > ok, that is very encouraging, now a last question > how can i hang the kernel to test that the watchdog kicks in? apart from writing a kernel module :-) > One thing to be careful of here is multicore systems. If you have a critical app running on a multicore system, that app can hang (maybe it tries to read from a device that has malfunctioned and essentially gets hung forever in a device driver that doesn't implement timeouts very well or something). In that case, only one core is hung, so watchdogd will be able to keep petting the dog to prevent a reboot, but since your app is hung on a different core, you aren't really getting the protection you need. The fix for that is to either turn you app into watchdogd (have it make the periodic ioctl() calls to pet the dog), or use the '-e cmd' option with watchdogd, and make 'cmd' be a script that somehow verifies that your critical application is still running properly. -- Ian From owner-freebsd-hackers@freebsd.org Thu Nov 14 18:20:16 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F302B1AF9E4 for ; Thu, 14 Nov 2019 18:20:16 +0000 (UTC) (envelope-from gordon@tetlows.org) Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47DVC40r0yz4KSt for ; Thu, 14 Nov 2019 18:20:14 +0000 (UTC) (envelope-from gordon@tetlows.org) Received: by mail-qt1-x829.google.com with SMTP id n4so7854860qte.2 for ; Thu, 14 Nov 2019 10:20:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tetlows.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=tJSNqmG2/HsUnS8Hsu26h8/9tQA1VzBpu7WLLx15FYE=; b=GvfQXEgG3MIqHmBkp8kwHMX36HD/IBpp+R6eJRF2GnlKhVbXtEuxsUDBAz3WVyzEiO B1kEfmSVS87OwOLjh1jBgK4fHouinWk0bb1bqQmiS693uCvxAK7qWm5fCgHfuew2ZJ7h wXZCyHu3M6JlJ/7FWc4fTI4YrEP2qM+4whaHI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=tJSNqmG2/HsUnS8Hsu26h8/9tQA1VzBpu7WLLx15FYE=; b=eP4wQ+m+djhWcEN3b1KpxTdl8hgSbs3rMknPEXQGsarYsakgVzB0FsnU4rNR5ilCZM hMnutloqZhmPlh629fs9L0zFc43fWxl+InrqRVuVedseTnV0ySqjm7UJBvipr+UOjULL lS0rd7+d/NJXvsk+FGg8b+eVPuqp+yLwjNuXdtrJz+nrZnpsoDX23Eym5G4TgvdH9OQl sC0Sqm9GaK0dO0P1wDhKZ5sy5yksUDHG+Jo6vXqW1O4aLinlD/If2tI7GihxnFD2pZ6n QtwOhk03v8gZS9ZSWA0bNSj0ukEzuQ/amgyHX8Y2jtIRyG5pU/GwaKME2sLzo2oKgCP5 x7bg== X-Gm-Message-State: APjAAAUiDcoSzzqkdl6PY7urdRKFN3YhcDjRos6x2vZxCNEXpgdVut/y PHxw31/qM8oolQP0c+wf09QGvoZ3+7/y X-Google-Smtp-Source: APXvYqwUmbYJcGqoRR2T5CBdcuwZVRdEqWxd6LM1D/8ZfHlHSdS7Mv2DdjFpSnlIVC+L4YaKBPj2cg== X-Received: by 2002:ac8:2d19:: with SMTP id n25mr9653294qta.144.1573755613178; Thu, 14 Nov 2019 10:20:13 -0800 (PST) Received: from gmail.com ([2607:fc50:0:7900:0:dead:beef:cafe]) by smtp.gmail.com with ESMTPSA id a137sm2936952qkg.75.2019.11.14.10.20.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Nov 2019 10:20:12 -0800 (PST) Date: Thu, 14 Nov 2019 10:20:10 -0800 From: Gordon Tetlow To: George Mitchell Cc: FreeBSD Hackers Subject: Re: Correct SVN revision for latest security fix Message-ID: <20191114182010.GG6969@gmail.com> References: <7d65fc8f-e9b9-6472-199e-41f5010a8714@m5p.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UKNXkkdQCYZ6W5l3" Content-Disposition: inline In-Reply-To: <7d65fc8f-e9b9-6472-199e-41f5010a8714@m5p.com> User-Agent: Mutt/1.12.2 (2019-09-21) X-Rspamd-Queue-Id: 47DVC40r0yz4KSt X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tetlows.org header.s=google header.b=GvfQXEgG; dmarc=pass (policy=none) header.from=tetlows.org; spf=pass (mx1.freebsd.org: domain of gordon@tetlows.org designates 2607:f8b0:4864:20::829 as permitted sender) smtp.mailfrom=gordon@tetlows.org X-Spamd-Result: default: False [-7.84 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[tetlows.org:s=google]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[freebsd]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[tetlows.org:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[9.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; DMARC_POLICY_ALLOW(-0.50)[tetlows.org,none]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; IP_SCORE(-2.74)[ip: (-9.33), ipnet: 2607:f8b0::/32(-2.32), asn: 15169(-1.99), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 18:20:17 -0000 --UKNXkkdQCYZ6W5l3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Resending this to the mailing list now that I have sorted my memberships to allow me to post to the list. On Wed, Nov 13, 2019 at 02:56:02PM -0500, George Mitchell wrote: > The attached security-advisories message cites an incorrect SVN revision > number for updating to fix CVE-2018-12207. The revision given is > r354653, but it should be r354654 to include the UPDATING fix and > the newvers.sh change to report the correct "p" level. I sent a > note about this as a reply to the message (so it actually went to > freebsd-security), but I suspect my reply is lost in the moderation > queue. Can someone please fix this? -- George SA's and EN's have always pointed to the actual patch to fix the issue, not the UPDATING/newvers.sh changes. Furthermore, it's not clear what the right order of operations should be when releasing a batch of SA's and EN's. There are 3 possible scenarios. 1. Commit everything in one giant commit. 2. Commit UPDATING/newvers.sh, then commit patches independently. 3. Commit patches independently, then commit UPDATING/newvers.sh. 1 is a non-starter as I don't want to commit everything at once. Downstream users may decide they don't want one particular update in a batch, but need to take everything else. If they are smushed together in a single commit, this is difficult. 2 causes a race condition. It's entirely possible to create a build that lists the patch version as being updated, but the patches haven't yet been pulled into that tree. This is the worst scenario in my book as the user may think they are protected when they haven't actually taken the update. I recognize this is a remote possibility due to timing, but I want to be able to guarantee if a user see -p1, they have the patches that were released as part of -p1. 2 gives a narrow window where we can't give that guarantee. 3 is what we do currently. This has the drawback you cite above. If you checkout the revision cited, the patch level hasn't been revved at this point. What I can say though, if you are running a system that lists -p1, then you are guaranteed to have the patches that were part of -p1. Between the options above, I'll pick option three. Best regards, Gordon Hat: Security Officer --UKNXkkdQCYZ6W5l3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAABCgB9FiEEuyjUCzYO7pNq7RVv5fe8y6O93fgFAl3NmtpfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEJC MjhENDBCMzYwRUVFOTM2QUVEMTU2RkU1RjdCQ0NCQTNCRERERjgACgkQ5fe8y6O9 3fiBAQf+MA+Xfll0qGq0bNxdGLGzHVsaoTLpOctAt0P87lAGQwf7Q9j6B74rI1WH NvPErBf8X4Q0s1hdOTERB+1fQdYKgleHQEvOP5vSSG3sBUxn2Pb0/+OQZYrDLA93 G274ffK7WhRGvuTIjbG81XBHNhAqwgjpLv9rpnsm5XkYMYvjKzXV+kY1gn6YbuLU IUcLZLe6DEZiqnzmPHBFrfIfKnZ255Hxev8OKmkmUlznRf2kBl0VRHdActaq1NTe wMzZCkN3y6Tng3pOXzUjSAmBMsHCcMX4jxGV2+oEhAiQNZxgeZQ2MvqKFRbKY/cf hxwQvwXKAR1X7xVVoPg5c/cFooJ2kw== =RwQT -----END PGP SIGNATURE----- --UKNXkkdQCYZ6W5l3-- From owner-freebsd-hackers@freebsd.org Thu Nov 14 20:03:05 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C536E1B1DF1 for ; Thu, 14 Nov 2019 20:03:05 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "m5p.com", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47DXTh5ggLz3GT5 for ; Thu, 14 Nov 2019 20:03:04 +0000 (UTC) (envelope-from george+freebsd@m5p.com) Received: from [IPv6:2001:470:1f07:15ff::26] (court.m5p.com [IPv6:2001:470:1f07:15ff:0:0:0:26]) (authenticated bits=0) by mailhost.m5p.com (8.15.2/8.15.2) with ESMTPSA id xAEK2oll017824 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 14 Nov 2019 15:02:57 -0500 (EST) (envelope-from george+freebsd@m5p.com) To: freebsd-hackers@freebsd.org References: <7d65fc8f-e9b9-6472-199e-41f5010a8714@m5p.com> <20191114182010.GG6969@gmail.com> From: George Mitchell Autocrypt: addr=george+freebsd@m5p.com; prefer-encrypt=mutual; keydata= mQINBFgnLnwBEADAJDiBKQX77LFRz9wZW8mz3KvaQol2nIremcws0F1mz/zgFlk6uhQVtwnL wb4XL5LdFwcNE1+QZzPLcbYWoWQlz0lBw1bMuKAgr0S6V2e0+I0DqhKeslVFctcTwtvT6pnK VLZXO/7ZGAaLzG4K5vSPzgoevU+YI/pxNsVCH2UO/c3jQW63uEt25mIZbCF1Pu4jgp4RhIgF ujn877r/j6OwBwjzRUu3E6ADp+U825d+5YCuQMEH0wIPnn9GTpXvfdKdbwOIl2akqXqs4cnk iATWfK3r6D4mvDEj1OPHlTvJYcfic7aOIiAwmx1C1v78GjXOdOOA0SGffNix3C2/8oZUO1+V Aet4MKpUKkduWSvULhIkHNZ5Nu8SIJOqge8pmtHxuNXAMfMrAjMdjPwwBFLsYg3Xa2E2oJwg ehTauwd/EDJFcVCyDCyCAYOi/BH/+XQyxzgDlY9N9qj9tHqhVPI6XK7t8UVffGiZUq4rHp5J RdOToqiTNC6eCJBczhMIW+DuFvWU9e6W708T1dz0Accn6Lrgk4eRIn3GFPBG+TxnpjAqHsbW 607dcnD3YKAqY4e+khczL4EObhe7dC1v2fmZiAC6Ds3WHR11IfqoUgCkIwJ590Ej+ElygJFF XxI82wtEz9hkeLLvItpyEJNVjppViRW+Dgl/U7ypHB3qDgYjgwARAQABtChHZW9yZ2UgTWl0 Y2hlbGwgPGdlb3JnZStmcmVlYnNkQG01cC5jb20+iQJUBBMBCAA+FiEENdM4ZHktsJW5kKZX wRES3m+p4fkFAlhZcR0CGyMFCQlmAYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQwRES 3m+p4flqmw/9Emr/ydTG2n9o/IX1yVCNcHVFenVrcOY0L+DGQYZRO/XpLvsGYcuSIQId1w7h l4HZKI89ri2fF2ks6upMqBajLf8s7a8PnYrbw5bPaoOFyNTjv57GLZVsYw95kmMUpK6siuAA fXvHfKUpC/sThbwSv/1CLryVG74+5vdI8j7cQeDM436FThxlVfHKrILIiL34D4WThFB3hV/Y 2A+mQwXmdLcuQXXeAazqsFJL8sgEKSC7GMcExDkVpGc5Rh2hu97a4Sa7qWX9G/YdZOrcDacJ XxfvePn3m3WfRtXN/r0lUfiVXiqkFfbvqSaZQ0I4UvZXNGd/gH4jKHtX9RTH9G96UZeHNoMo tPw9U0fx8Ceh72nUL9qzqnmok/ryWm+6gt4Q1eRP7QAosOa1g/RgUdS1Z9IuCmbXMDp5kbNw L4ZoDMF5U3mmh8/IOKkhGopNLbNv0mwUgC59pnCptiOVx8DyckXWC4L2r6PKbWGrcGIzsUER 9smfL10gpp5H5agjwwPZI6/kzJ0R5nBzQWAlwqI73YAy6JI0HTD6lvxW7yWm2fGjEfmyaBOU 8OLUin7auoFSn+QmD5yNCUn5Ls77qHARkT1ZGocAnQkvZBGTwXpvyJixygXsm+vSUFDYBOSn cR54vdXOEMqrJk6SGau5YI9V7EhQVveE1BUp8ofWf2oo4RG5Ag0EWCcufAEQALuTOxmqMFE+ ieev/rcL3wVJrcuKS+pBbKCY9IIL0OwVf98HQJJcgdOsdDhruVd19nJNlwZ3Fc34wLw7y2GO 9WrpZiYKnI4n9urhLE5r1ydBInlI/1UKZWgM3/dPjJtcXMsC3vnqR9DmOxW4/SbqJDjP3XzO FleT4yip3AaNhPGwEPTZrubVp5hp/JojaZn690TLRwOFXg8NcjpOEs0Bq9M+OLpmsF0flrgs yDfS7y+SQ17R4Iq9T7RxZvZVAh510yGGIZIETYO/4Dh417VVm+gaksOVh2egetpUUvYYc0Ub KaP+5F/WGNrmRb1F6SKypvLlKkYAHCsUUSzsAGl9gbQhEEpuOMbUKp1979HoRMkW+8046kIo 8BZ6ph8izG/g4dZOaEqKGEhqdhYIB7UwMtFFuPtSs5Nl6JrZYni/nzFtTmtVCgcj9PNqrzqt fNFYhNznD6St6wxp3TOm9D3TQF0dzwBM1jZpb8WvmK3k6oy8hbpjiBzxn3kyRA9Vzy+PdbN/ G5a1k0rpZu/ivpBuLCDVGljUmgQigXg6xkk5UxBoHp7MPvG9prZ5jqdEa2r1KgnGjaq+VJsu Uqrw10dVgeG1NulDU1+sQl+/mwtflbkimhjDDjxsVgfrv7uvV/9be+gGm1KATuqdgCboSb1s QAo5ARfwFfChrnh+fTfPpPKHABEBAAGJAiQEGAEIAA8FAlgnLnwCGwwFCQlmAYAACgkQwRES 3m+p4fno9w/4m+swztkzxSWdutjgSv2mw+PdrKWVGFAUD2HoY1Qpi5LNLE6s9pP3qzwpQYwK viOufVJYWZ540ss6BImZBGJwyHouacqrpZjpRo5+ftj07rY1SNd8QjcHDggPfpgJ1D4Il3Xi vRg5/gzkXnRu8dXeVvMP1Ndk/F5wcoLZlQwFtPfu2xyRYIsveXMoyypAvAFSaAGXU0hRzuDJ fGI3LFvpI9UXU2C4MMzjfyZyD2NJEDKOACTo85QQzxgheTDQaDocXW00wknXFMwEItiXp8dO 2zEml/3Kj4efDfjqGpjNefjK0cnj02Byt7y6GozWXyIylrXu0SN9qWRzUVZH3+q+ijA4q3Gm 9uWzLdpjN4QWAiiaEvMhLPohp9DdLsy3kAWWrA3+pAfHSTZXrobMMbSeBkE9E4/WxdKl0nM7 TNslAWcxkTd/7Ly9cxwT8wFdHuQB1hgCmIQxDNXHL1N1ANTeUYum1w9nUg6e1M0UWu+nk3Cw qL7oL2KZe13mQnU/CFwlhbf+i//j3SXrQLlIVQv9Fn805bxIcVo9yqUZyoiV7EUpvOsxDCZh ej3mNYF5nRCf6trEJQVk0aLC26zJAYExykdUlRqc4I13XPhlt+aFSMMkoL/thYO6e9oNFK6Q aJEKXomzxxqpceJVmPH6zvqJbOboAdE/mOD0PoS1M6saIQ== Subject: Re: Correct SVN revision for latest security fix Message-ID: Date: Thu, 14 Nov 2019 15:02:44 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 In-Reply-To: <20191114182010.GG6969@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VKKByPPEBnxa5UFo6F5ycfo9YntTza4Hc" X-Spam-Status: No, score=0.7 required=10.0 tests=HELO_MISC_IP,HELO_NO_DOMAIN autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mattapan.m5p.com X-Rspamd-Queue-Id: 47DXTh5ggLz3GT5 X-Spamd-Bar: ------- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of george@m5p.com designates 74.104.188.4 as permitted sender) smtp.mailfrom=george@m5p.com X-Spamd-Result: default: False [-7.20 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a]; TO_MATCH_ENVRCPT_ALL(0.00)[]; HAS_ATTACHMENT(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,multipart/mixed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_NONE(0.00)[]; IP_SCORE(-2.80)[ip: (-9.86), ipnet: 74.104.0.0/16(-4.93), asn: 701(0.86), country: US(-0.05)]; DMARC_NA(0.00)[m5p.com]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:+,3:~]; ASN(0.00)[asn:701, ipnet:74.104.0.0/16, country:US]; TAGGED_FROM(0.00)[freebsd]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2019 20:03:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --VKKByPPEBnxa5UFo6F5ycfo9YntTza4Hc Content-Type: multipart/mixed; boundary="5CBz8B9Xbtr1u6M7mIUBsj2QfaUtqhkF2"; protected-headers="v1" From: George Mitchell To: freebsd-hackers@freebsd.org Message-ID: Subject: Re: Correct SVN revision for latest security fix References: <7d65fc8f-e9b9-6472-199e-41f5010a8714@m5p.com> <20191114182010.GG6969@gmail.com> In-Reply-To: <20191114182010.GG6969@gmail.com> --5CBz8B9Xbtr1u6M7mIUBsj2QfaUtqhkF2 Content-Type: text/plain; charset=UTF-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2019-11-14 13:20, Gordon Tetlow wrote: > [... a very good explanation of the final steps of the commit process .= =2E.] > 3 is what we do currently. This has the drawback you cite above. If you= > checkout the revision cited, the patch level hasn't been revved at this= > point. What I can say though, if you are running a system that lists > -p1, then you are guaranteed to have the patches that were part of -p1.= >=20 > Between the options above, I'll pick option three. >=20 > Best regards, > Gordon > Hat: Security Officer >=20 There's nothing wrong with your process. But these two lines of the security announcement message seem to me to be contradictory in their implications. Taking 11.3-RELEASE as an example, the message started by announcing that the problem is corrected in: 2019-11-12 18:13:04 UTC (releng/11.3, 11.3-RELEASE-p5) But then near the end, it says: releng/11.3/ r354653 So I dutifully updated to r354653, recompiled, and reinstalled. Voil=C3=A0= ! uname -r told me "11.3-RELEASE-p4". On all previous occasions, when I updated to the SVN revision given in the email announcement, I would get the version cited in the announcement, so I was surprised by the discrepancy. And since newvers.sh was committed at Nov 12 18:13:51 UTC, and the security announcement was emailed at 12 Nov 2019 19:12:06 UTC, shouldn't the announcement have referred to revision 354654? When I updated to that version, recompiled, and reinstalled, sure enough uname -r told me "11.3-RELEASE-p5" as I expected in the first place. 354654 is also the correct revision for 12.0-RELEASE and 12.1-RELEASE. I would recommend emailing a corrected security advisory announcement for consistency with all previous security advisory announcements I've ever seen. Thank you for your attention. -- George --5CBz8B9Xbtr1u6M7mIUBsj2QfaUtqhkF2-- --VKKByPPEBnxa5UFo6F5ycfo9YntTza4Hc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEENdM4ZHktsJW5kKZXwRES3m+p4fkFAl3NsuoACgkQwRES3m+p 4fnWAw/9FdL5wrSLk1PoKd5c0pmZBjZoiey41ZdBFcDRhKSDc+06ZjmLmZmjOHnU z5okzRNEhKhTyyQNcU9pyGTrtJF8WOoxEjni6lZ3LSGcwz6FMy7F3N4hCRmpBwpK ij1DIEmzOzVaMMkmzJ1ROxXWqZOg/t05igZb4/W+zd5LHDutyanARgTxYQYP3Eb+ DucdctStZ+m5XXQf/BC1HGAukCg0ihYzckwy/4rf5ytqXVV8aEeBX7oKEodMkDQg mb7DSaWA4WTUdc3xu8TaCokxwx5b0e7tmz7I+/7YAnDfAEHo+dvGJEE4ANJJN0kc xL+XYMijIYrFOa6fnxMRDoV4wcqMx1+/cwWb7mg8gUERi3YERRP3Kb29vOgtBAaB Osb94kiuR+NrIpYwTQfxZ3U5Ehz6fpgyXSCqb8cD6YL8fU8SM/Ft9w1935UjscYg BBKNswvYa0hirQIwroXycko0cc9MOEiMfI8HvIGpD4sNDtk9B9ZRKxz2W6i9LnkO m217sK3z1d6IXJaPvOcp2gXS3e1iHRfnGQIXIXRUUEYeYxyS1FPpvIIUjMzja55w O9VR/wbfIHDKPlpj6J2J38wqvQb8zI9sot+VgRbcLetCR64w0yUhAwUIGCKshiqN 1EKGihVkqRcZF/9JL6NV7xlaOVfsAXgZI1J5/RUZ9LJQ/hjfZaA= =p6Pb -----END PGP SIGNATURE----- --VKKByPPEBnxa5UFo6F5ycfo9YntTza4Hc-- From owner-freebsd-hackers@freebsd.org Fri Nov 15 03:59:55 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4BE611BB9B3 for ; Fri, 15 Nov 2019 03:59:55 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Dl3s3wvgz4LLs; Fri, 15 Nov 2019 03:59:53 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13:0:0:0:5]) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id xAF3xLOh008435 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 15 Nov 2019 03:59:26 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: ian@freebsd.org Received: from [10.58.0.4] (dadv@[10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id xAF3xD2C007301 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 15 Nov 2019 10:59:13 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: can the hardware watchdog reboot a hung kernel? To: Ian Lepore , Daniel Braniss References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> Cc: freebsd-hackers From: Eugene Grosbein Message-ID: Date: Fri, 15 Nov 2019 10:59:13 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM, SPF_HELO_NONE,SPF_PASS,T_DATE_IN_FUTURE_Q_PLUS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record * 0.0 T_DATE_IN_FUTURE_Q_PLUS Date: is over 4 months after Received: * date * -0.0 SPF_PASS SPF: sender matches SPF record * 2.6 LOCAL_FROM From my domains X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on hz.grosbein.net X-Rspamd-Queue-Id: 47Dl3s3wvgz4LLs X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=permerror (mx1.freebsd.org: domain of eugen@grosbein.net uses mechanism not recognized by this client) smtp.mailfrom=eugen@grosbein.net X-Spamd-Result: default: False [-2.69 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; DMARC_NA(0.00)[grosbein.net]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; R_SPF_PERMFAIL(0.00)[]; IP_SCORE(-1.59)[ip: (-4.00), ipnet: 2a01:4f8::/29(-2.29), asn: 24940(-1.65), country: DE(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2019 03:59:55 -0000 15.11.2019 1:19, Ian Lepore wrote: > One thing to be careful of here is multicore systems. If you have a > critical app running on a multicore system, that app can hang (maybe it > tries to read from a device that has malfunctioned and essentially gets > hung forever in a device driver that doesn't implement timeouts very > well or something). In that case, only one core is hung, so watchdogd > will be able to keep petting the dog to prevent a reboot, but since > your app is hung on a different core, you aren't really getting the > protection you need. > > The fix for that is to either turn you app into watchdogd (have it make > the periodic ioctl() calls to pet the dog), or use the '-e cmd' option > with watchdogd, and make 'cmd' be a script that somehow verifies that > your critical application is still running properly. I have not tried it myself, but there may be easier way if the app is single-process and single-threaded: use cpuset(1) to bind both of the app and watchdogd to same core. From owner-freebsd-hackers@freebsd.org Fri Nov 15 04:24:19 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4B1511BC214 for ; Fri, 15 Nov 2019 04:24:19 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ipmail01.adl6.internode.on.net (ipmail01.adl6.internode.on.net [150.101.137.136]) by mx1.freebsd.org (Postfix) with ESMTP id 47Dlc034QFz3GcK for ; Fri, 15 Nov 2019 04:24:15 +0000 (UTC) (envelope-from darius@dons.net.au) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2D+AACO3/Jb/2hwAg5iGgEBAQEBAgEBA?= =?us-ascii?q?QEHAgEBAQGBZYIEgVYSJ4xvix0BSQIBAQEBAQEGgRAhBIkVkBsLAQErAYRAAoN?= =?us-ascii?q?sIzgSAQMBAQIBAQJtKIU8AQEBAQIBLA4cIwULCw4KLjkeBhODIYF1BQeodx6Jf?= =?us-ascii?q?hOMCXiBB4E4DBOCTIR+gzWCJgKfbwkCkSUYgViIK4Z6lRWCWgIKBxSBXSGBVWw?= =?us-ascii?q?ZZQGCQT6QLywBMoEFAQGNVQEB?= Received: from ppp14-2-112-104.adl-apt-pir-bras32.tpg.internode.on.net (HELO midget.dons.net.au) ([14.2.112.104]) by ipmail01.adl6.internode.on.net with ESMTP; 15 Nov 2019 14:54:10 +1030 Received: from midget.dons.net.au (localhost [127.0.0.1]) by midget.dons.net.au (8.15.2/8.15.2) with ESMTPS id xAF4NtGO003081 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Fri, 15 Nov 2019 14:54:05 +1030 (ACDT) (envelope-from darius@dons.net.au) Received: (from mailnull@localhost) by midget.dons.net.au (8.15.2/8.15.2/Submit) id xAF42ouY088533 for ; Fri, 15 Nov 2019 14:32:50 +1030 (ACDT) (envelope-from darius@dons.net.au) X-Authentication-Warning: midget.dons.net.au: mailnull set sender to using -f X-MIMEDefang-Relay-be813b1f1da6d6b27d681222cb70cc4f5b642383: 203.31.81.177 Received: from havok.gsoft.com.au (Havok.gsoft.com.au [203.31.81.177]) by ppp14-2-112-104.adl-apt-pir-bras32.tpg.internode.on.net (envelope-sender ) (MIMEDefang) with ESMTP id xAF42ifU088529; Fri, 15 Nov 2019 14:32:50 +1030 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: can the hardware watchdog reboot a hung kernel? From: "O'Connor, Daniel" In-Reply-To: Date: Fri, 15 Nov 2019 14:32:44 +1030 Cc: Ian Lepore , Daniel Braniss , freebsd-hackers Content-Transfer-Encoding: quoted-printable Message-Id: <92134BA3-3BB3-4377-B9A7-1B1D702824F7@dons.net.au> References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> To: Eugene Grosbein X-Mailer: Apple Mail (2.3445.104.11) X-Spam-Score: 0.4 () No, score=0.4 required=5.0 tests=KHOP_HELO_FCRDNS, SPF_HELO_NONE, SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Scanned-By: MIMEDefang 2.83 on 10.0.2.1 X-Rspamd-Queue-Id: 47Dlc034QFz3GcK X-Spamd-Bar: +++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of darius@dons.net.au has no SPF policy when checking 150.101.137.136) smtp.mailfrom=darius@dons.net.au X-Spamd-Result: default: False [5.88 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; HAS_XAW(0.00)[]; AUTH_NA(1.00)[]; DMARC_NA(0.00)[dons.net.au]; RCVD_COUNT_THREE(0.00)[4]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; NEURAL_SPAM_MEDIUM(0.98)[0.979,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[1.000,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:4739, ipnet:150.101.0.0/16, country:AU]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(1.50)[ip: (3.78), ipnet: 150.101.0.0/16(2.49), asn: 4739(1.25), country: AU(0.00)]; RCVD_IN_DNSWL_LOW(-0.10)[136.137.101.150.list.dnswl.org : 127.0.5.1] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2019 04:24:19 -0000 > On 15 Nov 2019, at 14:29, Eugene Grosbein wrote: >=20 > 15.11.2019 1:19, Ian Lepore wrote: >=20 >> One thing to be careful of here is multicore systems. If you have a >> critical app running on a multicore system, that app can hang (maybe = it >> tries to read from a device that has malfunctioned and essentially = gets >> hung forever in a device driver that doesn't implement timeouts very >> well or something). In that case, only one core is hung, so = watchdogd >> will be able to keep petting the dog to prevent a reboot, but since >> your app is hung on a different core, you aren't really getting the >> protection you need. >>=20 >> The fix for that is to either turn you app into watchdogd (have it = make >> the periodic ioctl() calls to pet the dog), or use the '-e cmd' = option >> with watchdogd, and make 'cmd' be a script that somehow verifies that >> your critical application is still running properly. >=20 > I have not tried it myself, but there may be easier way > if the app is single-process and single-threaded: use cpuset(1) to = bind > both of the app and watchdogd to same core. You can get watchdogd to run a script, so you could have it check for = liveness somehow and the dog will bite if it isn't. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum From owner-freebsd-hackers@freebsd.org Fri Nov 15 16:58:28 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C840E1AAC72 for ; Fri, 15 Nov 2019 16:58:28 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 47F4LB725xz3xHs; Fri, 15 Nov 2019 16:58:26 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=References:To:Cc:In-Reply-To:Date:Subject:Mime-Version:Content-Type:Message-Id:From; bh=eDL+gEg9RTXirOmGOMSiLRSf3yxtsHlajsZvjn+0d8g=; b=runL48Zd8pTx93vQKvt9rKuy26J8GiRNY+HKVMzDWNgF4HQoyBhRHwSM+p7/QHuHX5k9OJLIcyuPDvdCnANjzUnOUl+s/addjasUTRV/gumhu/F4Nxr3oO/PJh31VKPKnHJuxDsDamQj+/nFFnwIjPmnUOukAlI8lT7Sx3trfhhntrABx/fI8EuVUWFJJy25lrjOv2f14XLfhAp7T3G2Jfyxq/lEx656y0GtkLFan34NTciHhYoeoq6gBwg2ltVZ1R6daVVKVKLGlziJWor1cFn5uGt6TTpeiNd0bQFxCEsG5HGHvl3DeA/GYPqyRDmdi7fF5L9EUV+F1Er79fA62Q==; Received: from macmini.bk.cs.huji.ac.il ([132.65.179.19]) by kabab.cs.huji.ac.il with esmtp id 1iVevP-0005VA-Sb; Fri, 15 Nov 2019 18:58:23 +0200 From: Daniel Braniss Message-Id: Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: can the hardware watchdog reboot a hung kernel? Date: Fri, 15 Nov 2019 18:58:23 +0200 In-Reply-To: Cc: freebsd-hackers To: Ian Lepore References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47F4LB725xz3xHs X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cs.huji.ac.il header.s=57791128 header.b=runL48Zd; dmarc=pass (policy=none) header.from=huji.ac.il; spf=none (mx1.freebsd.org: domain of danny@cs.huji.ac.il has no SPF policy when checking 132.65.116.210) smtp.mailfrom=danny@cs.huji.ac.il X-Spamd-Result: default: False [-1.99 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.990,0]; R_DKIM_ALLOW(-0.20)[cs.huji.ac.il:s=57791128]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; IP_SCORE(-0.70)[ip: (-1.40), ipnet: 132.64.0.0/13(-1.20), asn: 378(-0.96), country: IL(0.05)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[cs.huji.ac.il:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[210.116.65.132.list.dnswl.org : 127.0.10.0]; DMARC_POLICY_ALLOW(-0.50)[huji.ac.il,none]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:378, ipnet:132.64.0.0/13, country:IL]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2019 16:58:28 -0000 > On 14 Nov 2019, at 20:19, Ian Lepore wrote: >=20 > On Thu, 2019-11-14 at 20:10 +0200, Daniel Braniss wrote: >>> On 14 Nov 2019, at 18:02, Ian Lepore wrote: >>>=20 >>> On Thu, 2019-11-14 at 17:35 +0200, Daniel Braniss wrote: >>>>> On 14 Nov 2019, at 17:28, Eugene Grosbein >>>>> wrote: >>>>>=20 >>>>> 14.11.2019 21:52, Daniel Braniss wrote: >>>>>=20 >>>>>> hi, >>>>>> I have serveral hundred Nano-pi NEO running, and sometimes they >>>>>> hang, since there is no console >>>>>> available, the only solution is to do a power cycle - not so easy >>>>>> since they are distributed in three buildings :-) >>>>>>=20 >>>>>> I am looking at the watchdog stuff, but it seems that what I want >>>>>> is not supported, i.e. >>>>>> reboot the kernel when hung=20 >>>>>>=20 >>>>>> wishful thinking? >>>>>=20 >>>>> It's possible if the hardware has such a watchdog and kernel >>>>> subsystem watchdog(4) supports it. >>>>> rc.conf(5) manual page describes watchdogd_enable option. >>>>>=20 >>>>=20 >>>> yes, but it relys on user land, what if the kernel is hung?=20 >>>>=20 >>>=20 >>> It relies on the userland daemon to issue the ioctl() calls to pet = the >>> dog. If the kernel is hung, then userland code isn't going to run >>> either, and the watchdog petting won't happen, and eventually the >>> hardware reboots. >>>=20 >>> We use this at $work specifically to reboot if the kernel hangs, = using >>> this config: >>>=20 >>> watchdogd_enable=3DYES >>> watchdogd_flags=3D"-s 16 -t 64 -x 64" >>>=20 >>> That says the daemon should pet the dog every 16 seconds, and the >>> hardware is programmed to reboot if 64 seconds elapses without = petting. >>> In addition, when watchdogd is shutdown normally (like during a = normal >>> system reboot) it doesn't disable the watchdog hardware, it sets the >>> timeout to 64s to protect against any kind of hang during the = reboot.=20 >>> The -t and -x times can be different, 64s just happens to work well = for >>> us in both cases. >>>=20 >>> -- Ian >>>=20 >>=20 >> ok, that is very encouraging, now a last question >> how can i hang the kernel to test that the watchdog kicks in? apart = from writing a kernel module :-) >>=20 >=20 > One thing to be careful of here is multicore systems. If you have a > critical app running on a multicore system, that app can hang (maybe = it > tries to read from a device that has malfunctioned and essentially = gets > hung forever in a device driver that doesn't implement timeouts very > well or something). In that case, only one core is hung, so watchdogd > will be able to keep petting the dog to prevent a reboot, but since > your app is hung on a different core, you aren't really getting the > protection you need. >=20 > The fix for that is to either turn you app into watchdogd (have it = make > the periodic ioctl() calls to pet the dog), or use the '-e cmd' option > with watchdogd, and make 'cmd' be a script that somehow verifies that > your critical application is still running properly. >=20 > =E2=80=94Ian in my case the kernel is hung, probably by my app - which is using 2 i2c = devices, , BTW, this does not happen very often,=20 maybe once a month, but is annoying. now the watchdog stuff: 1- the all winner/nanopi neo can only handle up to 8 sec timeout (the = next is 16sec (2^34)) the watchdogd complainsif >8sec: aw_wdog0: Can't arm, timeout is more than 16 sec and continues trying - IMHO it should exit. 2- this is a bit more annoying: entering the debugger will trigger the timeout and it will the = perform a clean reboot (*) doing a shutdown -r leaves the watchdog in some weird state so = the reboot hangs when starting the watchdog win some, loose some :-) *: in MHO, entering the debugger should stop the hardware timeout - or = at least optional cheers and thanks danny From owner-freebsd-hackers@freebsd.org Fri Nov 15 17:11:09 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DF4ED1AB22E for ; Fri, 15 Nov 2019 17:11:09 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47F4cs3Rydz4HQY for ; Fri, 15 Nov 2019 17:11:09 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1573837867; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=QF4i1y/h31AxpDVAys9Z/zN99yXv8eYmHSB7ecy0DZiPCVeikNG4ESzVmOCQzADJIGzmlHNgA+X9+ EhvV1qTp1DZygX4hSczMY7sL3hUtYP8xJDkC1ImyojO920oWHCDYg+05XWYQ7/hMxHLOwgndWt/PeQ ZxJ6OHg8NTJ965RlYtTxcq3Zu18dogXKV50fEafQexakI65YjHUfDxKWZavOXAQ7TB68RLm83POB5e 3GcZFcY+PK3PbnyPW21lp8b9c8ulbdRG+xWjqMT8L/iV652uoQNcoyBtZd+tDKCR+Y81CaAaUoFfPe 4hxq3mkRhvZAAag4fAmYvbf75rPvvBA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=9CPLTTKgVol/xnhZs1mogZGTTUKXDmjce7CuSR4W3/Q=; b=SG53Mf6ic0LRiXmHKCS1BN9ah/j8K5QdqkjqywMMHvxPId6/J0IPJzMJLBNHHK+NBZm6u3WSXP2Pk toMZlG9YaWjvX0n/O4iiCs3J9dQA4vmnUziZWq9jrDIskMB8UTtop6C13v6l8xlBGn6pOXPxdtRdSb YYt/cCIgBR8GjPlk5HzirnaeTRfMnvjuE+hljHAoK9McMmu0u2V4ymmR/CxyfNMbuxOIB1QjxQTCBX n8gzyp7BxQQAe0W3ZkJlqb4i8FYaqL3C0MO974qwWHMT5kQ1i2YyhWedMc4xluDVVEDd56/HW/WMb1 urKECvXR9Zv9wL17u+gmkrwwQvQrRLg== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=9CPLTTKgVol/xnhZs1mogZGTTUKXDmjce7CuSR4W3/Q=; b=SnqBcKWirona161bnjKNwOCzS+VdzTrsCR+y4SDpxQ4ekkVph3CsZcTLZiSH3Vh4BWvCxnNrrcdQd 0qXmwc+3+PJnKHD7Z0vyI5k0gSKTtuCHgBx+nRxzJR3opX+jd0+MkcTfE5tH8Z3yJmwq6kxkjruOv5 m2uC0hbtqpF1K/1Uf2lWrtt1ix0lo4x1/eZ47XEnbSxWfKwyr6bdLvzTbKH2dono5RaaE3Wb4VAObj mWxMDDyc8xJbq9p7sSzmsFGMMJ6vLFPvJX1+3ZJB5ERSK1z8TUXe/E3qJ1Lr7rSEGYlKTJBOXnkSuP w+ZE/6ZEcAo9kBCkerT3st+qkSNIY3Q== X-MHO-RoutePath: aGlwcGll X-MHO-User: e6f55d2b-07ca-11ea-b80c-052b4a66b6b2 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id e6f55d2b-07ca-11ea-b80c-052b4a66b6b2; Fri, 15 Nov 2019 17:11:06 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id xAFHB28P032161; Fri, 15 Nov 2019 10:11:02 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <9df4efbbbbb4fd4be81b94894f225c7ec92cc608.camel@freebsd.org> Subject: Re: can the hardware watchdog reboot a hung kernel? From: Ian Lepore To: Daniel Braniss Cc: freebsd-hackers Date: Fri, 15 Nov 2019 10:11:02 -0700 In-Reply-To: References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 47F4cs3Rydz4HQY X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.92 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.92)[-0.917,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Nov 2019 17:11:10 -0000 On Fri, 2019-11-15 at 18:58 +0200, Daniel Braniss wrote: > > On 14 Nov 2019, at 20:19, Ian Lepore wrote: > > > > [...] > > > > One thing to be careful of here is multicore systems. If you have > > a > > critical app running on a multicore system, that app can hang > > (maybe it > > tries to read from a device that has malfunctioned and essentially > > gets > > hung forever in a device driver that doesn't implement timeouts > > very > > well or something). In that case, only one core is hung, so > > watchdogd > > will be able to keep petting the dog to prevent a reboot, but since > > your app is hung on a different core, you aren't really getting the > > protection you need. > > > > The fix for that is to either turn you app into watchdogd (have it > > make > > the periodic ioctl() calls to pet the dog), or use the '-e cmd' > > option > > with watchdogd, and make 'cmd' be a script that somehow verifies > > that > > your critical application is still running properly. > > > > —Ian > > in my case the kernel is hung, probably by my app - which is using 2 > i2c devices, , BTW, this does not happen very often, > maybe once a month, but is annoying. > > now the watchdog stuff: > 1- the all winner/nanopi neo can only handle up to 8 sec timeout (the > next is 16sec (2^34)) > the watchdogd complainsif >8sec: > aw_wdog0: Can't arm, timeout is more than 16 sec > and continues trying - IMHO it should exit. > This basically comes down to "know your hardware and don't ask for things it can't do". There is a lot of variance in watchdog hardware, and unfortunately our watchdog software interface is kinda braindead. It uses a power-of-2 timeout which is great if you need a large variety of subsecond timeouts ranging from a few nanoseconds to a half second. But it's absolutely horrible for what the real world usually wants: some medium-sized integer number of seconds. Your choices are pretty much just 8, 16, 32, 64, 128. Lots of hardware maxes at 16 or 32 seconds. If aw maxes at 16 it's probably best to set it for that, with petting at either 4 or 8 second intervals. > 2- this is a bit more annoying: > entering the debugger will trigger the timeout and it will the > perform a clean reboot (*) In the debugger, enter "watchdog" without any parameter to disable the watchdog. (Or give a parameter to change the timeout.) Some watchdog hardware cannot be disabled once you've enabled it. > doing a shutdown -r leaves the watchdog in some weird state so > the reboot hangs when starting the watchdog > win some, loose some :-) > This is likely another flavor of "some watchdog hardware cannot be disabled". But it might just be a bug in the aw watchdog driver too. -- Ian From owner-freebsd-hackers@freebsd.org Sat Nov 16 09:09:56 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 621DE1BF92A for ; Sat, 16 Nov 2019 09:09:56 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 47FTv80gw1z3FSq; Sat, 16 Nov 2019 09:09:55 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cs.huji.ac.il; s=57791128; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version:Content-Type; bh=2IuvAzI2uZl69PujqaBOvP0O4JCoTCC+HRHN/naEcZg=; b=J5ptGsoGA1LmrlvuPhXd331NrD5Hi+eCs6FZTOdYmrJv6ylkdRNvPbVYanzOlFrSwhpAuNeiMaPEfh9Wi3c9eHyjOq6jlJSHtsf/nhgD+KsmfcOaJKxvsmQuNsMERmUTu5m14k4CW5s1S41umTwL0uCcOmDTnVBi/dp93qmb0QFM1qx4CeVBDx5cYJXmNAJKpx/jIX/ddeJMsblffOloCLdR4KqHsJ5BQQoOf5zVIIhfh8URYR0TzROoQkYBH8sYE7ZQ2OHqfLOWFywoK/z50gPwgnQi5tts7ZTaMt7GlzkmyhE3++s+G+xKSWbP1erptZUPH8Vo9GXOJOPkGoDmpg==; Received: from macmini.bk.cs.huji.ac.il ([132.65.179.19]) by kabab.cs.huji.ac.il with esmtp id 1iVu5Z-000EDJ-Ie; Sat, 16 Nov 2019 11:09:53 +0200 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: can the hardware watchdog reboot a hung kernel? From: Daniel Braniss In-Reply-To: <9df4efbbbbb4fd4be81b94894f225c7ec92cc608.camel@freebsd.org> Date: Sat, 16 Nov 2019 11:09:53 +0200 Cc: freebsd-hackers Content-Transfer-Encoding: quoted-printable Message-Id: <8ACEB61A-E76F-4226-B2F7-5AD753457002@cs.huji.ac.il> References: <9cded04a-9ae1-881e-3962-7ef0322e96ed@grosbein.net> <2AD912BF-97B0-421D-B561-722D74864DC9@cs.huji.ac.il> <828605fef472e04311c83a7de0d1f4df429ae717.camel@freebsd.org> <9df4efbbbbb4fd4be81b94894f225c7ec92cc608.camel@freebsd.org> To: Ian Lepore X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47FTv80gw1z3FSq X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.98 / 15.00]; NEURAL_HAM_MEDIUM(-0.98)[-0.982,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Nov 2019 09:09:56 -0000 > On 15 Nov 2019, at 19:11, Ian Lepore wrote: >=20 > On Fri, 2019-11-15 at 18:58 +0200, Daniel Braniss wrote: >>> On 14 Nov 2019, at 20:19, Ian Lepore wrote: >>>=20 >>>=20 > [...] >>>=20 >>> One thing to be careful of here is multicore systems. If you have >>> a >>> critical app running on a multicore system, that app can hang >>> (maybe it >>> tries to read from a device that has malfunctioned and essentially >>> gets >>> hung forever in a device driver that doesn't implement timeouts >>> very >>> well or something). In that case, only one core is hung, so >>> watchdogd >>> will be able to keep petting the dog to prevent a reboot, but since >>> your app is hung on a different core, you aren't really getting the >>> protection you need. >>>=20 >>> The fix for that is to either turn you app into watchdogd (have it >>> make >>> the periodic ioctl() calls to pet the dog), or use the '-e cmd' >>> option >>> with watchdogd, and make 'cmd' be a script that somehow verifies >>> that >>> your critical application is still running properly. >>>=20 >>> =E2=80=94Ian >>=20 >> in my case the kernel is hung, probably by my app - which is using 2 >> i2c devices, , BTW, this does not happen very often,=20 >> maybe once a month, but is annoying. >>=20 >> now the watchdog stuff: >> 1- the all winner/nanopi neo can only handle up to 8 sec timeout (the >> next is 16sec (2^34)) >> the watchdogd complainsif >8sec: >> aw_wdog0: Can't arm, timeout is more than 16 sec >> and continues trying - IMHO it should exit. >>=20 >=20 > This basically comes down to "know your hardware and don't ask for > things it can't do". There is a lot of variance in watchdog hardware, > and unfortunately our watchdog software interface is kinda braindead.=20= > It uses a power-of-2 timeout which is great if you need a large = variety > of subsecond timeouts ranging from a few nanoseconds to a half second.=20= > But it's absolutely horrible for what the real world usually wants:=20 > some medium-sized integer number of seconds. Your choices are pretty > much just 8, 16, 32, 64, 128. Lots of hardware maxes at 16 or 32 > seconds. >=20 > If aw maxes at 16 it's probably best to set it for that, with petting > at either 4 or 8 second intervals. >=20 >> 2- this is a bit more annoying: >> entering the debugger will trigger the timeout and it will the >> perform a clean reboot (*) >=20 > In the debugger, enter "watchdog" without any parameter to disable the > watchdog. (Or give a parameter to change the timeout.) >=20 > Some watchdog hardware cannot be disabled once you've enabled it. >=20 >> doing a shutdown -r leaves the watchdog in some weird state so >> the reboot hangs when starting the watchdog >> win some, loose some :-) >>=20 >=20 > This is likely another flavor of "some watchdog hardware cannot be > disabled". But it might just be a bug in the aw watchdog driver too. >=20 > =E2=80=94Ian >=20 >=20 i have a workaround, start the watchdogd by hand (not via rc.conf) then shutdown does not = stop the watchdog, and all is ok I guess there must be some bug in the reset logic in aw_dog.c danny