From owner-freebsd-hackers@freebsd.org Sun Dec 10 09:00:44 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94C22E86B25 for ; Sun, 10 Dec 2017 09:00:44 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 612306950D for ; Sun, 10 Dec 2017 09:00:42 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: by mail-qk0-x235.google.com with SMTP id h19so3726965qkj.11 for ; Sun, 10 Dec 2017 01:00:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NTVW4lxbjBbyYiQE9qEKi8Wl+3u9voBslW7XDhohK0E=; b=f5tK5m225viGDyQVCP87FXBSVnyZf1IX/iycK74ypGTFEQZzytxk75Y7bCt6N0HcS4 Ws+OSCe8i0M5FfZSI7yjBzgfuaDN0sjBFfICABkkAGvmzFR2tWys6UYT7prb+LPMErvK WKnm9ZeIhLgjv5V+T0gvGnl91M4EUika2DjcLa3+pDCSiUe28YQRgMohU1v/dLpuIhE/ 8FUl0zDzjI3Re7vRG+a04BvaiCU9buUc9Z/mh7cdMebGTMSdBBWfvxji8ofl+vUP4cjF YRORaW/EbT2osV3qTfyNoamWHfSueXSCRBaAoxty7wSrmKP9SIQBgz5727aKWnYmbcKN FN9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NTVW4lxbjBbyYiQE9qEKi8Wl+3u9voBslW7XDhohK0E=; b=E+2oJlW1FV0MLWHOlo6GxaTC+WnshvOux2WhRUv9oZdVKHkaBMzaVuOdBmKhx7gnOd OC9oiLTej3e3VU/vR3BnaUQDrLM29B9r0aTwlxpp8K3Js+e06UqhBStUagmhTuBjfDPB 073tul9CIwetOjKxHYgRAwLllIdk/bw1I3v5zRPrs4PhgCG0N38DwjFdry/Z4LlyvW38 vJeqUeR6LtBf34PQ2F4V38Q/08Kw6EY7zUNWZYAg61qz08itlYZS/Pskw93qQdsuVkja U6lcADmKpReN9ZUUbhCpm85sAs/GkUcgTcn54iV+Z1SWQ0/Y9Rwc9fCD4ok7eyaChBmy j0cA== X-Gm-Message-State: AKGB3mIQPJoSRd2echhDl3wr0Izju1hUCWXM2L81nFu5bIjk9R34QRIb cvN4ePSBkiE4N6K8vDgjphrzeO3xYkoo2rOwC+jbjA== X-Google-Smtp-Source: AGs4zMYN3MStQkNML5AfLLUWZPjF8ISo70qU731iZH5vQF6F3AO77Ak6WyqJ/jl04u6kWjfASIdvh8n0m7W8HLGjwrA= X-Received: by 10.55.104.198 with SMTP id d189mr41806281qkc.190.1512896441918; Sun, 10 Dec 2017 01:00:41 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.89.244 with HTTP; Sun, 10 Dec 2017 01:00:41 -0800 (PST) Received: by 10.140.89.244 with HTTP; Sun, 10 Dec 2017 01:00:41 -0800 (PST) In-Reply-To: <0dd5240f-6c70-425f-7e98-7946097ea3ef@metricspace.net> References: <0dd5240f-6c70-425f-7e98-7946097ea3ef@metricspace.net> From: Michael Zhilin Date: Sun, 10 Dec 2017 12:00:41 +0300 Message-ID: Subject: Re: Hopefully useful: macro-controlled logger To: Eric McCorkle Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 09:00:44 -0000 Hi Eric! Nice! This minimalistic and powerful approach looks very nice. We have similar thing in one of kernel driver: https://github.com/freebsd/freebsd/blob/master/sys/dev/bhnd/bhnd_debug.h In my opinion such kind of thing is demanded. Best regards, Michael. 9 =D0=B4=D0=B5=D0=BA. 2017 =D0=B3. 7:52 =D0=9F=D0=9F =D0=BF=D0=BE=D0=BB=D1= =8C=D0=B7=D0=BE=D0=B2=D0=B0=D1=82=D0=B5=D0=BB=D1=8C "Eric McCorkle" =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB: > Hi folks, > > At some point in the past, I recall reading about a log4j-inspired > logging API for C that used the preprocessor to avoid introducing > runtime overhead. However, I've never been able to find this library, > so I've used my own scrappy macro collection over the years. > > Anyway, on a recent flight I decided to implement a macro-controlled > logging API in earnest. > > The github project can be found here: https://github.com/emc2/mcl > > It provides the ability to define module-specific loggers, log at > different levels, and set a threshold for dynamically-controlled logging > levels. Any log message more severe than the dynamic range will be > hardwired in place, and any message less severe will be removed at > compilation time. > > It's not large or complicated at all, but hopefully someone will find it > useful. If they do, I'd be more than happy to have it added to the > FreeBSD base system. > _______________________________________________ > 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= " > From owner-freebsd-hackers@freebsd.org Sun Dec 10 10:45:59 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7A5FE88AD4 for ; Sun, 10 Dec 2017 10:45:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 716D86C0AB for ; Sun, 10 Dec 2017 10:45:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id vBAAjl6S066131 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 10 Dec 2017 12:45:50 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua vBAAjl6S066131 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id vBAAjlLR066126; Sun, 10 Dec 2017 12:45:47 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 10 Dec 2017 12:45:47 +0200 From: Konstantin Belousov To: Michael Zhilin Cc: freebsd-hackers@freebsd.org Subject: Re: Hopefully useful: macro-controlled logger Message-ID: <20171210104547.GX2272@kib.kiev.ua> References: <0dd5240f-6c70-425f-7e98-7946097ea3ef@metricspace.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 10:46:00 -0000 On Sun, Dec 10, 2017 at 12:00:41PM +0300, Michael Zhilin wrote: > Hi Eric! > > Nice! This minimalistic and powerful approach looks very nice. > > We have similar thing in one of kernel driver: > https://github.com/freebsd/freebsd/blob/master/sys/dev/bhnd/bhnd_debug.h > > In my opinion such kind of thing is demanded. We already have ktr(4). If it is too limited for some use, it should be extended instead of adding parallel half-done implementation. Kernel printf(9) introduces too much serialization which makes it impossible to reproduce an issue sometimes (or often). Also, kernel consoles are slow due to the nature of the hardware, and serialization blocks other threads trying to log while current message is printed. ktr(4) avoids both of the problems. From owner-freebsd-hackers@freebsd.org Sun Dec 10 16:44:42 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5E9AE90579; Sun, 10 Dec 2017 16:44:42 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A9730768CA; Sun, 10 Dec 2017 16:44:42 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 1B9AD29A2; Sun, 10 Dec 2017 17:44:34 +0100 (CET) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_1F6BB22A-1372-43C0-A58C-E065490740ED"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [PATCH] Document powl and tgammal kludges Date: Sun, 10 Dec 2017 17:44:33 +0100 In-Reply-To: <20171209010205.GA42226@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org To: sgk@troutmask.apl.washington.edu References: <20171209010205.GA42226@troutmask.apl.washington.edu> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 16:44:43 -0000 --Apple-Mail=_1F6BB22A-1372-43C0-A58C-E065490740ED Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 9 Dec 2017, at 02:02, Steve Kargl = wrote: >=20 > The following patch documents the remaining kludges that > theraven@ committed in r255294 on 2013-09-06. I have > cleaned up all of the others, but powl and tgammal remain. > ngie@ seems to have documented the existence of powl with > r290605, but did not document the rather poor numerical > accuracy of the result. tgammal remains undocumented. As it > is unlikely that theraven@ will document the nature of his > kludge nor the existence of tgammal, I have have prepared > a patch that documents the expected numerical accuracy in BUGS > sections, and have also documented tgammal. Thanks, committed in r326748. -Dimitry --Apple-Mail=_1F6BB22A-1372-43C0-A58C-E065490740ED Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWi1kcQAKCRCwXqMKLiCW oxQ6AKCPnLnE5VzWlJMkdnUoh0OPDvq/sgCgqm4/QkV28BFCKdQOaGEN/at51hA= =du+c -----END PGP SIGNATURE----- --Apple-Mail=_1F6BB22A-1372-43C0-A58C-E065490740ED-- From owner-freebsd-hackers@freebsd.org Sun Dec 10 17:12:29 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20D60E91393; Sun, 10 Dec 2017 17:12:29 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 022FB77A7C; Sun, 10 Dec 2017 17:12:28 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id vBAHCSx0048766 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 10 Dec 2017 09:12:28 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id vBAHCSDE048765; Sun, 10 Dec 2017 09:12:28 -0800 (PST) (envelope-from sgk) Date: Sun, 10 Dec 2017 09:12:28 -0800 From: Steve Kargl To: Dimitry Andric Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: [PATCH] Document powl and tgammal kludges Message-ID: <20171210171228.GB48536@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20171209010205.GA42226@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 17:12:29 -0000 On Sun, Dec 10, 2017 at 05:44:33PM +0100, Dimitry Andric wrote: > On 9 Dec 2017, at 02:02, Steve Kargl wrote: > > > > The following patch documents the remaining kludges that > > theraven@ committed in r255294 on 2013-09-06. I have > > cleaned up all of the others, but powl and tgammal remain. > > ngie@ seems to have documented the existence of powl with > > r290605, but did not document the rather poor numerical > > accuracy of the result. tgammal remains undocumented. As it > > is unlikely that theraven@ will document the nature of his > > kludge nor the existence of tgammal, I have have prepared > > a patch that documents the expected numerical accuracy in BUGS > > sections, and have also documented tgammal. > > Thanks, committed in r326748. > Thanks for the quick commit. -- Steve From owner-freebsd-hackers@freebsd.org Sun Dec 10 19:34:24 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E384AE9855C for ; Sun, 10 Dec 2017 19:34:24 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (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 C8DE67EA0D for ; Sun, 10 Dec 2017 19:34:24 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from process-dkim-sign-daemon.mr11p00im-asmtp003.me.com by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P0R00G00BKBFQ00@mr11p00im-asmtp003.me.com> for freebsd-hackers@freebsd.org; Sun, 10 Dec 2017 18:33:13 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=04042017; t=1512930792; bh=LvLW696T7ZGQ4sZvK3NsadOJVAXyzBBGWH0LKZS7Z0o=; h=Date:Subject:From:To:Message-id:MIME-version:Content-type; b=hcSbWJhDtC3eqZRuQloFI9yd0SxqeLwYXH7Ftl0HYqfnwUu4dZQntbaFU2gQSiSRh z9cekvDFhaGiA2K9avVZdXepWv904M3AerI2LKWo2h9jSURL32S0tpitaWpaDlWHYV 8hDPOh8P1gnYyhsfLd9hDGKi/LVgWIS0Jvem5c3IHqfkSASuhfb4EXtyKYKzZzCbsU wEl4YKWE70IDTlMrBd9OoFD5kGio4QxI1AtsT8kJHOLndzO3D4PwJYk+QehV4GGe/m P5vvjUM3idUyh9Zj1mH7GuUv1tBZmnRNHTAhJtdhgx8AJPWUgPCrSTVR9tjQiDY8wQ lyzmVegNmOOXg== Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P0R0049GCVB6C00@mr11p00im-asmtp003.me.com> for freebsd-hackers@freebsd.org; Sun, 10 Dec 2017 18:33:12 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-12-10_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1712100280 User-Agent: Microsoft-MacOutlook/f.28.0.171108 Date: Sun, 10 Dec 2017 10:33:10 -0800 Subject: Re: Hopefully useful: macro-controlled logger From: Ravi Pokala To: "freebsd-hackers@freebsd.org" Message-id: <75337BDB-3701-4215-974B-98C61997E145@mac.com> Thread-topic: Hopefully useful: macro-controlled logger MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Sun, 10 Dec 2017 20:17:40 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 19:34:25 -0000 Hi Eric, > Date: Sat, 9 Dec 2017 11:52:10 -0500 > From: Eric McCorkle > To: "freebsd-hackers@freebsd.org" > Subject: Hopefully useful: macro-controlled logger > Message-ID: <0dd5240f-6c70-425f-7e98-7946097ea3ef@metricspace.net> > Content-Type: text/plain; charset=utf-8 > > Hi folks, > > ... > > Anyway, on a recent flight I decided to implement a macro-controlled > logging API in earnest. > > The github project can be found here: https://github.com/emc2/mcl > > ... 0) The README should be a bit more informative. ;-) 1) Since we're adding SPDX tags for licenses, you should do that too. ;-) 2) Thanks for proper (Doxygen? JavaDoc?) comments! I wish more files included at least a file-level overview of the type of stuff in the file. 3) Since LOG_LVL_ are integer values and not a bitmap, couldn't they be converted to an enum? That would also allow for adding new levels between existing levels, without having to re-number everything. 4) Hrm. Although that doesn't really help the fact that you'd still have to add the definition of the LOG_ macro. Since they're all the same, it would be nice if they too could be generated. But that's where you get into doing multiple levels of the preprocessor, and things can get incomprehensible fast. :-/ 5) I think LOG_SYSTEM is poor wording -- when I first read it, I assumed it meant for differentiating between logging via printf() or via log(); I think LOG_MODULE would more clearly communicate that it's for differentiating between software modules. 6) That having been said, it would be useful if there was a way to select the log output destination. I hope you find that feedback useful. -Ravi (rpokala@) From owner-freebsd-hackers@freebsd.org Mon Dec 11 08:04:59 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F299E89640 for ; Mon, 11 Dec 2017 08:04:59 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from know-smtprelay-omc-3.server.virginmedia.net (know-smtprelay-omc-3.server.virginmedia.net [80.0.253.67]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7B1E6765FE for ; Mon, 11 Dec 2017 08:04:57 +0000 (UTC) (envelope-from j.deboynepollard-newsgroups@ntlworld.com) Received: from [192.168.1.5] ([86.10.211.13]) by know-smtprelay-3-imp with bizsmtp id kY3k1w00F0HtmFq01Y3k0y; Mon, 11 Dec 2017 08:03:44 +0000 X-Originating-IP: [86.10.211.13] X-Authenticated-User: J.deBoynePollard-newsgroups@NTLWorld.COM X-Spam: 0 X-Authority: v=2.1 cv=PpNuFF43 c=1 sm=1 tr=0 a=SB7hr1IvJSWWr45F2gQiKw==:117 a=SB7hr1IvJSWWr45F2gQiKw==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=x7bEGLp0ZPQA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=2rVjqWD_AAAA:8 a=6I5d2MoRAAAA:8 a=itly7gIdAAAA:8 a=Cb69w17K1QH6oR-ULXsA:9 a=QEXdDO2ut3YA:10 a=ZUGwP7LCt9cA:10 a=FSu5OgGmP5kA:10 a=-FEs8UIgK8oA:10 a=NWVoK91CQyQA:10 a=4CkMMMw_6ev3YZ4Hbd4A:9 a=AaE-UIcGpCdOuspD:21 a=_W_S_7VecoQA:10 a=ULaUcM2Ibn9MdPUUwucP:22 a=IjZwj45LgO3ly-622nXo:22 a=1RpNR2E4bTkVPcsa2RFZ:22 From: Jonathan de Boyne Pollard Subject: nosh version 1.36 To: Debian users , FreeBSD Hackers , Supervision References: <54430B41.3010301@NTLWorld.com> <76c00c13-4cc9-ed9c-f48f-81a3f050b80b@NTLWorld.com> <0d6afc48-3465-3509-ff46-494da45022bc@NTLWorld.com> <731531599.156033.1491767527334.JavaMail.open-xchange@oxbe4.tb.ukmail.iss.as9143.net> <592685009.2293134.1499287287329.JavaMail.open-xchange@oxbe2.tb.ukmail.iss.as9143.net> <43de321f-e66c-5353-09db-58b9921354b4@NTLWorld.COM> Message-ID: Date: Mon, 11 Dec 2017 08:03:43 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <43de321f-e66c-5353-09db-58b9921354b4@NTLWorld.COM> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 08:04:59 -0000 The nosh package is now up to version 1.36 . * http://jdebp.eu./Softwares/nosh/ * https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project * http://jdebp.info./Softwares/nosh/ More Java tools This release comes with the |find-default-jvm| and |find-matching-jvm| tools, which will set up the |JAVA_HOME| environment variable to point to a default/matching JVM directory, using the FreeBSD/TrueOS and Debian conventions for locating JVM directories. To match these, |convert-systemd-units| now recognizes |JVMDefault|, |JVMVersion|, |JVMOperatingSystem|, and |JVMManufacturer| extensions to the systemd unit file format. Tool improvements |convert-systemd-units| now recognizes a |MachineEnvironment| extension to the systemd unit file format, which controls the generation of an invocation of |machineenv|. It also now recognizes and translates |RDMAHCAHandlesMax| and |RDMAHCAObjectsMax| settings. The |unshare| command now has flags for specifying process ID and user ID namespaces on Linux. The |setup-machine-id| command now correctly falls back to the old D-Bus files on FreeBSD, which it had not been doing because of a bug. New system management features In support of an initiative by Warner Losh, there is support for power cycling via hardware and a kernel that support it. The system manager treats |SIGRTMIN+6|, unused in the systemd system, as a request to invoke a new |powercycle| service bundle; and |SIGRTMIN+16|, similarly unused, as the underlying actual powercycle request, which it translates to either |RB_POWERCYCLE| if it is present in the C library headers, or |RB_AUTOBOOT| if it is not. There is a new |system-control powercycle| subcommand, which defaults to sending these signals. Note that the binary packages are currently built on a system that lacks |RB_POWERCYCLE| in the C library. The compatibility |shutdown|, |reboot|, |halt|, and |poweroff| commands all now sport a new |-c|/|--powercycle| option. There are new |fastpowercycle| and |powercycle| commands. The |system-control init| subcommand now sports a new |c|/|C| argument, by analogy to |h|/|H|. And this is of course thus reflected automatically in the compatibility |telinit| command and the |initctl-read| server. Service bundles Fixing an oversight in 1.35, the per-user |dbus| services are now renamed to |dbus-daemon| too. There are a few more service bundles, including ones for |jenkins|, |apacheds|, |udisks2|, and |ndppd|. The |linux-utmp| service bundle has been retired, in favour of a unified |utx| service bundle, which was previously FreeBSD-only, that operates across platforms. In support of this, there is a new |login-update-utmpx| command, and a new |freebsd-shims| package that aliases that to the |utx| command on non-FreeBSD platforms. From owner-freebsd-hackers@freebsd.org Tue Dec 12 11:10:44 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9CE08E946C2 for ; Tue, 12 Dec 2017 11:10:44 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-160.reflexion.net [208.70.210.160]) (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 5C0F776986 for ; Tue, 12 Dec 2017 11:10:43 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 11518 invoked from network); 12 Dec 2017 11:10:36 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 12 Dec 2017 11:10:36 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Tue, 12 Dec 2017 06:10:36 -0500 (EST) Received: (qmail 11924 invoked from network); 12 Dec 2017 11:10:36 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 12 Dec 2017 11:10:36 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id D0258EC8B7B; Tue, 12 Dec 2017 03:10:35 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: A head kernel rpi2 boot-hang bisected: -r326346 good; -r326347 and later hangs-up during boot Message-Id: <32649011-1CFA-4215-BB37-00E4493882CD@dsl-only.net> Date: Tue, 12 Dec 2017 03:10:34 -0800 To: jeff@FreeBSD.org, Freebsd-arm , FreeBSD Hackers , FreeBSD Current X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 11:10:44 -0000 I initially jumped from -r326192 to -r326726 and ended up with a rpi2 that would normally hang somewhere around release APs being displayed. (I have had a couple of completed boots but many dozens of hung-up attempts.) Both a debug kernel and a non-debug kernel hang the same way. Bisecting the kernel (holding world -r326726 constant) showed: -r326346 did not hang (nor did before) -r326347 and later hung. Conclusion: -r326347 changes are involved in the boot hangups. Context: head -r326726 based (from before I did the bisect). My knowledge is limited so I may not have picked optimal material to get from the db> prompt. It appears that the messages about "random" occur during the hang (indefinite wait). As I remember, I have seen examples where the "Trying to mount" did not show up --but normally it did. And example from a hung boot: . . . Release APs Trying to mount root from ufs:/dev/ufs/RPI2rootfs [rw,noatime]... random: unblocking device. arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache The hang never seems to time out but just sits there, even for hours. It allows the ~^B sequence to get to the db> prompt. I've looked around a little a couple of times. One common point is that show allchains has everything listed as sleeping except: chain 32: thread 100001 (pid 1, kernel) blocked on sx "umadrain" XLOCK thread 100077 (pid 23, uma) is on a run queue chain 33: (Note: uma's thread number has varied, as has the one for [pagedaemon].) bd> ps pid ppid pgrp uid state wmesg wchan cmd 28 0 0 0 DL syncer 0xc095a31c [syncer] 27 0 0 0 DL vlruwt 0xd7417730 [vnlru] 26 0 0 0 DL psleep 0xc0959c00 [bufdaemon] 25 0 0 0 RL [bufspacedaemon] 24 0 0 0 DL psleep 0xc095e8f8 [vmdaemon] 23 0 0 0 RL (threaded) [pagedaemon] 100065 RunQ [pagedaemon] 100076 D launds 0xc095e804 [laundry: dom0] 100077 RunQ [uma] . . . 1 0 0 0 DL umadrai 0xc095e528 [kernel] 0 0 0 0 RLs (threaded) [kernel] 100000 D swapin 0xc09673c8 [swapper] . . . 100072 D - 0xd75b7e80 [if_io_tqg_1] 100073 RunQ [if_io_tqg_2] 100074 D - 0xd75b7d80 [if_io_tqg_3] 100075 D - 0xd75b7d00 [if_config_tqg_0] 100078 D - 0xd83dc100 [softirq_0] 100079 D - 0xd75b7c00 [softirq_1] 100080 RunQ [softirq_2] 100081 D - 0xd75b7b00 [softirq_3] (Which if_io_tqg_ and softirq_ pair has RunQ varies.) All RunQ's are shown above. One or two [idle: CPU]'s have state CanRun and the other [idle: CPU]'s have state RUN. They are the only items with those states. Example from the same hangup: 10 0 0 0 RL (threaded) [idle] 100002 Run CPU 0 [idle: cpu0] 100003 Run CPU 1 [idle: cpu1] 100004 CanRun [idle: cpu2] 100005 CanRun [idle: cpu3] db> show lock 0xc095e528 class: sx name: umadrain state: XLOCK: 0xd6cbe740 (tid 100077, pid 23, "uma") waiters: shared db> show thread 100001 Thread 100001 at 0xd40a7000: proc (pid 1): 0xd40a3000 name: kernel stack: 0xd40ac000-0xd40adfff flags: 0x4 pflags: 0x20000000 state: INHIBITED: {SLEEPING} wmesg: umadrain wchan: 0xc095e528 sleeptimo 0. 0 (curr 51d. = 5eac6a0400000000) priority: 84 container lock: sleepq chain (0xc0957244) last voluntary switch: 1297717 ms ago last involuntary switch: 1297809 ms ago db> show thread 100077 Thread 100077 at 0xd6cbe740: proc (pid 23): 0xd6cab000 name: uma stack: 0xd83ca000-0xd83cbfff flags: 0x4 pflags: 0x200000 state: RUNQ priority: 84 container lock: sched lock 2 (0xc0952640) last voluntary switch: 1297815 ms ago last involuntary switch: 1297815 ms ago db> show thread 100073 Thread 100073 at 0xd7406740: proc (pid 0): 0xc09673c8 name: if_io_tqg_2 stack: 0xd742a000-0xd742bfff flags: 0x4 pflags: 0x200000 state: RUNQ priority: 24 container lock: sched lock 2 (0xc0952640) last voluntary switch: 1297818 ms ago db> show thread 100080 Thread 100080 at 0xd7431ae0: proc (pid 0): 0xc09673c8 name: softirq_2 stack: 0xd83f5000-0xd83f6fff flags: 0x4 pflags: 0x200000 state: RUNQ priority: 24 container lock: sched lock 2 (0xc0952640) last voluntary switch: 1297816 ms ago db> show lock 0xc0952640 class: spin mutex name: sched lock 2 flags: {SPIN, RECURSE} state: {UNOWNED} db> show lock 0xc0957244 class: spin mutex name: sleepq chain flags: {SPIN, RECURSE} state: {UNOWNED} db> show thread 100065 Thread 100065 at 0xd6cbb000: proc (pid 23): 0xd6cab000 name: pagedaemon stack: 0xd7403000-0xd7404fff flags: 0x14 pflags: 0x20200000 state: RUNQ priority: 84 container lock: sched lock 1 (0xc0951f80) last voluntary switch: 1029 ms ago last involuntary switch: 28606 ms ago db> show lock 0xc0951f80 class: spin mutex name: sched lock 1 flags: {SPIN, RECURSE} state: {UNOWNED} =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Tue Dec 12 11:40:30 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACAACE953BE for ; Tue, 12 Dec 2017 11:40:30 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-129.reflexion.net [208.70.210.129]) (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 6D8E377C5F for ; Tue, 12 Dec 2017 11:40:29 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 28013 invoked from network); 12 Dec 2017 11:40:22 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 12 Dec 2017 11:40:22 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Tue, 12 Dec 2017 06:40:22 -0500 (EST) Received: (qmail 6924 invoked from network); 12 Dec 2017 11:40:22 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 12 Dec 2017 11:40:22 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 074D0EC861A; Tue, 12 Dec 2017 03:40:22 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: head -r326446 kernel and before: an example rpi2 panic: pmap_remove_pages: pmap 0xc3c06??? va 0x202????? pte2 0 panic: bad pte2 (2 examples) Message-Id: Date: Tue, 12 Dec 2017 03:40:21 -0800 To: Freebsd-arm , FreeBSD Hackers X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 11:40:30 -0000 -r326346 is the last kernel version that I can normally boot the rpi2 I use with. So I do not know about later versions. World was at -r326726 as I was bisecting a different issue based on kernel versions after updating had boot problems. I've only seen this type of panic a couple of times during the bisect, once at shutdown before buffers were flushed, once just after login. I've no, known way to reproduce this on demand. If I see it again, I'll try to get more information. I do have back traces from both examples below. Both involve exec_elf32_imgact . . . . Waiting for PIDS: 659pmap_remove_pages: pmap 0xc3c06564 va 0x202df000 pte2 0 panic: bad pte2 cpuid = 1 time = 1513072659 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc0561a88 lr = 0xc005f0d4 (db_trace_self_wrapper+0x30) sp = 0xc365e878 fp = 0xc365e990 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc005f0d4 lr = 0xc026abdc (vpanic+0x158) sp = 0xc365e998 fp = 0xc365e9b8 r4 = 0x00000100 r5 = 0x00000001 r6 = 0xc06e7d7a r7 = 0xc0933530 vpanic() at vpanic+0x158 pc = 0xc026abdc lr = 0xc026ac7c (kproc_shutdown) sp = 0xc365e9c0 fp = 0xc365e9c4 r4 = 0x00000000 r5 = 0x21dfb801 r6 = 0xc1e1e15c r7 = 0x00000001 r8 = 0xc3c06564 r9 = 0xc1e1e000 r10 = 0xc1e1e19c kproc_shutdown() at kproc_shutdown pc = 0xc026ac7c lr = 0xc057aee8 (pmap_remove_pages+0x8e0) sp = 0xc365e9cc fp = 0xc365ea28 r4 = 0xc026ac7c r5 = 0xc365e9cc pmap_remove_pages() at pmap_remove_pages+0x8e0 pc = 0xc057aee8 lr = 0xc022a304 (exec_new_vmspace+0x184) sp = 0xc365ea30 fp = 0xc365ea78 r4 = 0xc3a87f1c r5 = 0xc3a87f00 r6 = 0xc06a5655 r7 = 0xc4502730 r8 = 0xc3c064b0 r9 = 0xc08062c8 r10 = 0xc365ec20 exec_new_vmspace() at exec_new_vmspace+0x184 pc = 0xc022a304 lr = 0xc0207d98 (exec_elf32_imgact+0x86c) sp = 0xc365ea80 fp = 0xc365eb10 r4 = 0xc08062c8 r5 = 0xc09314fc r6 = 0xe695c134 r7 = 0xc0806380 r8 = 0x00000000 r9 = 0xc365ec20 r10 = 0xe695c000 exec_elf32_imgact() at exec_elf32_imgact+0x86c pc = 0xc0207d98 lr = 0xc0228f98 (kern_execve+0x66c) sp = 0xc365eb18 fp = 0xc365ed60 r4 = 0xc365ec20 r5 = 0x00000000 r6 = 0x00000004 r7 = 0x00000000 r8 = 0xc365ed70 r9 = 0xffffffff r10 = 0xc0931ba0 kern_execve() at kern_execve+0x66c pc = 0xc0228f98 lr = 0xc0228604 (sys_execve+0x58) sp = 0xc365ed68 fp = 0xc365edb0 r4 = 0xc4515740 r5 = 0x00000000 r6 = 0xc45159d8 r7 = 0x00000000 r8 = 0x00000000 r9 = 0xc4515740 r10 = 0xc45159d0 sys_execve() at sys_execve+0x58 pc = 0xc0228604 lr = 0xc0584eac (swi_handler+0x2c4) sp = 0xc365edb8 fp = 0xc365ee40 r4 = 0x200b2718 r5 = 0xc08242a4 r6 = 0xc4502730 r10 = 0xc45159d0 swi_handler() at swi_handler+0x2c4 pc = 0xc0584eac lr = 0xc056445c (swi_exit) sp = 0xc365ee48 fp = 0xbfbfdf78 r4 = 0x200b2718 r5 = 0x200b26cc r6 = 0x200b272c r7 = 0x0000003b r8 = 0xbfbfdf80 r9 = 0x200b2718 r10 = 0x00033844 swi_exit() at swi_exit pc = 0xc056445c lr = 0xc056445c (swi_exit) sp = 0xc365ee48 fp = 0xbfbfdf78 KDB: enter: panic [ thread pid 811 tid 100105 ] Stopped at $d.3: ldrb r15, [r15, r15, ror r15]! pmap_remove_pages: pmap 0xc3c060b4 va 0x20208000 pte2 0 panic: bad pte2 cpuid = 0 time = 1513077251 KDB: stack backtrace: db_trace_self() at db_trace_self pc = 0xc0562044 lr = 0xc005f0d4 (db_trace_self_wrapper+0x30) sp = 0xc1d8c878 fp = 0xc1d8c990 db_trace_self_wrapper() at db_trace_self_wrapper+0x30 pc = 0xc005f0d4 lr = 0xc026abdc (vpanic+0x158) sp = 0xc1d8c998 fp = 0xc1d8c9b8 r4 = 0x00000100 r5 = 0x00000001 r6 = 0xc06e8468 r7 = 0xc0933530 vpanic() at vpanic+0x158 pc = 0xc026abdc lr = 0xc026ac7c (kproc_shutdown) sp = 0xc1d8c9c0 fp = 0xc1d8c9c4 r4 = 0x00000000 r5 = 0x15f40801 r6 = 0xc1e2d828 r7 = 0x00000001 r8 = 0xc3c060b4 r9 = 0xc1e2d000 r10 = 0xc1e2d868 kproc_shutdown() at kproc_shutdown pc = 0xc026ac7c lr = 0xc057b4a8 (pmap_remove_pages+0x8e0) sp = 0xc1d8c9cc fp = 0xc1d8ca28 r4 = 0xc026ac7c r5 = 0xc1d8c9cc pmap_remove_pages() at pmap_remove_pages+0x8e0 pc = 0xc057b4a8 lr = 0xc022a304 (exec_new_vmspace+0x184) sp = 0xc1d8ca30 fp = 0xc1d8ca78 r4 = 0xc3a87f1c r5 = 0xc3a87f00 r6 = 0xc06a5c55 r7 = 0xc49f2ac8 r8 = 0xc3c06000 r9 = 0xc0806b08 r10 = 0xc1d8cc20 exec_new_vmspace() at exec_new_vmspace+0x184 pc = 0xc022a304 lr = 0xc0207d98 (exec_elf32_imgact+0x86c) sp = 0xc1d8ca80 fp = 0xc1d8cb10 r4 = 0xc0806b08 r5 = 0xc09314fc r6 = 0xe75bc134 r7 = 0xc0806bc0 r8 = 0x00000000 r9 = 0xc1d8cc20 r10 = 0xe75bc000 exec_elf32_imgact() at exec_elf32_imgact+0x86c pc = 0xc0207d98 lr = 0xc0228f98 (kern_execve+0x66c) sp = 0xc1d8cb18 fp = 0xc1d8cd60 r4 = 0xc1d8cc20 r5 = 0x00000000 r6 = 0x00000004 r7 = 0x00000000 r8 = 0xc1d8cd70 r9 = 0xffffffff r10 = 0xc0931ba0 kern_execve() at kern_execve+0x66c pc = 0xc0228f98 lr = 0xc0228604 (sys_execve+0x58) sp = 0xc1d8cd68 fp = 0xc1d8cdb0 r4 = 0xc4994ae0 r5 = 0x00000000 r6 = 0xc4994d78 r7 = 0x00000000 r8 = 0x00000000 r9 = 0xc4994ae0 r10 = 0xc4994d70 sys_execve() at sys_execve+0x58 pc = 0xc0228604 lr = 0xc05854ac (swi_handler+0x2c4) sp = 0xc1d8cdb8 fp = 0xc1d8ce40 r4 = 0x200ef268 r5 = 0xc0824ae4 r6 = 0xc49f2ac8 r10 = 0xc4994d70 swi_handler() at swi_handler+0x2c4 pc = 0xc05854ac lr = 0xc0564a18 (swi_exit) sp = 0xc1d8ce48 fp = 0xbfbfe5d0 r4 = 0x200ef268 r5 = 0x200ef210 r6 = 0x200ef29c r7 = 0x0000003b r8 = 0xbfbfe5d8 r9 = 0x200ef268 r10 = 0x00033844 swi_exit() at swi_exit pc = 0xc0564a18 lr = 0xc0564a18 (swi_exit) sp = 0xc1d8ce48 fp = 0xbfbfe5d0 KDB: enter: panic [ thread pid 712 tid 100152 ] Stopped at $d.3: ldrb r15, [r15, r15, ror r15]! === Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Tue Dec 12 17:26:14 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36960E9FBD2 for ; Tue, 12 Dec 2017 17:26:14 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x244.google.com (mail-lf0-x244.google.com [IPv6:2a00:1450:4010:c07::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C95E66EDA for ; Tue, 12 Dec 2017 17:26:13 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x244.google.com with SMTP id f18so24065437lfg.8 for ; Tue, 12 Dec 2017 09:26:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:cc; bh=X3QzjHhz4dZL6Jg+3WPa4fBxJJOvvzPpM0shuTeko34=; b=j9/ilHKNJAaBZOMAOvmfpWHB9FJBoc7uFg8nP6NCj8VHzadx3pGBppAXeB8odQIN0q 5DG9wZGDAOBYEcM81f3KaupP+5QJMLnK/fmej31vbbQPqbnuKmTwsm5D85aDnCEybHSS Ql/hnrWXVWrWxyAzoOOY/Ry8qp0yCDjl0VPcnA7J2Rgsv42Vb870psISH1gWJSCo5VsL +2jU/O1YnxTAlhDMixG1tXsyhujYIWdpL+Q3GkllCxhJIh96E4Us835ELWTBWi+mdPRN hTuH3di1b+neilQof7C3+IayHWXyemalRVrDu4gKoIxs2R6K5lB19iLeesA1dwF7DX05 2FDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:cc; bh=X3QzjHhz4dZL6Jg+3WPa4fBxJJOvvzPpM0shuTeko34=; b=tJLTkLnpv/Srg+noeuxgWRTnktRqLUXRPfIFLaYijNGjOVlkHMzg0OxT5Rw5BfN2/q CJw5CbfXO/zZWRW49FA+f8tyz+5CFAz7BUW3x09Q7erMrREgDd7jqTOOJRqJMABkZEEe pVCKTGKGykPNXnPoFmo4ku1Ap2hgVvG6H5vk7puHemBwJzPoM+n99Wa+erUJkS83aspy p2Pe6hCOxPtJx9RSI1jocIgyuKIdPvX9HK5bN21QVlxCazSVjb4q5SFwqmbzaSu06cR6 Vlywq8ILrMmsO6JgZTHvJ6mM92PVgAaWeQnSTR4wdxdOvo8htLOxSh0kA6n9JgU77yr2 l6uQ== X-Gm-Message-State: AKGB3mJ//mJT2qV2zz4s6AUQ41Gij9yQsPDNSy0Of9PA+IC1bWksfvCd G6c2OwTvKKsceXejGhCG28MfjnAJsqEvnSQKyjc= X-Received: by 10.46.84.86 with SMTP id y22mt2765680ljd.89.1513099570809; Tue, 12 Dec 2017 09:26:10 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.76.19 with HTTP; Tue, 12 Dec 2017 09:26:10 -0800 (PST) In-Reply-To: References: <620CD9B7-201A-46FD-8C9D-DD8DDA3A05C3@meetlost.com> <201712062204.vB6M4B03026339@donotpassgo.dyslexicfish.net> <201712062235.vB6MZlQv034650@donotpassgo.dyslexicfish.net> From: Alan Somers Date: Tue, 12 Dec 2017 10:26:10 -0700 X-Google-Sender-Auth: DA9PJwQPopD53BO7SVWR3aVGm-M Message-ID: Subject: Re: Strange behavior about pattern matching on manual pages [FIXED] Cc: Jamie Landeg-Jones , "freebsd-hackers@freebsd.org" , FreeBSD CURRENT , by@meetlost.com Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 17:26:14 -0000 On Wed, Dec 6, 2017 at 3:53 PM, Alan Somers wrote: > On Wed, Dec 6, 2017 at 3:35 PM, Jamie Landeg-Jones > wrote: > >> Alan Somers wrote: >> >> > How about just setting MANPAGER=less in your environment? >> >> Because some of us prefer "more"? >> >> And as I said, it's related to searching using the more(1) command >> generally. >> >> I was under the impression that fixing bugs in existing commands was a >> better >> solution than telling someone to simply use something else. >> > > Yes, it certainly is. Are you sure this is actually a bug in less, or is > it just weird-but-intended behavior when less is emulating some old version > of more? It would be worth comparing our less sources to upstream's to see > what differences have crept in, and svn blaming them to see why. > I finally traced down the origin of this weird behavior. It dates from FreeBSD r60816, which imported NetBSD's r1.6 (from CVS), which fixed NetBSD PR 227. While your patch fixes the problem by@meetlost.com reported, it regresses the problem described by PR 227. So I don't think we can commit it as-is. http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.bin/less/less/Attic/forwback.c.diff?r1=1.5&r2=1.6&only_with_tag=MAIN&f=h https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=227 For reference, I'll restate a reproduction case for PR 227: 1) Size your terminal to 25 lines 2) jot 20 > ~/tmp/20lines.txt 3) jot 100 120 1 > /tmp/20lines.2.txt 4) more /tmp/20lines.* 5) At the prompt, press spacebar to display the second file. The first file should remain in the scrollback buffer. -Alan From owner-freebsd-hackers@freebsd.org Tue Dec 12 21:31:56 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCE8CE857F4 for ; Tue, 12 Dec 2017 21:31:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-145.reflexion.net [208.70.210.145]) (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 807A073D1C for ; Tue, 12 Dec 2017 21:31:55 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 24728 invoked from network); 12 Dec 2017 21:31:49 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 12 Dec 2017 21:31:49 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Tue, 12 Dec 2017 16:31:49 -0500 (EST) Received: (qmail 10322 invoked from network); 12 Dec 2017 21:31:49 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 12 Dec 2017 21:31:49 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 55B69EC8FE9; Tue, 12 Dec 2017 13:31:48 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: head -r326346 (corrected) kernel and before: an example rpi2 panic: pmap_remove_pages: pmap 0xc3c06??? va 0x202????? pte2 0 panic: bad pte2 (2 examples) Date: Tue, 12 Dec 2017 13:31:47 -0800 References: To: Freebsd-arm , FreeBSD Hackers In-Reply-To: Message-Id: <5E7321BA-5745-497A-ABE8-7744C6CA69A7@dsl-only.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 21:31:56 -0000 [Simply a resend with a corrected Subject line.] On 2017-Dec-12, at 3:40 AM, Mark Millard wrote: > -r326346 is the last kernel version that I can > normally boot the rpi2 I use with. So I do not > know about later versions. World was at > -r326726 as I was bisecting a different > issue based on kernel versions after updating > had boot problems. >=20 > I've only seen this type of panic a couple of > times during the bisect, once at shutdown before > buffers were flushed, once just after login. > I've no, known way to reproduce this on demand. >=20 > If I see it again, I'll try to get more > information. I do have back traces from both > examples below. Both involve exec_elf32_imgact . >=20 > . . . > Waiting for PIDS: 659pmap_remove_pages: pmap 0xc3c06564 va 0x202df000 = pte2 0 > panic: bad pte2 > cpuid =3D 1 > time =3D 1513072659 > KDB: stack backtrace: > db_trace_self() at db_trace_self > pc =3D 0xc0561a88 lr =3D 0xc005f0d4 = (db_trace_self_wrapper+0x30) > sp =3D 0xc365e878 fp =3D 0xc365e990 > db_trace_self_wrapper() at db_trace_self_wrapper+0x30 > pc =3D 0xc005f0d4 lr =3D 0xc026abdc (vpanic+0x158) > sp =3D 0xc365e998 fp =3D 0xc365e9b8 > r4 =3D 0x00000100 r5 =3D 0x00000001 > r6 =3D 0xc06e7d7a r7 =3D 0xc0933530 > vpanic() at vpanic+0x158 > pc =3D 0xc026abdc lr =3D 0xc026ac7c (kproc_shutdown) > sp =3D 0xc365e9c0 fp =3D 0xc365e9c4 > r4 =3D 0x00000000 r5 =3D 0x21dfb801 > r6 =3D 0xc1e1e15c r7 =3D 0x00000001 > r8 =3D 0xc3c06564 r9 =3D 0xc1e1e000 > r10 =3D 0xc1e1e19c > kproc_shutdown() at kproc_shutdown > pc =3D 0xc026ac7c lr =3D 0xc057aee8 (pmap_remove_pages+0x8e0) > sp =3D 0xc365e9cc fp =3D 0xc365ea28 > r4 =3D 0xc026ac7c r5 =3D 0xc365e9cc > pmap_remove_pages() at pmap_remove_pages+0x8e0 > pc =3D 0xc057aee8 lr =3D 0xc022a304 (exec_new_vmspace+0x184) > sp =3D 0xc365ea30 fp =3D 0xc365ea78 > r4 =3D 0xc3a87f1c r5 =3D 0xc3a87f00 > r6 =3D 0xc06a5655 r7 =3D 0xc4502730 > r8 =3D 0xc3c064b0 r9 =3D 0xc08062c8 > r10 =3D 0xc365ec20 > exec_new_vmspace() at exec_new_vmspace+0x184 > pc =3D 0xc022a304 lr =3D 0xc0207d98 (exec_elf32_imgact+0x86c) > sp =3D 0xc365ea80 fp =3D 0xc365eb10 > r4 =3D 0xc08062c8 r5 =3D 0xc09314fc > r6 =3D 0xe695c134 r7 =3D 0xc0806380 > r8 =3D 0x00000000 r9 =3D 0xc365ec20 > r10 =3D 0xe695c000 > exec_elf32_imgact() at exec_elf32_imgact+0x86c > pc =3D 0xc0207d98 lr =3D 0xc0228f98 (kern_execve+0x66c) > sp =3D 0xc365eb18 fp =3D 0xc365ed60 > r4 =3D 0xc365ec20 r5 =3D 0x00000000 > r6 =3D 0x00000004 r7 =3D 0x00000000 > r8 =3D 0xc365ed70 r9 =3D 0xffffffff > r10 =3D 0xc0931ba0 > kern_execve() at kern_execve+0x66c > pc =3D 0xc0228f98 lr =3D 0xc0228604 (sys_execve+0x58) > sp =3D 0xc365ed68 fp =3D 0xc365edb0 > r4 =3D 0xc4515740 r5 =3D 0x00000000 > r6 =3D 0xc45159d8 r7 =3D 0x00000000 > r8 =3D 0x00000000 r9 =3D 0xc4515740 > r10 =3D 0xc45159d0 > sys_execve() at sys_execve+0x58 > pc =3D 0xc0228604 lr =3D 0xc0584eac (swi_handler+0x2c4) > sp =3D 0xc365edb8 fp =3D 0xc365ee40 > r4 =3D 0x200b2718 r5 =3D 0xc08242a4 > r6 =3D 0xc4502730 r10 =3D 0xc45159d0 > swi_handler() at swi_handler+0x2c4 > pc =3D 0xc0584eac lr =3D 0xc056445c (swi_exit) > sp =3D 0xc365ee48 fp =3D 0xbfbfdf78 > r4 =3D 0x200b2718 r5 =3D 0x200b26cc > r6 =3D 0x200b272c r7 =3D 0x0000003b > r8 =3D 0xbfbfdf80 r9 =3D 0x200b2718 > r10 =3D 0x00033844 > swi_exit() at swi_exit > pc =3D 0xc056445c lr =3D 0xc056445c (swi_exit) > sp =3D 0xc365ee48 fp =3D 0xbfbfdf78 > KDB: enter: panic > [ thread pid 811 tid 100105 ] > Stopped at $d.3: ldrb r15, [r15, r15, ror r15]! >=20 > pmap_remove_pages: pmap 0xc3c060b4 va 0x20208000 pte2 0 > panic: bad pte2 > cpuid =3D 0 > time =3D 1513077251 > KDB: stack backtrace: > db_trace_self() at db_trace_self > pc =3D 0xc0562044 lr =3D 0xc005f0d4 = (db_trace_self_wrapper+0x30) > sp =3D 0xc1d8c878 fp =3D 0xc1d8c990 > db_trace_self_wrapper() at db_trace_self_wrapper+0x30 > pc =3D 0xc005f0d4 lr =3D 0xc026abdc (vpanic+0x158) > sp =3D 0xc1d8c998 fp =3D 0xc1d8c9b8 > r4 =3D 0x00000100 r5 =3D 0x00000001 > r6 =3D 0xc06e8468 r7 =3D 0xc0933530 > vpanic() at vpanic+0x158 > pc =3D 0xc026abdc lr =3D 0xc026ac7c (kproc_shutdown) > sp =3D 0xc1d8c9c0 fp =3D 0xc1d8c9c4 > r4 =3D 0x00000000 r5 =3D 0x15f40801 > r6 =3D 0xc1e2d828 r7 =3D 0x00000001 > r8 =3D 0xc3c060b4 r9 =3D 0xc1e2d000 > r10 =3D 0xc1e2d868 > kproc_shutdown() at kproc_shutdown > pc =3D 0xc026ac7c lr =3D 0xc057b4a8 (pmap_remove_pages+0x8e0) > sp =3D 0xc1d8c9cc fp =3D 0xc1d8ca28 > r4 =3D 0xc026ac7c r5 =3D 0xc1d8c9cc > pmap_remove_pages() at pmap_remove_pages+0x8e0 > pc =3D 0xc057b4a8 lr =3D 0xc022a304 (exec_new_vmspace+0x184) > sp =3D 0xc1d8ca30 fp =3D 0xc1d8ca78 > r4 =3D 0xc3a87f1c r5 =3D 0xc3a87f00 > r6 =3D 0xc06a5c55 r7 =3D 0xc49f2ac8 > r8 =3D 0xc3c06000 r9 =3D 0xc0806b08 > r10 =3D 0xc1d8cc20 > exec_new_vmspace() at exec_new_vmspace+0x184 > pc =3D 0xc022a304 lr =3D 0xc0207d98 (exec_elf32_imgact+0x86c) > sp =3D 0xc1d8ca80 fp =3D 0xc1d8cb10 > r4 =3D 0xc0806b08 r5 =3D 0xc09314fc > r6 =3D 0xe75bc134 r7 =3D 0xc0806bc0 > r8 =3D 0x00000000 r9 =3D 0xc1d8cc20 > r10 =3D 0xe75bc000 > exec_elf32_imgact() at exec_elf32_imgact+0x86c > pc =3D 0xc0207d98 lr =3D 0xc0228f98 (kern_execve+0x66c) > sp =3D 0xc1d8cb18 fp =3D 0xc1d8cd60 > r4 =3D 0xc1d8cc20 r5 =3D 0x00000000 > r6 =3D 0x00000004 r7 =3D 0x00000000 > r8 =3D 0xc1d8cd70 r9 =3D 0xffffffff > r10 =3D 0xc0931ba0 > kern_execve() at kern_execve+0x66c > pc =3D 0xc0228f98 lr =3D 0xc0228604 (sys_execve+0x58) > sp =3D 0xc1d8cd68 fp =3D 0xc1d8cdb0 > r4 =3D 0xc4994ae0 r5 =3D 0x00000000 > r6 =3D 0xc4994d78 r7 =3D 0x00000000 > r8 =3D 0x00000000 r9 =3D 0xc4994ae0 > r10 =3D 0xc4994d70 > sys_execve() at sys_execve+0x58 > pc =3D 0xc0228604 lr =3D 0xc05854ac (swi_handler+0x2c4) > sp =3D 0xc1d8cdb8 fp =3D 0xc1d8ce40 > r4 =3D 0x200ef268 r5 =3D 0xc0824ae4 > r6 =3D 0xc49f2ac8 r10 =3D 0xc4994d70 > swi_handler() at swi_handler+0x2c4 > pc =3D 0xc05854ac lr =3D 0xc0564a18 (swi_exit) > sp =3D 0xc1d8ce48 fp =3D 0xbfbfe5d0 > r4 =3D 0x200ef268 r5 =3D 0x200ef210 > r6 =3D 0x200ef29c r7 =3D 0x0000003b > r8 =3D 0xbfbfe5d8 r9 =3D 0x200ef268 > r10 =3D 0x00033844 > swi_exit() at swi_exit > pc =3D 0xc0564a18 lr =3D 0xc0564a18 (swi_exit) > sp =3D 0xc1d8ce48 fp =3D 0xbfbfe5d0 > KDB: enter: panic > [ thread pid 712 tid 100152 ] > Stopped at $d.3: ldrb r15, [r15, r15, ror r15]! =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Tue Dec 12 23:19:32 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58579E88648 for ; Tue, 12 Dec 2017 23:19:32 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-159.reflexion.net [208.70.210.159]) (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 060A477C26 for ; Tue, 12 Dec 2017 23:19:31 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 32601 invoked from network); 12 Dec 2017 23:19:24 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 12 Dec 2017 23:19:24 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Tue, 12 Dec 2017 18:19:24 -0500 (EST) Received: (qmail 9279 invoked from network); 12 Dec 2017 23:19:24 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 12 Dec 2017 23:19:24 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 14E6FEC814E; Tue, 12 Dec 2017 15:19:24 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: A head kernel rpi2 boot-hang bisected: -r326346 good; -r326347 and later hangs-up during boot From: Mark Millard In-Reply-To: <4b2420e8899.5992ee2b@mail.schwarzes.net> Date: Tue, 12 Dec 2017 15:19:23 -0800 Cc: jeff@FreeBSD.org, Freebsd-arm , FreeBSD Hackers , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <241F43AF-23B2-4C54-9B77-A5A7CE3F8E57@dsl-only.net> References: <32649011-1CFA-4215-BB37-00E4493882CD@dsl-only.net> <4b2420e8899.5992ee2b@mail.schwarzes.net> To: Andreas Schwarz X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 23:19:32 -0000 On 2017-Dec-12, at 2:02 PM, Andreas Schwarz = wrote: > On 12.12.17, Mark Millard wrote: >=20 >> I initially jumped from -r326192 to -r326726 and >> ended up with a rpi2 that would normally hang >> somewhere around release APs being displayed. >> (I have had a couple of completed boots but many >> dozens of hung-up attempts.) Both a debug kernel >> and a non-debug kernel hang the same way. >>=20 >> Bisecting the kernel (holding world -r326726 >> constant) showed: >>=20 >> -r326346 did not hang (nor did before) >> -r326347 and later hung. >=20 > JFYI, the latest kernel (and world) running at one of my=20 > RPI2-B is r326631, without any issues. Interesting. (By the way: My context is with a V1.1 Cortex-A7 based rpi2, not V1.2 and Cortex-A53.) I've almost always run the root file system being on a USB SSD instead of on mmcsd0 . I wonder if that is somehow involved since it may be unusual. UFS file system. The USB SSD is on a powered hub that is in turn plugged into the rpi2. [I had the hang problem before the following and after.] The mechanism for holding mmcsd0 in failed recently but the ejection mechanism still works. So I hold in mmcsd0 until after I get a USB SSD boot now. (Interrupt boot, unload, boot/autoboot, picks up the kernel from the USB SSD.) This means that I effectively can not avoid the USB SSD any more unless I get my hands on a different V1.1 rpi2. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Tue Dec 12 22:03:20 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB0F7E868BF; Tue, 12 Dec 2017 22:03:20 +0000 (UTC) (envelope-from freebsd.asc@strcmp.org) Received: from onager.schwarzes.net (onager.schwarzes.net [IPv6:2a03:4000:8:2bb::5d22]) (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 4EE08753D8; Tue, 12 Dec 2017 22:03:19 +0000 (UTC) (envelope-from freebsd.asc@strcmp.org) Received: from [172.30.250.35] (x4dba65d2.dyn.telefonica.de [77.186.101.210]) (authenticated bits=0) by onager.schwarzes.net (8.15.2/8.15.2) with ESMTPA id vBCM2iHt062687; Tue, 12 Dec 2017 23:02:44 +0100 (CET) (envelope-from freebsd.asc@strcmp.org) From: Andreas Schwarz To: Mark Millard CC: jeff@FreeBSD.org, Freebsd-arm , FreeBSD Hackers , FreeBSD Current Mail-Reply-To: Andreas Schwarz Mail-Followup-To: freebsd-arm@FreeBSD.org Date: Tue, 12 Dec 2017 23:02:44 +0100 (CET) Message-ID: <4b2420e8899.5992ee2b@mail.schwarzes.net> In-Reply-To: <32649011-1CFA-4215-BB37-00E4493882CD@dsl-only.net> References: <32649011-1CFA-4215-BB37-00E4493882CD@dsl-only.net> User-Agent: YAM/2.9p1 (MorphOS; PPC; rv:20140418r7798) Subject: Re: A head kernel rpi2 boot-hang bisected: -r326346 good; -r326347 and later hangs-up during boot MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (onager.schwarzes.net [37.221.194.76]); Tue, 12 Dec 2017 23:02:45 +0100 (CET) X-Mailman-Approved-At: Tue, 12 Dec 2017 23:23:17 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 22:03:20 -0000 On 12.12.17, Mark Millard wrote: > I initially jumped from -r326192 to -r326726 and > ended up with a rpi2 that would normally hang > somewhere around release APs being displayed. > (I have had a couple of completed boots but many > dozens of hung-up attempts.) Both a debug kernel > and a non-debug kernel hang the same way. > > Bisecting the kernel (holding world -r326726 > constant) showed: > > -r326346 did not hang (nor did before) > -r326347 and later hung. JFYI, the latest kernel (and world) running at one of my RPI2-B is r326631, without any issues. -asc From owner-freebsd-hackers@freebsd.org Wed Dec 13 00:20:38 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E265E8AA59 for ; Wed, 13 Dec 2017 00:20:38 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-149.reflexion.net [208.70.210.149]) (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 1BE877A26A for ; Wed, 13 Dec 2017 00:20:37 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 10896 invoked from network); 13 Dec 2017 00:20:31 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 13 Dec 2017 00:20:31 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Tue, 12 Dec 2017 19:20:31 -0500 (EST) Received: (qmail 13273 invoked from network); 13 Dec 2017 00:20:31 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Dec 2017 00:20:31 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 30083EC814E; Tue, 12 Dec 2017 16:20:30 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: A head kernel rpi2 boot-hang bisected: -r326346 good; -r326347 and later hangs-up during boot From: Mark Millard In-Reply-To: <241F43AF-23B2-4C54-9B77-A5A7CE3F8E57@dsl-only.net> Date: Tue, 12 Dec 2017 16:20:29 -0800 Cc: FreeBSD Hackers , FreeBSD Current , Freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: References: <32649011-1CFA-4215-BB37-00E4493882CD@dsl-only.net> <4b2420e8899.5992ee2b@mail.schwarzes.net> <241F43AF-23B2-4C54-9B77-A5A7CE3F8E57@dsl-only.net> To: Andreas Schwarz , jeff@FreeBSD.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 00:20:38 -0000 On 2017-Dec-12, at 3:19 PM, Mark Millard wrote: > On 2017-Dec-12, at 2:02 PM, Andreas Schwarz wrote: >=20 >> On 12.12.17, Mark Millard wrote: >>=20 >>> I initially jumped from -r326192 to -r326726 and >>> ended up with a rpi2 that would normally hang >>> somewhere around release APs being displayed. >>> (I have had a couple of completed boots but many >>> dozens of hung-up attempts.) Both a debug kernel >>> and a non-debug kernel hang the same way. >>>=20 >>> Bisecting the kernel (holding world -r326726 >>> constant) showed: >>>=20 >>> -r326346 did not hang (nor did before) >>> -r326347 and later hung. >>=20 >> JFYI, the latest kernel (and world) running at one of my=20 >> RPI2-B is r326631, without any issues. >=20 > Interesting. (By the way: My context > is with a V1.1 Cortex-A7 based rpi2, > not V1.2 and Cortex-A53.) >=20 > I've almost always run the root file > system being on a USB SSD instead of > on mmcsd0 . I wonder if that is > somehow involved since it may be > unusual. UFS file system. >=20 > The USB SSD is on a powered hub that > is in turn plugged into the rpi2. >=20 > [I had the hang problem before the > following and after.] >=20 > The mechanism for holding mmcsd0 in > failed recently but the ejection > mechanism still works. So I hold > in mmcsd0 until after I get a USB > SSD boot now. (Interrupt boot, unload, > boot/autoboot, picks up the kernel > from the USB SSD.) >=20 > This means that I effectively can > not avoid the USB SSD any more > unless I get my hands on a different > V1.1 rpi2. Looks like I'll get my hands on a different rpi2 V1.1 in a few days. So I should then be able to do reasonable mmcsd0-only experiments. At least once I find the time. FYI, in case boot details are involved in reproducing the problem. . . On the mmcsd0 I have /boot/loader.conf with: kern.cam.boot_delay=3D"10000" vfs.mountroot.timeout=3D"10" and /etc/fstab with: /dev/ufs/RPI2rootfs / ufs rw,noatime 1 1 /dev/label/RPI2Aswap none swap sw 0 0 /dev/label/RPI2Aboot /boot/msdos msdosfs rw,noatime 0 0 where the /dev/ufs/RPI2rootfs was the USB SSD. However, I interrupt the loader and unload and then boot or autoboot. (But the hangs started before this extra sequence was involved.) On the USB SSD I have /boot/loader.conf with: kern.cam.boot_delay=3D"10000" vfs.mountroot.timeout=3D"10" and /etc/fstab with: /dev/da0p1 / ufs rw,noatime 1 1 /dev/da0p2 none swap sw 0 0 What db> showed does point to things that -r326347 involve: chain 32: thread 100001 (pid 1, kernel) blocked on sx "umadrain" XLOCK thread 100077 (pid 23, uma) is on a run queue But for all I know -r326347 could be depending on something required to be true but not correct elsewhere in the rpi2 support. I'm not claiming that -r326347 is wrong, just that it is involved. I've way to little knowledge to claim to know what is wrong on the evidence that I have. I've not yet tried a bpi-m3 Cortex-A7 context or a pine64+ 2GB or rpi3 Cortex-A53 context. Nor powerpc64 nor powerpc. At some point I'll get the time for one or more of these. I've not had amd64 problems in this area. I may not be able to test the bpi-m3: its barrel connector for power seems flaky and it is difficult to keep the board powered for long periods in recent times. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Wed Dec 13 00:20:08 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71767E8A9AF; Wed, 13 Dec 2017 00:20:08 +0000 (UTC) (envelope-from freebsd.asc@strcmp.org) Received: from onager.schwarzes.net (onager.schwarzes.net [IPv6:2a03:4000:8:2bb::5d22]) (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 B00867A1EB; Wed, 13 Dec 2017 00:20:07 +0000 (UTC) (envelope-from freebsd.asc@strcmp.org) Received: from [172.30.250.35] (x4dba65d2.dyn.telefonica.de [77.186.101.210]) (authenticated bits=0) by onager.schwarzes.net (8.15.2/8.15.2) with ESMTPA id vBD0K2mT063453; Wed, 13 Dec 2017 01:20:02 +0100 (CET) (envelope-from freebsd.asc@strcmp.org) From: Andreas Schwarz To: Mark Millard CC: jeff@FreeBSD.org, Freebsd-arm , FreeBSD Hackers , FreeBSD Current Mail-Reply-To: Andreas Schwarz Mail-Followup-To: freebsd-arm@FreeBSD.org Date: Wed, 13 Dec 2017 01:20:01 +0100 (CET) Message-ID: <4b24414033.695511f0@mail.schwarzes.net> In-Reply-To: <241F43AF-23B2-4C54-9B77-A5A7CE3F8E57@dsl-only.net> References: <32649011-1CFA-4215-BB37-00E4493882CD@dsl-only.net> <4b2420e8899.5992ee2b@mail.schwarzes.net> <241F43AF-23B2-4C54-9B77-A5A7CE3F8E57@dsl-only.net> User-Agent: YAM/2.9p1 (MorphOS; PPC; rv:20140418r7798) Subject: Re: A head kernel rpi2 boot-hang bisected: -r326346 good; -r326347 and later hangs-up during boot MIME-Version: 1.0 Content-Type: text/plain X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (onager.schwarzes.net [37.221.194.76]); Wed, 13 Dec 2017 01:20:02 +0100 (CET) X-Mailman-Approved-At: Wed, 13 Dec 2017 01:40:48 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 00:20:08 -0000 On 12.12.17, Mark Millard wrote: > On 2017-Dec-12, at 2:02 PM, Andreas Schwarz wrote: >> JFYI, the latest kernel (and world) running at one of my >> RPI2-B is r326631, without any issues. > > Interesting. (By the way: My context > is with a V1.1 Cortex-A7 based rpi2, > not V1.2 and Cortex-A53.) Same here. The RPI2-B (not V1.2) is the most stable system of all my SBCs running FreeBSD. > I've almost always run the root file > system being on a USB SSD instead of > on mmcsd0 . I wonder if that is > somehow involved since it may be > unusual. UFS file system. > > The USB SSD is on a powered hub that > is in turn plugged into the rpi2. Ok, I don't use an USB HDD, the limited USB bridge is the weakest point at the whole rpi, so there are probably not much users with this setup. I understand that you are forced to use ist -asc From owner-freebsd-hackers@freebsd.org Wed Dec 13 01:46:03 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CFF2E8CB7F for ; Wed, 13 Dec 2017 01:46:03 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-133.reflexion.net [208.70.210.133]) (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 EEC1E7CAA0 for ; Wed, 13 Dec 2017 01:46:02 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 31472 invoked from network); 13 Dec 2017 01:46:00 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 13 Dec 2017 01:46:00 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Tue, 12 Dec 2017 20:46:00 -0500 (EST) Received: (qmail 1238 invoked from network); 13 Dec 2017 01:46:00 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Dec 2017 01:46:00 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id CD280EC86EF; Tue, 12 Dec 2017 17:45:59 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: A head kernel rpi2 boot-hang bisected: -r326346 good; -r326347 and later hangs-up during boot [backtraces added] From: Mark Millard In-Reply-To: Date: Tue, 12 Dec 2017 17:45:59 -0800 Cc: FreeBSD Hackers , Freebsd-arm , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <21626363-B6F9-44CE-82C2-91BF0A9F5E4F@dsl-only.net> References: <32649011-1CFA-4215-BB37-00E4493882CD@dsl-only.net> <4b2420e8899.5992ee2b@mail.schwarzes.net> <241F43AF-23B2-4C54-9B77-A5A7CE3F8E57@dsl-only.net> To: jeff@FreeBSD.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 01:46:03 -0000 [Just adding back traces. ffs_mount use of uma_zcreate is involved in the kernel thread, as is uma_reclaim_worker's use of uma_reclaim_locked in the uma thread.] On 2017-Dec-12, at 4:20 PM, Mark Millard wrote: > On 2017-Dec-12, at 3:19 PM, Mark Millard = wrote: >=20 >> On 2017-Dec-12, at 2:02 PM, Andreas Schwarz wrote: >>=20 >>> On 12.12.17, Mark Millard wrote: >>>=20 >>>> I initially jumped from -r326192 to -r326726 and >>>> ended up with a rpi2 that would normally hang >>>> somewhere around release APs being displayed. >>>> (I have had a couple of completed boots but many >>>> dozens of hung-up attempts.) Both a debug kernel >>>> and a non-debug kernel hang the same way. >>>>=20 >>>> Bisecting the kernel (holding world -r326726 >>>> constant) showed: >>>>=20 >>>> -r326346 did not hang (nor did before) >>>> -r326347 and later hung. >>>=20 >>> JFYI, the latest kernel (and world) running at one of my=20 >>> RPI2-B is r326631, without any issues. >>=20 >> Interesting. (By the way: My context >> is with a V1.1 Cortex-A7 based rpi2, >> not V1.2 and Cortex-A53.) >>=20 >> I've almost always run the root file >> system being on a USB SSD instead of >> on mmcsd0 . I wonder if that is >> somehow involved since it may be >> unusual. UFS file system. >>=20 >> The USB SSD is on a powered hub that >> is in turn plugged into the rpi2. >>=20 >> [I had the hang problem before the >> following and after.] >>=20 >> The mechanism for holding mmcsd0 in >> failed recently but the ejection >> mechanism still works. So I hold >> in mmcsd0 until after I get a USB >> SSD boot now. (Interrupt boot, unload, >> boot/autoboot, picks up the kernel >> from the USB SSD.) >>=20 >> This means that I effectively can >> not avoid the USB SSD any more >> unless I get my hands on a different >> V1.1 rpi2. >=20 > Looks like I'll get my hands on a different > rpi2 V1.1 in a few days. So I should then > be able to do reasonable mmcsd0-only > experiments. At least once I find the time. >=20 > FYI, in case boot details are involved > in reproducing the problem. . . >=20 > On the mmcsd0 I have /boot/loader.conf with: >=20 > kern.cam.boot_delay=3D"10000" > vfs.mountroot.timeout=3D"10" >=20 > and /etc/fstab with: >=20 > /dev/ufs/RPI2rootfs / ufs rw,noatime 1 1 > /dev/label/RPI2Aswap none swap sw 0 0 > /dev/label/RPI2Aboot /boot/msdos msdosfs rw,noatime 0 0 >=20 > where the /dev/ufs/RPI2rootfs was the USB SSD. >=20 > However, I interrupt the loader and unload and > then boot or autoboot. (But the hangs started > before this extra sequence was involved.) >=20 > On the USB SSD I have /boot/loader.conf with: >=20 > kern.cam.boot_delay=3D"10000" > vfs.mountroot.timeout=3D"10" >=20 > and /etc/fstab with: >=20 > /dev/da0p1 / ufs rw,noatime 1 1 > /dev/da0p2 none swap sw 0 0 >=20 >=20 > What db> showed does point to things that > -r326347 involve: >=20 > chain 32: > thread 100001 (pid 1, kernel) blocked on sx "umadrain" XLOCK > thread 100077 (pid 23, uma) is on a run queue >=20 > But for all I know -r326347 could be depending > on something required to be true but not correct > elsewhere in the rpi2 support. I'm not claiming > that -r326347 is wrong, just that it is involved. > I've way to little knowledge to claim to know > what is wrong on the evidence that I have. >=20 > I've not yet tried a bpi-m3 Cortex-A7 context or > a pine64+ 2GB or rpi3 Cortex-A53 context. Nor > powerpc64 nor powerpc. At some point I'll get the > time for one or more of these. I've not had amd64 > problems in this area. >=20 > I may not be able to test the bpi-m3: its barrel > connector for power seems flaky and it is > difficult to keep the board powered for long > periods in recent times. For this new example -r326347 kernel based boot-hang: chain 35: thread 100001 (pid 1, kernel) blocked on sx "umadrain" XLOCK thread 100073 (pid 23, uma) is on a run queue db> bt Tracing pid 1 tid 100001 td 0xd429f000 cpu_switch() at cpu_switch+0x18 pc =3D 0xc0584f80 lr =3D 0xc0299ad8 (sched_switch+0x5c0) sp =3D 0xd42a56b8 fp =3D 0xd42a56e8 sched_switch() at sched_switch+0x5c0 pc =3D 0xc0299ad8 lr =3D 0xc0275f28 (mi_switch+0x258) sp =3D 0xd42a56f0 fp =3D 0xd42a5718 r4 =3D 0x0001f0f5 r5 =3D 0x00000000 r6 =3D 0xd429f000 r7 =3D 0x0006612d r8 =3D 0x00000000 r9 =3D 0x00000104 r10 =3D 0xc08073f0 mi_switch() at mi_switch+0x258 pc =3D 0xc0275f28 lr =3D 0xc02c1508 (sleepq_switch+0x1c0) sp =3D 0xd42a5720 fp =3D 0xd42a5748 r4 =3D 0xd429f000 r5 =3D 0xc0947dc4 r6 =3D 0xc09a9c68 r7 =3D 0xc0947dc0 r8 =3D 0x00000000 r9 =3D 0xc09440c0 r10 =3D 0x000000f4 sleepq_switch() at sleepq_switch+0x1c0 pc =3D 0xc02c1508 lr =3D 0xc02c1308 (sleepq_wait+0x48) sp =3D 0xd42a5750 fp =3D 0xd42a5760 r4 =3D 0xd429f000 r5 =3D 0x00000000 r6 =3D 0xc09a9c68 r7 =3D 0xc06b415c r8 =3D 0x00000001 r9 =3D 0xc09a9c78 r10 =3D 0x00000000 sleepq_wait() at sleepq_wait+0x48 pc =3D 0xc02c1308 lr =3D 0xc02748b0 (_sx_slock_hard+0x298) sp =3D 0xd42a5768 fp =3D 0xd42a57c8 r4 =3D 0xc09a9c68 r5 =3D 0xc0823ac0 r6 =3D 0xc06ae146 r7 =3D 0x00000000 _sx_slock_hard() at _sx_slock_hard+0x298 pc =3D 0xc02748b0 lr =3D 0xc027457c (_sx_slock_int+0x140) sp =3D 0xd42a57d0 fp =3D 0xd42a57f8 r4 =3D 0x00000078 r5 =3D 0x00000765 r6 =3D 0xc09a9c68 r7 =3D 0x00000765 r8 =3D 0xc09a9c78 r9 =3D 0xd7ad8740 r10 =3D 0x00000000 _sx_slock_int() at _sx_slock_int+0x140 pc =3D 0xc027457c lr =3D 0xc052b024 (uma_zcreate+0x10c) sp =3D 0xd42a5800 fp =3D 0xd42a5850 r4 =3D 0x00000078 r5 =3D 0xc09a9c68 r6 =3D 0xc06df86e r7 =3D 0xc06dd153 r8 =3D 0x00000000 r9 =3D 0x00000000 r10 =3D 0x00000000 uma_zcreate() at uma_zcreate+0x10c pc =3D 0xc052b024 lr =3D 0xc050cc90 (ffs_mount+0x80) sp =3D 0xd42a5858 fp =3D 0xd42a5980 r4 =3D 0xd7844000 r5 =3D 0x00000000 r6 =3D 0x00000003 r7 =3D 0xc09a99c0 r8 =3D 0x00000000 r9 =3D 0xd429f000 r10 =3D 0xd828c400 ffs_mount() at ffs_mount+0x80 pc =3D 0xc050cc90 lr =3D 0xc032e1d4 (vfs_donmount+0xeec) sp =3D 0xd42a5988 fp =3D 0xd42a5b38 r4 =3D 0xffffffff r5 =3D 0xd74ec120 r6 =3D 0xd429f000 r7 =3D 0x00000000 r8 =3D 0x00000000 r9 =3D 0xc425acd0 r10 =3D 0xd828c400 vfs_donmount() at vfs_donmount+0xeec pc =3D 0xc032e1d4 lr =3D 0xc0330ea8 (kernel_mount+0x70) sp =3D 0xd42a5b40 fp =3D 0xd42a5b78 r4 =3D 0xd82a9000 r5 =3D 0x00000000 r6 =3D 0x00004000 r7 =3D 0x00000000 r8 =3D 0xd87e2050 r9 =3D 0xd87e2040 r10 =3D 0x00000000 kernel_mount() at kernel_mount+0x70 pc =3D 0xc0330ea8 lr =3D 0xc03335dc (parse_mount+0x458) sp =3D 0xd42a5b80 fp =3D 0xd42a5c60 r4 =3D 0xd4263500 r5 =3D 0xd87e2054 r6 =3D 0xd82a9000 r7 =3D 0x00000000 parse_mount() at parse_mount+0x458 pc =3D 0xc03335dc lr =3D 0xc0331a44 ($a.2+0x28) sp =3D 0xd42a5c68 fp =3D 0xd42a5dc8 r4 =3D 0xd7845018 r5 =3D 0x00000000 r6 =3D 0xd7845018 r7 =3D 0xd78404da r8 =3D 0xc06bfbd4 r9 =3D 0xfffffff7 r10 =3D 0xd7836380 $a.2() at $a.2+0x28 pc =3D 0xc0331a44 lr =3D 0xc020a82c (start_init+0x5c) sp =3D 0xd42a5dd0 fp =3D 0xd42a5e20 r4 =3D 0xc06a370c r5 =3D 0xc0823ad0 r6 =3D 0x00000000 r7 =3D 0x00000000 r8 =3D 0xd42a5e48 r9 =3D 0x00000000 r10 =3D 0xd429b000 start_init() at start_init+0x5c pc =3D 0xc020a82c lr =3D 0xc0230f10 (fork_exit+0xa0) sp =3D 0xd42a5e28 fp =3D 0xd42a5e40 r4 =3D 0xd429f000 r5 =3D 0xd429b000 r6 =3D 0xc020a7d0 r7 =3D 0x00000000 r8 =3D 0xd42a5e48 r9 =3D 0x00000000 r10 =3D 0x00000000 fork_exit() at fork_exit+0xa0 pc =3D 0xc0230f10 lr =3D 0xc0564c8c (swi_exit) sp =3D 0xd42a5e48 fp =3D 0x00000000 r4 =3D 0xc020a7d0 r5 =3D 0x00000000 r6 =3D 0x00000000 r7 =3D 0x00000000 r8 =3D 0x00000000 r10 =3D 0x00000000 swi_exit() at swi_exit pc =3D 0xc0564c8c lr =3D 0xc0564c8c (swi_exit) sp =3D 0xd42a5e48 fp =3D 0x00000000 db> bt Tracing pid 23 tid 100073 td 0xd7ad8740 cpu_switch() at cpu_switch+0x18 pc =3D 0xc0584f80 lr =3D 0xc0299ad8 (sched_switch+0x5c0) sp =3D 0xd87dad58 fp =3D 0xd87dad88 sched_switch() at sched_switch+0x5c0 pc =3D 0xc0299ad8 lr =3D 0xc0275f28 (mi_switch+0x258) sp =3D 0xd87dad90 fp =3D 0xd87dadb8 r4 =3D 0x00000025 r5 =3D 0x00000000 r6 =3D 0xd7ad8740 r7 =3D 0x000240ea r8 =3D 0x00000000 r9 =3D 0x00000100 r10 =3D 0xc08073f0 mi_switch() at mi_switch+0x258 pc =3D 0xc0275f28 lr =3D 0xc052d9f8 (uma_reclaim_locked+0x200) sp =3D 0xd87dadc0 fp =3D 0xd87dade8 r4 =3D 0x00000003 r5 =3D 0xc08073f0 r6 =3D 0xc08073f0 r7 =3D 0x00000000 r8 =3D 0x00000000 r9 =3D 0xc0824310 r10 =3D 0xc06df86e uma_reclaim_locked() at uma_reclaim_locked+0x200 pc =3D 0xc052d9f8 lr =3D 0xc052de70 (uma_reclaim_worker+0x4c) sp =3D 0xd87dadf0 fp =3D 0xd87dae20 r4 =3D 0xc09a9c68 r5 =3D 0xc4242d80 r6 =3D 0xc06df86e r7 =3D 0x00000000 r8 =3D 0x00000100 r9 =3D 0xc09b3d08 r10 =3D 0xc09a9c7c uma_reclaim_worker() at uma_reclaim_worker+0x4c pc =3D 0xc052de70 lr =3D 0xc0230f10 (fork_exit+0xa0) sp =3D 0xd87dae28 fp =3D 0xd87dae40 r4 =3D 0xd7ad8740 r5 =3D 0xd70ce000 r6 =3D 0xc052de24 r7 =3D 0x00000000 r8 =3D 0xd87dae48 r9 =3D 0xd7ada3a0 r10 =3D 0xc0824e8c fork_exit() at fork_exit+0xa0 pc =3D 0xc0230f10 lr =3D 0xc0564c8c (swi_exit) sp =3D 0xd87dae48 fp =3D 0x00000000 r4 =3D 0xc052de24 r5 =3D 0x00000000 r6 =3D 0x7ff6d83f r7 =3D 0xd6f583a0 r8 =3D 0xc0824dcc r10 =3D 0xc0824e8c swi_exit() at swi_exit pc =3D 0xc0564c8c lr =3D 0xc0564c8c (swi_exit) sp =3D 0xd87dae48 fp =3D 0x00000000 db> show thread 100001 Thread 100001 at 0xd429f000: proc (pid 1): 0xd429b000 name: kernel stack: 0xd42a4000-0xd42a5fff flags: 0x4 pflags: 0x20000000 state: INHIBITED: {SLEEPING} wmesg: umadrain wchan: 0xc09a9c68 sleeptimo 0. 0 (curr 26. = e3fd787f00000000) priority: 84 container lock: sleepq chain (0xc0947dc4) last voluntary switch: 26523 ms ago last involuntary switch: 26695 ms ago db> show thread 100073 Thread 100073 at 0xd7ad8740: proc (pid 23): 0xd70ce000 name: uma stack: 0xd87d9000-0xd87dafff flags: 0x4 pflags: 0x200000 state: RUNQ priority: 84 container lock: sched lock 3 (0xc0942ec0) last voluntary switch: 26694 ms ago db> show lock 0xc0942ec0 class: spin mutex name: sched lock 3 flags: {SPIN, RECURSE} state: {UNOWNED} =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Wed Dec 13 19:12:20 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9758E83D2A for ; Wed, 13 Dec 2017 19:12:20 +0000 (UTC) (envelope-from mmcco@mykolab.com) Received: from mx.kolabnow.com (mx.kolabnow.com [95.128.36.41]) (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 6B3B87EA7E for ; Wed, 13 Dec 2017 19:12:20 +0000 (UTC) (envelope-from mmcco@mykolab.com) Received: from localhost (unknown [127.0.0.1]) by ext-mx-out001.mykolab.com (Postfix) with ESMTP id 2AF77108E for ; Wed, 13 Dec 2017 20:02:35 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mykolab.com; h= content-disposition:content-type:content-type:mime-version :message-id:subject:subject:from:from:date:date:received :received:received; s=dkim20160331; t=1513191754; x=1513191776; bh=XAaIHd08JM53wlkjmReqHBbYh/2xQqKsxsPMraD7qUo=; b=0RdEDhxezhZw PejK4l2fnUpiL8z9TCoCXnk+dPJAiIl/CwAjWIqlCf+b556v1YtqGIDCfbNT8N3n 4BtP/49tw9c+NjR9Yik+r2QQuLtB54OmaLssPplhDwoHR4I9w8PlFtE9zK1CVqaX HJ2DB+f3Z5AacpjoP4mi0DPayTNvJatjn6vMlFDFiTk7mr+CejTLYei5G0fYLvA5 EiFgP37LsD0GtDf2U+/so+rPTGIaK1qDEFOcDtBdRk96R3dWs9KTdcEG5D70uRal z0pBijt19NB1FSxMmSnnq5gSiphKtXq1mGBlorfMjjfqeSue/5BnlDWBtTH9F055 CChTw5dxzegnlJe5YBbUesvIKqXFmZhKlJhma7wrxnyB5E7ayOMt+5rqUpsblfBL zzSfIb3XSsc0saNnVcDGgpOI7DAJKntx1nk6QD2RiC7BFkEYcZKkhsl0lbKNH+3c 1KjIraK5raFnH3DrFpkK78r4z92w/c2ikM3j8fxOnZtVPmGh4IX1+j52WbkDcgd1 t49oYvoptwyZYuXuY9FwBuKJ9ckh+pNWyhUJ2IJCFSFli9GnfVKjZAUoBYx4vWHc 3tECZVq2eC+MGDlp2fGDT1C+QfKQ3CPeH3bWMeJJLy9bpgIZRrcT3pZH1epSFm5+ GmWmm5hih9GehrvleUgg7QDfgGLLQfE= X-Virus-Scanned: amavisd-new at mykolab.com X-Spam-Flag: NO X-Spam-Score: -0.871 X-Spam-Level: X-Spam-Status: No, score=-0.871 tagged_above=-10 required=4.5 tests=[ALL_TRUSTED=-1, AWL=0.128, FREEMAIL_FROM=0.001] autolearn=ham autolearn_force=no Received: from mx.kolabnow.com ([127.0.0.1]) by localhost (ext-mx-out001.mykolab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMHIsw_7kwAU for ; Wed, 13 Dec 2017 20:02:34 +0100 (CET) Received: from int-mx002.mykolab.com (unknown [10.9.13.2]) by ext-mx-out001.mykolab.com (Postfix) with ESMTPS id C66157A8 for ; Wed, 13 Dec 2017 20:02:34 +0100 (CET) Received: from ext-subm003.mykolab.com (unknown [10.9.6.3]) by int-mx002.mykolab.com (Postfix) with ESMTPS id AC4E4234A for ; Wed, 13 Dec 2017 20:02:34 +0100 (CET) Date: Wed, 13 Dec 2017 12:02:31 -0700 From: Michael McConville To: freebsd-hackers@freebsd.org Subject: Possibly misordered arguments to memset(3) Message-ID: <20171213190230.gf5gax7vswakgrd4@t240> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 19:12:20 -0000 I can't claim to understand this function, but it seems unlikely that the current ordering of the arguments was intentional. Thanks for your time, Michael McConville University of Utah diff --git a/tools/tools/netmap/pkt-gen.c b/tools/tools/netmap/pkt-gen.c index 168e022cfba..6946ac3ba0e 100644 --- a/tools/tools/netmap/pkt-gen.c +++ b/tools/tools/netmap/pkt-gen.c @@ -612,7 +612,7 @@ dump_payload(const char *_p, int len, struct netmap_ring *ring, int cur) ring->slot[cur].flags, len); /* hexdump routine */ for (i = 0; i < len; ) { - memset(buf, sizeof(buf), ' '); + memset(buf, ' ', sizeof(buf)); sprintf(buf, "%5d: ", i); i0 = i; for (j=0; j < 16 && i < len; i++, j++) From owner-freebsd-hackers@freebsd.org Wed Dec 13 20:06:09 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DD3BE84FAD for ; Wed, 13 Dec 2017 20:06:09 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4156D808DE for ; Wed, 13 Dec 2017 20:06:08 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with SMTP id PDHzeJQH7GvLHPDI0eD6LU; Wed, 13 Dec 2017 13:06:02 -0700 X-Authority-Analysis: v=2.2 cv=a9pAzQaF c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=kj9zAlcOel0A:10 a=ocR9PWop10UA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=8pX2ZrVakdhmeEh2UWIA:9 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id 25EF236A; Wed, 13 Dec 2017 12:05:59 -0800 (PST) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id vBDK5gwG003756; Wed, 13 Dec 2017 12:05:42 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id vBDK5g6G003753; Wed, 13 Dec 2017 12:05:42 -0800 (PST) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201712132005.vBDK5g6G003753@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Michael McConville cc: freebsd-hackers@freebsd.org Subject: Re: Possibly misordered arguments to memset(3) In-Reply-To: Message from Michael McConville of "Wed, 13 Dec 2017 12:02:31 -0700." <20171213190230.gf5gax7vswakgrd4@t240> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 13 Dec 2017 12:05:42 -0800 X-CMAE-Envelope: MS4wfGMAbYWuBmwqBheLC9TndcBroL91LbEOEToGEqYwgdjDWHxpwP+3x87WmYTpmMu7I7pQPh3p5INckipA7OBGWuzOJ3zD8whQ0UdLhOOI8nJt21WcRUpb bFWUll2E9HBcIElI7CUzFP1DmUKRjHuD5AzFOBUtCCELBoZdwm+ZKN/27bHcAMF3yTJZCFnklxKWX/OrmMfy3rG8ADmm09MGcXg= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 20:06:09 -0000 In message <20171213190230.gf5gax7vswakgrd4@t240>, Michael McConville writes: > I can't claim to understand this function, but it seems unlikely that the > current ordering of the arguments was intentional. > > Thanks for your time, > Michael McConville > University of Utah > > diff --git a/tools/tools/netmap/pkt-gen.c b/tools/tools/netmap/pkt-gen.c > index 168e022cfba..6946ac3ba0e 100644 > --- a/tools/tools/netmap/pkt-gen.c > +++ b/tools/tools/netmap/pkt-gen.c > @@ -612,7 +612,7 @@ dump_payload(const char *_p, int len, struct netmap_ring > *ring, int cur) > ring->slot[cur].flags, len); > /* hexdump routine */ > for (i = 0; i < len; ) { > - memset(buf, sizeof(buf), ' '); > + memset(buf, ' ', sizeof(buf)); > sprintf(buf, "%5d: ", i); > i0 = i; > for (j=0; j < 16 && i < len; i++, j++) Good catch. Looks like it's been corrected already. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-hackers@freebsd.org Wed Dec 13 20:35:31 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63BC6E85ECD for ; Wed, 13 Dec 2017 20:35:31 +0000 (UTC) (envelope-from mmcco@mykolab.com) Received: from mx.kolabnow.com (mx.kolabnow.com [95.128.36.41]) (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 1D2841D4C for ; Wed, 13 Dec 2017 20:35:30 +0000 (UTC) (envelope-from mmcco@mykolab.com) Received: from localhost (unknown [127.0.0.1]) by ext-mx-out001.mykolab.com (Postfix) with ESMTP id 938D11533 for ; Wed, 13 Dec 2017 21:35:27 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mykolab.com; h= content-disposition:content-type:content-type:mime-version :message-id:subject:subject:from:from:date:date:received :received:received; s=dkim20160331; t=1513197327; x=1513197349; bh=7jlFFIwzGSHoe55gqkczC4sQYlYq/KeeZNquN4y+Izo=; b=kWQTJtkYmgYc u1riNLGn14CgwGC62ZgtkVQDFlRwJA40so4KrXAgaqSt7tngm5gvbgmgElU7f5kJ mjnrhr1zBSOGxOEVxVWzvCLtU4BK21QdKv7rnF6r3VfQkSfWKYIMJDQXMJIIUQfe EEfmeBWKgFsEPO8P8zHs2djTK6ZipdDo4xgvTx0PNAcyzH+MM8Zgb3ZdAyO5rRs4 iGyOkdxr1Pwmsgya158bkEUnMps7zHQCP51UXMr5PJpGTX7VyJ4xrt6X5f8/7Dle aJh5MBD/qTlei12ZUfb718RBvGk8qZrBODvjb48aoNwh9jgKtc0dYMaIhSMv8H6l LsSSRD+hf57/Hol7aP08Z9zj+P+HPDC3mjwTSZaN9o4IZVgTm8UJv8ePKp0W3Zl1 WZ0lltmc1peqoL493IaMJrr5Uv2UV8i6N+VkDCKUzClCKC1TxxplIspJZGibSFHH +FJ0aeoNPSprvE72/9zOQ6CjR2B9LvtzJuMutQFgSKpVaVCV1FpkH8eLka2x+q6o h+qIL2OkDWGtIQUW6eGgf7/aRbbY+NxeqAtvkrA7lgMwZCHOQI1X5LqFrINXcwRU rsGySQ9EtkeETep6intRoWCVvD8vf7rBKHNvviY1mf9QPVxGLe/nf/+z458GFsuY qwK0pCdvsDDa6xCjbCCZ6rkXQrIpBts= X-Virus-Scanned: amavisd-new at mykolab.com X-Spam-Flag: NO X-Spam-Score: -0.873 X-Spam-Level: X-Spam-Status: No, score=-0.873 tagged_above=-10 required=4.5 tests=[ALL_TRUSTED=-1, AWL=0.126, FREEMAIL_FROM=0.001] autolearn=ham autolearn_force=no Received: from mx.kolabnow.com ([127.0.0.1]) by localhost (ext-mx-out001.mykolab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQl5pL5ehZoH for ; Wed, 13 Dec 2017 21:35:27 +0100 (CET) Received: from int-mx002.mykolab.com (unknown [10.9.13.2]) by ext-mx-out001.mykolab.com (Postfix) with ESMTPS id 59AFF108E for ; Wed, 13 Dec 2017 21:35:27 +0100 (CET) Received: from ext-subm002.mykolab.com (unknown [10.9.6.2]) by int-mx002.mykolab.com (Postfix) with ESMTPS id 4189723CF for ; Wed, 13 Dec 2017 21:35:27 +0100 (CET) Date: Wed, 13 Dec 2017 13:35:24 -0700 From: Michael McConville To: freebsd-hackers@freebsd.org Subject: Avoid undefined shift overflow in dhclient Message-ID: <20171213203522.2ytizwymoawwltle@t240> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 20:35:31 -0000 It seems like I should have sent this patch to this list rather than opening a ticket: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208007 Thanks for your time, Michael McConville University of Utah From owner-freebsd-hackers@freebsd.org Wed Dec 13 21:00:31 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7FDA1E87055 for ; Wed, 13 Dec 2017 21:00:31 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 032D963BA5 for ; Wed, 13 Dec 2017 21:00:31 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22a.google.com with SMTP id x204so4202072lfa.11 for ; Wed, 13 Dec 2017 13:00:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zWN9l6ma2BQbSFObo6WELqHFMkAJvU2Ei/Js70tYCjI=; b=qYy3Dj1kLUIjuD4DJwISsDOshlswI+aXmV59CSDs9f7ZHL+dYlF5pHR/9fN6Ns+lof PmE8blI1rbcIx+D1MkpuUQPIMVmRMm+twIG2QwZpQfUoDmUjnNwY2uYnoduN6zxuLEJb 4ZH1TEmaakliN3knX1Ri/7uVBoYz7pvrKQlpEtHRBb9xOgdvoutzb/ZBTWg4szjHONoh BoxVn605XNJ+Lm2VhSNj3gikLCFtk/oQ7wzDiXqrs2WKibG9kDWm8q2XyGNMj45Wq6uT Mo7s3eLFOJSS76DIxShonlZUCHzBuFylR9vAXI6T9MjtBJVPX0rlLBhijXgkK9gz6Yxr MwWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zWN9l6ma2BQbSFObo6WELqHFMkAJvU2Ei/Js70tYCjI=; b=dklbzkd9hEpe2cHa0B4mtfoZzLQEK1QmuD+39Du2seqN7QJJ11BKx43AofDaDyfvjt uOr+nCoKcnAnIAIS+XrNDlMJ51KBVSDFRpm0F9M9wMjFCuamvlLTw97YG75VWt6ancHD TI66ik+xIBtswmn9tBd2YpvX9EQdsljWogtrF766fboylUxX8jCWXjAj3e8NTD0NG8k0 d746i1GAtRslRelvSgYtj8dSHzEzWkwDEUw74qm8hSzyDop7qXCOXmlOHCdH9s8kgqSD hojvdtbdadyxLbECOpa5bAS2bzaJn2uloIKiRD4clVkiL38o6zV4M8urrfE1dVSGjk/h 4FwA== X-Gm-Message-State: AKGB3mKsjb1VH0EDWJ6z91Ks16AdX61J63FN6LaAcGgT+DyD17d8NY7Q oiQIzVO6IT2oldTo/QygmaTbUGXWG5WRgFahkuc= X-Google-Smtp-Source: ACJfBos1g658rXCNPhiEOHJcLLgNspga/ycqyFUfANTAk2gO8IJBXbno7CGDc9P2UuuPhWlLyJWqPDTVNOFLs83PvKs= X-Received: by 10.46.66.69 with SMTP id p66mr2259465lja.18.1513198829010; Wed, 13 Dec 2017 13:00:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.179.76.19 with HTTP; Wed, 13 Dec 2017 13:00:28 -0800 (PST) In-Reply-To: <20171213203522.2ytizwymoawwltle@t240> References: <20171213203522.2ytizwymoawwltle@t240> From: alan somers Date: Wed, 13 Dec 2017 14:00:28 -0700 Message-ID: Subject: Re: Avoid undefined shift overflow in dhclient To: Michael McConville Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 21:00:31 -0000 Thanks for your submission. While your reasoning seems correct, I'm still baffled that neither Clang nor Coverity complains about it. Fixed now. -Alan On Wed, Dec 13, 2017 at 1:35 PM, Michael McConville wrote: > It seems like I should have sent this patch to this list rather than > opening a > ticket: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208007 > > Thanks for your time, > Michael McConville > University of Utah > _______________________________________________ > 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" > From owner-freebsd-hackers@freebsd.org Thu Dec 14 16:39:29 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CA85E86806; Thu, 14 Dec 2017 16:39:29 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:a:dead:bad:faff]) (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 16BB06BCB6; Thu, 14 Dec 2017 16:39:28 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id vBEGdQ1T068839; Thu, 14 Dec 2017 16:39:27 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id vBEGdQYx068838; Thu, 14 Dec 2017 16:39:26 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201712141639.vBEGdQYx068838@donotpassgo.dyslexicfish.net> Date: Thu, 14 Dec 2017 16:39:26 +0000 Organization: Dyslexic Fish To: asomers@freebsd.org Cc: jamie@catflap.org, freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, by@meetlost.com Subject: Re: Strange behavior about pattern matching on manual pages [FIXED] References: <620CD9B7-201A-46FD-8C9D-DD8DDA3A05C3@meetlost.com> <201712062204.vB6M4B03026339@donotpassgo.dyslexicfish.net> <201712062235.vB6MZlQv034650@donotpassgo.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Thu, 14 Dec 2017 16:39:27 +0000 (GMT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 16:39:29 -0000 Alan Somers wrote: > > Yes, it certainly is. Are you sure this is actually a bug in less, or is > > it just weird-but-intended behavior when less is emulating some old version > > of more? It would be worth comparing our less sources to upstream's to see > > what differences have crept in, and svn blaming them to see why. Firstly, apologies for the delay in replying - I've been away. I was planning on investigating further, which is why I hadn't yet formally submitted it. Your info would have been a useful next step to follow, so cheers. > I finally traced down the origin of this weird behavior. It dates from > FreeBSD r60816, which imported NetBSD's r1.6 (from CVS), which fixed NetBSD > PR 227. While your patch fixes the problem by@meetlost.com reported, it > regresses the problem described by PR 227. So I don't think we can commit > it as-is. Thanks for doing that. Of course, it's fine to not apply the patch as in this case. > http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.bin/less/less/Attic/forwback.c.diff?r1=1.5&r2=1.6&only_with_tag=MAIN&f=h > https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=227 > > For reference, I'll restate a reproduction case for PR 227: > 1) Size your terminal to 25 lines > 2) jot 20 > ~/tmp/20lines.txt > 3) jot 100 120 1 > /tmp/20lines.2.txt > 4) more /tmp/20lines.* > 5) At the prompt, press spacebar to display the second file. The first > file should remain in the scrollback buffer. Thanks again. I'll check the PR's, other patches, and your test-case will help greatly. I'll post again when I find a better overall solution. Cheers! Jamie From owner-freebsd-hackers@freebsd.org Thu Dec 14 17:15:21 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D5497E87E9A; Thu, 14 Dec 2017 17:15:21 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 975046E1FE; Thu, 14 Dec 2017 17:15:20 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with ESMTPA id PX6EeVRmUZ8gBPX6FeEDdQ; Thu, 14 Dec 2017 10:15:13 -0700 X-Authority-Analysis: v=2.2 cv=M/g9E24s c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=ocR9PWop10UA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=ag-Oz_82AAAA:8 a=y7kuYUb7n4ZtsMVESh4A:9 a=-XGfW9zKAOz1BphD:21 a=yamhFKWKcW2d2CGF:21 a=mFyHDrcPJccA:10 a=EiQzijv-fp3qqrEWvpUA:9 a=MgieDgEhSvx3FaOa:21 a=OOLWG9eCQyoiPi5M:21 a=2upJ1smRiR5NLq4u:21 a=_W_S_7VecoQA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=4IXIeQpRH-eFAbtnDlMd:22 Received: from [25.81.38.66] (S0106d4ca6d8943b0.gv.shawcable.net [70.66.132.207]) by spqr.komquats.com (Postfix) with ESMTPSA id 31B3F2D9; Thu, 14 Dec 2017 09:15:10 -0800 (PST) MIME-Version: 1.0 From: Cy Schubert Subject: RE: Strange behavior about pattern matching on manual pages [FIXED] Date: Thu, 14 Dec 2017 09:15:13 -0800 To: by , Alan Somers CC: "freebsd-hackers@freebsd.org" , Jamie Landeg-Jones , FreeBSD CURRENT Message-Id: <20171214171510.31B3F2D9@spqr.komquats.com> X-CMAE-Envelope: MS4wfCnVh+dANOvqXBUhqHOZjZodHkUq6ZQgorvk18W9PruxCa5yVekepkZ0pk5703LCPAZ6ogBOjZGKoajewLEtSHti6cU7rDwUOzwcehVP18ttG3oWIF3l O2IE5922MvzkX1d5pvJ4BA2c0RrakYJh6yeSfdfmg0uDaQHlmB5puTnl7rWwtQTZHjvlyKz7BLtf/cpChjme9tZW5KMIFZkkCm26jqzsNRasqqYbzQUubIOM GfA7PT797snt7DR018+94+A0hxgbX3UqRWKk+hiGmtk= Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 17:15:21 -0000 SUlSQywgYXMgSSBzY3JpcHRlZCB0aGlzIGFuZCBoYXZlbid0IGxvb2tlZCBhdCBpdCBmb3IgYSBs b25nIHRpbWU6IExFU1M9LU1Ncw0KDQotLS0NClNlbnQgdXNpbmcgYSB0aW55IHBob25lIGtleWJv YXJkLg0KQXBvbG9naWVzIGZvciBhbnkgdHlwb3MgYW5kIGF1dG9jb3JyZWN0Lg0KQWxzbywgdGhp cyBvbGQgcGhvbmUgb25seSBzdXBwb3J0cyB0b3AgcG9zdC4gQXBvbG9naWVzLg0KDQpDeSBTY2h1 YmVydA0KPEN5LlNjaHViZXJ0QGNzY2h1YmVydC5jb20+IG9yIDxjeUBmcmVlYnNkLm9yZz4NClRo ZSBuZWVkIG9mIHRoZSBtYW55IG91dHdlaWdocyB0aGUgZ3JlZWQgb2YgdGhlIGZldy4NCi0tLQ0K DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogYnkNClNlbnQ6IDA2LzEyLzIwMTcg MTU6MDMNClRvOiBBbGFuIFNvbWVycw0KQ2M6IGZyZWVic2QtaGFja2Vyc0BmcmVlYnNkLm9yZzsg SmFtaWUgTGFuZGVnLUpvbmVzOyBGcmVlQlNEIENVUlJFTlQNClN1YmplY3Q6IFJlOiBTdHJhbmdl IGJlaGF2aW9yIGFib3V0IHBhdHRlcm4gbWF0Y2hpbmcgb24gbWFudWFsIHBhZ2VzIFtGSVhFRF0N Cg0KCj4g1NogMjAxN8TqMTLUwjfI1aOsMDY6NTOjrEFsYW4gU29tZXJzIDxhc29tZXJzQGZyZWVi c2Qub3JnPiDQtLXAo7oKPiAKPiBPbiBXZWQsIERlYyA2LCAyMDE3IGF0IDM6MzUgUE0sIEphbWll IExhbmRlZy1Kb25lcyA8amFtaWVAY2F0ZmxhcC5vcmcgPG1haWx0bzpqYW1pZUBjYXRmbGFwLm9y Zz4+IHdyb3RlOgo+IEFsYW4gU29tZXJzIDxhc29tZXJzQGZyZWVic2Qub3JnIDxtYWlsdG86YXNv bWVyc0BmcmVlYnNkLm9yZz4+IHdyb3RlOgo+IAo+ID4gSG93IGFib3V0IGp1c3Qgc2V0dGluZyBN QU5QQUdFUj1sZXNzIGluIHlvdXIgZW52aXJvbm1lbnQ/Cj4gCj4gQmVjYXVzZSBzb21lIG9mIHVz IHByZWZlciAibW9yZSI/Cj4gCj4gQW5kIGFzIEkgc2FpZCwgaXQncyByZWxhdGVkIHRvIHNlYXJj aGluZyB1c2luZyB0aGUgbW9yZSgxKSBjb21tYW5kIGdlbmVyYWxseS4KPiAKPiBJIHdhcyB1bmRl ciB0aGUgaW1wcmVzc2lvbiB0aGF0IGZpeGluZyBidWdzIGluIGV4aXN0aW5nIGNvbW1hbmRzIHdh cyBhIGJldHRlcgo+IHNvbHV0aW9uIHRoYW4gdGVsbGluZyBzb21lb25lIHRvIHNpbXBseSB1c2Ug c29tZXRoaW5nIGVsc2UuCj4gCj4gWWVzLCBpdCBjZXJ0YWlubHkgaXMuICBBcmUgeW91IHN1cmUg dGhpcyBpcyBhY3R1YWxseSBhIGJ1ZyBpbiBsZXNzLCBvciBpcyBpdCBqdXN0IHdlaXJkLWJ1dC1p bnRlbmRlZCBiZWhhdmlvciB3aGVuIGxlc3MgaXMgZW11bGF0aW5nIHNvbWUgb2xkIHZlcnNpb24g b2YgbW9yZT8gIEl0IHdvdWxkIGJlIHdvcnRoIGNvbXBhcmluZyBvdXIgbGVzcyBzb3VyY2VzIHRv IHVwc3RyZWFtJ3MgdG8gc2VlIHdoYXQgZGlmZmVyZW5jZXMgaGF2ZSBjcmVwdCBpbiwgYW5kIHN2 biBibGFtaW5nIHRoZW0gdG8gc2VlIHdoeS4KPiAKPiAtQWxhbgoKSSBqdXN0IHRlc3QgaXQgaW4g RnJlZUJTRCAxMS4xLVJFTEVBU0UtcDUKCkl0IHdvcmtzIHdlbGwgd2hlbiBJIGNoYW5nZSBQQUdF Uj1tb3JlIHRvIFBBR0VSPWxlc3MgYmVmb3JlIG1hbigxKS4KCkFuZCBJIGZvdW5kIG1vcmUoMSkg YW5kIGxlc3MoMSkgaXMgdGhlIHNhbWUgdGhpbmcodGhleSBoYXZlIHRoZSBzYW1lIGlub2RlIG51 bWJlciBsYXlpbmcgaW4gZnMpLCBtYXkgYmUganVzdCBkaWZmZXJlbnQgY29tbWFuZCBuYW1lLCBk aWZmZXJlbnQgYmVoYXZpb3IuCgpJZiBpdCBpcyBlbXVsYXRpbmcgbW9yZSgxKSBiZWhhdmlvciBi eSBsZXNzKDEpLCB3aHkgbm90IGp1c3QgcmVwbGFjZSBkZWZhdWx0IFBBR0VSPWxlc3MgPwoKCmJ5 Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCmZyZWVic2Qt aGFja2Vyc0BmcmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QKaHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9y Zy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2QtaGFja2VycwpUbyB1bnN1YnNjcmliZSwgc2VuZCBh bnkgbWFpbCB0byAiZnJlZWJzZC1oYWNrZXJzLXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIgo= From owner-freebsd-hackers@freebsd.org Thu Dec 14 19:11:01 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3862E8BF37 for ; Thu, 14 Dec 2017 19:11:01 +0000 (UTC) (envelope-from alexandrugoia9@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A4E5E73B59 for ; Thu, 14 Dec 2017 19:11:01 +0000 (UTC) (envelope-from alexandrugoia9@gmail.com) Received: by mail-oi0-x22f.google.com with SMTP id y75so4620870oie.4 for ; Thu, 14 Dec 2017 11:11:01 -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=4S6yxMc6jZJwZTysJ/5EpUD2TWpjNhe+/x05EVFGJ7o=; b=Sbl6pizwX44E6KlcIPnyFM9sX+/U4YCXXWwXRvDd1Hu441H6q/jyEEEeu+jiteya/j 6ilgZkPHgug96yyd1FWCJT4zrUe1asmeg1JQIsYHub/tN0jj0GgvGEefTrjiENSg56us XPmz9VJpIRAMjUo+CqT7eUM+mOv/yR/ao6Kk+LlD5e6t1BQ6lk3Mv1+lF+MsC4FZ3RUU rnfSkaEHr1risW2I8nv7FwH44BINUseDYUIFlItKazk9D89u95X3XVt6aidDbeORFvP4 sVm78X8UpbLgbZTaoUddUD5KudlKekFkJS4shagngTcQ1KBioL/aneRExlZmWaHaqPJ8 H5AQ== 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=4S6yxMc6jZJwZTysJ/5EpUD2TWpjNhe+/x05EVFGJ7o=; b=ZNtGgpdLjB7hMfwo4OVimKHrwYf46/TqhIw+tTuBbw8oV62iV61cWhE0EItMaqqpwh /9p8LjWHprPz+wsQExITIipQzbDTE8Uc7ThFQkv6OL0SZ30Vqy91wajoq8wB2kBR9LGg 9lzpPL/pTw4DUiYaSaf04+3ukxL9veLQ1SBzf9bEbIfR9eeEXi9fNvuDW0YLzR/jtvDD yEFW1bJ78laKiT/aHR+YKs+a8IwIWytsqJgKQLTpRVUxouG+BtnQOCJAAg94HWR6hpAz vXCAm4z/bwn178TW0akLt1OQxKOL2W/S2NknWHi4nH3KyaMTqg1kAbUdSJK9/nom95Ev FsGw== X-Gm-Message-State: AKGB3mIaiaNwOJpsEMif1nN5yZ1vPh+wbz9/Xu55B+MEZaP2PVBhtwPC gBQbD8bUfM047B+SNGWGlKmWRFUUrqJlzLsaDm8= X-Google-Smtp-Source: ACJfBouPHnar+2W5WWYfIU2RtDaxBT3uqRnjWIgwnWtM7mmyFSMuQKzcarAcGVL4pK1/Kns/Wt6YELu9ONVw49DY6xM= X-Received: by 10.202.188.6 with SMTP id m6mr4868500oif.257.1513278660551; Thu, 14 Dec 2017 11:11:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.74.180.140 with HTTP; Thu, 14 Dec 2017 11:10:59 -0800 (PST) From: Alexandru Goia Date: Thu, 14 Dec 2017 21:10:59 +0200 Message-ID: Subject: * current of freebsd To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 19:11:02 -0000 Greetings, What is the analog of * current from linux, in freebsd ? Thank you ! Alexander -- *Alexandru Goia -- free Unix programmerhttp://www.goia.go.ro/ * *https://github.com/alexandergoia/kewl-source-code/ https://alexandria-kewl-things.blogspot.ro/ * From owner-freebsd-hackers@freebsd.org Thu Dec 14 21:04:46 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9FFFE8FC0C for ; Thu, 14 Dec 2017 21:04:46 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:300:2185:a:dead:bad:faff]) (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 86BEF79C4D for ; Thu, 14 Dec 2017 21:04:46 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [104.207.135.49]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id vBEL4iQg051305; Thu, 14 Dec 2017 21:04:45 GMT (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id vBEL4i7s051297; Thu, 14 Dec 2017 21:04:44 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201712142104.vBEL4i7s051297@donotpassgo.dyslexicfish.net> Date: Thu, 14 Dec 2017 21:04:43 +0000 Organization: Dyslexic Fish To: freebsd-hackers@freebsd.org, alexandrugoia9@gmail.com Subject: Re: * current of freebsd References: In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [104.207.135.49]); Thu, 14 Dec 2017 21:04:45 +0000 (GMT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 21:04:46 -0000 Alexandru Goia wrote: > Greetings, > > What is the analog of * current from linux, in freebsd ? It's called "CURRENT" and is referenced by the version number it will maintain when it becomes STABLE - it's currently tagged 12.0-CURRENT, and is available as "head" in the source code: https://svnweb.freebsd.org/base/head/ Cheers, Jamie From owner-freebsd-hackers@freebsd.org Thu Dec 14 21:26:01 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D99BCE9053C for ; Thu, 14 Dec 2017 21:26:01 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 B2C5B7A5DC for ; Thu, 14 Dec 2017 21:26:01 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id vBELPvRv098977; Thu, 14 Dec 2017 13:25:57 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id vBELPuWw098976; Thu, 14 Dec 2017 13:25:56 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201712142125.vBELPuWw098976@pdx.rh.CN85.dnsmgr.net> Subject: Re: * current of freebsd In-Reply-To: <201712142104.vBEL4i7s051297@donotpassgo.dyslexicfish.net> To: Jamie Landeg-Jones Date: Thu, 14 Dec 2017 13:25:56 -0800 (PST) CC: freebsd-hackers@freebsd.org, alexandrugoia9@gmail.com X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Thu, 14 Dec 2017 22:37:09 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 21:26:01 -0000 > Alexandru Goia wrote: > > > Greetings, > > > > What is the analog of * current from linux, in freebsd ? > > It's called "CURRENT" and is referenced by the version number it will maintain > when it becomes STABLE - it's currently tagged 12.0-CURRENT, and is available as > "head" in the source code: > > https://svnweb.freebsd.org/base/head/ I believe the person is asking more specifically "what is the name of the kernel variable that points to a the process currently running "this" system call in the kernel, which I believe to be curthread->td_proc which is usually refered to via #define curproc curthread->td_proc -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-hackers@freebsd.org Fri Dec 15 04:16:17 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE92DE99D3C for ; Fri, 15 Dec 2017 04:16:17 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x22a.google.com (mail-yb0-x22a.google.com [IPv6:2607:f8b0:4002:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7317F65FAA for ; Fri, 15 Dec 2017 04:16:17 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x22a.google.com with SMTP id z62so5189641yba.11 for ; Thu, 14 Dec 2017 20:16:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to; bh=WK9LGH1uHkgoL/Q6UunCGgi/c+EgVbCnSU1YsrD7QK4=; b=tuJQx6CxxquPdcELxlBmxE7D4lzwHv46Vta0EipjC6tvK2OXB+IvZJZYcyy4SXdH26 NWQGEUpFSMffpoLy5ycsm7Ql5PgFO/G5KF54Fg0wBJ/s0JLzN+8T/czbMF4UemlsPlO/ V5CF3KTpuSvGVPc66zEu6acZuX10N9knosW/w= 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=WK9LGH1uHkgoL/Q6UunCGgi/c+EgVbCnSU1YsrD7QK4=; b=M7gWFKThgVu9JWKt6vRm+7LOEFTfVVP4+55NCqhIbk7OsPZq61bnAhqJLVBbjV0VeX bqpnWzfUVhrfOkMUpUhZb5++4YLHsZlAi0oGlXa7qjriryAFFFj+PVLGVIIamMym0bS5 UeQLOhZ2V0RVDtSh+s+Tx3DjTZ5k3t22zsQWPFE4G6ukM5tyoTvBPYxw2SBnZNJAtssV 3lNACgcbZMG+PMpMmL1WlXKcajfqsER5kkxEetb3rRQ5Cc/0rfJOTe3UortUePCgu/iD qTlyZGJq2C4BjLRts6nxwWe+Snd+zPMy1A6ONfF5ZIvr68goIP6jrPVvNsTaIzC3Mv16 UBWA== X-Gm-Message-State: AKGB3mIuiEp2QnKZX1YQbNQ7Pm1s6j0xYr7hI0nilyzAo1que/eJXlj7 yJlEjT1fvjpT/AgZMJS1QQTm4FqFObOVWf8zq9qbGVng X-Google-Smtp-Source: ACJfBosIHv/Xmi5i3q2q2fgJ358aoEHv9ZtQjWwompguV6PrSKvAOZkrYrQFoApyaN7dLoi2C2NvTqizfkFpEcKfmT8= X-Received: by 10.129.85.11 with SMTP id j11mr6099262ywb.434.1513311376145; Thu, 14 Dec 2017 20:16:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.15.66 with HTTP; Thu, 14 Dec 2017 20:15:45 -0800 (PST) From: Eitan Adler Date: Thu, 14 Dec 2017 20:15:45 -0800 Message-ID: Subject: Objections to converting bsd-family-tree to a dot file To: FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 04:16:17 -0000 Hi all, I've been attempting to maintain bsd-family-tree (available as share/misc/bsd-family-tree) as a plain text file across 3 different operating systems: NetBSD, DragonFly, and FreeBSD. It has to be maintained by hand, and can't be parsed to do anything more useful (like turn it into an image). In addition, formatting differences between the different projects have led to minor differenes that are difficult to merge. I'd like to turn this into into a dot file (https://en.wikipedia.org/wiki/DOT_(graph_description_language)) which is a more natural format for a graph. Any objections? It isn't used for much beyond documentation so changing the format isn't expected to cause any negative effects. -- Eitan Adler From owner-freebsd-hackers@freebsd.org Fri Dec 15 04:58:43 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4991FE9AD64 for ; Fri, 15 Dec 2017 04:58:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1051867395 for ; Fri, 15 Dec 2017 04:58:43 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x236.google.com with SMTP id p139so16763023itb.1 for ; Thu, 14 Dec 2017 20:58:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=lJGUCagQIUtANzqDz0vKuBRVY7urKBOyqLwNjsqVxmY=; b=0SP+zr5VJGyK48zRRtq7R5OkrLczfUw4qP7znVjgM1S0hrVan68xSNS7YjoRH6nG8W nPCGCWfdxw0f47ns7qJwtxLCz72ixkxUlrIyxRGQZh7cTtBtfv+dAUCUs8b8pSnoOt4T X7LFKdIT8EapktI0OHZnXZbMrMh3Kh1TQRODNrr8hLVXiO0vTC/q+Paz6/vPGMORQL81 PXoo/6Ck59BQOQiFBiDrrN7Q/6UQms9dLTQ9MliBfwOaxtlyImIIOYGqa0Ju8cONnW7H ykVXtiaHKldgdBrw1Ej5yW6qHh+4d4PRNpv0jXHYgUihsmy3r5CQyd8VLZ6CAFsM/40U ycjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=lJGUCagQIUtANzqDz0vKuBRVY7urKBOyqLwNjsqVxmY=; b=K7n2kYjPHLtq0iZrwr/rmW2zGTcLJrjrOLdq6DP9bE9QSebgNeUI1cHxYEnXgY8nR6 W3qtO6SyraZMMg33mQF6am9d/7+KX/qwX1LEvX5AEMjHkoPJPMJmMawWp1JTJkaY0oFJ pFtBNKGd+w14JEMhoYWaMOCGleMkIAlCzQMYv4EbqAMfEt3UnSDZ8ynLVqulRUZ8lYNd e9cqsFZrsdEtrabLIHyGYWy+dOzUC6QotRL5iboxVmRZISuuBGf0ktKxe2Q5jw33pyzL FJqaU2Nr0cv6trSr7KTSVlBGsObD+iDOOTcgfTBi4OrgPcXRBnfUam1iVIgxLrbuJx9s +LiQ== X-Gm-Message-State: AKGB3mIN58M/bEGJ9j7ipmRW9rZDZRRPm2fGLdxA1uw8k4ncnMYkkpag R2VqVbWqjJbYKevY9fiUvWOYpBh8XvxuMznEEfH3Yg== X-Google-Smtp-Source: ACJfBosBhGMCP29uCiJg2gOtBhfj7ZR03oBGcl6rSZ3kIYUHsUF/NWH3t62y200MXobx+Fjb53n7EedegWbZXIlb3YA= X-Received: by 10.36.147.193 with SMTP id y184mr6184184itd.64.1513313922144; Thu, 14 Dec 2017 20:58:42 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Thu, 14 Dec 2017 20:58:41 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: From: Warner Losh Date: Thu, 14 Dec 2017 21:58:41 -0700 X-Google-Sender-Auth: 4N3rDcnpPXRA4yE0KDbDnevvO9I Message-ID: Subject: Re: Objections to converting bsd-family-tree to a dot file To: Eitan Adler Cc: FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 04:58:43 -0000 On Thu, Dec 14, 2017 at 9:15 PM, Eitan Adler wrote: > Hi all, > > I've been attempting to maintain bsd-family-tree (available as > share/misc/bsd-family-tree) as a plain text file across 3 different > operating systems: NetBSD, DragonFly, and FreeBSD. > > It has to be maintained by hand, and can't be parsed to do anything > more useful (like turn it into an image). In addition, formatting > differences between the different projects have led to minor > differenes that are difficult to merge. > > I'd like to turn this into into a dot file > (https://en.wikipedia.org/wiki/DOT_(graph_description_language)) which > is a more natural format for a graph. > > Any objections? It isn't used for much beyond documentation so > changing the format isn't expected to cause any negative effects. > Show Me The Money! That is, show me how it will be rendered in the new format and we can talk. A dot format would definitely be useful in addition to what we have now (which includes release dates with useful sources). My concern is that it will render a useless hodgepodge that obscures the main narrative. Warner From owner-freebsd-hackers@freebsd.org Fri Dec 15 07:02:29 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 17C99E9D9DB for ; Fri, 15 Dec 2017 07:02:29 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC9596AD1B for ; Fri, 15 Dec 2017 07:02:28 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x22a.google.com with SMTP id d16so16772873itj.1 for ; Thu, 14 Dec 2017 23:02:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=gLDNR3HYmvQ46nds1jNGmfnxT+y38NuQfQOAPH/6vAw=; b=tKB7MsAQXFUoRxXA66YI6HV98OGaxiq25YBbLk+91p9NbAPHXou0PFEwyAvLxvBwW3 V7kbdU4FTxqrDkHMQ4/8S8cZ9fAi0qV5HfjZ3Us5+BQ5B5Vw2XmjGuKmpEgob0wOgpNq /I0Zi+X6KG+kN47FVk0L3MEpmYXwYlAJ2tcLLZDcwPeVB2aAAjB8GYPvyqLhN3zGpURc 9kcOGMMljiNTdrlK7IrbkzQwsE016/OVJhycZZ84w4vFcYSJCI+TfIH4GZndoLmwfN/G V4gvw1jxsm092/Fe7+gMYJnQrD9f13rl5KgKMm/NHYc9wJGuk3KAhWHmqB0Rjy6fDPwO 41UQ== 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=gLDNR3HYmvQ46nds1jNGmfnxT+y38NuQfQOAPH/6vAw=; b=VXzYq5/SiOKswk2jwGldh2cIiDO/u81vBUuAEEpEhKLvwASR7dGhrenJw5D6vg7seK K//I0LlzJOgUZAxyPoyQoQ+2EFU5h3WTGL89FC5616tEAKX/XCkoLjqUD6GnzPZtEXpJ nvVf5Pazqy4YFyNT6MbT5KSYj6lxyERu2Iunv1TK/zYd6GE3pihgiAT7QjIpZ/nbHpsn OXd852OZgbozYjrfhkb6qLn0nWGdrKpT2Crki+yQ7M8UoHuYcqKeHn1tOZkXLiU25xMK voWzeBsipOMK5x32eTNeRlfvUSsCeZrOSBtvFEFD/9kTXOuuiJgpGM55s0HI4C8aLMqG V7Yw== X-Gm-Message-State: AKGB3mK2PjPPLKwWB52H4aD0/iocA8em3qF8oEjQIir3Xsani/C8XYj5 P2K+zNaVrOTppTfyYmQt1Nh6MGdseQ1shhD+VSGatg== X-Google-Smtp-Source: ACJfBosB+Cv/z1vhsBN6B+ezf2iyohJB+Lw3o/YgkEFMW2YjbOHWr3ZyvvEmDdO5K8bNgCGNP4l2LcaK2LiJcyxCmDI= X-Received: by 10.36.163.138 with SMTP id p132mr6446445ite.57.1513321347739; Thu, 14 Dec 2017 23:02:27 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.125.79 with HTTP; Thu, 14 Dec 2017 23:02:27 -0800 (PST) From: Lee Brown Date: Thu, 14 Dec 2017 23:02:27 -0800 Message-ID: Subject: Unable to build world someplace not /usr/obj To: FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 07:02:29 -0000 I have been trying to buildworld with the following, but it always faults on contrib/tcsh/sh.c (not related) make -C /scratch/11.1-releng/src MAKEOBJDIRPREFIX=/scratch/11.1-releng/obj buildworld If I just remove the variable, it works fine, except the files don't go where I want of course. make -C /scratch/11.1-releng/src buildworld The build machine is 11.1-RELEASE (r321309) and the source is the same version. Can anybody clue me into what I'm doing wrong? I'm sure I used to do this no problem. There are no packages installed, just a vanilla system. Thanks in advance -- lee From owner-freebsd-hackers@freebsd.org Fri Dec 15 07:52:11 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87375E9E8E1 for ; Fri, 15 Dec 2017 07:52:11 +0000 (UTC) (envelope-from herbert@gojira.at) Received: from mail.bsd4all.net (mail.bsd4all.net [IPv6:2a01:4f8:191:217b::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.bsd4all.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 558F46BF71 for ; Fri, 15 Dec 2017 07:52:11 +0000 (UTC) (envelope-from herbert@gojira.at) Received: by mail.bsd4all.net (Postfix, from userid 1001) id 3yyjLv72GnzW5F; Fri, 15 Dec 2017 08:52:07 +0100 (CET) Date: Fri, 15 Dec 2017 08:52:07 +0100 From: "Herbert J. Skuhra" To: Lee Brown Cc: FreeBSD Hackers Subject: Re: Unable to build world someplace not /usr/obj Message-ID: <20171215075207.GA21190@mail.bsd4all.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 07:52:11 -0000 On Thu, Dec 14, 2017 at 11:02:27PM -0800, Lee Brown wrote: > I have been trying to buildworld with the following, but it always faults > on contrib/tcsh/sh.c (not related) > > make -C /scratch/11.1-releng/src MAKEOBJDIRPREFIX=/scratch/11.1-releng/obj > buildworld > > If I just remove the variable, it works fine, except the files don't go > where I want of course. > > make -C /scratch/11.1-releng/src buildworld > > The build machine is 11.1-RELEASE (r321309) and the source is the same > version. > > Can anybody clue me into what I'm doing wrong? I'm sure I used to do this > no problem. There are no packages installed, just a vanilla system. % man make.conf Note, that MAKEOBJDIRPREFIX and MAKEOBJDIR are environment variables and should not be set in make.conf or as command line arguments to make(1), but in make's environment. -- Herbert From owner-freebsd-hackers@freebsd.org Fri Dec 15 08:51:50 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A3C3E9FD6B for ; Fri, 15 Dec 2017 08:51:50 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36BA26D6E5 for ; Fri, 15 Dec 2017 08:51:50 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x229.google.com with SMTP id t127so5546768ybf.9 for ; Fri, 15 Dec 2017 00:51:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=691T1LZ2GmUQhJX2EOI4vQkjvJGS7GBpaP1NyB9UrUE=; b=Uef+N+x6dmfjB+uHC2doSacNy9YBYxnGsm80QBMFe9/UGt11LN51erKg6TQtMlA8sH W8TcD247xoTNyQ3CEbOmtOxgSMfHMJvPcJatXsoHR0aWjQIZdwnPBKeJCut811KwhAbw oZ0aGsMU/ilfMw0UgL/dt9UuXroN6xkzECVvM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=691T1LZ2GmUQhJX2EOI4vQkjvJGS7GBpaP1NyB9UrUE=; b=baoOOWLwzCKdWs6De35j7hedyDD8pxdVqvIDNwfpnyQkO9whV4oojCoatkvLNq5V2W Tj98Ge3Opx4jax/if2Io0KehrYaz5VGiyR2vldDDJAQOHF+H7jbyBiMceMxDhY+2s9B4 DClredFrML7Chl5/e3/yHOtBGZTUmwV9BaO7BXsrfvcvpcvzk+ztqFbOEgZs1MduG+xt OM8wIXX/zNZn/F1pbs3yGv8uhvVfszxKTNThKZow/+qylaz/tkIzsV4GK73MCWpt0SX3 yC2y2cLv5dfL0i8ho1a6FvkPvToif/Z/6HMogIw/p9XmkDJNaMgtmhmkZ7SkWHixdK0e 8lYw== X-Gm-Message-State: AKGB3mIuVk1HmEkSDRP+ZHiI7idcU5E23g0nV5RUJ2jDVu2AYSoeGMaB +4zwEsHv1zZ1G76rgyrt4bnk2zzct78iwiKgEnsbhw== X-Google-Smtp-Source: ACJfBovXunQ5FdR+dIgBuwCQBlUy2zO5ICeOL/Tl12uVI9sK807Z1qUGvv0/koHyWDI4/muDzh59rhdOCRW7CAl/13g= X-Received: by 10.37.136.7 with SMTP id c7mr6644376ybl.171.1513327909262; Fri, 15 Dec 2017 00:51:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.15.66 with HTTP; Fri, 15 Dec 2017 00:51:18 -0800 (PST) In-Reply-To: References: From: Eitan Adler Date: Fri, 15 Dec 2017 00:51:18 -0800 Message-ID: Subject: Re: Objections to converting bsd-family-tree to a dot file To: Maxim Konovalov Cc: FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 08:51:50 -0000 > Show Me The Money! See examples at the bottom > How easy would it be to render something like the existing bsd-family-tree, e.g. something that is reasonably intelligent when viewed with more(1) or less(1) with the same basic information that it has now? Pretty easy. Examples below. Note its just a first draft. That said, I did find several unconnected nodes: some of which are corrected in this version. > Also, would rendering it be something that can reasonably be done while building the system, or would it need to be pre-rendered and the result checked into the SCM (keep in mind that NetBSD's build.sh is portable, i.e. you can build NetBSD on Windows if you feel like it)? It'll likely be easier to check it to the repo. It can be done reasonably portably using graphviz, but its not likely worth it. >> Any objections? It isn't used for much beyond documentation so >> changing the format isn't expected to cause any negative effects. >> > Today it is very simple plaintext thing. For me, the complexity will > overweight the value of this file. It isn't really complex: https://people.freebsd.org/~eadler/files/family-tree/by-hand-1.dot.txt https://people.freebsd.org/~eadler/files/family-tree/ -- Eitan Adler From owner-freebsd-hackers@freebsd.org Fri Dec 15 06:38:53 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56F85E9D241 for ; Fri, 15 Dec 2017 06:38:53 +0000 (UTC) (envelope-from cue@cornerstoneservice.ca) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E96C6A151 for ; Fri, 15 Dec 2017 06:38:51 +0000 (UTC) (envelope-from cue@cornerstoneservice.ca) Received: from CornerstoneService.ca ([70.67.47.252]) by shaw.ca with ESMTP id PjdreYYYCZ8gBPjdseGxlh; Thu, 14 Dec 2017 23:38:50 -0700 X-Authority-Analysis: v=2.2 cv=M/g9E24s c=1 sm=1 tr=0 a=pdF43hDbDFbgfWjnaID4Kg==:117 a=pdF43hDbDFbgfWjnaID4Kg==:17 a=ocR9PWop10UA:10 a=8pif782wAAAA:8 a=FKwB20J3IQbkyv-GcMkA:9 Received: from server.cornerstoneservice.ca (localhost [127.0.0.1]) by CornerstoneService.ca (8.15.2/8.15.1) with ESMTP id vBF6PEP4011573; Thu, 14 Dec 2017 22:25:14 -0800 (PST) Received: (from cue@localhost) by server.cornerstoneservice.ca (8.15.2/8.14.5/Submit) id vBF6PDcl029968; Thu, 14 Dec 2017 22:25:13 -0800 (PST) Message-Id: <201712150625.vBF6PDcl029968@server.cornerstoneservice.ca> From: John Nemeth Date: Thu, 14 Dec 2017 22:25:13 -0800 In-Reply-To: X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: Eitan Adler , FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file X-Scanned-By: MIMEDefang 2.78 on 192.168.1.250 X-CMAE-Envelope: MS4wfP3TeMI1JcQxRvAFUgjs6dTHda8vxNwvJQvhmFAdfXf2jQykJyMBm4P1OLjZ9C21JtquAHagE50f7Q6dh2mhro3dgQ7kH/qIgxh2HVfSVk783Nejybn7 swebYUpLmueWd0jEdG7M9vofpWAcOVEA/s15m1w19Mq3XSaKuyaOa5FuBVDAsK4vG/mU7oaMie2xubyTJFlBnhiFYh55JHWdeDE9v0t9HFICkUL4fuszNrmS tA/mi8x9xq0r4xv3MAlOIrFRswsb47OkcjwBsv4sBzVbsQdVY3IgduzVNm22hQCW X-Mailman-Approved-At: Fri, 15 Dec 2017 11:19:32 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 06:38:53 -0000 On Dec 14, 8:15pm, Eitan Adler wrote: } } I've been attempting to maintain bsd-family-tree (available as } share/misc/bsd-family-tree) as a plain text file across 3 different } operating systems: NetBSD, DragonFly, and FreeBSD. } } It has to be maintained by hand, and can't be parsed to do anything } more useful (like turn it into an image). In addition, formatting } differences between the different projects have led to minor } differenes that are difficult to merge. } } I'd like to turn this into into a dot file } (https://en.wikipedia.org/wiki/DOT_(graph_description_language)) which } is a more natural format for a graph. } } Any objections? It isn't used for much beyond documentation so } changing the format isn't expected to cause any negative effects. How easy would it be to render something like the existing bsd-family-tree, e.g. something that is reasonably intelligent when viewed with more(1) or less(1) with the same basic information that it has now? Also, would rendering it be something that can reasonably be done while building the system, or would it need to be pre-rendered and the result checked into the SCM (keep in mind that NetBSD's build.sh is portable, i.e. you can build NetBSD on Windows if you feel like it)? }-- End of excerpt from Eitan Adler From owner-freebsd-hackers@freebsd.org Fri Dec 15 08:26:53 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00CECE9F413 for ; Fri, 15 Dec 2017 08:26:53 +0000 (UTC) (envelope-from maxim.konovalov@gmail.com) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 830326CBBB for ; Fri, 15 Dec 2017 08:26:52 +0000 (UTC) (envelope-from maxim.konovalov@gmail.com) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.15.2/8.15.2) with ESMTP id vBF8QigI033382; Fri, 15 Dec 2017 11:26:44 +0300 (MSK) (envelope-from maxim.konovalov@gmail.com) Date: Fri, 15 Dec 2017 11:26:44 +0300 (MSK) From: Maxim Konovalov To: Eitan Adler cc: FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Fri, 15 Dec 2017 11:33:41 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 08:26:53 -0000 Hi Eitan, On Thu, 14 Dec 2017, 20:15-0800, Eitan Adler wrote: > Hi all, > > I've been attempting to maintain bsd-family-tree (available as > share/misc/bsd-family-tree) as a plain text file across 3 different > operating systems: NetBSD, DragonFly, and FreeBSD. > > It has to be maintained by hand, and can't be parsed to do anything > more useful (like turn it into an image). In addition, formatting > differences between the different projects have led to minor > differenes that are difficult to merge. > > I'd like to turn this into into a dot file > (https://en.wikipedia.org/wiki/DOT_(graph_description_language)) which > is a more natural format for a graph. > How does this solve the maintanance issue across different OSes? > Any objections? It isn't used for much beyond documentation so > changing the format isn't expected to cause any negative effects. > Today it is very simple plaintext thing. For me, the complexity will overweight the value of this file. -- Maxim Konovalov From owner-freebsd-hackers@freebsd.org Fri Dec 15 09:33:14 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A63D8EA0E68 for ; Fri, 15 Dec 2017 09:33:14 +0000 (UTC) (envelope-from maxim.konovalov@gmail.com) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 18B706EADB for ; Fri, 15 Dec 2017 09:33:13 +0000 (UTC) (envelope-from maxim.konovalov@gmail.com) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.15.2/8.15.2) with ESMTP id vBF9X55w009446; Fri, 15 Dec 2017 12:33:05 +0300 (MSK) (envelope-from maxim.konovalov@gmail.com) Date: Fri, 15 Dec 2017 12:33:05 +0300 (MSK) From: Maxim Konovalov To: Eitan Adler cc: FreeBSD Hackers , tech-misc@netbsd.org, Kernel@dragonflybsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Fri, 15 Dec 2017 11:33:52 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 09:33:14 -0000 [..] > > Today it is very simple plaintext thing. For me, the complexity will > > overweight the value of this file. > > It isn't really complex: > https://people.freebsd.org/~eadler/files/family-tree/by-hand-1.dot.txt > https://people.freebsd.org/~eadler/files/family-tree/ > Right, but you need a separate tool for conversion. -- Maxim Konovalov From owner-freebsd-hackers@freebsd.org Fri Dec 15 15:46:11 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC716E84B0E for ; Fri, 15 Dec 2017 15:46:11 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CAF087AA9E for ; Fri, 15 Dec 2017 15:46:11 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id vBFFlfjP027529; Fri, 15 Dec 2017 07:47:47 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "FreeBSD Hackers" , , , "Maxim Konovalov" In-Reply-To: From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Eitan Adler" Subject: Re: Objections to converting bsd-family-tree to a dot file Date: Fri, 15 Dec 2017 07:47:47 -0800 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 15:46:12 -0000 On Fri, 15 Dec 2017 00:51:18 -0800 "Eitan Adler" sai= d > > Show Me The Money! >=20 > See examples at the bottom >=20 >=20 > > How easy would it be to render something like the existing > bsd-family-tree, e=2Eg=2E something that is reasonably intelligent when > viewed with more(1) or less(1) with the same basic information that > it has now? >=20 > Pretty easy=2E Examples below=2E Note its just a first draft=2E That said, I > did find several unconnected nodes: some of which are corrected in > this version=2E >=20 > > Also, would rendering it be something that can reasonably > be done while building the system, or would it need to be pre-rendered > and the result checked into the SCM (keep in mind that NetBSD's > build=2Esh is portable, i=2Ee=2E you can build NetBSD on Windows if you > feel like it)? >=20 > It'll likely be easier to check it to the repo=2E It can be done > reasonably portably using graphviz, but its not likely worth it=2E >=20 >=20 > >> Any objections? It isn't used for much beyond documentation so > >> changing the format isn't expected to cause any negative effects=2E > >> > > Today it is very simple plaintext thing=2E For me, the complexity will > > overweight the value of this file=2E >=20 >=20 > It isn't really complex: > https://people=2Efreebsd=2Eorg/~eadler/files/family-tree/by-hand-1=2Edot=2Etxt First off, thanks for maintaining this, Eitan=2E :-) I realize this is a first draft=2E But from my reading, it looks like you might be mixing tabs, and spaces=2E Not sure if it makes a difference to the graphviz output=2E But as memory serves, it does=2E Hope this helps, and thanks again! --Chris > https://people=2Efreebsd=2Eorg/~eadler/files/family-tree/ >=20 >=20 >=20 > --=20 > Eitan Adler From owner-freebsd-hackers@freebsd.org Fri Dec 15 17:28:50 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38788E870C9 for ; Fri, 15 Dec 2017 17:28:50 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 07E637DF9B for ; Fri, 15 Dec 2017 17:28:49 +0000 (UTC) (envelope-from leeb@ratnaling.org) Received: by mail-it0-x229.google.com with SMTP id x28so21327632ita.0 for ; Fri, 15 Dec 2017 09:28:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ratnaling-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RaF9Q+03ab8wU0IxotX7e7Qp0y/ufdaW9YXnyrewJSI=; b=GY4LRg66qLSDS48ppYTjnalw+y3nRJHvU8nIr3b8YpYdA8CkzgiuGPxT6/5PfxqRFT 2OeHCnbE5+v0UfEq2KJCf2CEfT2NF14kj46TPk5bNKnKfQbheL8wKA8bnV67QBBDwhEX +l3MlrIy1oZn2Z2UgZa9pfm5dZ8+p7r7FUEcL6r4XKRWAF3AH53YY9qVIU5gBOaIXPe9 xRE/oxh9tpJSkbpUox/rgLj8WkzJakLR6gC1PePr9VIMfcSBWllYUjcjNhzqPmcYXa1Y CGRYeOIDJiE+oLEcK6R8voh4cDHEVfpdBzPrgBd7UBabdsa+qUURSPESKAIZSxJ2xhIk e9Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RaF9Q+03ab8wU0IxotX7e7Qp0y/ufdaW9YXnyrewJSI=; b=nxRx47NDSed93pblRVbSSHrk3LBgXhxwQpOIAR6D0gliwOaQQehpgIjshMMEU+OGzK RIYvut3J4l8TWt+04oGx/mmPpp72vBkGCtFsC7fm4cwrHgRhuPCPAVyiQRi0rGZNbnb9 9rUU3HyGDA8AoCaIIfdqnNSw/sNc3Mr4pUpSPqXsdiIyRv8KFcDUhsO9crGtFRwLARhM lGex2tGmkEPkQN2FzX8cb4c1dr52HbEzByPG7RX3cIuSusJ1KHVwyKpH01nRzcnTGPPJ 5nL/Da8ODwsL0oFl5RV83JcgTrGlsde6z/d6KALqjZi41b7f2to0W0PpEjZvG3Mds/z8 sA8Q== X-Gm-Message-State: AKGB3mIBwNVAll8mbiT/IlHeKllCbVEoeeMdJpvMuEHoZ8s0NEnd+Wx4 uZhDWJM/yBGCRwsWdLWxuz2g1xtR4G4eDkabkfOD8A== X-Google-Smtp-Source: ACJfBovl9Evm9mBP6yScgtUYfW9UZBBssOaIw0FErQtNNn+lipbWzM/9vV2b8qg3N/B9CrdOjY8NXO8v1/1rlShuw5M= X-Received: by 10.107.8.72 with SMTP id 69mr12447131ioi.271.1513358928478; Fri, 15 Dec 2017 09:28:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.125.79 with HTTP; Fri, 15 Dec 2017 09:28:47 -0800 (PST) In-Reply-To: <20171215075207.GA21190@mail.bsd4all.net> References: <20171215075207.GA21190@mail.bsd4all.net> From: Lee Brown Date: Fri, 15 Dec 2017 09:28:47 -0800 Message-ID: Subject: Re: Unable to build world someplace not /usr/obj To: "Herbert J. Skuhra" Cc: FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 17:28:50 -0000 On Thu, Dec 14, 2017 at 11:52 PM, Herbert J. Skuhra wrote: > On Thu, Dec 14, 2017 at 11:02:27PM -0800, Lee Brown wrote: > > I have been trying to buildworld with the following, but it always faults > > on contrib/tcsh/sh.c (not related) > > > > make -C /scratch/11.1-releng/src MAKEOBJDIRPREFIX=/scratch/11. > 1-releng/obj > > buildworld > > > > If I just remove the variable, it works fine, except the files don't go > > where I want of course. > > > > make -C /scratch/11.1-releng/src buildworld > > > > The build machine is 11.1-RELEASE (r321309) and the source is the same > > version. > > > > Can anybody clue me into what I'm doing wrong? I'm sure I used to do > this > > no problem. There are no packages installed, just a vanilla system. > > % man make.conf > > Note, that MAKEOBJDIRPREFIX and MAKEOBJDIR are environment variables > and > should not be set in make.conf or as command line arguments to > make(1), > but in make's environment. > > -- > Herbert > Thank you for that. I slapped my forehead in shame. From owner-freebsd-hackers@freebsd.org Fri Dec 15 16:43:50 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D7A7E85F7F for ; Fri, 15 Dec 2017 16:43:50 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from orthanc.ca (orthanc.ca [IPv6:2607:f2f8:abf8::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "orthanc.ca", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1653B7C7BD for ; Fri, 15 Dec 2017 16:43:50 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from localhost (localhost [IPv6:0:0:0:0:0:0:0:1]) by orthanc.ca (8.15.2/8.15.2) with ESMTPS id vBFGhlDE035967 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 Dec 2017 08:43:47 -0800 (PST) (envelope-from lyndon@orthanc.ca) Date: Fri, 15 Dec 2017 08:43:47 -0800 (PST) From: Lyndon Nerenberg To: Eitan Adler cc: FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (BSF 202 2017-01-01) Organization: The Frobozz Magic Homing Pigeon Company MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, MISSING_DATE,MISSING_MID,NO_RECEIVED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on orthanc.ca X-Mailman-Approved-At: Fri, 15 Dec 2017 17:34:51 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 16:43:50 -0000 > I'd like to turn this into into a dot file Sounds like a reasonable idea. With care, the source (text) file(s) can often be formatted in a way that's at least semi-readable. I assume this would ship with pregenerated images (PDF, SVG) so people don't have to install the port to render the graph? --lyndon From owner-freebsd-hackers@freebsd.org Fri Dec 15 17:50:54 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F7DEE87AFB for ; Fri, 15 Dec 2017 17:50:54 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E1ECA7ED2E for ; Fri, 15 Dec 2017 17:50:53 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with ESMTPA id Pu8GenAfHb3YIPu8HedcDw; Fri, 15 Dec 2017 10:50:52 -0700 X-Authority-Analysis: v=2.2 cv=J/va1EvS c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=ocR9PWop10UA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=_ctWjzdLAAAA:8 a=8ggJXkvBAAAA:8 a=jPSH_t4RsDjJbzh3J4UA:9 a=6v1Q-wxHxk9pcBVL:21 a=EguX4USaTb-PdkOv:21 a=CjuIK1q_8ugA:10 a=zRL81u0_o21GlWo_nKIA:9 a=hZP07T1VIOTtOGmo:21 a=iCUxsc7A8H8cSbrn:21 a=tE_AOXnkh-z5xQPU:21 a=_W_S_7VecoQA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=WoGCsytTnHKj16XvecxK:22 a=GHEzSmbhvkB-cyu2CITy:22 Received: from [25.81.38.66] (S0106d4ca6d8943b0.gv.shawcable.net [70.66.132.207]) by spqr.komquats.com (Postfix) with ESMTPSA id EAF1818C; Fri, 15 Dec 2017 09:50:47 -0800 (PST) MIME-Version: 1.0 From: Cy Schubert Subject: RE: Objections to converting bsd-family-tree to a dot file Date: Fri, 15 Dec 2017 09:50:52 -0800 To: Lyndon Nerenberg , Eitan Adler CC: FreeBSD Hackers , "tech-misc@netbsd.org" , "Kernel@dragonflybsd.org" Message-Id: <20171215175047.EAF1818C@spqr.komquats.com> X-CMAE-Envelope: MS4wfD+MuHMqjRob9NRRpCPt6IxsjoX/GxgMr7v1JWnM7jwDlM7lASiqlcCHLuQPopgVZf4jv/OTG49Vmse3swWgHgnxUVOTdIDWAHcJGtgQ5gjBxbVoYe2I 2zzswXVFGsAtVBbHvyyuwus5RkTj4+Q6d3ziQsZ7/1GHf80jkWsP/Lb9yQd/c6vlYE8L/YwLfwQcVSfn2mgknzpNhKmqzT9xcv1T9ZFI2dBh4W0Vl+5etk1m M8MwweaZgcaiylso0ooL0EbOKKn+IS5l0cSJT0mkvcKBptOEvtAGxJSqjqRG03ag Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 17:50:54 -0000 Why is the family tree still in base? Shouldn't it be in doc? --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -----Original Message----- From: Lyndon Nerenberg Sent: 15/12/2017 09:35 To: Eitan Adler Cc: FreeBSD Hackers; tech-misc@netbsd.org; Kernel@dragonflybsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file > I'd like to turn this into into a dot file Sounds like a reasonable idea. With care, the source (text) file(s) can=20 often be formatted in a way that's at least semi-readable. I assume this=20 would ship with pregenerated images (PDF, SVG) so people don't have to=20 install the port to render the graph? --lyndon _______________________________________________ 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" From owner-freebsd-hackers@freebsd.org Fri Dec 15 17:21:31 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4850EE86E53 for ; Fri, 15 Dec 2017 17:21:31 +0000 (UTC) (envelope-from jlmuir@imca.aps.anl.gov) Received: from tuna.imca.aps.anl.gov (tuna.imca.aps.anl.gov [164.54.200.33]) (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 2DFB57DCD8 for ; Fri, 15 Dec 2017 17:21:30 +0000 (UTC) (envelope-from jlmuir@imca.aps.anl.gov) Received: by tuna.imca.aps.anl.gov (Postfix, from userid 502) id 00D392005D; Fri, 15 Dec 2017 11:11:35 -0600 (CST) Date: Fri, 15 Dec 2017 11:11:35 -0600 From: "J. Lewis Muir" To: John Nemeth Cc: Eitan Adler , FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Subject: Re: Objections to converting bsd-family-tree to a dot file Message-ID: <20171215171135.GA17739@tuna.imca.aps.anl.gov> References: <201712150625.vBF6PDcl029968@server.cornerstoneservice.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201712150625.vBF6PDcl029968@server.cornerstoneservice.ca> X-Mailman-Approved-At: Fri, 15 Dec 2017 18:52:52 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 17:21:31 -0000 On 12/14, John Nemeth wrote: > On Dec 14, 8:15pm, Eitan Adler wrote: > } I'd like to turn this into into a dot file > > How easy would it be to render something like the existing > bsd-family-tree, e.g. something that is reasonably intelligent when > viewed with more(1) or less(1) with the same basic information that > it has now? Also, would rendering it be something that can reasonably > be done while building the system, or would it need to be pre-rendered > and the result checked into the SCM (keep in mind that NetBSD's > build.sh is portable, i.e. you can build NetBSD on Windows if you > feel like it)? Maybe Graph-Easy could be used? I've never used it, but it claims to support generating graphs as ASCII art. Lewis From owner-freebsd-hackers@freebsd.org Sat Dec 16 18:26:34 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6072EE8A748 for ; Sat, 16 Dec 2017 18:26:34 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 27A616D9AB for ; Sat, 16 Dec 2017 18:26:34 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x22d.google.com with SMTP id g198so1863200yba.7 for ; Sat, 16 Dec 2017 10:26:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JLC6DiV5Ko2TzUoUlphQR8Rb6y9h7rdxL3sl4l95wBo=; b=rMQRqoGFnZz+cUKYUnWX3YV2Se0pKOhjsOSCt3PdVF/HY8axo/uMXkaIhcjM96Cvo6 HYXhI+Zx1LBzKcTPE26bIUMJwoK655gCKu4n0phCvtvb1IzOMYu2bINXWTKbYD9sdCE3 iOCBRj1qp4v1HDntL+h6085x2tP2gT9wwDEmE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JLC6DiV5Ko2TzUoUlphQR8Rb6y9h7rdxL3sl4l95wBo=; b=bxDBodKFdUNwWcg9qhg7DuKrP2SBXBwECIybCqhWS8gvzGSp0o1/M9pzxZblESJrto 2z11anC75P17RzwkvUZKOa+6ZdOeKf2laoBNPIcTfqz5QdCOyULTmxRG+pQ6kyxxBs00 FM87qKxyMTNea3um8DPKhEWgJ6NiU+B88S9j4J5HCYsi1e9nmzgtqVvXaGc89yQ3jTGC v+ahNc8xLMvhbgPvTUbWMny+M6ABNjb+t2kossrGV6CBiBIhd/SJBoTcjTUTsbVpVUX2 uAyV7oDNlNRMdG62pWSPwQ7jIpkRdcYSGUeupDReZ6oyM+8shqfvrmP/8YIqscZZkQIM h6eg== X-Gm-Message-State: AKGB3mJUb0F/0QBDsHrbNGznQFxWi4+bcXRbYxXNHD65yQ0eT+veibIv bFr+nt3GIsKabrq2kLtL1R018YXfOcdwWJDfcJ9TrQ== X-Google-Smtp-Source: ACJfBosCmMMSiRvQ0yjfiKDqU7B3qu21RoWQFdziJeuMWe13iWAoP0vy9OzTEO1XAH6AEKM0H9xi/iGsTPQGyxsV1hA= X-Received: by 10.129.82.212 with SMTP id g203mr10224774ywb.207.1513448792631; Sat, 16 Dec 2017 10:26:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.15.66 with HTTP; Sat, 16 Dec 2017 10:26:02 -0800 (PST) In-Reply-To: References: From: Eitan Adler Date: Sat, 16 Dec 2017 10:26:02 -0800 Message-ID: Subject: Re: Objections to converting bsd-family-tree to a dot file To: Lyndon Nerenberg Cc: FreeBSD Hackers , Kernel@dragonflybsd.org, tech-misc@netbsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 18:26:34 -0000 On 15 December 2017 at 08:43, Lyndon Nerenberg wrote: >> I'd like to turn this into into a dot file > Sounds like a reasonable idea. With care, the source (text) file(s) can > often be formatted in a way that's at least semi-readable. I assume this > would ship with pregenerated images (PDF, SVG) so people don't have to > install the port to render the graph? The overall consensus seems to be: so long as there is a reasonable way to view this file in plaintext without requiring a tool in base, its fine. I'll likely run with that after ironing out the conversion bit. -- Eitan Adler From owner-freebsd-hackers@freebsd.org Sat Dec 16 19:47:58 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7A9BE8CA67 for ; Sat, 16 Dec 2017 19:47:58 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-96.reflexion.net [208.70.210.96]) (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 7422470132 for ; Sat, 16 Dec 2017 19:47:57 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 22626 invoked from network); 16 Dec 2017 18:47:51 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 16 Dec 2017 18:47:51 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 16 Dec 2017 13:47:51 -0500 (EST) Received: (qmail 22848 invoked from network); 16 Dec 2017 18:47:51 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 16 Dec 2017 18:47:51 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id C2D4CEC7848; Sat, 16 Dec 2017 10:47:50 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: faq/troubleshoot.html#indefinite-wait-buffer has the direction of transfer wrong (head -r326888 /usr/src/) Message-Id: Date: Sat, 16 Dec 2017 10:47:50 -0800 To: FreeBSD Hackers , FreeBSD Current X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 19:47:58 -0000 I got a "swap_pager: indefinite wait buffer" notice and looked it up. (This was on a rpi2 booted (kernel and world) from a USB SSD, swap partition in use instead of a swap file. It was building devel/cmake via poudriere-devel .) https://www.freebsd.org/doc/faq/troubleshoot.html#indefinite-wait-buffer reads like it is for page-out to disk: QUOTE 5.9. What does the error swap_pager: indefinite wait buffer: mean? This means that a process is trying to page memory to disk, and the page = attempt has hung trying to access the disk for more than 20 seconds. It = might be caused by bad blocks on the disk drive, disk wiring, cables, or = any other disk I/O-related hardware. If the drive itself is bad, disk = errors will appear in /var/log/messages and in the output of dmesg. = Otherwise, check the cables and connections. ENDQUOTE But the code containing the message is for "swread": (head -r326888) # grep -r "indefinite wait buffer" /usr/src/sys/ | more /usr/src/sys/vm/swap_pager.c:"swap_pager: indefinite wait buffer: = bufobj: %p, blkno: %jd, size: %ld\n", Looking there. . . static int swap_pager_getpages(vm_object_t object, vm_page_t *m, int count, int = *rbehind, int *rahead) { . . . VM_OBJECT_WLOCK(object); while ((m[0]->oflags & VPO_SWAPINPROG) !=3D 0) { m[0]->oflags |=3D VPO_SWAPSLEEP; VM_CNT_INC(v_intrans); if (VM_OBJECT_SLEEP(object, &object->paging_in_progress, = PSWP, "swread", hz * 20)) { printf( "swap_pager: indefinite wait buffer: bufobj: %p, blkno: %jd, size: = %ld\n", bp->b_bufobj, (intmax_t)bp->b_blkno, = bp->b_bcount); } } . . . =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-hackers@freebsd.org Sat Dec 16 19:49:58 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87C89E8CC9B for ; Sat, 16 Dec 2017 19:49:58 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 67AC5703A1 for ; Sat, 16 Dec 2017 19:49:57 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id vBGJnqeg008333; Sat, 16 Dec 2017 11:49:52 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id vBGJnnMR008332; Sat, 16 Dec 2017 11:49:49 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201712161949.vBGJnnMR008332@pdx.rh.CN85.dnsmgr.net> Subject: Re: Objections to converting bsd-family-tree to a dot file In-Reply-To: To: Eitan Adler Date: Sat, 16 Dec 2017 11:49:49 -0800 (PST) CC: Lyndon Nerenberg , FreeBSD Hackers , tech-misc@netbsd.org, Kernel@dragonflybsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Sat, 16 Dec 2017 20:22:39 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 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 Dec 2017 19:49:58 -0000 > On 15 December 2017 at 08:43, Lyndon Nerenberg wrote: > >> I'd like to turn this into into a dot file > > Sounds like a reasonable idea. With care, the source (text) file(s) can > > often be formatted in a way that's at least semi-readable. I assume this > > would ship with pregenerated images (PDF, SVG) so people don't have to > > install the port to render the graph? > > > The overall consensus seems to be: so long as there is a reasonable > way to view this file in plaintext without requiring a tool in base, > its fine. I'll likely run with that after ironing out the conversion > bit. I have seen no presentation of a reasonable way to view the graph in plain text. Nor do I find the output you presented as a sample very usable due to scaling issues, one of the graphs was massively wide, the other was ok but at such a scale had to be zoomed significantly to read. Though they are "pretty" I find them cumbersumb to use. And that means they wont be used. -- Rod Grimes rgrimes@freebsd.org