From owner-freebsd-current@freebsd.org Mon Feb 12 04:50:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EA1FF16AE8 for ; Mon, 12 Feb 2018 04:50:45 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2297F7D9DE for ; Mon, 12 Feb 2018 04:50:45 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x234.google.com with SMTP id w1so2328742qti.4 for ; Sun, 11 Feb 2018 20:50:45 -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=SF0rr9ir23sBA6gZAfcBQ4sBxiCQxPXwIfsQE6ND++U=; b=tB0Mpo1yglCgSWLosggojuQ+foh7pLQgA/pVGqY9lZnwLRk/7O5WQ80P/EIKTJonl7 RmPe3uQLKqeb1f3ryBnoNW4+jHdRptvOarR2kecOUp9clnRzUnw4uM9AXFBK+OeFXey7 I7tZIvjcaBU5gxFIbTxK+GHBD/6N65/FmzQ/jLqrANNLw+f09EBhMVMisfwVQpiFx+1x +F8h1uU+E18uOPdu0BG7FpuJdJlvmGbXBUGvJM2EiaQ15SJaV11It/wc0s8CWV6wpQAN ZtbqJTCjyeYXH/QnlHK0AEKnqB1/peZiStSmO9xDOVGbPjGkiYqmwvc36b2U8Skg9P0x GW7A== 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=SF0rr9ir23sBA6gZAfcBQ4sBxiCQxPXwIfsQE6ND++U=; b=gd08KZJEroW7IST4EgT41zE9Joc0THFW7jdt2pUQ9GQSOKpQj9guBCjkARzT7e0NBD 5mDvNeVY1cNGICwS2t2eF6PHRE4sJUR2a/dJbiZNG2FTPwGP08+3EJQi4fLbEJCPXXwb Ih0nb7Ix0lcvNwmsxMiNIoBCj2kEAzRiKAPt4iid0+qthHSTFsjWDgT32oT0LmadMhrz vzineW5RJacf52DBl4vdceE5AB26YNX7asmK4DH9jOVRe/VfnWJSH3+pRJLs570MVkPg 8tklIQ6LaaCqKxQw1GvsPr0WmqtMa94hxmwLPFgjLrNE8VhNUHZfH1dGrI96hol/t/Z+ 7ZEA== X-Gm-Message-State: APf1xPANpRLeaxkyxVJbdj0pxhMWuHms0INJb3li7yF0Eg6w2A0N7iPc epzteRIWMQg/gZ3OttvmmbUpjiadIW5VfUwQt+W2Cg== X-Google-Smtp-Source: AH8x224dFjdeHbnKlbLVzEGwxJFRBZe380SDmJKG8CwePnlwUeoMALU/xRci5Hdp3z0+JJJJlFm+tHikvK0G2Zpo430= X-Received: by 10.237.42.87 with SMTP id k23mr13897919qtf.24.1518411044372; Sun, 11 Feb 2018 20:50:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.50.228 with HTTP; Sun, 11 Feb 2018 20:50:43 -0800 (PST) From: Ryan Stone Date: Sun, 11 Feb 2018 23:50:43 -0500 Message-ID: Subject: Panic in prison_alloc() on boot To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 04:50:45 -0000 I'm getting a persistent panic on boot in prison_allow(). The first case that I hit is this: Fatal trap 12: page fault while in kernel mode cpuid = 10; apic id = 22 fault virtual address = 0x30 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80ab9674 stack pointer = 0x28:0xfffffe00f8bb16f0 frame pointer = 0x28:0xfffffe00f8bb16f0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 90 (mount_nullfs) [ thread pid 90 tid 100913 ] Stopped at prison_allow+0x4: movq ll+0xf(%rdi),%rax db> bt Tracing pid 90 tid 100913 td 0xfffff801a5aab000 prison_allow() at prison_allow+0x4/frame 0xfffffe00f8bb16f0 nullfs_mount() at nullfs_mount+0x31/frame 0xfffffe00f8bb1830 vfs_donmount() at vfs_donmount+0x1415/frame 0xfffffe00f8bb1a80 sys_nmount() at sys_nmount+0x72/frame 0xfffffe00f8bb1ac0 amd64_syscall() at amd64_syscall+0xa48/frame 0xfffffe00f8bb1bf0 fast_syscall_common() at fast_syscall_common+0x101/frame 0x7fffffffecb0 However if I comment out my nullfs mounts in /etc/fstab, I just get a panic in prison_allow() called from elsewhere. I've seen this panic with r328936 (Feb 6), r329091 (Feb 9) and r329142 (Feb 11) From owner-freebsd-current@freebsd.org Mon Feb 12 08:29:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15F1BF02004; Mon, 12 Feb 2018 08:29:11 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7B49F8663E; Mon, 12 Feb 2018 08:29:09 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MCcE2-1euXQ602Gw-009RRe; Mon, 12 Feb 2018 09:29:08 +0100 Date: Mon, 12 Feb 2018 09:29:01 +0100 From: "O. Hartmann" To: freebsd-jail@freebsd.org, freebsd-current Cc: Olivier =?ISO-8859-1?Q?Cochard-Labb=E9?= , "O. Hartmann" Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <20180212092901.671488e6@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:xeiWk3e6P1ysv2nemTrqbfFuU5y+BVkJ7RPywnMfoMo4e7LOTsi /UmEZ4PP8MKzY/+Mm+I/v3HM7mMEK6f3KSn1F1goLu2qnEeag/h1LBpwBMu2+BbVFPM4KiE 6F+eVajLraBMTGaAAgBGkPBmZ6h8ui0sYmcbgbBlFrg8xIAXPS/lmaujQFWQIxxb8EI2Chp VXXPvYaN1OZfgOL1WNycw== X-UI-Out-Filterresults: notjunk:1;V01:K0:ZiupmWK6Xbo=:lVrXy8dwYRblhadOqr4+Dv +9p94GKozoxUPshvC0HXz2ZMxcN6gqECvRDbwNaYa4mQ8ohJpGf+cj6SgzZfb2tbZw13/9wZQ CBzcGuM633hfX90crPMTTMvkI3DD1cIUXvD+LLpXN+PsimbGgWKveioUDIB4tkhqlRQLRXeto wFfVI6Qv57q7IEB6dn1BnAXxQiFazkwrkS0P73K5mHPNppf3+ZbfM402MuSdUv2nr7moHU+BJ hUaUAixRmlXnPncg9VC2BsX+lYNwdiAd19XLPlnL8y09eGJDRb/TQKzqAqpCymcNuhEA0/qSI HUdpIz/n6c5uDUG3yMBMSirF5rzxUIG36NH3hRq7O3x5YLVTu/pLk8VrC/UEzE7odyxbBaawn UFN5V0w6TTxPOnWUyQ0f2xhVz0n/BcwjFsZ7AQTRRjv9RzvMVEGk0C8SmK5uOkjTflimIswfN WzJlG+GV/HXNkTOwBssY9R/8mgSeRMfBGTAh21wnldn7dQhiB3dW2DLI2GvXoxvrl1GibsoWd M0tAUXbNeDHty+iMaOAKIabBE6KxaFodj+j0Mo8pdAlPCt56ySciK21jGdD5f3drW1ymAwrBr 40zaX5T4dAB2uLZ2kTRtOmvJSqF7w2uW26eOMTQkygCSsM10KIKmNzuI9YcRGeMnU6NDBvrF7 LI64nWEehIEqDJ51sPGmLqxdD3cZdMp7OzzGws4sKW+WfcmXAgAYnb3diUr/buA+Hi8zW/372 D2+FIr79ar1M2rqnIgvvwtQLFtOGoHmjk2KoWTQFcv3EFKA9EcNBmkuUJFFqnn1GS+pb2S6FU /IyX9WUXO1VC47yCKxjKiGG3+uHjLrHMyfuaJO+TxssGSDDlpU= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 08:29:11 -0000 On Sat, 10 Feb 2018 11:52:18 +0100 Olivier Cochard-Labb=C3=A9 wrote: > On Sat, Feb 10, 2018 at 8:52 AM, O. Hartmann wro= te: >=20 > > > > The moment any of the bridges gets an additional member epair interface > > (so the bridge > > has at least three members including the on reaching into the virtual > > router jail) the > > vbridge seems to operate unpredictable (to me). Pinging jails memeber of > > that vbridge > > are unreachable. > > > > =20 > =E2=80=8BFirst idea: > Did you try with a more simple setup, like with just 3 jails members of o= ne > bridge ? > =3D> I've tried it on a -head, and all 4 members (3 jails and the host) = =20 > reach to communicate. Yes, I did. I used to setup one bridge (bridge0) and three jails. Each jail owns its epairXXa device with IP assigned. epairXXb of each jail is member of the bridge. Bridge is up, epairXXb is up. >=20 > Second idea: > Can you check that all epairs have different MAC address each ?=E2=80=8B > I hit this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176671 Very good shot! Thanks. No, they do not have all of them unique MAC adrress= es and in some occassions members of the very same bridge have the very same M= AC addresses, mostly the a-part of the epair: =46rom console: [...] ng_ether_ifnet_arrival_event: can't re-name node epair10250a =3D=3D>> epair20128a: Ethernet address: 02:ce:d0:00:07:0a epair20128b: Ethernet address: 02:ce:d0:00:13:0b epair20128a: link state changed to UP epair20128b: link state changed to UP epair20128b: promiscuous mode enabled ng_ether_ifnet_arrival_event: can't re-name node epair20128a =3D=3D>> epair20129a: Ethernet address: 02:ce:d0:00:07:0a epair20129b: Ethernet address: 02:ce:d0:00:14:0b epair20129a: link state changed to UP epair20129b: link state changed to UP epair20129b: promiscuous mode enabled ng_ether_ifnet_arrival_event: can't re-name node epair20129a epair20XXX are member of bridge2 and dedicated epairs of jails. The following is the desastrous picture of bridge1: [...] =3D=3D>> epair235a: Ethernet address: 02:ce:d0:00:07:0a epair235b: Ethernet address: 02:ce:d0:00:0d:0b epair235a: link state changed to UP epair235b: link state changed to UP epair235b: promiscuous mode enabled ng_ether_ifnet_arrival_event: can't re-name node epair235a =3D=3D>> epair237a: Ethernet address: 02:ce:d0:00:07:0a epair237b: Ethernet address: 02:ce:d0:00:0e:0b epair237a: link state changed to UP epair237b: link state changed to UP epair237b: promiscuous mode enabled ng_ether_ifnet_arrival_event: can't re-name node epair237a =3D=3D>> epair251a: Ethernet address: 02:ce:d0:00:07:0a epair251b: Ethernet address: 02:ce:d0:00:0f:0b epair251a: link state changed to UP epair251b: link state changed to UP epair251b: promiscuous mode enabled ng_ether_ifnet_arrival_event: can't re-name node epair251a =3D=3D>> epair238a: Ethernet address: 02:ce:d0:00:07:0a epair238b: Ethernet address: 02:ce:d0:00:10:0b epair238a: link state changed to UP epair238b: link state changed to UP epair238b: promiscuous mode enabled ng_ether_ifnet_arrival_event: can't re-name node epair238a [...] This is on CURRENT (FreeBSD 12.0-CURRENT #36 r329150: Mon Feb 12 06:30:47 C= ET 2018 amd64). I did check on Friday in the bureau and didn't catch it since I was checkin= g on each jail, but the console log accessed via dmesg revealed the problem very easily. I did a check on the 11.1-RELENG-p6 box and I got the same picture there, different, but very similar setup.=20 So I didn't see it in the masses of epairs our setup requires :-( I'll go now for setting MAC addresses manually and check functionality agai= n. >=20 > Regards, >=20 > Olivier Kind regards, Oliver From owner-freebsd-current@freebsd.org Mon Feb 12 08:43:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20216F03275; Mon, 12 Feb 2018 08:43:01 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7AC4D872E3; Mon, 12 Feb 2018 08:43:00 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MV30j-1fIwHx0WGT-00YRAT; Mon, 12 Feb 2018 09:37:48 +0100 Date: Mon, 12 Feb 2018 09:37:47 +0100 From: "O. Hartmann" To: Olivier =?ISO-8859-1?Q?Cochard-Labb=E9?= Cc: "O. Hartmann" , freebsd-jail@freebsd.org, freebsd-current Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <20180212093747.20024e5f@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:J4ZmmFcj0ZX5QXQJkpi7TzdFxvRbabQZ1FysksWkVhUYmlRgp6O zrx4I368uHPPzsha0adbaxqMvtzgD9uulwqZ91sbypYSTabJxkW9nuIeXjsxuz1d7/3Tkad Jei4HvJ2lN+WfeNKAjyf0pLissyNncVkUsEmhcMMQ61/mYM8la8oQh6OR2WA6u3kMZy/c5z 1ERXfSnxqRbNRzQY+Co4Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:LtV6hFVb1Ek=:KGhazDgW8ZHrCpQtsvw7Gi V46jdJSTKS8FkGfeEPmfuyovX6koCCth7XagGf/a4AR8FvARvISmxIGDOSSsPRnOMj5SkwJhi cbs316mVFT9YIy4dx99ApcG/RN2L79aYetTPO4fJXKWXRytdd0S3p6eoUVIGfZjI/5tscAz+P b3nfGJcI3KFHK9pQMXEpgwTbv5U4ReWAMYQSUay53aY8d+/h5QaPzljcdcd+5dJ33EJWsQtF2 oODJQeTO1WvzzOUXm1X10tkeMsISUEM/sqzC8rvPDVQXSb3ZXZwURSOD5dP3eactUaC4V50bF wVhDcII5DLfpiAIWRDu6uGBWkiWQqmvLNaPoIv1xpFYv1P4cQNApZl3PyBgEloOXr1/yxbZrf 1uGjEZHvhPnWAuyC1jZcpa1xv6lzFzRjH4ma+wQkUypKTHexEJSLOBlEFv5LOA/Ll3uzRDLN3 lXqAvYKcmpSTXWv+UHK3WGLD0uvq8fW+vzi97Fn76chv1ZdgMDiUGdZM1x0zI4BYip+///+3l 9PR3Xl660QSMt11af0zFJK57vGIxHbO6JK5VyMSmIFr55KplNVVJ1xjjf9hE5CnTEIqNCjEgw 8z1DTvZuCFh4T1LyiL3Lk9oAIIKg9MkdLeE72xNoxhoz7hNNfo2G+8gGihCPsxrEQOcj/Ct5s w4w+8Pa6a9Gg3HwypfbEXumfVLgXOArxtwMSYXe3tDS0f9IeZK8aXEaMyIW8afxzm9l+FqYFg OJGfMRrbuQsXejUnMJlcfUvP4TJ8EJKwuKXniCbqAT9czoun9YWzC5dFIjHTLy/TAodX5H1bL mgfMMaiYnKDcM3424W+IeYDZbnDCTIpINcaZRiOhfq2u82QYgg= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 08:43:01 -0000 On Sat, 10 Feb 2018 11:52:18 +0100 Olivier Cochard-Labb=C3=A9 wrote: > On Sat, Feb 10, 2018 at 8:52 AM, O. Hartmann wro= te: >=20 > > > > The moment any of the bridges gets an additional member epair interface > > (so the bridge > > has at least three members including the on reaching into the virtual > > router jail) the > > vbridge seems to operate unpredictable (to me). Pinging jails memeber of > > that vbridge > > are unreachable. > > > > =20 > =E2=80=8BFirst idea: > Did you try with a more simple setup, like with just 3 jails members of o= ne > bridge ? > =3D> I've tried it on a -head, and all 4 members (3 jails and the host) = =20 > reach to communicate. >=20 > Second idea: > Can you check that all epairs have different MAC address each ?=E2=80=8B > I hit this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176671 Wow, that PR is from 2013(!) and it is still not solved? >=20 > Regards, >=20 > Olivier > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Mon Feb 12 08:59:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D7D9F0457D for ; Mon, 12 Feb 2018 08:59:08 +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 7282D87D11 for ; Mon, 12 Feb 2018 08:59:07 +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 w1C8wqPe047235 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 12 Feb 2018 10:58:55 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w1C8wqPe047235 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w1C8wqpc047234; Mon, 12 Feb 2018 10:58:52 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 12 Feb 2018 10:58:52 +0200 From: Konstantin Belousov To: Ryan Stone Cc: FreeBSD Current Subject: Re: Panic in prison_alloc() on boot Message-ID: <20180212085852.GA94212@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) 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-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 08:59:08 -0000 On Sun, Feb 11, 2018 at 11:50:43PM -0500, Ryan Stone wrote: > I'm getting a persistent panic on boot in prison_allow(). The first > case that I hit is this: > > Fatal trap 12: page fault while in kernel mode > cpuid = 10; apic id = 22 > fault virtual address = 0x30 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80ab9674 > stack pointer = 0x28:0xfffffe00f8bb16f0 > frame pointer = 0x28:0xfffffe00f8bb16f0 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 90 (mount_nullfs) > [ thread pid 90 tid 100913 ] > Stopped at prison_allow+0x4: movq ll+0xf(%rdi),%rax > db> bt > Tracing pid 90 tid 100913 td 0xfffff801a5aab000 > prison_allow() at prison_allow+0x4/frame 0xfffffe00f8bb16f0 Can you get the core dump and look at the arguments ? It is most likely cred->cr_prison which is NULL. > nullfs_mount() at nullfs_mount+0x31/frame 0xfffffe00f8bb1830 > vfs_donmount() at vfs_donmount+0x1415/frame 0xfffffe00f8bb1a80 > sys_nmount() at sys_nmount+0x72/frame 0xfffffe00f8bb1ac0 > amd64_syscall() at amd64_syscall+0xa48/frame 0xfffffe00f8bb1bf0 > fast_syscall_common() at fast_syscall_common+0x101/frame 0x7fffffffecb0 > > However if I comment out my nullfs mounts in /etc/fstab, I just get a > panic in prison_allow() called from elsewhere. > > I've seen this panic with r328936 (Feb 6), r329091 (Feb 9) and r329142 (Feb 11) > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Mon Feb 12 11:06:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E0E7F0F06B; Mon, 12 Feb 2018 11:06:54 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AEE46E1D4; Mon, 12 Feb 2018 11:06:53 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LgptO-1eQvZ52KQg-00oG2L; Mon, 12 Feb 2018 12:06:45 +0100 Date: Mon, 12 Feb 2018 12:06:39 +0100 From: "O. Hartmann" To: freebsd-jail@freebsd.org, freebsd-current Cc: "O. Hartmann" , Olivier =?ISO-8859-1?Q?Cochard?= =?ISO-8859-1?Q?-Labb=E9?= Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <20180212120639.7931f609@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20180212093747.20024e5f@freyja.zeit4.iv.bundesimmobilien.de> References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> <20180212093747.20024e5f@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:22WH3ZncUiXy9S5kWV1v51sv7V+50pBCZke/JciCicLz9S9gyAO uLexVLwD0Gq7+GOX0jXs/Z1y/FHAkrbtlkx5Kc0PsL0MgCiXkzgFyNhNbP1/aX2vkKZSxh2 yrEUbk3xb6/bkJeHSoTrJ/iFftAjKZOHsIY0xD2fiAj9qzEQnKji2Mjt35rdcz5ZL51tiWO QCfeADEBExffj3NYYgrSg== X-UI-Out-Filterresults: notjunk:1;V01:K0:Kwjy5f30NRA=:8FZUJATBQYjiq0/CblSDU8 0MsgUT+Yh5XaPdTjaYsyAOvIsBO05w2+eMpuMgdKJZLACZ1nWzY7Fzy+W0TyffJehOKkgKhCh Ebd2witOnGXRWhzeSn3YIN7uPgZcBuz42TmefxuwVkT445gX+fICAiNjSCnRBOJxNKnOZiavP kBwRZ7BhZ0xl95Em4HBNQ8NWoU1jd0L0CxHmif/VcDUnDLMHohfvzx7lmBIbQz1b91wQusmPI XN8BlwJL9dlKS6lZfmrGTLvfYaQb6FhUsfhtbAvsbnFEBekMgGhLyD18PjtsbOPUWussgjXHT lDs6SgfE0mv9+MhGN3KwIaaHykpZZWgWyNJGij/71bJzY+TFRA3cEnxHtJl4qbnTRogFpmkzx cwxsFdnnG+cHbAhdoadb41uKYCsjSugGijj7TOkdlWd8BqcSF5ZVJ8bO4tEcNsPvrGcg+fpnO GE9zdO8iCnr5yKoZMlLkG9JXmy16kTASeEHW+hi6MVPFNTeoubR0VhAdqcqmDKNKUu+wgDsEG /Iu15JVtw1jJdB+gYFd7QHX3Cgu6ZU4oOPv9Vk2jdNM+wj+yGtKJz+LGhN78bEvK7jjNmXWoH dXFM2hQ8uXXNCmP8ZT8UnCkMzBGlk77GV9bzVh/ilH0mxrT2X1KMY52LSGAC4frJTv1w1SJ7T SLchy8b7nICtYK0LFe89sqQQlXBdzz3+RvXARrU+QcEAPip8EtHGJJWOkMC+3QxoI/aG+aJuu Y4zdGAEm/Guu5u6bpIQAbsEQ6Qz4rnc2dXc2gwGQkz0Lr39+nVQuNkOu6yaLXfgFeOjglzEgt wk5sqjpRblTyeKgQeO/+I6sd3Q/yN3tsVJymhODflO9+mR0Osg= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 11:06:54 -0000 On Mon, 12 Feb 2018 09:37:47 +0100 "O. Hartmann" wrote: > On Sat, 10 Feb 2018 11:52:18 +0100 > Olivier Cochard-Labb=C3=A9 wrote: >=20 > > On Sat, Feb 10, 2018 at 8:52 AM, O. Hartmann w= rote: > > =20 > > > > > > The moment any of the bridges gets an additional member epair interfa= ce > > > (so the bridge > > > has at least three members including the on reaching into the virtual > > > router jail) the > > > vbridge seems to operate unpredictable (to me). Pinging jails memeber= of > > > that vbridge > > > are unreachable. > > > > > > =20 > > =E2=80=8BFirst idea: > > Did you try with a more simple setup, like with just 3 jails members of= one > > bridge ? =20 > > =3D> I've tried it on a -head, and all 4 members (3 jails and the host= ) =20 > > reach to communicate. > >=20 > > Second idea: > > Can you check that all epairs have different MAC address each ?=E2=80=8B > > I hit this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176= 671 =20 >=20 > Wow, that PR is from 2013(!) and it is still not solved? >=20 > >=20 > > Regards, > >=20 > > Olivier > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" =20 >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" After rebooting recent CURRENT, the view with "ifconfig -a ether" looked go= od so far, each epair/bridge has its unique MAC. But then, login on the jails and checking the epair's counterpart owned by = the VIMAGE jail, I found almost EVERY jail has the same MAC, even those jails members of the same bridge: [...] jail 11 on bridge2 epair20129a: flags=3D8843 metric 0 = mtu 1500 options=3D8 ether 02:68:d0:00:07:0a jail 10 on bridge2 epair20128a: flags=3D8843 metric 0 = mtu 1500 options=3D8 ether 02:68:d0:00:07:0a jail 9 on bridge 1 epair10250a: flags=3D8843 metric 0 = mtu 1500 options=3D8 ether 02:68:d0:00:07:0a jail 8 on bridge1 epair10238a: flags=3D8843 metric 0 = mtu 1500 options=3D8 ether 02:68:d0:00:07:0a jail 7 on bridge0 epair238a: flags=3D8843 metric 0 mt= u 1500 options=3D8 ether 02:68:d0:00:07:0a epair251a: flags=3D8843 metric 0 mt= u 1500 options=3D8 ether 02:68:d0:00:07:0a The way I create epairs and put them into a jail's context/domain is straig= ht forward. In jail.conf, I have more generic setup with variables like: # DNS Master ns1 { $if =3D "2"; $ip4_addr =3D "10.10.0.${if}"; $ip4_cidr =3D "24"; $ip4_my_default_route =3D "10.10.0.1"; $vnet_if =3D "epair${if}"; $home_bridge =3D "${if_bridge_core}"; depend=3D "vrouter"; allow.raw_sockets=3D "1"; } and in the common portion of jail.conf definitions, I use this: [...] vnet =3D "new"; vnet.interface =3D "${vnet_if}a"; persist; exec.clean; exec.start=3D ""; exec.start+=3D "/sbin/ifconfig ${vnet_if}a inet ${ip4_addr}/${ip4_cidr} up"; exec.start+=3D "/bin/sh /etc/rc"; exec.start+=3D "/sbin/route add default ${ip4_my_default_route}"; exec.start+=3D "/sbin/sysctl net.link.bridge.pfil_member=3D0"; exec.start+=3D "/sbin/sysctl net.link.bridge.pfil_bridge=3D0"; exec.start+=3D "/sbin/sysctl net.link.bridge.pfil_onlyip=3D0"; exec.stop=3D "/bin/sh /etc/rc.shutdown"; exec.prestart=3D ""; exec.prestart+=3D "ifconfig ${vnet_if} create"; exec.prestart+=3D "ifconfig ${vnet_if}b up"; exec.prestart+=3D "ifconfig ${home_bridge} addm ${vnet_if}b up"; exec.poststop=3D "ifconfig ${home_bridge} deletem ${vnet_if}b"; exec.poststop+=3D "ifconfig ${vnet_if}b destroy"; exec.consolelog=3D "/var/log/jail_${name}_console.log"; The big question here is: when a jail with VIMAGE kernel "swallows" a epair-pseudo device, it leaves the ciontext or visibility of the host. How = can the FreeBSD VIMAGE kernel then know about what former epair's MAC was? Is t= his mechanism maybe the culprit? It is just a thought, so I do not want to be beheaded - I'm not much into system development. Kind regards, O. Hartmann From owner-freebsd-current@freebsd.org Mon Feb 12 14:54:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE27CF210FA for ; Mon, 12 Feb 2018 14:54:34 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::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 3919B783A0; Mon, 12 Feb 2018 14:54:34 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id 37so1925713lfs.7; Mon, 12 Feb 2018 06:54:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=huQvqAxam4YpaRMsOwK1TMq0Qp2MTpJ4CBa+V4nd28w=; b=dSoak4wQTbWOFF4x9udN0QgIMk8PBytWm3N7kpwZSyuXlaFtoHbBpS/Aqk9zfqgiu1 qDtrCMBQMDyo+9fqt9AwX67JO86mhdJa8W2UqF6sm+fJpQCnUHgFCJY8EDBGA4I65nQQ aCgLa6WLc5Phy2IVYCMdWeGmlrKH5GHSypkC6nEkXUbucafpIHSqZ1F/tVuqCEAmmQhL zqimPkyXmqbMPtl0fUQ9ll4SOktUvv8OYxN4iEpT/HO0qqZmsbvD9hHFbLogPH8ErWF/ DS+ca5K8TNsYVc2Y+ZwqPx9sqq2UsgWYHuI2T6jMtmO0zKIEJvANu9tqWfP9Yr4Y4wyl zEwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=huQvqAxam4YpaRMsOwK1TMq0Qp2MTpJ4CBa+V4nd28w=; b=HzrTQdgiENPgjhMJxZq3RmNPu3JMrhJOfUekeQ/TUHU65aPGqo93lx0IynPDccIAYa jOQ9DZEBP0a15cHVGdg7W4GUTZDgaDi84qtMowi23hfcSXgfNFUVWTxLM7dFnvfrMGNd fMnpC/UsEphf4AD8UWsO6xF8h5lbI91KjEll0l2ILo4QCSdT40wgMuOcZyP+d7Ys2r15 smoCsGqW0KVY+B71/ipA1cZVzY/CW1SVM+KaC+sDDm7S03tqQ1HaKEkQ9hlioO4JSbox C1KRCsCpDpASa+J54MDRo2nTGV1YMoLpUgZTF8p5bCyeLTGcPhuBr4zDxIdfNa0Z73ea fKbQ== X-Gm-Message-State: APf1xPAcIbv6LAA3Qev89wIHXqiS2hIJG8U+ds4nLtbq7RBtyAYSNMq3 LSArtZxaFC6fIHf6bAa6kpmI7fhg X-Google-Smtp-Source: AH8x227CszjanPntMbT29fGTwCeRqT69m80Q8mCDiTiLCVW6I6zh1DIR9nOzKne+pCfoBo/wjvCYnQ== X-Received: by 10.46.82.26 with SMTP id g26mr2810371ljb.67.1518447272376; Mon, 12 Feb 2018 06:54:32 -0800 (PST) Received: from localhost ([81.19.73.153]) by smtp.gmail.com with ESMTPSA id h78sm1731000lfk.31.2018.02.12.06.54.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Feb 2018 06:54:31 -0800 (PST) Date: Mon, 12 Feb 2018 17:54:30 +0300 From: Vladimir Zakharov To: Bryan Drewery Cc: freebsd-current@freebsd.org Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive Message-ID: <20180212145430.r5ygphq3yskm7gxi@vzakharov> References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> X-Operating-System: FreeBSD 12.0-CURRENT amd64 X-PGP-Key: http://vzakharov.ru/pubkey.asc User-Agent: NeoMutt/20171215 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 14:54:35 -0000 Hello, Bryan! On Fri, Feb 09, 2018, Bryan Drewery wrote: > On 2/1/2018 1:10 AM, Vladimir Zakharov wrote: > > Hello! > > > > For some time (about a week) building and installing kernel fails with > > the error "Variable OBJTOP is recursive." when going to build/install > > module from ports. > > > > Last successful build was at r328426. Next build at r328527 failed and > > still broken at r328649. > > > > Without PORTS_MODULES building and installing kernel succeeds. Another > > workaround: ignore error and build/install module directly from ports. > > > > # cat /etc/make.conf > > MALLOC_PRODUCTION=yes > > KERNCONF=GENERIC-NODEBUG GENERIC > > #KERNCONF= GENERIC-NODEBUG > > CPUTYPE?=native > > #PORTS_MODULES = graphics/drm-next-kmod emulators/virtualbox-ose-kmod > > PORTS_MODULES = graphics/drm-next-kmod > > > > DOC_LANG = en_US.ISO8859-1 ru_RU.KOI8-R > > > > WITH_DEBUG_PORTS = mail/neomutt > > > > WITH_CCACHE_BUILD=yes > > CCACHE_DIR=/home/ccache > > > > #DEVELOPER=yes > > > > ... > > Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.full > > --- kernel.full --- > > linking kernel.full > > ctfmerge -L VERSION -g -o kernel.full ... > > text data bss dec hex filename > > 22584632 1376209 4748888 28709729 0x1b61361 kernel.full > > Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.debug > > Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel > > --- all --- > > ===> Ports module graphics/drm-next-kmod (all) > > cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env -u CC -u CXX > > -u CPP -u MAKESYSPATH MAKEFLAGS="-j 4 -J 15,16 -j 4 -J 15,16 -D > > NO_MODULES_OBJ .MAKE.LEVEL.ENV=MAKELEVEL KERNEL=kernel TARGET=amd64 > > TARGET_ARCH=amd64" SYSDIR=/usr/src/sys > > PATH= > > SRC_BASE=/usr/src OSVERSION=1200056 > > WRKDIRPREFIX=/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B > > clean build > > ===> Cleaning for drm-next-kmod-g20180117 > > ===> License BSD2CLAUSE MIT GPLv2 accepted by the user > > ===> drm-next-kmod-g20180117 depends on file: /usr/local/sbin/pkg - found > > ===> Fetching all distfiles required by drm-next-kmod-g20180117 for building > > ===> Extracting for drm-next-kmod-g20180117 > > => SHA256 Checksum OK for FreeBSDDesktop-kms-drm-g20180117-622fdd1_GH0.tar.gz. > > ===> Patching for drm-next-kmod-g20180117 > > ===> drm-next-kmod-g20180117 depends on file: /usr/local/bin/ccache - found > > ===> Configuring for drm-next-kmod-g20180117 > > ===> Building for drm-next-kmod-g20180117 > > ===> drm (all) > > Variable OBJTOP is recursive. > > For some reason I cannot recreate this issue. It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. At least, removing it fixes build for me. Build successful with the following settings: # cat /etc/src-env.conf WITH_META_MODE= #WITH_AUTO_OBJ= # env | grep MAKE MAKEOBJDIRPREFIX=/home/obj # cat /etc/make.conf MALLOC_PRODUCTION=yes KERNCONF= GENERIC-NODEBUG CPUTYPE?=native PORTS_MODULES= graphics/drm-next-kmod DOC_LANG = en_US.ISO8859-1 ru_RU.KOI8-R WITH_DEBUG_PORTS = mail/neomutt WITH_CCACHE_BUILD=yes CCACHE_DIR=/home/ccache DEVELOPER=yes -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra From owner-freebsd-current@freebsd.org Mon Feb 12 15:27:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EDB3F009DE for ; Mon, 12 Feb 2018 15:27:30 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05919798BA for ; Mon, 12 Feb 2018 15:27:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id c80so6904670itb.4 for ; Mon, 12 Feb 2018 07:27:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=x0amZjqTDafe+3Gpl9Vu/r19Jkx+5gyM8iMRyFdrrGs=; b=eq3yowcZDsQxXjlVnAQqVwuj2kSFWevo5RN8XLAxpMMtGQs+eIVPDxNL0NMZ/vm9PE k0mfY87mjB75g6V8x8iEk/tVnyFTs2Etms6ipJQV9Rk4+FOL2IeeJ/LM+BljPxo/6JTB 3QHbMbIC2VGwHm4cyZRYwgcrijeOUzPSfjuCu8bQoEz3uVSoDvkNXDSmwXkgRo7SIBta ngNTD5oySF1lfOg4ChVEB9tRm1mV6f6YDwhz9KVRrUymyd7AF//iyBlDGqdzd78DJfys 4WNGkXLxN1zXh6Y4Y76cvglAfaG3NtOCaNpOc86aqbNw4++6quEvMpa3o4KEsF/o2kvS LXDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=x0amZjqTDafe+3Gpl9Vu/r19Jkx+5gyM8iMRyFdrrGs=; b=ipCIoAljkB5MMyeRbWjjT6ZzvNVdMSSwfm4t5CiEn1VELYSOfu+4eGwPVWB4R+nA9q gzmEEyiS8Iwt+xvAL9xehvaG11IWInfdKVznJErmcluvqZT+EZ22eBRMPtpZUk5hHcna sR7QdRS4YIyXlOSChy5wF/XwHQSp92kJGnYsAI4WC4yrmOl/7mE5gi8aEWWTOM9gvi8q EvJiBssMEG5K8o2cP/MgU4eMas2y7q16NI7f11VHp3UvrhHCxw4v6gEnaALV4Z+IDiDZ awSZXlmwCoj+p9r3gWZtSE+fFGOJP1suGd2U+nSPsx93RJ7w/2UiK5tbLMyFwmVBe86p Nn+w== X-Gm-Message-State: APf1xPAC+5vxFmCNXHOlociE4Bw0S02h3427R+1SwH1Vf0q8OPULyng/ RzcgtwaPQcOobxbMPn7jpMtq5BxpWR5RYljeR9acH+1X X-Google-Smtp-Source: AH8x226Nzy/B+mLkI+x1RcTXzDA+2ajB7JR+UOREVJYYTTcEQ9kFEMOaV451ShYaEJbeuHh1Lfc+rlFE++L1QfVTEII= X-Received: by 10.36.250.193 with SMTP id v184mr5358360ith.64.1518449248744; Mon, 12 Feb 2018 07:27:28 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Mon, 12 Feb 2018 07:27:27 -0800 (PST) X-Originating-IP: [50.253.99.174] From: Warner Losh Date: Mon, 12 Feb 2018 08:27:27 -0700 X-Google-Sender-Auth: Nb7CdAJJgidAGHJswPdYYa73SOA Message-ID: Subject: LUA boot loader coming very soon To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 15:27:30 -0000 Greetings, As you may know, the Lua (http://www.lua.org) boot loader has been in the works for some time. It started out life as a GSoC in 2014 by Pedro Souza mentored by Wojciech A. Koszek. Rui Paulo created a svn project branch to try to integrate it. I rebased that effort into a github branch which Pedro Arthur fixed up. Over the past year, I've been cleaning up the boot loader for other reasons, and found the time was ripe to start integrating this into the tree. However, those integration efforts have taken a while as my day-job work on the boot loader took priority. In the mean time, Ed Maste and the FreeBSD Foundation funded Zakary Nafziger to enhance the original GSoC Lua scripts to bring it closer to parity with the evolution of the FORTH menu system since the GSoC project started. I'm pleased to announce that all these threads of development have converged and I'll be pushing the FreeBSD Lua Loader later today. This loader uses Lua as its scripting language instead of FORTH. While co-existance is planned, the timeline for it is looking to be a few weeks and I didn't want to delay pushing this into the tree for that. To try the loader, you'll need to build WITHOUT_FORTH=yes and WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to do this, you can do it in src/stand and install the result (be sure to have the options for both the build and the install). This will replace your current /boot/loader that is scripted with FORTH to one that's scripted with Lua. It will install the lua scripts in /boot/lua. The boot is scripted with /boot/lua/loader.lua instead of /boot/loader.rc. You are strongly advised to create a backup copy of /boot/loader before testing (eg cp /boot/loader /boot/loader_forth), since you'll need to boot that from boot2 if something goes wrong. I've tested it extensively, though, with userboot.so and it's test program, so all the initial kinks of finding the lua scripts, etc have been worked out. While it's possible to build all the /boot/loader variants with Lua, I've just tested a BIOS booting /boot/loader both with and without menus enabled. I've not tested any of the other variants and the instructions for testing some of them may be rather tedious (especially UEFI, if you want a simple path to back out). Since there's not been full convergence testing, you'll almost certainly find bumps in this system. Also, all the build-system APIs are likely not yet final. I put MFC after a month on the commit. Due to the heroic (dare I say almost crazy) work of Kyle Evans on merging all the revs from -current to 11, I'm planning a MFC to 11 after the co-existence issues are hammered out. In 11, FORTH will be the default, and Lua will be built by default, but users will have to do something to use it. 12, both FORTH and Lua will be built and installed, with Lua as default (barring unforeseen complications). Once the co-existence stuff goes in, I imagine we'll make the switch to Lua by default shortly after that. In 13, FORTH will be removed unless there's a really really compelling case made to keep it. So please give it a spin and give me any feedback, documentation updates and/or bug fixes. I'm especially interested in reviews from people that have embedded Lua in other projects or experts in Lua that can improve the robustness of the menu code. Warner From owner-freebsd-current@freebsd.org Mon Feb 12 16:27:14 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C34AEF059AB for ; Mon, 12 Feb 2018 16:27:14 +0000 (UTC) (envelope-from kris@ixsystems.com) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 624357D5FD for ; Mon, 12 Feb 2018 16:27:14 +0000 (UTC) (envelope-from kris@ixsystems.com) Received: by mail-yw0-x231.google.com with SMTP id y186so2342522ywf.7 for ; Mon, 12 Feb 2018 08:27:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=NW7HE3I0TkARXL0P9Mlm6wonOIUTLuAh34C4Em0Heu8=; b=KZW9IE3d0AbaJxtKLwuGPF2ZvSk9sZ18BwdSAUCcBW7DTQJYVppezyEfgoRGlYqp2V /wc2PQRbpvYOv5bzFyr42CcAJ4yB5Riuhrxqkt9o8u5xlaaWS1QjliZe7YhjQ81O+PPb nS07mwMoUCa/FsuyCiKLHEzsm9JByEh4zrDhEVSaOBJ3s9/ha/Syohdytg7YEm0HPluI 1pjzjjvZo19p+IgExAOWa8ljG+1QCD1OT7cUOPom1n7+h1WpT77BK8UArsUseunm7xpz Xo7HR0yGdesy+doeVjRM4VpKF/EHDVXzsZvqv2SkNZujbRb7N/9rxvrG3KWZZh3rNxt8 P2cQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=NW7HE3I0TkARXL0P9Mlm6wonOIUTLuAh34C4Em0Heu8=; b=ll9pCVZAvk0tQ+bWV6/XtDGXxMx/cwM0Fsp0vZxQCXJLeplEys/xeMVndXTgU0SSEc dldhFpzvRZFELdJTmrAusGRX12c9NVb7DxDyqUEgr4uzsZt4BJIbL63An3ipuZa+8p2d ze7Jrnw3llTwA6Ev66KWB3FoxnKstj3BksHTFn9PbT32p6gJWDjxkNA7v00ULxn2gHr8 NZEi+COfX1Ygo28RmXrhJwtb/oFDNdQoeCdoj+PPsj0FETfG04K5q3Xgxv+0Rot00uZq 01j9OlwmyzdGO3cXo2yuiAmjA4h4TFEoh4xkymLg73g1UyVxYsEPEDxmgIx4gr550EL+ G1yg== X-Gm-Message-State: APf1xPA5+RC3zhFdU97KZVnyQqI9jN2yJ5CzSmN5vSBw7b8OmiXaiNQS sMeDg/WjP84xqHTpUZIxu60gpFkO0pa35KaGBj/pKMymWxXU5bjSzxEIc4ca0D1U8soV9J97hYO gxI61PlaBbfnWzs0nGHWP8wNMDaiETQomFH3AAhU/z+NDA1M1mI6fqKqGCXbAiMfR0ZNt X-Google-Smtp-Source: AH8x226q/lXa+0N3eraqg2Drf4gMCuTwpw9ZC4IsEcAFYk++EeHHzycwaYOiOqO+BO/tVelyH1Dtcw== X-Received: by 10.37.221.69 with SMTP id u66mr1110558ybg.113.1518452833039; Mon, 12 Feb 2018 08:27:13 -0800 (PST) Received: from [10.231.2.154] ([12.164.17.129]) by smtp.gmail.com with ESMTPSA id t1sm3402693ywd.45.2018.02.12.08.27.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Feb 2018 08:27:12 -0800 (PST) Subject: Re: LUA boot loader coming very soon To: freebsd-current@freebsd.org References: From: Kris Moore Message-ID: <741cdd4f-c4f3-5909-26a9-4cc8f5231eea@ixsystems.com> Date: Mon, 12 Feb 2018 11:26:33 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 16:27:15 -0000 On 02/12/2018 10:27, Warner Losh wrote: > Greetings, > > As you may know, the Lua (http://www.lua.org) boot loader has been in the > works for some time. It started out life as a GSoC in 2014 by Pedro Souza > mentored by Wojciech A. Koszek. Rui Paulo created a svn project branch to > try to integrate it. I rebased that effort into a github branch which Pedro > Arthur fixed up. Over the past year, I've been cleaning up the boot loader > for other reasons, and found the time was ripe to start integrating this > into the tree. However, those integration efforts have taken a while as my > day-job work on the boot loader took priority. In the mean time, Ed Maste > and the FreeBSD Foundation funded Zakary Nafziger to enhance the original > GSoC Lua scripts to bring it closer to parity with the evolution of the > FORTH menu system since the GSoC project started. > > I'm pleased to announce that all these threads of development have > converged and I'll be pushing the FreeBSD Lua Loader later today. This > loader uses Lua as its scripting language instead of FORTH. While > co-existance is planned, the timeline for it is looking to be a few weeks > and I didn't want to delay pushing this into the tree for that. > > To try the loader, you'll need to build WITHOUT_FORTH=yes and > WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to do this, > you can do it in src/stand and install the result (be sure to have the > options for both the build and the install). This will replace your current > /boot/loader that is scripted with FORTH to one that's scripted with Lua. > It will install the lua scripts in /boot/lua. The boot is scripted with > /boot/lua/loader.lua instead of /boot/loader.rc. You are strongly advised > to create a backup copy of /boot/loader before testing (eg cp /boot/loader > /boot/loader_forth), since you'll need to boot that from boot2 if something > goes wrong. I've tested it extensively, though, with userboot.so and it's > test program, so all the initial kinks of finding the lua scripts, etc have > been worked out. > > While it's possible to build all the /boot/loader variants with Lua, I've > just tested a BIOS booting /boot/loader both with and without menus > enabled. I've not tested any of the other variants and the instructions for > testing some of them may be rather tedious (especially UEFI, if you want a > simple path to back out). Since there's not been full convergence testing, > you'll almost certainly find bumps in this system. Also, all the > build-system APIs are likely not yet final. > > I put MFC after a month on the commit. Due to the heroic (dare I say > almost crazy) work of Kyle Evans on merging all the revs from -current to > 11, I'm planning a MFC to 11 after the co-existence issues are hammered > out. In 11, FORTH will be the default, and Lua will be built by default, > but users will have to do something to use it. 12, both FORTH and Lua will > be built and installed, with Lua as default (barring unforeseen > complications). Once the co-existence stuff goes in, I imagine we'll make > the switch to Lua by default shortly after that. In 13, FORTH will be > removed unless there's a really really compelling case made to keep it. > > So please give it a spin and give me any feedback, documentation updates > and/or bug fixes. I'm especially interested in reviews from people that > have embedded Lua in other projects or experts in Lua that can improve the > robustness of the menu code. > > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Warner & Co, Great job all! Been wanting this for years, very excited to see it start landing :) One question, if we switch to Lua loader in TrueOS, do you know if the ZFS boot-environment menus have been implemented / tested yet? -- Kris Moore Vice President of Engineering iXsystems Enterprise Storage & Servers Driven By Open Source From owner-freebsd-current@freebsd.org Mon Feb 12 16:32:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A34FF0607C for ; Mon, 12 Feb 2018 16:32:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::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 CC9627D996 for ; Mon, 12 Feb 2018 16:31:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x235.google.com with SMTP id 193so4495571iti.1 for ; Mon, 12 Feb 2018 08:31:59 -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=TY+yM/BhXRV6KrPNsZp+AIP4OpcAei5GC83JJw+Wd1k=; b=oFag4DTPJHVh2M+D8R5Y1jknkgOGQzTrAht4Wzm/1fiOdMgBhQqJSDOiNqVD6faKCb jmS9BXKGjFpBeW0Wd8/kh5KpsG69iwqIPU4rpzhGOZxHHjGpEf2GyxRBjdaFLN87LFSo 4vebUHgnRuKSdQKSRBo6zybRsPFflJN4M6ZP/j/cP6Ykfbv4z8hxOCGEluq2VW8wRef2 QQdM8d7dAvWJ+bLT0OG5iqyNeopmHn+4Uco6tSwWodCR7NfONU6UBawM6Hh5GlScXzeR i1CVUQLzUx73A5PQIRvKwnLXjzd5BdYTvabDa2V5tuIwZtDZ+qfJD6FJbuJJ5osak+nM OsMQ== 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=TY+yM/BhXRV6KrPNsZp+AIP4OpcAei5GC83JJw+Wd1k=; b=XXraq7XTDum3m1QWTMq3Bj2kykkX9nuNH01qWQErkfFYJ/EUBdLjeurYXqwTiFDZ9v GrHF8ZD1BbTt5/gDaM665LK0oZPgwUzqk8IJcVlMjXloZI1uPt15AeMrTBZo6wKC/TTs Ofy4s7s1IhWuTjnlrum5RHUsGsSNS6TxmQjWlvNw/K4Xr+nxS8nJF5HNmi30UEnzJ3bw 7l5yy3eoYPOuf3vlJXEqyvni4KEYweTLd33+8yv7k0GGo8Qe/fkwrAjdxYN5cEr5LWN9 CrzDX/BiuunnY4PPRwE+sBeoxCdZrKs0an8ZyTqhRIFaPSd9lzCAfhNMYCnWrnNvQ5A2 YXbQ== X-Gm-Message-State: APf1xPBfRz2UsdoRuKzOSoHDgwZmev1hc5ybGEPNezUq6F8hFbNW3vA8 UPLGaFK8Uol9Y8MbrQeLT6OLX4Ye04HCwjBA05ytzw== X-Google-Smtp-Source: AH8x226hQB0iGg6sKYmHI4/GFlI3BtUCGstPeQGQJGwvWqPIADvock/jrLXAOmudxVl04muDoEaK+fFt/LiOIjG50TQ= X-Received: by 10.36.145.139 with SMTP id i133mr6468877ite.69.1518453119053; Mon, 12 Feb 2018 08:31:59 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Mon, 12 Feb 2018 08:31:58 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <741cdd4f-c4f3-5909-26a9-4cc8f5231eea@ixsystems.com> References: <741cdd4f-c4f3-5909-26a9-4cc8f5231eea@ixsystems.com> From: Warner Losh Date: Mon, 12 Feb 2018 09:31:58 -0700 X-Google-Sender-Auth: RCgNXO03I8PmH_3XXbT7aLSRM7A Message-ID: Subject: Re: LUA boot loader coming very soon To: Kris Moore Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 16:32:00 -0000 On Mon, Feb 12, 2018 at 9:26 AM, Kris Moore wrote: > On 02/12/2018 10:27, Warner Losh wrote: > > Greetings, > > > > As you may know, the Lua (http://www.lua.org) boot loader has been in > the > > works for some time. It started out life as a GSoC in 2014 by Pedro Souza > > mentored by Wojciech A. Koszek. Rui Paulo created a svn project branch to > > try to integrate it. I rebased that effort into a github branch which > Pedro > > Arthur fixed up. Over the past year, I've been cleaning up the boot > loader > > for other reasons, and found the time was ripe to start integrating this > > into the tree. However, those integration efforts have taken a while as > my > > day-job work on the boot loader took priority. In the mean time, Ed Maste > > and the FreeBSD Foundation funded Zakary Nafziger to enhance the original > > GSoC Lua scripts to bring it closer to parity with the evolution of the > > FORTH menu system since the GSoC project started. > > > > I'm pleased to announce that all these threads of development have > > converged and I'll be pushing the FreeBSD Lua Loader later today. This > > loader uses Lua as its scripting language instead of FORTH. While > > co-existance is planned, the timeline for it is looking to be a few weeks > > and I didn't want to delay pushing this into the tree for that. > > > > To try the loader, you'll need to build WITHOUT_FORTH=yes and > > WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to do this, > > you can do it in src/stand and install the result (be sure to have the > > options for both the build and the install). This will replace your > current > > /boot/loader that is scripted with FORTH to one that's scripted with Lua. > > It will install the lua scripts in /boot/lua. The boot is scripted with > > /boot/lua/loader.lua instead of /boot/loader.rc. You are strongly advised > > to create a backup copy of /boot/loader before testing (eg cp > /boot/loader > > /boot/loader_forth), since you'll need to boot that from boot2 if > something > > goes wrong. I've tested it extensively, though, with userboot.so and it's > > test program, so all the initial kinks of finding the lua scripts, etc > have > > been worked out. > > > > While it's possible to build all the /boot/loader variants with Lua, I've > > just tested a BIOS booting /boot/loader both with and without menus > > enabled. I've not tested any of the other variants and the instructions > for > > testing some of them may be rather tedious (especially UEFI, if you want > a > > simple path to back out). Since there's not been full convergence > testing, > > you'll almost certainly find bumps in this system. Also, all the > > build-system APIs are likely not yet final. > > > > I put MFC after a month on the commit. Due to the heroic (dare I say > > almost crazy) work of Kyle Evans on merging all the revs from -current to > > 11, I'm planning a MFC to 11 after the co-existence issues are hammered > > out. In 11, FORTH will be the default, and Lua will be built by default, > > but users will have to do something to use it. 12, both FORTH and Lua > will > > be built and installed, with Lua as default (barring unforeseen > > complications). Once the co-existence stuff goes in, I imagine we'll make > > the switch to Lua by default shortly after that. In 13, FORTH will be > > removed unless there's a really really compelling case made to keep it. > > > > So please give it a spin and give me any feedback, documentation updates > > and/or bug fixes. I'm especially interested in reviews from people that > > have embedded Lua in other projects or experts in Lua that can improve > the > > robustness of the menu code. > > > > Warner > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@ > freebsd.org" > > Warner & Co, > > Great job all! Been wanting this for years, very excited to see it start > landing :) > > One question, if we switch to Lua loader in TrueOS, do you know if the > ZFS boot-environment menus have been implemented / tested yet? I don't think that they have been implemented yet. I've certainly not tested them. Warner From owner-freebsd-current@freebsd.org Mon Feb 12 16:46:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C91C4F071AD for ; Mon, 12 Feb 2018 16:46:09 +0000 (UTC) (envelope-from kris@ixsystems.com) Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 54FF27E423 for ; Mon, 12 Feb 2018 16:46:09 +0000 (UTC) (envelope-from kris@ixsystems.com) Received: by mail-yw0-x233.google.com with SMTP id t129so10296445ywc.3 for ; Mon, 12 Feb 2018 08:46:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=hDwBert6y6z7lSwt9k0PdphDXMUdNBn7mKuoD/2TpMU=; b=0LFkvjxchsJl+b8VHvbqs2zA7b/e4HMEo6zW+kkaHsX59ZNuSOvJrnTfysE6/+ICaR 6am688ZzsNr20QSLzy9n6Grzs2J8vVrWlA9Umg2a8cNwlYSriCPEPqqOI9C8Ldrfayn3 rER46aQN6ixQ/sYnhdb4DPfkhd4Pavhk9b4ZqA6cB85JcpOCLh3vTNnv2ZK9xnCRHkUC i8C08v25xHSJlpnfjgf4MRR9dVBcdziSijvZRtg1ZOosV1Qnwa7R1JqsVgw+5+kOa8aj SpbcePgx3Ckx5yYYV1FYPEB4MFIlPiuAAYl0ZjolBmPIOBuCM3ue9YfUYGc3suxpttzZ xsew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=hDwBert6y6z7lSwt9k0PdphDXMUdNBn7mKuoD/2TpMU=; b=LYWQq16k3JICql2/drRV3V0IoJe9mPsS5hzVtrl/U+rfFKxaOLeVJ4iuMT8L65Ac2L QQmIunwkEuL0MRsJRcMSP1Z+eo0s8cvnTvJaredIQd2zAPiRrCtwejllCQTErhxHHwCQ DvVp4Gd/JBhtUGSyyZhv4hCQNfhzI6spivlNMicMjqBUDmR2r06cJAsTQR3pnH85jd7K ELjWq4xWzFxRPG80GYn/kU5Hjcv34qFwdkKCuoULpMuBVhnAuC3Q5M8tD3eCZYOe8EQc alltqJISMnrohOLIu2icUUnKpxHGD/C54fjfDnIq6DjvJxlhK3qplVUNfC3feWgmnYHI L0Vw== X-Gm-Message-State: APf1xPC/yoXBEm6Qc2QEl3AuvPxtE4zjUZGH89bH1zx0cyOhYJYjbmfu 9RWDD1dCjND0Y6/GmAcDfccKkhccLniv+hEEZ7owphk3YU1H4M9ZYv7Pu0gGrbDXZEfnnAaIbY8 xqTJj1IIviRAGFWoa1I6M709BnRf/peSlMHUQkGaSqOOJB9TTP8iuh+ZDczlgs1+3O6AB X-Google-Smtp-Source: AH8x224Qxv8tLB++oKnsjh08XFcMTuMYoEnR/CVwprd3W3Lk5sbTfQYxvQ8Jxguqbqe9+sPg0t377Q== X-Received: by 10.129.131.196 with SMTP id t187mr4969652ywf.403.1518453968358; Mon, 12 Feb 2018 08:46:08 -0800 (PST) Received: from [10.231.2.154] ([12.164.17.129]) by smtp.gmail.com with ESMTPSA id c13sm3483746ywm.74.2018.02.12.08.46.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Feb 2018 08:46:07 -0800 (PST) Subject: Re: LUA boot loader coming very soon To: Warner Losh Cc: FreeBSD Current References: <741cdd4f-c4f3-5909-26a9-4cc8f5231eea@ixsystems.com> From: Kris Moore Message-ID: <623bcb5c-8ddb-4d38-7826-0c9e344502a3@ixsystems.com> Date: Mon, 12 Feb 2018 11:45:28 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 16:46:10 -0000 On 02/12/2018 11:31, Warner Losh wrote: > > > On Mon, Feb 12, 2018 at 9:26 AM, Kris Moore > wrote: > > On 02/12/2018 10:27, Warner Losh wrote: > > Greetings, > > > > As you may know, the Lua (http://www.lua.org) boot loader has > been in the > > works for some time. It started out life as a GSoC in 2014 by > Pedro Souza > > mentored by Wojciech A. Koszek. Rui Paulo created a svn project > branch to > > try to integrate it. I rebased that effort into a github branch > which Pedro > > Arthur fixed up. Over the past year, I've been cleaning up the > boot loader > > for other reasons, and found the time was ripe to start > integrating this > > into the tree. However, those integration efforts have taken a > while as my > > day-job work on the boot loader took priority. In the mean time, > Ed Maste > > and the FreeBSD Foundation funded Zakary Nafziger to enhance the > original > > GSoC Lua scripts to bring it closer to parity with the evolution > of the > > FORTH menu system since the GSoC project started. > > > > I'm pleased to announce that all these threads of development have > > converged and I'll be pushing the FreeBSD Lua Loader later > today. This > > loader uses Lua as its scripting language instead of FORTH. While > > co-existance is planned, the timeline for it is looking to be a > few weeks > > and I didn't want to delay pushing this into the tree for that. > > > > To try the loader, you'll need to build WITHOUT_FORTH=yes and > > WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to > do this, > > you can do it in src/stand and install the result (be sure to > have the > > options for both the build and the install). This will replace > your current > > /boot/loader that is scripted with FORTH to one that's scripted > with Lua. > > It will install the lua scripts in /boot/lua. The boot is > scripted with > > /boot/lua/loader.lua instead of /boot/loader.rc. You are > strongly advised > > to create a backup copy of /boot/loader before testing (eg cp > /boot/loader > > /boot/loader_forth), since you'll need to boot that from boot2 > if something > > goes wrong. I've tested it extensively, though, with userboot.so > and it's > > test program, so all the initial kinks of finding the lua > scripts, etc have > > been worked out. > > > > While it's possible to build all the /boot/loader variants with > Lua, I've > > just tested a BIOS booting /boot/loader both with and without menus > > enabled. I've not tested any of the other variants and the > instructions for > > testing some of them may be rather tedious (especially UEFI, if > you want a > > simple path to back out). Since there's not been full > convergence testing, > > you'll almost certainly find bumps in this system. Also, all the > > build-system APIs are likely not yet final. > > > > I put  MFC after a month on the commit. Due to the heroic (dare > I say > > almost crazy) work of Kyle Evans on merging all the revs from > -current to > > 11, I'm planning a MFC to 11 after the co-existence issues are > hammered > > out. In 11, FORTH will be the default, and Lua will  be built by > default, > > but users will have to do something to use it. 12, both FORTH > and Lua will > > be built and installed, with Lua as default (barring unforeseen > > complications). Once the co-existence stuff goes in, I imagine > we'll make > > the switch to Lua by default shortly after that. In 13, FORTH > will be > > removed unless there's a really really compelling case made to > keep it. > > > > So please give it a spin and give me any feedback, documentation > updates > > and/or bug fixes. I'm especially interested in reviews from > people that > > have embedded Lua in other projects or experts in Lua that can > improve the > > robustness of the menu code. > > > > Warner > > _______________________________________________ > > freebsd-current@freebsd.org > mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org > " > > Warner & Co, > > Great job all! Been wanting this for years, very excited to see it > start > landing :) > > One question, if we switch to Lua loader in TrueOS, do you know if the > ZFS boot-environment menus have been implemented / tested yet? > > > I don't think that they have been implemented yet. I've certainly not > tested them. > > Warner  > Ok, I'll have to mess about with it. I recall there was some library which created to expose ZFS in limited functionality over to the FORTH code. That's probably a good place to start and see if that still works and Lua can probe the pool for BE information. -- Kris Moore Vice President of Engineering iXsystems Enterprise Storage & Servers Driven By Open Source From owner-freebsd-current@freebsd.org Mon Feb 12 16:51:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4300F077A1 for ; Mon, 12 Feb 2018 16:51:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001: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 514C07E774 for ; Mon, 12 Feb 2018 16:51:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22f.google.com with SMTP id t22so17966916ioa.7 for ; Mon, 12 Feb 2018 08:51:06 -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=0Y9XDBvh62la9h4zhkRiTA7wGnppDGKZ/B9XSwH9JG8=; b=2DvujFpcl8evopjYENM74AM1PxyukqyU350Q2WZdMh+1y3L9Zhwaq+OhmqGiZW2013 0GILnKhwhdSRX0tbuFgATiIO1AdY7Mbes9kl2QrwfZiO6ko+QIFTj4iLtPXw9nFgZGZF uEkDU20UzyeKoRia57sicS2yEjkkXC+v4lclwXD7gESBY+1GN4/IHRqd0DC1YxvE/AU+ X+g4wxsX4Nw2/rbU5vl9nOABKrZzRhfmPy1zpe8mFlBgtcg9SeX9qkmZrhY0r9cWWHoP qUqpPawyQOY0sJBC5fSVbEocdwDm7Zz55Nk2NhCGIqHND4aNKFVaXDWePXG5udvv1NZU eFtA== 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=0Y9XDBvh62la9h4zhkRiTA7wGnppDGKZ/B9XSwH9JG8=; b=e6tSS8xk0ZyJGquq0AvYc+bajiLeVCWLSp4ncyuW1XBkIURX5oWRR3jpDFwnMIv+kv WK7hltbXflz4a6Fb2xgTNb9GFa3nRacuttnLMq3SUQFfR9Hkkih3M9lzDoAuny2kz4NH aJEDQSMjFx/fFV5e4XrCKUyLZFYQgKT7XdN39N4BzmHu79pN/5NRi3Gxc7xCZbzF6t41 d3Me2av3lbu5MvqtyVVyU/+VdQBIBpDCexSaEqo/xW2gIBTSbLGyBt5jJd9gE89BamK3 QehrFDjv43+PVIpd2REVkTnoBM7N6ECJpzEObTH6OqxSf7OzwCea1CruTW3bCZenHcGj ncpA== X-Gm-Message-State: APf1xPCQKka0iHof/pDvLJT0IN8tyGSgFkgqfUwGRtJ1biAJ8LYZN5YB bCmMoGC6Jzn55KOgzkNZ2sPO9R90TbzBD3EZqsW22w== X-Google-Smtp-Source: AH8x227NRriBimG1s8LcQ4V09LNnKXEfgYG+bLtKkPGlloIPI9a6hs8f/H+Wpkkw67bobzWU1NrZ4OsSajxgqZD73M4= X-Received: by 10.107.167.69 with SMTP id q66mr13143012ioe.130.1518454265413; Mon, 12 Feb 2018 08:51:05 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Mon, 12 Feb 2018 08:51:04 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <623bcb5c-8ddb-4d38-7826-0c9e344502a3@ixsystems.com> References: <741cdd4f-c4f3-5909-26a9-4cc8f5231eea@ixsystems.com> <623bcb5c-8ddb-4d38-7826-0c9e344502a3@ixsystems.com> From: Warner Losh Date: Mon, 12 Feb 2018 09:51:04 -0700 X-Google-Sender-Auth: v2ShTPkBNfxCyHhi1QKw7loZLnE Message-ID: Subject: Re: LUA boot loader coming very soon To: Kris Moore Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 16:51:07 -0000 On Mon, Feb 12, 2018 at 9:45 AM, Kris Moore wrote: > On 02/12/2018 11:31, Warner Losh wrote: > > > > On Mon, Feb 12, 2018 at 9:26 AM, Kris Moore wrote: > >> On 02/12/2018 10:27, Warner Losh wrote: >> > Greetings, >> > >> > As you may know, the Lua (http://www.lua.org) boot loader has been in >> the >> > works for some time. It started out life as a GSoC in 2014 by Pedro >> Souza >> > mentored by Wojciech A. Koszek. Rui Paulo created a svn project branch >> to >> > try to integrate it. I rebased that effort into a github branch which >> Pedro >> > Arthur fixed up. Over the past year, I've been cleaning up the boot >> loader >> > for other reasons, and found the time was ripe to start integrating this >> > into the tree. However, those integration efforts have taken a while as >> my >> > day-job work on the boot loader took priority. In the mean time, Ed >> Maste >> > and the FreeBSD Foundation funded Zakary Nafziger to enhance the >> original >> > GSoC Lua scripts to bring it closer to parity with the evolution of the >> > FORTH menu system since the GSoC project started. >> > >> > I'm pleased to announce that all these threads of development have >> > converged and I'll be pushing the FreeBSD Lua Loader later today. This >> > loader uses Lua as its scripting language instead of FORTH. While >> > co-existance is planned, the timeline for it is looking to be a few >> weeks >> > and I didn't want to delay pushing this into the tree for that. >> > >> > To try the loader, you'll need to build WITHOUT_FORTH=yes and >> > WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to do >> this, >> > you can do it in src/stand and install the result (be sure to have the >> > options for both the build and the install). This will replace your >> current >> > /boot/loader that is scripted with FORTH to one that's scripted with >> Lua. >> > It will install the lua scripts in /boot/lua. The boot is scripted with >> > /boot/lua/loader.lua instead of /boot/loader.rc. You are strongly >> advised >> > to create a backup copy of /boot/loader before testing (eg cp >> /boot/loader >> > /boot/loader_forth), since you'll need to boot that from boot2 if >> something >> > goes wrong. I've tested it extensively, though, with userboot.so and >> it's >> > test program, so all the initial kinks of finding the lua scripts, etc >> have >> > been worked out. >> > >> > While it's possible to build all the /boot/loader variants with Lua, >> I've >> > just tested a BIOS booting /boot/loader both with and without menus >> > enabled. I've not tested any of the other variants and the instructions >> for >> > testing some of them may be rather tedious (especially UEFI, if you >> want a >> > simple path to back out). Since there's not been full convergence >> testing, >> > you'll almost certainly find bumps in this system. Also, all the >> > build-system APIs are likely not yet final. >> > >> > I put MFC after a month on the commit. Due to the heroic (dare I say >> > almost crazy) work of Kyle Evans on merging all the revs from -current >> to >> > 11, I'm planning a MFC to 11 after the co-existence issues are hammered >> > out. In 11, FORTH will be the default, and Lua will be built by >> default, >> > but users will have to do something to use it. 12, both FORTH and Lua >> will >> > be built and installed, with Lua as default (barring unforeseen >> > complications). Once the co-existence stuff goes in, I imagine we'll >> make >> > the switch to Lua by default shortly after that. In 13, FORTH will be >> > removed unless there's a really really compelling case made to keep it. >> > >> > So please give it a spin and give me any feedback, documentation updates >> > and/or bug fixes. I'm especially interested in reviews from people that >> > have embedded Lua in other projects or experts in Lua that can improve >> the >> > robustness of the menu code. >> > >> > Warner >> > _______________________________________________ >> > freebsd-current@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >> reebsd.org" >> >> Warner & Co, >> >> Great job all! Been wanting this for years, very excited to see it start >> landing :) >> >> One question, if we switch to Lua loader in TrueOS, do you know if the >> ZFS boot-environment menus have been implemented / tested yet? > > > I don't think that they have been implemented yet. I've certainly not > tested them. > > Warner > > Ok, I'll have to mess about with it. I recall there was some library which > created to expose ZFS in limited functionality over to the FORTH code. > That's probably a good place to start and see if that still works and Lua > can probe the pool for BE information. > OK. There's no such functionality in FORTH in the tree today. However, zfs sets a number of env vars that loader.getenv() can get in lua. Warner From owner-freebsd-current@freebsd.org Mon Feb 12 16:58:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 626A5F0823E for ; Mon, 12 Feb 2018 16:58:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E95147EE6E for ; Mon, 12 Feb 2018 16:58:57 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id e1so7307983ita.0 for ; Mon, 12 Feb 2018 08:58:57 -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=IDM59U8v9thGzHjiSnxEdRg5htd+gNZ2gyR0Q6wrj5k=; b=kOqOcjD2S2ZY4vjD5zVvO3R5V6a5sMTv/fCbGpR6/KoyihQvInAernGhG0nIA+OWFj BR0cweVSAhnPuezSWUMZDPc9QMe4q/mUsll5jwyWohZ076zIPERpjQrXGcGfB9pmLF8y tr55pZMdYooyaV/yAyBU93cyRrPJnyU1VUygKaSAatUbniJfmBLxvFp05O2K/Jp7+jVO GmiBL/9y2XT4u2OftbibO4Kjvry9mfmqqFb0LGhC0y57lkHWEleyz2I4fXbSIPlEfLa5 B/BawEdVoOp/tBnURkTv528m494picz3pGMMoF98P0Q042Lje5ZdHZt1DyPT9fPLUU9+ 9ToQ== 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=IDM59U8v9thGzHjiSnxEdRg5htd+gNZ2gyR0Q6wrj5k=; b=nRgKgHb2iSZT/m9EoRtdZPulNAkx+syLee0KX6AXd2ifug4DAE7xX2puixC29lW6Sl R8I0dKHs01W1G6s18AyeqKjhlWmycqHnoJwx+u9gtgaLi9m9DWSQp9E0DMzWxrPqmeEB hVT6PNhSnbvF7Z+TbuKta/lnlKBhwhJUt6f5r13EiPldDzxAiW/6BOficXbKkpjBFooP hIt+c6+hSqdvxtyRKoBcS/bSNn/arem9nAAGnrKOUHOXge/3nsBu6QLUQEqCrWRh9nTU rVZJ6QGofv1tyiXNG6eta7CcWYIr4r3jYVQj8uksCpmhqn7+u0fL2q7aqRspfKrRqM+t o5uw== X-Gm-Message-State: APf1xPBvTTHfYMvhBWje1bAQyXI97KVeiVUx+2PNCuIe82LrpHxR1mUs +4Np8kAXsiu7fLir1OnBARm4XXUbqrFILGS0q3Un6A== X-Google-Smtp-Source: AH8x226WD2CR4MG0+wJCbqHWvBWPX4nbH+LjSmEUdzZFNfGW6hzHumskwB4vbbZm9GqxH7icUVi6RAbes7eAZVkbfqA= X-Received: by 10.36.54.66 with SMTP id l63mr6298551itl.50.1518454737243; Mon, 12 Feb 2018 08:58:57 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Mon, 12 Feb 2018 08:58:56 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <741cdd4f-c4f3-5909-26a9-4cc8f5231eea@ixsystems.com> <623bcb5c-8ddb-4d38-7826-0c9e344502a3@ixsystems.com> From: Warner Losh Date: Mon, 12 Feb 2018 09:58:56 -0700 X-Google-Sender-Auth: kpKe4YtJZPo4RdC8ZwPu-6hLUZQ Message-ID: Subject: Re: LUA boot loader coming very soon To: Kris Moore Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 16:58:58 -0000 On Mon, Feb 12, 2018 at 9:51 AM, Warner Losh wrote: > > > On Mon, Feb 12, 2018 at 9:45 AM, Kris Moore wrote: > >> On 02/12/2018 11:31, Warner Losh wrote: >> >> >> >> On Mon, Feb 12, 2018 at 9:26 AM, Kris Moore wrote: >> >>> On 02/12/2018 10:27, Warner Losh wrote: >>> > Greetings, >>> > >>> > As you may know, the Lua (http://www.lua.org) boot loader has been in >>> the >>> > works for some time. It started out life as a GSoC in 2014 by Pedro >>> Souza >>> > mentored by Wojciech A. Koszek. Rui Paulo created a svn project branch >>> to >>> > try to integrate it. I rebased that effort into a github branch which >>> Pedro >>> > Arthur fixed up. Over the past year, I've been cleaning up the boot >>> loader >>> > for other reasons, and found the time was ripe to start integrating >>> this >>> > into the tree. However, those integration efforts have taken a while >>> as my >>> > day-job work on the boot loader took priority. In the mean time, Ed >>> Maste >>> > and the FreeBSD Foundation funded Zakary Nafziger to enhance the >>> original >>> > GSoC Lua scripts to bring it closer to parity with the evolution of the >>> > FORTH menu system since the GSoC project started. >>> > >>> > I'm pleased to announce that all these threads of development have >>> > converged and I'll be pushing the FreeBSD Lua Loader later today. This >>> > loader uses Lua as its scripting language instead of FORTH. While >>> > co-existance is planned, the timeline for it is looking to be a few >>> weeks >>> > and I didn't want to delay pushing this into the tree for that. >>> > >>> > To try the loader, you'll need to build WITHOUT_FORTH=yes and >>> > WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to do >>> this, >>> > you can do it in src/stand and install the result (be sure to have the >>> > options for both the build and the install). This will replace your >>> current >>> > /boot/loader that is scripted with FORTH to one that's scripted with >>> Lua. >>> > It will install the lua scripts in /boot/lua. The boot is scripted with >>> > /boot/lua/loader.lua instead of /boot/loader.rc. You are strongly >>> advised >>> > to create a backup copy of /boot/loader before testing (eg cp >>> /boot/loader >>> > /boot/loader_forth), since you'll need to boot that from boot2 if >>> something >>> > goes wrong. I've tested it extensively, though, with userboot.so and >>> it's >>> > test program, so all the initial kinks of finding the lua scripts, etc >>> have >>> > been worked out. >>> > >>> > While it's possible to build all the /boot/loader variants with Lua, >>> I've >>> > just tested a BIOS booting /boot/loader both with and without menus >>> > enabled. I've not tested any of the other variants and the >>> instructions for >>> > testing some of them may be rather tedious (especially UEFI, if you >>> want a >>> > simple path to back out). Since there's not been full convergence >>> testing, >>> > you'll almost certainly find bumps in this system. Also, all the >>> > build-system APIs are likely not yet final. >>> > >>> > I put MFC after a month on the commit. Due to the heroic (dare I say >>> > almost crazy) work of Kyle Evans on merging all the revs from -current >>> to >>> > 11, I'm planning a MFC to 11 after the co-existence issues are hammered >>> > out. In 11, FORTH will be the default, and Lua will be built by >>> default, >>> > but users will have to do something to use it. 12, both FORTH and Lua >>> will >>> > be built and installed, with Lua as default (barring unforeseen >>> > complications). Once the co-existence stuff goes in, I imagine we'll >>> make >>> > the switch to Lua by default shortly after that. In 13, FORTH will be >>> > removed unless there's a really really compelling case made to keep it. >>> > >>> > So please give it a spin and give me any feedback, documentation >>> updates >>> > and/or bug fixes. I'm especially interested in reviews from people that >>> > have embedded Lua in other projects or experts in Lua that can improve >>> the >>> > robustness of the menu code. >>> > >>> > Warner >>> > _______________________________________________ >>> > freebsd-current@freebsd.org mailing list >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> > To unsubscribe, send any mail to "freebsd-current-unsubscribe@f >>> reebsd.org" >>> >>> Warner & Co, >>> >>> Great job all! Been wanting this for years, very excited to see it start >>> landing :) >>> >>> One question, if we switch to Lua loader in TrueOS, do you know if the >>> ZFS boot-environment menus have been implemented / tested yet? >> >> >> I don't think that they have been implemented yet. I've certainly not >> tested them. >> >> Warner >> >> Ok, I'll have to mess about with it. I recall there was some library >> which created to expose ZFS in limited functionality over to the FORTH >> code. That's probably a good place to start and see if that still works and >> Lua can probe the pool for BE information. >> > > OK. There's no such functionality in FORTH in the tree today. However, zfs > sets a number of env vars that loader.getenv() can get in lua. > There's also a 'reloadbe' boot loader command that's independent of interpreter. Sadly, it's reimplemented three times identically, with a single comment being the only difference. Now that's something that's ripe for cleanup... Warner From owner-freebsd-current@freebsd.org Mon Feb 12 18:47:21 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07656F114BE for ; Mon, 12 Feb 2018 18:47:21 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 988D684F62; Mon, 12 Feb 2018 18:47:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id A0E0710A8C2; Mon, 12 Feb 2018 13:47:19 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Cc: Garrett Wollman , asomers@freebsd.org Subject: Re: posix_fallocate on ZFS Date: Mon, 12 Feb 2018 09:04:57 -0800 Message-ID: <1868530.6C5Wu4I1lN@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <201802101846.w1AIkX4Y000167@hergotha.csail.mit.edu> References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> <201802101846.w1AIkX4Y000167@hergotha.csail.mit.edu> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 12 Feb 2018 13:47:19 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 18:47:21 -0000 On Saturday, February 10, 2018 01:46:33 PM Garrett Wollman wrote: > In article > , > asomers@freebsd.org writes: > > >On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen > >wrote: > > >> Is there any expectation that this is going to fixed in any near future? > > >No. It's fundamentally impossible to support posix_fallocate on a COW > >filesystem like ZFS. Ceph should be taught to ignore an EINVAL result, > >since the system call is merely advisory. > > I don't think it's true that this is _fundamentally_ impossible. What > the standard requires would in essence be a per-object refreservation. > ZFS supports refreservation, obviously, but not on a per-object basis. > Furthermore, there are mechanisms to preallocate blocks for things > like dumps. So it *could* be done (as in, the concept is there), but > it may not be practical. (And ultimately, there are ways in which the > administrator might manage the system that would defeat the desired > effect, but that's out of the standard's scope.) Given the semantic > mismatch, though, I suspect it's unreasonable to expect anyone to > prioritize implementation of such a feature. I don't think posix_fallocate() can be compatible with COW. Suppose you do reserve a fixed set of blocks. That ensures the first write has a place to write, but not if you overwrite one of those blocks. You'd have to reserve another block to maintain the reservation each time you wrote to a block, or you'd have to have a way to mark a file as not COW. The first case isn't really any better than not using posix_fallocate() in the first place as you are still requiring writes to allocate blocks, and the second seems a bit fraught with peril as well if the application is expecting the non-COW'd file to be in sync with other files in the system since presumably non-COW'd files couldn't be snapshotted, etc. -- John Baldwin From owner-freebsd-current@freebsd.org Mon Feb 12 18:47:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90232F114F5 for ; Mon, 12 Feb 2018 18:47:24 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2054D84F87 for ; Mon, 12 Feb 2018 18:47:24 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 2B27810A8BE; Mon, 12 Feb 2018 13:47:18 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Cc: Warner Losh Subject: Re: LUA boot loader coming very soon Date: Mon, 12 Feb 2018 09:12:27 -0800 Message-ID: <2333272.J6kp8cXjfh@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 12 Feb 2018 13:47:18 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 18:47:24 -0000 On Monday, February 12, 2018 08:27:27 AM Warner Losh wrote: > Greetings, > > As you may know, the Lua (http://www.lua.org) boot loader has been in the > works for some time. It started out life as a GSoC in 2014 by Pedro Souza > mentored by Wojciech A. Koszek. Rui Paulo created a svn project branch to > try to integrate it. I rebased that effort into a github branch which Pedro > Arthur fixed up. Over the past year, I've been cleaning up the boot loader > for other reasons, and found the time was ripe to start integrating this > into the tree. However, those integration efforts have taken a while as my > day-job work on the boot loader took priority. In the mean time, Ed Maste > and the FreeBSD Foundation funded Zakary Nafziger to enhance the original > GSoC Lua scripts to bring it closer to parity with the evolution of the > FORTH menu system since the GSoC project started. > > I'm pleased to announce that all these threads of development have > converged and I'll be pushing the FreeBSD Lua Loader later today. This > loader uses Lua as its scripting language instead of FORTH. While > co-existance is planned, the timeline for it is looking to be a few weeks > and I didn't want to delay pushing this into the tree for that. > > To try the loader, you'll need to build WITHOUT_FORTH=yes and > WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to do this, > you can do it in src/stand and install the result (be sure to have the > options for both the build and the install). This will replace your current > /boot/loader that is scripted with FORTH to one that's scripted with Lua. > It will install the lua scripts in /boot/lua. The boot is scripted with > /boot/lua/loader.lua instead of /boot/loader.rc. You are strongly advised > to create a backup copy of /boot/loader before testing (eg cp /boot/loader > /boot/loader_forth), since you'll need to boot that from boot2 if something > goes wrong. I've tested it extensively, though, with userboot.so and it's > test program, so all the initial kinks of finding the lua scripts, etc have > been worked out. > > While it's possible to build all the /boot/loader variants with Lua, I've > just tested a BIOS booting /boot/loader both with and without menus > enabled. I've not tested any of the other variants and the instructions for > testing some of them may be rather tedious (especially UEFI, if you want a > simple path to back out). Since there's not been full convergence testing, > you'll almost certainly find bumps in this system. Also, all the > build-system APIs are likely not yet final. > > I put MFC after a month on the commit. Due to the heroic (dare I say > almost crazy) work of Kyle Evans on merging all the revs from -current to > 11, I'm planning a MFC to 11 after the co-existence issues are hammered > out. In 11, FORTH will be the default, and Lua will be built by default, > but users will have to do something to use it. 12, both FORTH and Lua will > be built and installed, with Lua as default (barring unforeseen > complications). Once the co-existence stuff goes in, I imagine we'll make > the switch to Lua by default shortly after that. In 13, FORTH will be > removed unless there's a really really compelling case made to keep it. > > So please give it a spin and give me any feedback, documentation updates > and/or bug fixes. I'm especially interested in reviews from people that > have embedded Lua in other projects or experts in Lua that can improve the > robustness of the menu code. Do you have some memory usage numbers for LUA vs forth for the different BIOS loaders (text/data/bss sizes)? For the EFI case we probably have lots of room, but for the non-EFI case we are constrained to 0xa0000 - 0xa000 for the text/data/bss and stack (in some cases like PXE booting the top can be lower than 0xa0000). I'm not sure if we have any other platforms with similar memory constraints. -- John Baldwin From owner-freebsd-current@freebsd.org Mon Feb 12 21:28:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCB8DF1E7BD for ; Mon, 12 Feb 2018 21:28:11 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D5076EB64; Mon, 12 Feb 2018 21:28:11 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 0F499EE1C; Mon, 12 Feb 2018 21:28:11 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id EEA3A8189; Mon, 12 Feb 2018 21:28:09 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id lOfXiHFCBuho; Mon, 12 Feb 2018 21:28:07 +0000 (UTC) Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com 5052E8184 To: Vladimir Zakharov , David Wolfskill Cc: freebsd-current@freebsd.org References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> <20180212145430.r5ygphq3yskm7gxi@vzakharov> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: Date: Mon, 12 Feb 2018 13:27:56 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180212145430.r5ygphq3yskm7gxi@vzakharov> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yn9XXJ8VpPX900SrDDfJzVyBMKzhzwCvB" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 21:28:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --yn9XXJ8VpPX900SrDDfJzVyBMKzhzwCvB Content-Type: multipart/mixed; boundary="uLCcFQvc19NLicarwfI9Epwvrk3UFQ5ep"; protected-headers="v1" From: Bryan Drewery To: Vladimir Zakharov , David Wolfskill Cc: freebsd-current@freebsd.org Message-ID: Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> <20180212145430.r5ygphq3yskm7gxi@vzakharov> In-Reply-To: <20180212145430.r5ygphq3yskm7gxi@vzakharov> --uLCcFQvc19NLicarwfI9Epwvrk3UFQ5ep Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2/12/2018 6:54 AM, Vladimir Zakharov wrote: > Hello, Bryan! >=20 > On Fri, Feb 09, 2018, Bryan Drewery wrote: >> On 2/1/2018 1:10 AM, Vladimir Zakharov wrote: >>> Hello! >>> >>> For some time (about a week) building and installing kernel fails wit= h >>> the error "Variable OBJTOP is recursive." when going to build/install= >>> module from ports. >>> >>> Last successful build was at r328426. Next build at r328527 failed an= d >>> still broken at r328649. >>> >>> Without PORTS_MODULES building and installing kernel succeeds. Anothe= r >>> workaround: ignore error and build/install module directly from ports= =2E >>> >>> # cat /etc/make.conf >>> MALLOC_PRODUCTION=3Dyes >>> KERNCONF=3DGENERIC-NODEBUG GENERIC >>> #KERNCONF=3D GENERIC-NODEBUG >>> CPUTYPE?=3Dnative >>> #PORTS_MODULES =3D graphics/drm-next-kmod emulators/virtualbox-ose-km= od >>> PORTS_MODULES =3D graphics/drm-next-kmod=20 >>> >>> DOC_LANG =3D en_US.ISO8859-1 ru_RU.KOI8-R=20 >>> >>> WITH_DEBUG_PORTS =3D mail/neomutt >>> >>> WITH_CCACHE_BUILD=3Dyes >>> CCACHE_DIR=3D/home/ccache >>> >>> #DEVELOPER=3Dyes >>> >>> ... >>> Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.ful= l >>> --- kernel.full --- >>> linking kernel.full >>> ctfmerge -L VERSION -g -o kernel.full ... >>> text data bss dec hex filename >>> 22584632 1376209 4748888 28709729 0x1b61361 kernel.full >>> Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel.deb= ug >>> Building /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/kernel >>> --- all --- >>> =3D=3D=3D> Ports module graphics/drm-next-kmod (all) >>> cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env -u CC -u CXX= >>> -u CPP -u MAKESYSPATH MAKEFLAGS=3D"-j 4 -J 15,16 -j 4 -J 15,16 -D >>> NO_MODULES_OBJ .MAKE.LEVEL.ENV=3DMAKELEVEL KERNEL=3Dkernel TARGET=3Da= md64 >>> TARGET_ARCH=3Damd64" SYSDIR=3D/usr/src/sys >>> PATH=3D >>> SRC_BASE=3D/usr/src OSVERSION=3D1200056 >>> WRKDIRPREFIX=3D/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make= -B >>> clean build >>> =3D=3D=3D> Cleaning for drm-next-kmod-g20180117 >>> =3D=3D=3D> License BSD2CLAUSE MIT GPLv2 accepted by the user >>> =3D=3D=3D> drm-next-kmod-g20180117 depends on file: /usr/local/sbin= /pkg - found >>> =3D=3D=3D> Fetching all distfiles required by drm-next-kmod-g20180117= for building >>> =3D=3D=3D> Extracting for drm-next-kmod-g20180117 >>> =3D> SHA256 Checksum OK for FreeBSDDesktop-kms-drm-g20180117-622fdd1_= GH0.tar.gz. >>> =3D=3D=3D> Patching for drm-next-kmod-g20180117 >>> =3D=3D=3D> drm-next-kmod-g20180117 depends on file: /usr/local/bin/= ccache - found >>> =3D=3D=3D> Configuring for drm-next-kmod-g20180117 >>> =3D=3D=3D> Building for drm-next-kmod-g20180117 >>> =3D=3D=3D> drm (all) >>> Variable OBJTOP is recursive. >> >> For some reason I cannot recreate this issue. >=20 > It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. > At least, removing it fixes build for me. >=20 > Build successful with the following settings: > # cat /etc/src-env.conf > WITH_META_MODE=3D > #WITH_AUTO_OBJ=3D >=20 > # env | grep MAKE > MAKEOBJDIRPREFIX=3D/home/obj >=20 > # cat /etc/make.conf > MALLOC_PRODUCTION=3Dyes > KERNCONF=3D GENERIC-NODEBUG > CPUTYPE?=3Dnative > PORTS_MODULES=3D graphics/drm-next-kmod=20 > DOC_LANG =3D en_US.ISO8859-1 ru_RU.KOI8-R=20 > WITH_DEBUG_PORTS =3D mail/neomutt > WITH_CCACHE_BUILD=3Dyes > CCACHE_DIR=3D/home/ccache > DEVELOPER=3Dyes >=20 Please try this patch (requires a buildkernel). https://people.freebsd.org/~bdrewery/patches/kernel-portsmodules.diff --=20 Regards, Bryan Drewery --uLCcFQvc19NLicarwfI9Epwvrk3UFQ5ep-- --yn9XXJ8VpPX900SrDDfJzVyBMKzhzwCvB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJaggbmAAoJEDXXcbtuRpfPzUkH/jCje82VTQvEKpiqnJE1BvpS nG7VO7/1C2dY5ser/JDDUvxe/37pHHtMKk912TgIp2A/qSCc8t7DD58u95xSY7KT IqT3vnmnwXK8a3Pgxex8qxO4BCnm8W3WdBW2LelFbRcvMyQk1Uya6g3xGUTnp9Nj AIZkV3jo1Bz7D/FEvVQkpB8RhZixI5nMV9dwtUKgkqIwGxMbCxk3THmJ8j+rvyBu caUU/kMlOlapQlZxmg6NloX8b6HUTkmbrjJf1mwvB4OWud+pkcsDE3Pmn5COJ4vW P4pdAcpWRs/v6fkFrwgiU4NVUibsOl7+uataMguPVYNE4B7BbgzAwDw0KErkSAM= =P7fM -----END PGP SIGNATURE----- --yn9XXJ8VpPX900SrDDfJzVyBMKzhzwCvB-- From owner-freebsd-current@freebsd.org Mon Feb 12 21:31:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B64AFF1EEBA for ; Mon, 12 Feb 2018 21:31:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C8146EF03 for ; Mon, 12 Feb 2018 21:31:47 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id g14so12721811iob.9 for ; Mon, 12 Feb 2018 13:31:47 -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=DGmRnoDVfFu1tE31Bmj1rCcPAf9d5RSFHMLI2FvLzOI=; b=LUHDF7jpMJKhbGT2ZcHSSzDVR8GKrUoMUR5PRH+5cvwU04qaukBVzbFPOd/iFOSGeT vlnGxdIxOylSW10bJO9l4oN1t7NnT344G8zlA/7Um+Z9SBablB5Imr9XcwqjGap3x95B 9p4lmgU8b287AoMqioR7mso2Y/I7txOpP6Bv8voyGIhXjTD+8GpXaVqDkDRa9USAW2Nw gY/n0dVbYeo7YNLGS4SCE8pPEQMrnHzGojUlEVaKI4WgrJXVB0PB1tr6kEsoYJllFnC5 Qmm09qteSm2ykbmcr/mvfFaCy+gilA93TuWtRKrtOZr+c7hFzsH82QcMrGxXjnFmFcK5 ZIDA== 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=DGmRnoDVfFu1tE31Bmj1rCcPAf9d5RSFHMLI2FvLzOI=; b=opfSuaG+A5dBbVRv6fo0KiLVhp9UOz35UzlLzwC5oWQXgYCR1mywDsECAaP8MlkqX2 lETxC3H6qmmHZGfSsdw3ojm6WJFX1dUD90w7S0FstuKu7kunL6PKjNThtkmVEGtj2VKG MIdy2GbOQ5FrdFzu/ldC8CEazSf8UfZEjZdERKxBGj5s+nQa34Y//0wag3YPeSNkPMpZ mphto2YQN2x47ooSRuM9yzw+YSaD824BiXJNVUbuIlE2OkJKmVXi3GQ82cM0Bug1kFnw MgmTo94iHTozcK2JWLp3YruO5hguQ6igCPELXVTsvnTXWmqg3eZBq0qC1iEr904dWBys GBww== X-Gm-Message-State: APf1xPB3j4+4Qn2kEU87aPEjJfK3bsf1AB7o+E0XP8SqGhOSuSVQKCPp CF/3g6FxWWLn2bWgtSPNAgkyEdZJQH4n8o/XTAYmUPkD X-Google-Smtp-Source: AH8x2273cq7ZZAP2rqurJ61hjT46fOR3aVO6+Iolatr/kpkXQJrX4Xh2aU+Gj6kxbgf8XE5RXgSEjDWuSK1a8qSWKXs= X-Received: by 10.107.172.130 with SMTP id v124mr10619054ioe.301.1518471106662; Mon, 12 Feb 2018 13:31:46 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Mon, 12 Feb 2018 13:31:46 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <2333272.J6kp8cXjfh@ralph.baldwin.cx> References: <2333272.J6kp8cXjfh@ralph.baldwin.cx> From: Warner Losh Date: Mon, 12 Feb 2018 14:31:46 -0700 X-Google-Sender-Auth: xs41IuxZ-W7dDQQvi-IIWO15TZQ Message-ID: Subject: Re: LUA boot loader coming very soon To: John Baldwin Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 21:31:48 -0000 On Mon, Feb 12, 2018 at 10:12 AM, John Baldwin wrote: > On Monday, February 12, 2018 08:27:27 AM Warner Losh wrote: > > Greetings, > > > > As you may know, the Lua (http://www.lua.org) boot loader has been in > the > > works for some time. It started out life as a GSoC in 2014 by Pedro Souza > > mentored by Wojciech A. Koszek. Rui Paulo created a svn project branch to > > try to integrate it. I rebased that effort into a github branch which > Pedro > > Arthur fixed up. Over the past year, I've been cleaning up the boot > loader > > for other reasons, and found the time was ripe to start integrating this > > into the tree. However, those integration efforts have taken a while as > my > > day-job work on the boot loader took priority. In the mean time, Ed Maste > > and the FreeBSD Foundation funded Zakary Nafziger to enhance the original > > GSoC Lua scripts to bring it closer to parity with the evolution of the > > FORTH menu system since the GSoC project started. > > > > I'm pleased to announce that all these threads of development have > > converged and I'll be pushing the FreeBSD Lua Loader later today. This > > loader uses Lua as its scripting language instead of FORTH. While > > co-existance is planned, the timeline for it is looking to be a few weeks > > and I didn't want to delay pushing this into the tree for that. > > > > To try the loader, you'll need to build WITHOUT_FORTH=yes and > > WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to do this, > > you can do it in src/stand and install the result (be sure to have the > > options for both the build and the install). This will replace your > current > > /boot/loader that is scripted with FORTH to one that's scripted with Lua. > > It will install the lua scripts in /boot/lua. The boot is scripted with > > /boot/lua/loader.lua instead of /boot/loader.rc. You are strongly advised > > to create a backup copy of /boot/loader before testing (eg cp > /boot/loader > > /boot/loader_forth), since you'll need to boot that from boot2 if > something > > goes wrong. I've tested it extensively, though, with userboot.so and it's > > test program, so all the initial kinks of finding the lua scripts, etc > have > > been worked out. > > > > While it's possible to build all the /boot/loader variants with Lua, I've > > just tested a BIOS booting /boot/loader both with and without menus > > enabled. I've not tested any of the other variants and the instructions > for > > testing some of them may be rather tedious (especially UEFI, if you want > a > > simple path to back out). Since there's not been full convergence > testing, > > you'll almost certainly find bumps in this system. Also, all the > > build-system APIs are likely not yet final. > > > > I put MFC after a month on the commit. Due to the heroic (dare I say > > almost crazy) work of Kyle Evans on merging all the revs from -current to > > 11, I'm planning a MFC to 11 after the co-existence issues are hammered > > out. In 11, FORTH will be the default, and Lua will be built by default, > > but users will have to do something to use it. 12, both FORTH and Lua > will > > be built and installed, with Lua as default (barring unforeseen > > complications). Once the co-existence stuff goes in, I imagine we'll make > > the switch to Lua by default shortly after that. In 13, FORTH will be > > removed unless there's a really really compelling case made to keep it. > > > > So please give it a spin and give me any feedback, documentation updates > > and/or bug fixes. I'm especially interested in reviews from people that > > have embedded Lua in other projects or experts in Lua that can improve > the > > robustness of the menu code. > > Do you have some memory usage numbers for LUA vs forth for the different > BIOS loaders (text/data/bss sizes)? For the EFI case we probably have lots > of room, but for the non-EFI case we are constrained to 0xa0000 - 0xa000 > for the text/data/bss and stack (in some cases like PXE booting the top > can be lower than 0xa0000). I'm not sure if we have any other platforms > with similar memory constraints. > Lua is about 60-70k larger than FORTH for this application: Forth based: -r-xr-xr-x 1 root wheel 385024 Feb 12 14:14 /home/imp/roots/amd64/boot/loader -r-xr-xr-x 1 root wheel 450560 Feb 12 14:14 /home/imp/roots/amd64/boot/zfsloader Lua based: -r-xr-xr-x 1 root wheel 450560 Feb 12 14:20 /home/imp/roots/amd64/boot/loader -r-xr-xr-x 1 root wheel 520192 Feb 12 14:20 /home/imp/roots/amd64/boot/zfsloader So with Lua: % size loader.bin text data bss dec hex filename 411840 22264 48304 482408 0x75c68 loader.bin % size zfsloader.bin text data bss dec hex filename 478712 22968 52368 554048 0x87440 zfsloader.bin so we're at 555k out of 640k before we look at heap usage. Of course, these numbers are only going to get a lot worse as we pile-in new crypto features... I know that the normal loader works, but I've not tried the zfsloader. We might be able to do some slimming of LUA. I've honestly not tried super-hard to do that, but do presently omit a lot of the standard libraries which saves some space. Warner From owner-freebsd-current@freebsd.org Mon Feb 12 21:54:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23170F20C9C for ; Mon, 12 Feb 2018 21:54:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ADF0D7028A for ; Mon, 12 Feb 2018 21:54:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 9E98F10A8C2; Mon, 12 Feb 2018 16:54:09 -0500 (EST) From: John Baldwin To: Warner Losh Cc: FreeBSD Current Subject: Re: LUA boot loader coming very soon Date: Mon, 12 Feb 2018 13:53:59 -0800 Message-ID: <27682255.x3aPd9zKdx@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: References: <2333272.J6kp8cXjfh@ralph.baldwin.cx> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 12 Feb 2018 16:54:09 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 21:54:11 -0000 On Monday, February 12, 2018 02:31:46 PM Warner Losh wrote: > On Mon, Feb 12, 2018 at 10:12 AM, John Baldwin wrote: > > > On Monday, February 12, 2018 08:27:27 AM Warner Losh wrote: > > > Greetings, > > > > > > As you may know, the Lua (http://www.lua.org) boot loader has been in > > the > > > works for some time. It started out life as a GSoC in 2014 by Pedro Souza > > > mentored by Wojciech A. Koszek. Rui Paulo created a svn project branch to > > > try to integrate it. I rebased that effort into a github branch which > > Pedro > > > Arthur fixed up. Over the past year, I've been cleaning up the boot > > loader > > > for other reasons, and found the time was ripe to start integrating this > > > into the tree. However, those integration efforts have taken a while as > > my > > > day-job work on the boot loader took priority. In the mean time, Ed Maste > > > and the FreeBSD Foundation funded Zakary Nafziger to enhance the original > > > GSoC Lua scripts to bring it closer to parity with the evolution of the > > > FORTH menu system since the GSoC project started. > > > > > > I'm pleased to announce that all these threads of development have > > > converged and I'll be pushing the FreeBSD Lua Loader later today. This > > > loader uses Lua as its scripting language instead of FORTH. While > > > co-existance is planned, the timeline for it is looking to be a few weeks > > > and I didn't want to delay pushing this into the tree for that. > > > > > > To try the loader, you'll need to build WITHOUT_FORTH=yes and > > > WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to do this, > > > you can do it in src/stand and install the result (be sure to have the > > > options for both the build and the install). This will replace your > > current > > > /boot/loader that is scripted with FORTH to one that's scripted with Lua. > > > It will install the lua scripts in /boot/lua. The boot is scripted with > > > /boot/lua/loader.lua instead of /boot/loader.rc. You are strongly advised > > > to create a backup copy of /boot/loader before testing (eg cp > > /boot/loader > > > /boot/loader_forth), since you'll need to boot that from boot2 if > > something > > > goes wrong. I've tested it extensively, though, with userboot.so and it's > > > test program, so all the initial kinks of finding the lua scripts, etc > > have > > > been worked out. > > > > > > While it's possible to build all the /boot/loader variants with Lua, I've > > > just tested a BIOS booting /boot/loader both with and without menus > > > enabled. I've not tested any of the other variants and the instructions > > for > > > testing some of them may be rather tedious (especially UEFI, if you want > > a > > > simple path to back out). Since there's not been full convergence > > testing, > > > you'll almost certainly find bumps in this system. Also, all the > > > build-system APIs are likely not yet final. > > > > > > I put MFC after a month on the commit. Due to the heroic (dare I say > > > almost crazy) work of Kyle Evans on merging all the revs from -current to > > > 11, I'm planning a MFC to 11 after the co-existence issues are hammered > > > out. In 11, FORTH will be the default, and Lua will be built by default, > > > but users will have to do something to use it. 12, both FORTH and Lua > > will > > > be built and installed, with Lua as default (barring unforeseen > > > complications). Once the co-existence stuff goes in, I imagine we'll make > > > the switch to Lua by default shortly after that. In 13, FORTH will be > > > removed unless there's a really really compelling case made to keep it. > > > > > > So please give it a spin and give me any feedback, documentation updates > > > and/or bug fixes. I'm especially interested in reviews from people that > > > have embedded Lua in other projects or experts in Lua that can improve > > the > > > robustness of the menu code. > > > > Do you have some memory usage numbers for LUA vs forth for the different > > BIOS loaders (text/data/bss sizes)? For the EFI case we probably have lots > > of room, but for the non-EFI case we are constrained to 0xa0000 - 0xa000 > > for the text/data/bss and stack (in some cases like PXE booting the top > > can be lower than 0xa0000). I'm not sure if we have any other platforms > > with similar memory constraints. > > > > Lua is about 60-70k larger than FORTH for this application: > > Forth based: > -r-xr-xr-x 1 root wheel 385024 Feb 12 14:14 > /home/imp/roots/amd64/boot/loader > -r-xr-xr-x 1 root wheel 450560 Feb 12 14:14 > /home/imp/roots/amd64/boot/zfsloader > Lua based: > -r-xr-xr-x 1 root wheel 450560 Feb 12 14:20 > /home/imp/roots/amd64/boot/loader > -r-xr-xr-x 1 root wheel 520192 Feb 12 14:20 > /home/imp/roots/amd64/boot/zfsloader > > So with Lua: > % size loader.bin > text data bss dec hex filename > 411840 22264 48304 482408 0x75c68 loader.bin > % size zfsloader.bin > text data bss dec hex filename > 478712 22968 52368 554048 0x87440 zfsloader.bin > > so we're at 555k out of 640k before we look at heap usage. Of course, these > numbers are only going to get a lot worse as we pile-in new crypto > features... I know that the normal loader works, but I've not tried the > zfsloader. Woof, on stable/11 the forth ones are quite a bit smaller: -r-xr-xr-x 1 root wheel 315392 Dec 16 13:39 /boot/loader -r-xr-xr-x 1 root wheel 356352 Dec 16 13:39 /boot/zfsloader % size /usr/obj/usr/src/sys/boot/i386/loader/loader.bin text data bss dec hex filename 274913 22624 46560 344097 0x54021 /usr/obj/usr/src/sys/boot/i386/loader/loader.bin % size /usr/obj/usr/src/sys/boot/i386/zfsloader/zfsloader.bin text data bss dec hex filename 313865 23184 50624 387673 0x5ea59 /usr/obj/usr/src/sys/boot/i386/zfsloader/zfsloader.bin Note that it's not 640k, it's 0xa0000 (640k) - the start address of the loader: 0xa000 (40k), so text/data/bss + stack has 600k of room. The heap isn't in low memory anymore, so we don't have to worry about that. 555k for ZFS loader leaves around 45k for stack. If the ZFS loader code is anything like the kernel code then ZFS probably uses deeper stacks than UFS. :( One of the larger uses of stack in the loader is probably gzipfs, so loading a mfsroot.gz from the loader might be a good test. Unfortunately, there isn't a good way to really detect stack overflow other than silent corruption in bss. If we could create a 'volatile int canary' in the bss and force it to be the last thing in the bss we could check the value of 'canary' in the loader's main loop perhaps and complain if it is ever non-zero. -- John Baldwin From owner-freebsd-current@freebsd.org Mon Feb 12 22:25:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A73EF22F5B for ; Mon, 12 Feb 2018 22:25:45 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F75371C9E for ; Mon, 12 Feb 2018 22:25:44 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22a.google.com with SMTP id 72so19087549iom.10 for ; Mon, 12 Feb 2018 14:25:44 -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=OCjxLaknND19iV4aWf/kzbMniI5lEGN+ui2BvsR6ZTo=; b=tau21zr7HfH9rz5nC+IWFTntM5zkG65IFBZjVmYITZf9erxz1SoQ/E3GnUN8GHp2YS 7vzCvUZqwOTkZ5/6eDHzyV8jYo3zzE6JcjwMVNOsijc2ZiemMrjzVqzmYt1sBIsgRVkE Gjon6BiRk1+hDo4+I1IB0iDZck/7E/uBr1ZpnvJNK92Bh1+yWSEeeYIWm3vHp7/vjfui J+S4802M403mdWi3Q/6vQbDNx5IAnfWfCF3sdSt1S7848dHa1kExHhbmIhiQItdQZn7n iU4Rbl2Rxs+cvSIwyqbbtD3u5QPcswy6XsZnMfm2KIptZNd4B9D9MCTQBnueaLzsK/6J XwEQ== 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=OCjxLaknND19iV4aWf/kzbMniI5lEGN+ui2BvsR6ZTo=; b=gOp9NF2Rg1RZBMGLpiA5mN0jH2uQrxJOlFl4oEWh2vp4ytaNicRYEwixZtYT5lDA8+ 9eyNFC+6PM8NpmkIGHIZnCQ6w4FNYejPTBMsVAnnu1x/OFQsFOSUsME+V5UtGaRU6idx NhZpq+k86JFi8oIU648NT2K4JUxe14yMHoW6V+owLSoj4uHD0hD3orNO1wzi5gRhe0qx OkmbbQaQE9362AyOdGNt2/pZY8q+aOneTG6dilQMDhde6KBIGBezv31NIkIbjRFcw89G jn/eGFfof0R/E6kBQnFD+bi8SacxFvFahXeHj4/3sPdgH12uhK2sZ6CBBn6NBGS4NmDR EYfw== X-Gm-Message-State: APf1xPC/LBFLLImOmSJ26pwwmsOx29n7bO75jcChB7VaQ4jxx8qWClcR BpqhzTekRwxMsLoQpFGac8+OZEyZddxjTzXq+6kWVA== X-Google-Smtp-Source: AH8x226BfOmSY8tIFr6QB8txAC3Q+gQOTuULnxdjT13ISU17RXQCRuATVOntK99R0Z4avcoImDfn4DevsLNDW/zi4TU= X-Received: by 10.107.88.12 with SMTP id m12mr13763694iob.136.1518474343568; Mon, 12 Feb 2018 14:25:43 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Mon, 12 Feb 2018 14:25:42 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <27682255.x3aPd9zKdx@ralph.baldwin.cx> References: <2333272.J6kp8cXjfh@ralph.baldwin.cx> <27682255.x3aPd9zKdx@ralph.baldwin.cx> From: Warner Losh Date: Mon, 12 Feb 2018 15:25:42 -0700 X-Google-Sender-Auth: N5gTaZknxEsubZX3KBCwYbXaVk4 Message-ID: Subject: Re: LUA boot loader coming very soon To: John Baldwin Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 22:25:45 -0000 On Mon, Feb 12, 2018 at 2:53 PM, John Baldwin wrote: > On Monday, February 12, 2018 02:31:46 PM Warner Losh wrote: > > On Mon, Feb 12, 2018 at 10:12 AM, John Baldwin wrote: > > > > > On Monday, February 12, 2018 08:27:27 AM Warner Losh wrote: > > > > Greetings, > > > > > > > > As you may know, the Lua (http://www.lua.org) boot loader has been > in > > > the > > > > works for some time. It started out life as a GSoC in 2014 by Pedro > Souza > > > > mentored by Wojciech A. Koszek. Rui Paulo created a svn project > branch to > > > > try to integrate it. I rebased that effort into a github branch which > > > Pedro > > > > Arthur fixed up. Over the past year, I've been cleaning up the boot > > > loader > > > > for other reasons, and found the time was ripe to start integrating > this > > > > into the tree. However, those integration efforts have taken a while > as > > > my > > > > day-job work on the boot loader took priority. In the mean time, Ed > Maste > > > > and the FreeBSD Foundation funded Zakary Nafziger to enhance the > original > > > > GSoC Lua scripts to bring it closer to parity with the evolution of > the > > > > FORTH menu system since the GSoC project started. > > > > > > > > I'm pleased to announce that all these threads of development have > > > > converged and I'll be pushing the FreeBSD Lua Loader later today. > This > > > > loader uses Lua as its scripting language instead of FORTH. While > > > > co-existance is planned, the timeline for it is looking to be a few > weeks > > > > and I didn't want to delay pushing this into the tree for that. > > > > > > > > To try the loader, you'll need to build WITHOUT_FORTH=yes and > > > > WITH_LOADER_LUA=yes. Fortunately, you needn't do a full world to do > this, > > > > you can do it in src/stand and install the result (be sure to have > the > > > > options for both the build and the install). This will replace your > > > current > > > > /boot/loader that is scripted with FORTH to one that's scripted with > Lua. > > > > It will install the lua scripts in /boot/lua. The boot is scripted > with > > > > /boot/lua/loader.lua instead of /boot/loader.rc. You are strongly > advised > > > > to create a backup copy of /boot/loader before testing (eg cp > > > /boot/loader > > > > /boot/loader_forth), since you'll need to boot that from boot2 if > > > something > > > > goes wrong. I've tested it extensively, though, with userboot.so and > it's > > > > test program, so all the initial kinks of finding the lua scripts, > etc > > > have > > > > been worked out. > > > > > > > > While it's possible to build all the /boot/loader variants with Lua, > I've > > > > just tested a BIOS booting /boot/loader both with and without menus > > > > enabled. I've not tested any of the other variants and the > instructions > > > for > > > > testing some of them may be rather tedious (especially UEFI, if you > want > > > a > > > > simple path to back out). Since there's not been full convergence > > > testing, > > > > you'll almost certainly find bumps in this system. Also, all the > > > > build-system APIs are likely not yet final. > > > > > > > > I put MFC after a month on the commit. Due to the heroic (dare I say > > > > almost crazy) work of Kyle Evans on merging all the revs from > -current to > > > > 11, I'm planning a MFC to 11 after the co-existence issues are > hammered > > > > out. In 11, FORTH will be the default, and Lua will be built by > default, > > > > but users will have to do something to use it. 12, both FORTH and Lua > > > will > > > > be built and installed, with Lua as default (barring unforeseen > > > > complications). Once the co-existence stuff goes in, I imagine we'll > make > > > > the switch to Lua by default shortly after that. In 13, FORTH will be > > > > removed unless there's a really really compelling case made to keep > it. > > > > > > > > So please give it a spin and give me any feedback, documentation > updates > > > > and/or bug fixes. I'm especially interested in reviews from people > that > > > > have embedded Lua in other projects or experts in Lua that can > improve > > > the > > > > robustness of the menu code. > > > > > > Do you have some memory usage numbers for LUA vs forth for the > different > > > BIOS loaders (text/data/bss sizes)? For the EFI case we probably have > lots > > > of room, but for the non-EFI case we are constrained to 0xa0000 - > 0xa000 > > > for the text/data/bss and stack (in some cases like PXE booting the top > > > can be lower than 0xa0000). I'm not sure if we have any other > platforms > > > with similar memory constraints. > > > > > > > Lua is about 60-70k larger than FORTH for this application: > > > > Forth based: > > -r-xr-xr-x 1 root wheel 385024 Feb 12 14:14 > > /home/imp/roots/amd64/boot/loader > > -r-xr-xr-x 1 root wheel 450560 Feb 12 14:14 > > /home/imp/roots/amd64/boot/zfsloader > > Lua based: > > -r-xr-xr-x 1 root wheel 450560 Feb 12 14:20 > > /home/imp/roots/amd64/boot/loader > > -r-xr-xr-x 1 root wheel 520192 Feb 12 14:20 > > /home/imp/roots/amd64/boot/zfsloader > > > > So with Lua: > > % size loader.bin > > text data bss dec hex filename > > 411840 22264 48304 482408 0x75c68 loader.bin > > % size zfsloader.bin > > text data bss dec hex filename > > 478712 22968 52368 554048 0x87440 zfsloader.bin > > > > so we're at 555k out of 640k before we look at heap usage. Of course, > these > > numbers are only going to get a lot worse as we pile-in new crypto > > features... I know that the normal loader works, but I've not tried the > > zfsloader. > > Woof, on stable/11 the forth ones are quite a bit smaller: > > -r-xr-xr-x 1 root wheel 315392 Dec 16 13:39 /boot/loader > -r-xr-xr-x 1 root wheel 356352 Dec 16 13:39 /boot/zfsloader > > % size /usr/obj/usr/src/sys/boot/i386/loader/loader.bin > text data bss dec hex filename > 274913 22624 46560 344097 0x54021 /usr/obj/usr/src/sys/boot/ > i386/loader/loader.bin > % size /usr/obj/usr/src/sys/boot/i386/zfsloader/zfsloader.bin > text data bss dec hex filename > 313865 23184 50624 387673 0x5ea59 /usr/obj/usr/src/sys/boot/ > i386/zfsloader/zfsloader.bin > > Note that it's not 640k, it's 0xa0000 (640k) - the start address of the > loader: 0xa000 (40k), so text/data/bss + stack has 600k of room. The heap > isn't in low memory anymore, so we don't have to worry about that. 555k > for > ZFS loader leaves around 45k for stack. If the ZFS loader code is anything > like the kernel code then ZFS probably uses deeper stacks than UFS. :( > Yea. We support more FS types than in 11 now I think (at least more than in 10), so we might want to look to trimming that. I don't think we need 3 different compressed filesystem formats compiled in by default, for example... > One of the larger uses of stack in the loader is probably gzipfs, so > loading > a mfsroot.gz from the loader might be a good test. Unfortunately, there > isn't > a good way to really detect stack overflow other than silent corruption in > bss. If we could create a 'volatile int canary' in the bss and force it > to be > the last thing in the bss we could check the value of 'canary' in the > loader's > main loop perhaps and complain if it is ever non-zero. > That's not a terrible idea... Assuming that the corruption is such that it's right at the end of bss, and not something a bit before it... Warner From owner-freebsd-current@freebsd.org Tue Feb 13 08:02:27 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40925F076E8 for ; Tue, 13 Feb 2018 08:02:27 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D8C669E72; Tue, 13 Feb 2018 08:02:26 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id h78so16719378lfg.6; Tue, 13 Feb 2018 00:02:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=MCo1suAOTO2dVcc83mjQ5lXiRUCaLprfpV11qMZKQNc=; b=PzW2RCIA0YFXhi9H/SCQZYG6RVxACcSY9sMmGKICVNqiiY0qDR0ro2nqApo8KTfBIj N4HfFfa8BXgxKnhDQKL0BX7qL8kupjHK84X5DFgNDrh4HncFEnYvR+nGCUpsIHsQOHCG Jl6iMROZvy8pcPUGkGnfSyz5bwuOqU3hQPZHBWpMcJfy2Au6TLSHDy5XchTN6EVSqcZ1 /KAn2W7tLY8yP2AeBqID43uiUb6MaMGtcsRf0rzzrbpYxT8GqIeuF/o1TBF4wJDkyA0F /RnST7jC0Plk6MihVEeqjbImqkP8qJeBkQXZLPI38eFeQPsdD7A5B+ex5ho/WPC89ro2 26pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=MCo1suAOTO2dVcc83mjQ5lXiRUCaLprfpV11qMZKQNc=; b=i2N0IwGcK1Aum+6vu5n2q/B4Rp9bZ5wyBE0R+f8kQNJCWmmuafAuEUhDxc4UaB0bHe HZTHhvLmjaa9miSG3A5iulWKxbvfYuA1r7a0hTwFlTyWD97zqE0RoKRjXizhlwcS6ZQJ iEk6hsUAn1P1GCevI5J89zUTjZO34p2iPuXaoNceveFRMP+DanIymTZJ5ZukcA2yV3n/ 0rfBMVfPK0mi3+/X/cVN7PBqyRqL+Lh8hvFRURlo9Q/wGXwGfAKijjLGnN6HwvBxV7cn +9AJDZOxnvEFGrpg2HXI46qJ7kQQzfWYzGAOOGST09BEXXfzes+0DB8wAFYOPuHZ1K95 kvYA== X-Gm-Message-State: APf1xPBHCA76oTKO2k6kUOHba2CwW5BUzsntwuATKUcgr0JhA8PpEr2C LSWRPQ+dwgL2cLkMSjQRkav4lg== X-Google-Smtp-Source: AH8x225ClCGymLA4Gr5cS6D/474COvnE4PdnpFYYnKvT23kxA0DVUqLa7R0XRYoFb5CDVEch6FpTdw== X-Received: by 10.46.88.27 with SMTP id m27mr299304ljb.132.1518508944573; Tue, 13 Feb 2018 00:02:24 -0800 (PST) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id 17sm119721ljj.9.2018.02.13.00.02.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 00:02:23 -0800 (PST) To: FreeBSD CURRENT , imp@freebsd.org From: "Alex V. Petrov" Subject: devd in r329188M don't start Message-ID: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> Date: Tue, 13 Feb 2018 15:02:21 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 08:02:27 -0000 after update, devd don't starting with: devd: Cannot parse /etc/devd/devmatch.conf at line 13 (file default!) If I disable it, don't work mouse in xorg. -- ----- Alex. From owner-freebsd-current@freebsd.org Tue Feb 13 08:04:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A93B4F078B6; Tue, 13 Feb 2018 08:04:11 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 15F3B69FA7; Tue, 13 Feb 2018 08:04:10 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MdEsh-1f2thG0D8V-00IQLk; Tue, 13 Feb 2018 09:04:05 +0100 Date: Tue, 13 Feb 2018 09:03:58 +0100 From: "O. Hartmann" To: Marko Zec Cc: "O. Hartmann" , "Bjoern A. Zeeb" , , freebsd-current Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <20180213090358.3729045e@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20180210095449.3117e6d9@x23> References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> <20180210095449.3117e6d9@x23> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:IsPhPT5Ge3OatU0uG11pn72RAKohf+PH+WTfKT42c/RQcw+iKkF GtkBa+cTfyzaOcCYn1wFrx81So9noKlwXmlDNTRqRGwFAUoWeqQwq5MS3Dz/B8yiriLpWiH QZ/vPcHhlsUMt1z2MSH9VyrmSLMSLdrJ/v7llmpjUgebAg9pt+pxHxaWpGwSFUNWGTiCOqv Z8EzzS7GV5P7Y5DbnvcrQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:UAuk+mpzsuk=:+3YKZZIw9EsdYfRqlU74ex 1iUZUifTxHQFfsd2okdgFssuWlGcd18rNP9fksc1WmS3j3pr4dEEQE1rPtUG6ealfMZAZMb/g 5uQggT3d32AHX3pGaGMNG6mbiaHm18wppyTGg72lpMsYc5FlpBeZNlwhqWJQ3Ur0sYOrh1waO JM7VMRaW/6fR5ry44lPEypNArABvzORPg/U2RelYStouQjggwHxcGx214kfLUtBCbqzWDNaTf I6PO3cP6ZF72x6voqZLxRCFq2Ba03lCCCHv3lTaS3bMHTb1dxRfiuuJFda6jXIJOyV7I7x0rB oaKXwakCvctAFZ2AA6YdYibnlWuG2Y0lF1+tT25Hfxa0275KFgI/1vB6ONkcCH7h2oNfbZdbJ 0bqAzEHcZ5IBrw5FfzoQLEPaHhH3hI+fvcI0IlVHBWgfag4FNumRhH9Jp1xeTqFA8U61B6LZL KKXLPH3+Cbo/DdQ9pBMqqY0NOAaCDmkn14TMxFAEnY+qLLnpg7AOpY+iv5ASuPOv7PLrtQimK S3yhfjOXyUgjH6cyhxSCne8FE+7FrEAS6DijhWsxAhMEB2GXP+HUXunPitgD9irLMOzO8CtcS A3gx0LKmB+u5JoXshYGivCEoxFG5sUwpcTnssogmn7jytZMN6MoFJANweXhTBPkhVsz9Qrnm4 vPeFdz13QUTJhNKWD4KVqUFjmIjlHYjJ4wxotnBztI3QmYb+R/VLKRXkQ7NFEt754PMU9oHdr 4xpPmbXR7CtXlTZLm7/KL9jK3X00DnFymJPzxce3SnNKuhTq9aEajvDuKlqmAV6QPU+QO7nnK oRhqjeaOtQRZ2H1aTOjFDh9/xFCxnaIpK34DrPO43Aol8ZJ0GE= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 08:04:12 -0000 On Sat, 10 Feb 2018 09:54:49 +0100 Marko Zec wrote: > On Sat, 10 Feb 2018 08:52:21 +0100 > "O. Hartmann" wrote: > > > Am Fri, 09 Feb 2018 16:43:17 +0000 > > "Bjoern A. Zeeb" schrieb: > > > > > On 9 Feb 2018, at 16:22, O. Hartmann wrote: > > > > > > > Am Thu, 8 Feb 2018 09:31:15 +0100 > > > > "O. Hartmann" schrieb: > > > > > > > > Is this problem to trivial? > > > > > > I read through it yesterday and found myself in the position that I > > > need a whiteboard or paper and pencil or an ASCII art of your > > > situation. But by the time I made it to the question I was > > > basically lost. Could you massively simplify this and maybe > > > produce the ASCII art? > > > > > > /bz > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to > > > "freebsd-current-unsubscribe@freebsd.org" > > > > All right. > > > > I'm not much of an artist and at this very moment, I haven't much > > experience with neat ASCII art tools. But I'll provide a sketch > > later, but I also will simplify the situation. > > > > Consider three "vswitches", basically based on the creation of > > bridges, bridge0, bridge1, bridge2. Create at least three individual > > vnet-jails attached to each vbridge. Those jails have epair pseudo > > devices. The jail itself owns the "a-part" of the epair and the > > b-part is "member of the bridge". Each jail's epairXXXa has an IP > > assigned of the network the vswitch is part of. I mention a- and > > b-part of the epair here, because I thought it could matter, but I > > think for symmetry reasons it doesn't. > > > > Now consider a further, special jail. This jail is supposed to have > > three epair devices, each one is reaching into one of the vbridges. > > This jail is the router/routing jail. Later, this jail should filter > > via IPFW the traffic between the three vbridges according to rules, > > but this doesn't matter here, beacuase the basics are not working as > > expected. > > > > Now the problems. It doesn't matter on which jail of the three > > vswitches I login, the moment a vbridge has more than two member > > epairs (one is alway member of the routing jail, now consider a > > database jail and a webserver jail), pinging each jail or the routing > > jail fails. It works sometimes for a couple of ICMP packets and then > > stops. > > > > If each vbridge has only one member jail, I have NO PROBLEMS > > traversing accordingly to the static routing rules from one vbridge > > to any other, say from vbridge1 to vbridge0 or vbridge2 and any > > permutation of that. > > > > The moment any of the bridges gets an additional member epair > > interface (so the bridge has at least three members including the on > > reaching into the virtual router jail) the vbridge seems to operate > > unpredictable (to me). Pinging jails memeber of that vbridge are > > unreachable. > > > > Technical information: > > > > The kernel has options IPFIREWALL, VIMAGE. The host's ipfw (kernel) > > declines packets by default. Each jail is configured to have ipfw > > "open". > > > > Thanks for the patience. > > If you could provide a script which sets up the topology you described > in two lengthy posts then others could reproduce this, and your chances > of getting useful feedback would certainly increase. > > We also have a graphical tool (https://github.com/imunes/imunes) which > can set up a topology like you described in a few clicks of a mouse, > albeit using netgraph and ng_eiface instead of epairs, but I assume this > is irellevant as long as you are not aiming for maximum packet > throughputs. If you attempt to use this tool, note that selecting > "stpswitch" will create if_bridge instances, whereas "lanswitch" > creates ng_bridge instances. > > Good luck, > > Marko > > > > > > Kind regards, > > > > O. Hartmann > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Hello Marko, thanks for your response. First of all: I looked at "imunes". From the first glimpse it looks great! Something really usefull; I regret not having a port for this tool or the chance to package it via poudriere. The problems I faced seem to be related to a bug Olivier Cochard-Labbe pointed me at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176671 Checking the MAC of the epairs created revealed, that either doubles or even more occur on the host side of the epair (in my case, all the b-parts of an epair), or, if there is nothing irregular, then the a-parts (owned by the VIMAGE jail) have same MAC. The more jails I create, the more ambiguous MACs are present. It is the first time I ran into a more complex network topology and thanks for the hint using netgraph. Kind regards, Oliver From owner-freebsd-current@freebsd.org Tue Feb 13 08:07:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1185FF07DED for ; Tue, 13 Feb 2018 08:07:24 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 A68F26A1ED; Tue, 13 Feb 2018 08:07:23 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id E786E260809; Tue, 13 Feb 2018 09:07:21 +0100 (CET) Subject: Re: devd in r329188M don't start To: "Alex V. Petrov" , FreeBSD CURRENT , imp@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> From: Hans Petter Selasky Message-ID: <4c3e58ff-7c6a-578a-d629-01d4dc271bcf@selasky.org> Date: Tue, 13 Feb 2018 09:04:26 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 08:07:24 -0000 On 02/13/18 09:02, Alex V. Petrov wrote: > after update, devd don't starting with: > devd: Cannot parse /etc/devd/devmatch.conf at line 13 > > (file default!) > > If I disable it, don't work mouse in xorg. > I think there is a missing ";" at the end of line 13. Try adding one. --HPS From owner-freebsd-current@freebsd.org Tue Feb 13 08:10:57 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16E34F08294 for ; Tue, 13 Feb 2018 08:10:57 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 AAC8F6A541; Tue, 13 Feb 2018 08:10:56 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 9842D260809; Tue, 13 Feb 2018 09:10:55 +0100 (CET) Subject: Re: devd in r329188M don't start To: "Alex V. Petrov" , FreeBSD CURRENT , imp@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> From: Hans Petter Selasky Message-ID: Date: Tue, 13 Feb 2018 09:08:00 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 08:10:57 -0000 On 02/13/18 09:02, Alex V. Petrov wrote: > after update, devd don't starting with: > devd: Cannot parse /etc/devd/devmatch.conf at line 13 > > (file default!) > > If I disable it, don't work mouse in xorg. > https://svnweb.freebsd.org/changeset/base/329194 --HPS From owner-freebsd-current@freebsd.org Tue Feb 13 08:18:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A8B8F09202 for ; Tue, 13 Feb 2018 08:18:16 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 82AA96AFF7; Tue, 13 Feb 2018 08:18:15 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x231.google.com with SMTP id t79so23973151lfe.3; Tue, 13 Feb 2018 00:18:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=45Ie0rEASC0JeTuM+QgGfFSi3cW2hlwB0FdA6OkSltE=; b=aAoO3CAgdwZt+9dpMgC+iHYzrqcQeaGxGsgbpJOOJ+/8bHolV8J/6sgO6bACPqeL3f byj+Hzd1Im6RsZ87sAIpTYKhURnlUx0PdXUSB1Hk8VuaJPloJ79y++R15qSNFQVfxAdX gnzVaPaFxPq4qHqyTdrsWblIh59EMe5liWAbW0rkyhxp0DLeLLuZyFPh20s5gVpZWw9T CG4re6fwPmWYCQDmD92hNE8aaEOWRkmV/YeEw8hc4UNe2WwnW/cPC/PJzJg/R+L/YL2d JzjijHtFX9PwFtw6LB0mO1DvWhMYpnCG7PInfYr//vebPQGbcG90nddonoHzm4P7IaKe uW8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=45Ie0rEASC0JeTuM+QgGfFSi3cW2hlwB0FdA6OkSltE=; b=VEA+lAeXB8IUpiVxYu7FjArT0v68I3dxZ0NToV1A/qskIh7qqCmFiIQgnCdHyyBTrZ rANy6Wwc79TeARRryk9Bdc6vXW5AzzuGdbrCHpa1T9odpOkcAJJNVdpNhCXgVk+TKWiK cFAxkuzIdzC3U9Rfbx6+EFmGaK/A+CKMZG2LKNT1+JHgrgiXHTGJWt9Ds8H2qkf0+Vhw ccwpM2kL3xuvJxGwumb/i9v4TgX8DPo/0dfrZf84hCxeGZwpZalqwo2dj0aT1Khpsdjp sEJCEw+BD60ZLC8Mqfaa7qmynDfAmBBU+YBMrSYgTNa1M9INyLcO/uEJfeBfsbkhGu26 BZXg== X-Gm-Message-State: APf1xPCZ5CBX8DsKpo8tvwBwQwraZdoN4Y19LoEztUy+XkidreBjCyEF w0DwRd/VrUcV+NHzaQdkdI0fUK4T X-Google-Smtp-Source: AH8x224LO0ksB2bukOWTb6xoD1vT7DnNDZP38kNWEixgi/paqPaSRk0rjyGLvNhxoWXYZkjbcGzC1w== X-Received: by 10.46.114.10 with SMTP id n10mr347318ljc.74.1518509893914; Tue, 13 Feb 2018 00:18:13 -0800 (PST) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id c12sm1951178ljd.60.2018.02.13.00.18.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 00:18:12 -0800 (PST) Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , FreeBSD CURRENT , imp@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> From: "Alex V. Petrov" Message-ID: <35bd6f9e-6e18-a5a2-8d22-ee60a5ffbce9@gmail.com> Date: Tue, 13 Feb 2018 15:18:11 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 08:18:16 -0000 In /var/log/messages: devd: line 13: }: syntax error File /etc/devd/devmatch.conf (11-13 lines): nomatch 100 { action "service devmatch start" }; 13.02.2018 15:08, Hans Petter Selasky пишет: > On 02/13/18 09:02, Alex V. Petrov wrote: >> after update, devd don't starting with: >> devd: Cannot parse /etc/devd/devmatch.conf at line 13 >> >> (file default!) >> >> If I disable it, don't work mouse in xorg. >> > > https://svnweb.freebsd.org/changeset/base/329194 > > --HPS > -- ----- Alex. From owner-freebsd-current@freebsd.org Tue Feb 13 09:20:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18FFAF0DF93 for ; Tue, 13 Feb 2018 09:20:17 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84F8C6D81F; Tue, 13 Feb 2018 09:20:16 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x232.google.com with SMTP id t79so24192082lfe.3; Tue, 13 Feb 2018 01:20:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=g1b5h6TMVvoiRo+CUKEKOTLeaPCTpdOwbdvn1uy6VyY=; b=K/IgUTCPC8tbV4EBHWC93vtTqdnKgusy3dJe7XE7yMdgltBNa3wuCTzeF3UJfB1yoi s390j0qANYOQ4wwgZABiifIk9c0if20urCRNjHkqmoq880Q9w6NkT5twJRkYOI7cg8TC p/IkKShgcwqrwLn+uu+PPBAFMlOvYrxpG7jdYr/msNh0ehQfJHG8ZEc49zn3TMAgJpnc O9UNYIItpPmBsojzGtF7jlft39mI3uYef0rBfZKyBcYsmYYBCRa8cBRsG18YG1zCd9fe N8rWoCeokcPOwIqbcewz6V9yGaD4C0detXfZOexQLelWhxrSh+0TqtsOPkjm8IEuBzS1 4sUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=g1b5h6TMVvoiRo+CUKEKOTLeaPCTpdOwbdvn1uy6VyY=; b=SktwkYuQfGvDPDWNzoEHBL9GCLbNDnEW3AnIERjXVpA8B1qny4Z0XZ/alm5iPBKXNW QsCwWBSdS+bvPqGYZVz5MntBcxHwHN4gg1ynPar6vvM9Q46pjK5rBSVHvyxEYTrWqah9 8E5k1boBAzRVSSLLrym0P2OCRQDyr9DKCFc/EtOu8v3XA+7tkEZBBlhQUAyjWY+VhoIv qrC/uRMYeCnLNzH7ZwHhtAsChI1vEARvSnFWuhEjIxr/3TZ2qmtgHKDJBvf8DD2eugNo cT9kabEdkeH8YWPN50qlvfRRUiB0qyDOvKCIFCUAoT4YEN98Csrc2+maCO40gfyvMpLT VExw== X-Gm-Message-State: APf1xPD1ErakZuUiT5aBbf4xrWPIwYxyKKvB6mi+eqlcU/6AmN3yYwVh 4PnaabdqrNCL1bnNPXTqPc25audh X-Google-Smtp-Source: AH8x226LLWAcsz9CeRNowAIJfTAzPjLs5lGANMdUAR53TL2zoCEjr+cGxSNaghJT1MSS9HwJFY6llQ== X-Received: by 10.25.25.208 with SMTP id 199mr496471lfz.146.1518513614348; Tue, 13 Feb 2018 01:20:14 -0800 (PST) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id h13sm213532ljb.47.2018.02.13.01.20.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 01:20:13 -0800 (PST) Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , FreeBSD CURRENT , imp@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> From: "Alex V. Petrov" Message-ID: <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> Date: Tue, 13 Feb 2018 16:20:12 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 09:20:17 -0000 Mouse start work only after handly: kldload ums usb.conf is not found anywhere in the system. This is normal? 13.02.2018 15:08, Hans Petter Selasky пишет: > On 02/13/18 09:02, Alex V. Petrov wrote: >> after update, devd don't starting with: >> devd: Cannot parse /etc/devd/devmatch.conf at line 13 >> >> (file default!) >> >> If I disable it, don't work mouse in xorg. >> > > https://svnweb.freebsd.org/changeset/base/329194 > > --HPS > -- ----- Alex. From owner-freebsd-current@freebsd.org Tue Feb 13 09:22:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62A0FF0E3AB for ; Tue, 13 Feb 2018 09:22:11 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 048A66DBF3; Tue, 13 Feb 2018 09:22:10 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 95A6C2600EC; Tue, 13 Feb 2018 10:22:08 +0100 (CET) Subject: Re: devd in r329188M don't start To: "Alex V. Petrov" , FreeBSD CURRENT , imp@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> From: Hans Petter Selasky Message-ID: <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> Date: Tue, 13 Feb 2018 10:19:13 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 09:22:11 -0000 On 02/13/18 10:20, Alex V. Petrov wrote: > usb.conf is not found anywhere in the system. This is normal? devmatch is supposed to replace usb.conf . The contents of usb.conf is now part of the linker hints, /boot/kernel/linker.hints . --HPS From owner-freebsd-current@freebsd.org Tue Feb 13 09:34:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9B55F0F398 for ; Tue, 13 Feb 2018 09:34:48 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 406A06E765; Tue, 13 Feb 2018 09:34:48 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id q69so6374256lfi.10; Tue, 13 Feb 2018 01:34:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=QyLEJ1kyOKIZKpDyZ9eVv6CC/q6Nx9yqum1waYvvjb4=; b=rBdY/YISp/af3JJLitQ0lzaCvoRTEweML3fJrgQT8Ylmp3m5wbfsC2fr/8EUrIZbtY xKJpOPUeAgsEeI+HDBE9ufco7JGB3Mxxk0BzKCACGYPdIwXN6OiZ+4CXb9AiFtOPUb9S e1GJCck61heDqqbE/uoxzr0l4buNtixFUVadL5FxUSmM6zaxyTLcKtLTt6G1x1RX/DHi yuq5KOvYHCmdKQX3RnCMf602AubkSIWd56IevY4M/eS4W/fDtLt05tN3DPix1osS2qeR EDWsniYiqpSHM9dLgNlaKYeGCtN9QkhYM1ch2jia3/i5ejurXnK4lz34FEGnQYfl97+e nn9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=QyLEJ1kyOKIZKpDyZ9eVv6CC/q6Nx9yqum1waYvvjb4=; b=G7yeF4zoiYhfyZEV5QYjGKXxr03G3GJK++hSOyEHb7Fog/6EsFxe+pMGgnTfYkjyOm pWZXKgGwweIz5rh8zlW+w+eArw91R43Pp1nRlNCu7ZwFw4IU8ZLzgrRL0dIVb4R6ghsF YLmXxEI21PSYuZf/JF9v6N9ZaT/jR8s+7DghNYnYMBoFjrb9sCQLK8hbhXXkg/m4+GNM BraNuc1aRc5L1dfcxzBrREbEluLJkACJidwL9tajhaHOxNjeQdhLlcBWczXj6uzsiXn3 nEY4rTb016DS6jk16vWFXa+0TEBylmVMXjfmjdYBaHYTxGjYBQpsMZBMq0tqrCV4AvAS /keQ== X-Gm-Message-State: APf1xPAHbplBY+6ZqcS1ThPvEF6P3Vbi8xLuQ/BWDrsHqJv272GuMOz1 wyKz+nJT/bOz9gLQaC4YayI4bCVM X-Google-Smtp-Source: AH8x224MoAno2NUpw1391+DnM3WDwhIHpGS9cniP0rWrlNrQGd+Leh3wbI0nYqjfR4U9wUmpwyoQ3w== X-Received: by 10.46.111.27 with SMTP id k27mr494450ljc.123.1518514486391; Tue, 13 Feb 2018 01:34:46 -0800 (PST) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id p76sm2099136lfp.36.2018.02.13.01.34.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 01:34:45 -0800 (PST) Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , FreeBSD CURRENT , imp@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> From: "Alex V. Petrov" Message-ID: <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> Date: Tue, 13 Feb 2018 16:34:44 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 09:34:49 -0000 Why is not the driver loaded when the mouse is connected? 13.02.2018 16:19, Hans Petter Selasky пишет: > On 02/13/18 10:20, Alex V. Petrov wrote: >> usb.conf is not found anywhere in the system. This is normal? > > devmatch is supposed to replace usb.conf . The contents of usb.conf is > now part of the linker hints, /boot/kernel/linker.hints . > > --HPS > -- ----- Alex. From owner-freebsd-current@freebsd.org Tue Feb 13 09:48:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB010F104E2 for ; Tue, 13 Feb 2018 09:48:22 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::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 237FF6EFD4; Tue, 13 Feb 2018 09:48:22 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: by mail-lf0-x22f.google.com with SMTP id q194so24253247lfe.13; Tue, 13 Feb 2018 01:48:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=nA1Oo0UEI8JOC6VBllLULx283ZUT+w4YS/5aM9MAI+s=; b=n5DgA/P8zxJxRM87wBpcDLThk1lnVpeQsWcBvBqxtkP7lAz0AHj9OJoPi1+wOfRDyw UTCJXdOCSdVeIkZuPK/O4dXdbYwATb/31Dk57XQidzvvqCprjXMfXH0yOFrl2wyafR1G f7i9zfOKAZ4w1nvj4q4YhjVWuZ4dsk4SGunHOKpcHG6fEF7DWa3uqjQqpE/qqQmptHYd RUurlnGvvA2nU/uQGTQyAu8KUh4sU6UV2wAB31ifj5hMu7v2Pzb3NiPQWsgQDJ3kHrPP pdvq2zYAKtkQCv+X/qVlD7qN6kdyi9fb9/5GDe0KA/wNG3jQF7eySRu3zk0RsxGeMIAc yKWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=nA1Oo0UEI8JOC6VBllLULx283ZUT+w4YS/5aM9MAI+s=; b=UdYmOkNRXoA057g2WsVyA1dAOXemHiOTDYcL8RlZ7fC+jpXhxtBfLxRU+icGzk2Wzq 5WofufjxVXlqj9j4NbUwxQ5gHFfAHd2KSMii/3O47nS1bBV9P42nVpH/t//5eC32kN/z FnVRuZVpSJE5cU1tfFa98EyfdXG0kr5G/RuWree017oSxqs9nr5N7BQZaJvMZdl4bOcA Bf68r3SYfl0d/q/uIWtJy26bDXm/ea38EaOybDiweUVucabcc0qSx8xESXCZ5VjQiv8+ oARdSUsPfUTGtzHnANVhapoxKA5aUzxk2a9XpimsWZzTcX5xZQY44yDWC53zNMPtWkZj MIFg== X-Gm-Message-State: APf1xPCfKz+lVFFwEZpn/vgHJ/DtuBiS8HUjyFDC+QukClTY5ziQV0YN odxlN1kfNR+5xwMigwWKq4b6sFcM X-Google-Smtp-Source: AH8x226WgM0nGrK6UHxOmGrNtw1uKV/Y/7FDAG9Rc7XYmucXxei8/TWcjBMKG5CjNeUKFYx5lQX75Q== X-Received: by 10.25.83.203 with SMTP id h72mr540246lfl.135.1518515300451; Tue, 13 Feb 2018 01:48:20 -0800 (PST) Received: from localhost ([81.19.73.153]) by smtp.gmail.com with ESMTPSA id r68sm1976762lja.8.2018.02.13.01.48.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 01:48:19 -0800 (PST) Date: Tue, 13 Feb 2018 12:48:19 +0300 From: Vladimir Zakharov To: Bryan Drewery Cc: David Wolfskill , freebsd-current@freebsd.org Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive Message-ID: <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> <20180212145430.r5ygphq3yskm7gxi@vzakharov> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 12.0-CURRENT amd64 X-PGP-Key: http://vzakharov.ru/pubkey.asc User-Agent: NeoMutt/20171215 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 09:48:23 -0000 On Mon, Feb 12, 2018, Bryan Drewery wrote: > On 2/12/2018 6:54 AM, Vladimir Zakharov wrote: > > Hello, Bryan! > > > > On Fri, Feb 09, 2018, Bryan Drewery wrote: > >> On 2/1/2018 1:10 AM, Vladimir Zakharov wrote: > >>> Hello! > >>> > >>> For some time (about a week) building and installing kernel fails with > >>> the error "Variable OBJTOP is recursive." when going to build/install > >>> module from ports. > >>> > >>> Last successful build was at r328426. Next build at r328527 failed and > >>> still broken at r328649. > >>> > >>> Without PORTS_MODULES building and installing kernel succeeds. Another > >>> workaround: ignore error and build/install module directly from ports. > >>> ... > >> > >> For some reason I cannot recreate this issue. > > > > It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. > > At least, removing it fixes build for me. > > > > Build successful with the following settings: > > # cat /etc/src-env.conf > > WITH_META_MODE= > > #WITH_AUTO_OBJ= > > > > Please try this patch (requires a buildkernel). > > https://people.freebsd.org/~bdrewery/patches/kernel-portsmodules.diff > Fixed partly: | buildkernel | installkernel | r329196 | OK | FAIL(*) | r329169 + patch | OK | OK | r329196 + WITH_AUTO_OBJ | FAIL | | r329169 + WITH_AUTO_OBJ + patch | FAIL | | (*) - same error "Variable OBJTOP is recursive". -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra From owner-freebsd-current@freebsd.org Tue Feb 13 10:14:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0343FF124F0 for ; Tue, 13 Feb 2018 10:14:05 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 9B555702A6 for ; Tue, 13 Feb 2018 10:14:04 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-18bc70d5.06-431-73746f70.cust.bredbandsbolaget.se ([213.112.188.24] helo=sigyn.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1elXB4-000BFD-Gv for freebsd-current@freebsd.org; Tue, 13 Feb 2018 10:47:06 +0100 Received: from gw.bright-group.se ([193.12.143.142] helo=[192.168.30.20]) by sigyn.alvermark.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1elXB3-00080o-QU for freebsd-current@freebsd.org; Tue, 13 Feb 2018 10:47:05 +0100 Subject: Re: devd in r329188M don't start To: freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> From: Jakob Alvermark Message-ID: Date: Tue, 13 Feb 2018 10:47:05 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 10:14:05 -0000 +1 My USB mouse was working fine before the switch to devmatch. Now I have to 'kldload ums' manually. Same for USB audio, snd_uaudio.ko was loaded by devd before. Jakob On 02/13/18 10:34, Alex V. Petrov wrote: > Why is not the driver loaded when the mouse is connected? > > 13.02.2018 16:19, Hans Petter Selasky пишет: >> On 02/13/18 10:20, Alex V. Petrov wrote: >>> usb.conf is not found anywhere in the system. This is normal? >> devmatch is supposed to replace usb.conf . The contents of usb.conf is >> now part of the linker hints, /boot/kernel/linker.hints . >> >> --HPS >> From owner-freebsd-current@freebsd.org Tue Feb 13 12:53:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3F0FF1FE2E for ; Tue, 13 Feb 2018 12:53:22 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 68EF876D64 for ; Tue, 13 Feb 2018 12:53:22 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id BED99260329; Tue, 13 Feb 2018 13:53:19 +0100 (CET) Subject: Re: devd in r329188M don't start To: Jakob Alvermark , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> From: Hans Petter Selasky Message-ID: Date: Tue, 13 Feb 2018 13:50:24 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------75CE02947371056AAE27BFDE" Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 12:53:23 -0000 This is a multi-part message in MIME format. --------------75CE02947371056AAE27BFDE Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 02/13/18 10:47, Jakob Alvermark wrote: > +1 > > My USB mouse was working fine before the switch to devmatch. Now I have > to 'kldload ums' manually. > > Same for USB audio, snd_uaudio.ko was loaded by devd before. > Hi, This is a known issue. Can you try the attached patch? Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and /etc/rc.d/devmatch only. --HPS --------------75CE02947371056AAE27BFDE Content-Type: text/x-patch; name="devmatch.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="devmatch.diff" Index: etc/defaults/rc.conf =================================================================== --- etc/defaults/rc.conf (revision 329193) +++ etc/defaults/rc.conf (working copy) @@ -41,7 +41,8 @@ ddb_config="/etc/ddb.conf" # ddb(8) config file. devd_enable="YES" # Run devd, to trigger programs on device tree changes. devd_flags="" # Additional flags for devd(8). -devmatch_enable="YES" # Demand load kernel modules based on device ids. +devmatch_enable="YES" # Demand load kernel modules based on device IDs. +devmatch_flags="" # Additional flags for devmatch(8). #kld_list="" # Kernel modules to load after local disks are mounted kldxref_enable="NO" # Build linker.hints files with kldxref(8). kldxref_clobber="NO" # Overwrite old linker.hints at boot. Index: etc/devd/devmatch.conf =================================================================== --- etc/devd/devmatch.conf (revision 329194) +++ etc/devd/devmatch.conf (working copy) @@ -7,14 +7,10 @@ # loading what modules we can based on nomatch # events. # -# Generic NOMATCH event + +# USB NOMATCH event nomatch 100 { - action "service devmatch start"; + match "bus" "uhub[0-9]+"; + action "/etc/rc.d/devmatch start 'bus=usb device=$ugen vendor=$vendor product=$product devclass=$devclass devsubclass=$devsubclass devprotocol=$devproto release=$release intclass=$intclass intsubclass=$intsubclass intprotocol=$intprotocol mode=$mode'"; }; -# Add the following to devd.conf to prevent this from running: -# nomatch 1000 { -# action "true"; -# }; -# it replaces the generic event with one of higher priority that -# does nothing. You can also set 'devmatch_enable=NO' in /etc/rc.conf Index: etc/rc.d/devmatch =================================================================== --- etc/rc.d/devmatch (revision 329193) +++ etc/rc.d/devmatch (working copy) @@ -38,17 +38,54 @@ start_cmd="${name}_start" stop_cmd=':' -devmatch_start() +fixed_pnpinfo=${2} + +devmatch_start_default() { local x + local m - x=$(devmatch | sort -u) + x=$(devmatch $devmatch_flags | sort -u) - [ -n "$x" ] || return + # + # Load modules one by one, because + # kldload will bail out on the first + # failure: + # + for m in ${x} + do + echo "Autoloading module: ${m}" + kldload -n ${m} + done +} - echo "Autoloading modules: ${x}" - kldload ${x} +devmatch_start_pnpinfo() +{ + local x + local m + + x=$(devmatch -p "$fixed_pnpinfo" | sort -u) + + # + # Load modules one by one, because + # kldload will bail out on the first + # failure: + # + for m in ${x} + do + echo "Autoloading module: ${m}" + kldload -n ${m} + done } +devmatch_start() +{ + if [ "$fixed_pnpinfo" ]; then + devmatch_start_pnpinfo + else + devmatch_start_default + fi +} + load_rc_config $name run_rc_command "$1" Index: sbin/devmatch/devmatch.8 =================================================================== --- sbin/devmatch/devmatch.8 (revision 329193) +++ sbin/devmatch/devmatch.8 (working copy) @@ -25,7 +25,7 @@ .\" .\" $FreeBSD$ .\" -.Dd February 12, 2018 +.Dd February 13, 2018 .Dt DEVMATCH 8 .Os .Sh NAME @@ -33,9 +33,10 @@ .Nd print information about unattached devices .Sh SYNOPSIS .Nm -.Op Fl aduv +.Op Fl adpuv .Op Fl -all .Op Fl -dump +.Op Fl -pnpinfo .Op Fl -unbound .Op Fl -verbose .Sh DESCRIPTION @@ -50,6 +51,8 @@ Produce a human readable dump of the .Pa linker.hints file. +.It Fl p Fl -pnpinfo +Specify plug and play information to be used when matching a driver. .It Fl u Fl -unbound Attempt to produce a list of those drivers with PNP info whose driver tables with that PNP info can't be found. Index: sbin/devmatch/devmatch.c =================================================================== --- sbin/devmatch/devmatch.c (revision 329193) +++ sbin/devmatch/devmatch.c (working copy) @@ -47,6 +47,7 @@ static struct option longopts[] = { { "all", no_argument, NULL, 'a' }, { "dump", no_argument, NULL, 'd' }, + { "pnpinfo", required_argument, NULL, 'p' }, { "unbound", no_argument, NULL, 'u' }, { "verbose", no_argument, NULL, 'v' }, { NULL, 0, NULL, 0 } @@ -59,6 +60,7 @@ static void *hints; static void *hints_end; +static const char *fixed_pnpinfo; static void read_linker_hints(void) @@ -137,36 +139,83 @@ } static int +extract_key(char *key, const char *val, int size, char end) +{ + char *old = key; + + /* prepend a space character */ + *key++ = ' '; + size--; + + /* extract key */ + while (1) { + if (*val == '\0' || *val == ';') + break; + if (size < 3) { + warnx("Key is too long."); + return (-1); + } + *key++ = *val++; + size--; + } + + /* append end character, if any */ + if (end != '\0') + *key++ = end; + + /* zero terminate */ + *key = '\0'; + + /* return string length */ + return (key - old); +} + +static int pnpval_as_int(const char *val, const char *pnpinfo) { + char key[256]; + int len; int rv; - char key[256]; - char *cp; if (pnpinfo == NULL) - return -1; + return (-1); - cp = strchr(val, ';'); - key[0] = ' '; - if (cp == NULL) - strlcpy(key + 1, val, sizeof(key) - 1); - else { - memcpy(key + 1, val, cp - val); - key[cp - val + 1] = '\0'; - } - strlcat(key, "=", sizeof(key)); - if (strncmp(key + 1, pnpinfo, strlen(key + 1)) == 0) - rv = strtol(pnpinfo + strlen(key + 1), NULL, 0); - else { - cp = strstr(pnpinfo, key); + len = extract_key(key, val, sizeof(key), '='); + if (len < 1) + return (-1); + + /* check for match at beginning, skipping first space */ + if (strncmp(key + 1, pnpinfo, len - 1) == 0) { + rv = strtol(pnpinfo + len - 1, NULL, 0); + } else { + /* check for match inside */ + const char *cp = strstr(pnpinfo, key); if (cp == NULL) rv = -1; else - rv = strtol(cp + strlen(key), NULL, 0); + rv = strtol(cp + len, NULL, 0); } - return rv; + return (rv); } +static int +pnpval_as_type_match(const char *val, const char *pnpinfo) +{ + char key[256]; + int len; + + if (pnpinfo == NULL) + return (0); + + len = extract_key(key, val, sizeof(key), '\0'); + if (len < 1) + return (0); + + /* check for match */ + return (strncmp(key + 1, pnpinfo, len - 1) == 0 || + strstr(pnpinfo, key) != NULL); +} + static void quoted_strcpy(char *dst, const char *src) { @@ -180,37 +229,35 @@ // XXX overflow } -static char * +static const char * pnpval_as_str(const char *val, const char *pnpinfo) { static char retval[256]; char key[256]; - char *cp; + int len; if (pnpinfo == NULL) { - *retval = '\0'; - return retval; + retval[0] = '\0'; + return (retval); } - cp = strchr(val, ';'); - key[0] = ' '; - if (cp == NULL) - strlcpy(key + 1, val, sizeof(key) - 1); - else { - memcpy(key + 1, val, cp - val); - key[cp - val + 1] = '\0'; + len = extract_key(key, val, sizeof(key), '='); + if (len < 1) { + retval[0] = '\0'; + return (retval); } - strlcat(key, "=", sizeof(key)); - if (strncmp(key + 1, pnpinfo, strlen(key + 1)) == 0) - quoted_strcpy(retval, pnpinfo + strlen(key + 1)); - else { - cp = strstr(pnpinfo, key); + + /* check for match at beginning, skipping first space */ + if (strncmp(key + 1, pnpinfo, len - 1) == 0) { + quoted_strcpy(retval, pnpinfo + len - 1); + } else { + const char *cp = strstr(pnpinfo, key); if (cp == NULL) strcpy(retval, "MISSING"); else - quoted_strcpy(retval, cp + strlen(key)); + quoted_strcpy(retval, cp + len); } - return retval; + return (retval); } static void @@ -219,7 +266,8 @@ char val1[256], val2[256]; int ival, len, ents, i, notme, mask, bit, v, found; void *ptr, *walker; - char *lastmod = NULL, *cp, *s; + char *lastmod = NULL; + const char *cp, *s; walker = hints; getint(&walker); @@ -284,7 +332,7 @@ break; /*FALLTHROUGH*/ case 'I': - if (v != ival && ival != 0) + if (v != ival) notme++; break; case 'G': @@ -313,6 +361,16 @@ if (strcmp(s, val1) != 0) notme++; break; + case 'T': + if (dump_flag) { + int x; + for (x = 2; cp[x] != '\0' && cp[x] != ';'; x++) + putchar(cp[x]); + break; + } + if (!pnpval_as_type_match(cp + 2, pnpinfo)) + notme++; + break; default: break; } @@ -382,7 +440,7 @@ usage(void) { - errx(1, "devmatch [-adv]"); + errx(1, "devmatch [-adv] [-p ]"); } int @@ -391,7 +449,7 @@ struct devinfo_dev *root; int ch; - while ((ch = getopt_long(argc, argv, "aduv", + while ((ch = getopt_long(argc, argv, "aduvp:", longopts, NULL)) != -1) { switch (ch) { case 'a': @@ -403,6 +461,9 @@ case 'u': unbound_flag++; break; + case 'p': + fixed_pnpinfo = optarg; + break; case 'v': verbose_flag++; break; @@ -422,6 +483,13 @@ exit(0); } + if (fixed_pnpinfo != NULL) { + const char *bus = strdup(pnpval_as_str("bus", fixed_pnpinfo)); + const char *dev = strdup(pnpval_as_str("device", fixed_pnpinfo)); + search_hints(bus, dev, fixed_pnpinfo); + exit(0); + } + if (devinfo_init()) err(1, "devinfo_init"); if ((root = devinfo_handle_to_device(DEVINFO_ROOT_DEVICE)) == NULL) --------------75CE02947371056AAE27BFDE-- From owner-freebsd-current@freebsd.org Tue Feb 13 14:02:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E11DEF027B7 for ; Tue, 13 Feb 2018 14:02:11 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 3F06279F4A; Tue, 13 Feb 2018 14:02:10 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w1DE28F0029127; Tue, 13 Feb 2018 14:02:08 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w1DE28pj029126; Tue, 13 Feb 2018 06:02:08 -0800 (PST) (envelope-from david) Date: Tue, 13 Feb 2018 06:02:08 -0800 From: David Wolfskill To: Vladimir Zakharov Cc: Bryan Drewery , freebsd-current@freebsd.org Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive Message-ID: <20180213140208.GA1180@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Vladimir Zakharov , Bryan Drewery , freebsd-current@freebsd.org References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> <20180212145430.r5ygphq3yskm7gxi@vzakharov> <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="4tkssvp36SW1tyIS" Content-Disposition: inline In-Reply-To: <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 14:02:12 -0000 --4tkssvp36SW1tyIS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 13, 2018 at 12:48:19PM +0300, Vladimir Zakharov wrote: > .... > > > It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. > > > At least, removing it fixes build for me. FWIW, I have never specified WITH_AUTO_OBJ -- and I do encounter the "Variable OBJTOP is recursive" during the "make install kernel" phase unless I take evasive action (patches). > ... > > Please try this patch (requires a buildkernel). > >=20 > > https://people.freebsd.org/~bdrewery/patches/kernel-portsmodules.diff > >=20 >=20 > Fixed partly: > | buildkernel | installkernel | > r329196 | OK | FAIL(*) | > r329169 + patch | OK | OK | > r329196 + WITH_AUTO_OBJ | FAIL | | > r329169 + WITH_AUTO_OBJ + patch | FAIL | | >=20 > (*) - same error "Variable OBJTOP is recursive". > .... In my case, I started with r329155, updated sources to r329197, reverted an earlier patch to src/sys/conf/kern.post.mk, applied the above, and rebuilt with no issues -- both on my headless build machine (which runs a GENERIC kernel, has no kernel modules from ports, did not exhibit the problem, and verified that the patch doesn't break the "vanilla" configuration. My laptop, which runs a moderately-customized kernel ("CANARY") based on GENERIC, uses the x11/nvidia-driver-340 kernel module, and has exhibited the problem in the past, made it through the build/install/smoke test without issue (with the above patch). Peace, david --=20 David H. Wolfskill david@catwhisker.org The circus around that memo helps confirm that Mr. Trump is unfit for offic= e. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --4tkssvp36SW1tyIS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqC7+BfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hfOIgf/cQQgyoVymVZUQANE1bYpOVzHo04Tn0vglV6Vgk8GXGXpo4ns7hb0NSya hi6LGdDDEzvsUQCzQZonuali/HBVMvRrFp29j+xtV+Rbj/GHnSffu2+EX2J0YO/E f5FobsU6TjJ5+Nj2O08yzx6IqC9a67w+3x/54MN9WwZtNEi2KdWDmSIrN6sPCgoS +e6Sq8AY73+KXhwYjwayAcy3Q33b7aVasPh8q4mFYk8uhzpZWQg05YG3/EfL7bXi s4SB8rDkwDZdQzlPiUSFJHUVRDOrsC23QLMc3QY8HcMI6OnLCY78N1aK6rjY7Zmu VDg246aqAZw0i32/KfGabrrblCJuXg== =LH42 -----END PGP SIGNATURE----- --4tkssvp36SW1tyIS-- From owner-freebsd-current@freebsd.org Tue Feb 13 14:26:46 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AB0DF045EC for ; Tue, 13 Feb 2018 14:26:46 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x242.google.com (mail-lf0-x242.google.com [IPv6:2a00:1450:4010:c07::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 64A917AF02 for ; Tue, 13 Feb 2018 14:26:45 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x242.google.com with SMTP id f136so25295647lff.8 for ; Tue, 13 Feb 2018 06:26:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=DSZq/ywcW7ygRhcUfvHTmOyEbMAO5zXxkNr85OJ7RI8=; b=qJIGzdtlou5eaH/sNrkt9CbUWN3+WHT45pIn586+A2vB2xXmcO90xMt2bwSRDal6SY q+ECfEPKSGd9dZt/Vuq/XF/GK159qB1YXNsGcnaCvkehJrSrVYJ+CFBIyvf4Z41CaWIk UfPplSigPbQjmXHNrT72aiRjRy+9L15H9e90hX52KPKEVEZEf1oxOyqvOkQ5dw4I8iqz H6HOx2EVdn0TJotKWkRWpgHmS5Jwh7Vm58ropIiL69SXhjcfsER+1OyyUFyBNVmVPR46 6VjZovukxof9pXBKOluVLJ3Rp2oTYnF/IonmDadVnYi/rcrdXlQbVPja8xUzW4v6y/Ot yVCw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=DSZq/ywcW7ygRhcUfvHTmOyEbMAO5zXxkNr85OJ7RI8=; b=YDCDQYuAI++2ZKQnZyPbao0omt0LHELZHeAtFkPK9yf1HJ14FYcoZDB9x+63MH5H2d 9pNbKJZzqGQ3niFU6QHzBbfiM0Xs/V2njlVfwuZN+vbwkUoe7QX0OuR7redmX1/VqCTW KzlyHjjENSObs5KCbyTTksfYOGjM+OCYZMJM8VjdD4YoUCwn5It7GAlzaef5OoRvwuYC 8gcER+K0b3F8E5YzJkdvrcNBfMxxEQ6Z7QJXJZBUxCJFAq0iygd3/maaMEWZ5DvnxBYO 1Rw2dmrEjzk+ieYWAhs7O0H5/UyP3CKuBTnc0TlomlihWO0K5pYTOljr+ZY1R+iV7iFy 09/A== X-Gm-Message-State: APf1xPDmXJ4P1FKEdbUjpFKU+UGVo3zO8YKGGqdtD1oxBdr/fh4v2Q01 bNnW8ywffaoy1xUNGwRnDJoY7Z+N X-Google-Smtp-Source: AH8x22705b6Re1QZyexRqAU5xM8n8Qsd04wRuh5z4ndRxI9bmKPPhshbwV/yRsffWapcUXMv72Ub2w== X-Received: by 10.46.60.2 with SMTP id j2mr1064299lja.24.1518532002972; Tue, 13 Feb 2018 06:26:42 -0800 (PST) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id c12sm2086965ljd.60.2018.02.13.06.26.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 06:26:41 -0800 (PST) Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , Jakob Alvermark , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> From: "Alex V. Petrov" Message-ID: <5d6bb6de-31ff-bf8f-104b-5c8fb323ac0c@gmail.com> Date: Tue, 13 Feb 2018 21:26:40 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 14:26:46 -0000 Yes, for me it works. Thank you. 13.02.2018 19:50, Hans Petter Selasky пишет: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB audio, snd_uaudio.ko was loaded by devd before. >> > > Hi, > > This is a known issue. > > Can you try the attached patch? > > Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and > /etc/rc.d/devmatch only. > > --HPS > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- ----- Alex. From owner-freebsd-current@freebsd.org Tue Feb 13 17:51:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15811F1551F for ; Tue, 13 Feb 2018 17:51:34 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AFF2F86E3A; Tue, 13 Feb 2018 17:51:33 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 7E17D5C5C; Tue, 13 Feb 2018 17:51:33 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id C0CB8F1A; Tue, 13 Feb 2018 17:51:32 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id 98EprBHWeU3w; Tue, 13 Feb 2018 17:51:30 +0000 (UTC) Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com 3BA9FF15 To: Vladimir Zakharov Cc: David Wolfskill , freebsd-current@freebsd.org References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> <20180212145430.r5ygphq3yskm7gxi@vzakharov> <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: Date: Tue, 13 Feb 2018 09:51:31 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vfkbTZaQaKlTGWLQQfHrpweX6TchdEYyq" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 17:51:34 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vfkbTZaQaKlTGWLQQfHrpweX6TchdEYyq Content-Type: multipart/mixed; boundary="6wH9PLQCY2G0DephcmkG3xUzbAkN33eKg"; protected-headers="v1" From: Bryan Drewery To: Vladimir Zakharov Cc: David Wolfskill , freebsd-current@freebsd.org Message-ID: Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> <20180212145430.r5ygphq3yskm7gxi@vzakharov> <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> In-Reply-To: <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> --6wH9PLQCY2G0DephcmkG3xUzbAkN33eKg Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2/13/2018 1:48 AM, Vladimir Zakharov wrote: > On Mon, Feb 12, 2018, Bryan Drewery wrote: >> On 2/12/2018 6:54 AM, Vladimir Zakharov wrote: >>> Hello, Bryan! >>> >>> On Fri, Feb 09, 2018, Bryan Drewery wrote: >>>> On 2/1/2018 1:10 AM, Vladimir Zakharov wrote: >>>>> Hello! >>>>> >>>>> For some time (about a week) building and installing kernel fails w= ith >>>>> the error "Variable OBJTOP is recursive." when going to build/insta= ll >>>>> module from ports. >>>>> >>>>> Last successful build was at r328426. Next build at r328527 failed = and >>>>> still broken at r328649. >>>>> >>>>> Without PORTS_MODULES building and installing kernel succeeds. Anot= her >>>>> workaround: ignore error and build/install module directly from por= ts. >>>>> ... >>>> >>>> For some reason I cannot recreate this issue. >>> >>> It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error.= >>> At least, removing it fixes build for me. >>> >>> Build successful with the following settings: >>> # cat /etc/src-env.conf >>> WITH_META_MODE=3D >>> #WITH_AUTO_OBJ=3D >>> >> >> Please try this patch (requires a buildkernel). >> >> https://people.freebsd.org/~bdrewery/patches/kernel-portsmodules.diff >> >=20 > Fixed partly: > | buildkernel | installkernel | > r329196 | OK | FAIL(*) | > r329169 + patch | OK | OK | > r329196 + WITH_AUTO_OBJ | FAIL | | > r329169 + WITH_AUTO_OBJ + patch | FAIL | | >=20 > (*) - same error "Variable OBJTOP is recursive". >=20 Thanks, r329232 should fix it. --=20 Regards, Bryan Drewery --6wH9PLQCY2G0DephcmkG3xUzbAkN33eKg-- --vfkbTZaQaKlTGWLQQfHrpweX6TchdEYyq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJagyWjAAoJEDXXcbtuRpfP7w0H/393jfev4PWtHFrToIZVsyye DOLB8dVBDZcOMJmS6bWiJMvbc68MLVVhaHNv3Idcb9xEtBRLXn4MOJRVF0qu97om MgYyF9D1gWdZ6R5V5XSU4xAZxlqrbPLiWCyWrhXxiILCXI+yxuJ3Ao9XESd0XrK+ lTtAxQPhL3xk1I7W6FY8Ks+uLFupInIRTepEky2+uL6E+/We4A5zJKFeJREsNOTr +K+OPfRSzCaBVVxQgmJ31xpWuRVg26OJZSR8ocgqz3s4T/ljNQyKyI8hN0GEVwhx fH9oBHWDblJNKp1scOwTip4acuK2o1SAWm59qSs/52GVnAmTO45Rq5YyoiRN1+8= =FxlI -----END PGP SIGNATURE----- --vfkbTZaQaKlTGWLQQfHrpweX6TchdEYyq-- From owner-freebsd-current@freebsd.org Tue Feb 13 18:34:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38739F18D10 for ; Tue, 13 Feb 2018 18:34:35 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-io0-f177.google.com (mail-io0-f177.google.com [209.85.223.177]) (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 C871D69270 for ; Tue, 13 Feb 2018 18:34:34 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-io0-f177.google.com with SMTP id g14so16139658iob.9 for ; Tue, 13 Feb 2018 10:34:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=epcSkBVfvQ26jL7Q0vJX5KSQBFeemMNQ5xglb7GhuC0=; b=NFhqF59olApWB1LfHXFIRCdSWknuO01IKXmnfLWCZH7BiZIg+4RyXKCXsr4oNkAUr1 j1dSFKePrAXA53bxsUR/hrIzZcH2QP6rFfTwdTbDI0NPS1Y611yMZnW7foXCZngNiS8X 66g2eaWamu3rSdqu/YC6W5KImm5Tfr0+wCPKfXNfaAspieAy0YO5cLOvzwomt4vjOKsb cf6888usExeeR14bNCPYBGkHYh7pqKXV63xbYOzSLcIQpWYrXlW4YhJB6HUO+S6ZiZwI se6E8+xzJA+rIz5iuJba9gqjYjdiAV8q6pIMbitESHj1TCHPptwdpAVTB1i+cjFI/8rO Lk8w== X-Gm-Message-State: APf1xPDiS3Ax/mLUklTEbu15DnOzYOJOXcrJLlSUBLM9nFIQpv+BpVmG CiZayILGC+YzV2KW6r315ZzIy/eR X-Google-Smtp-Source: AH8x225UfR0cWVTfEQ4NmKHg+g64SeaMcntpZyTmmjE18JgWkIRChYlJWn26BUFe3m/FIhT9mX1fmA== X-Received: by 10.107.37.19 with SMTP id l19mr2630206iol.193.1518546867846; Tue, 13 Feb 2018 10:34:27 -0800 (PST) Received: from mail-io0-f175.google.com (mail-io0-f175.google.com. [209.85.223.175]) by smtp.gmail.com with ESMTPSA id s8sm11891937itb.39.2018.02.13.10.34.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 10:34:27 -0800 (PST) Received: by mail-io0-f175.google.com with SMTP id f4so22340714ioh.8 for ; Tue, 13 Feb 2018 10:34:27 -0800 (PST) X-Received: by 10.107.15.8 with SMTP id x8mr2609980ioi.38.1518546867430; Tue, 13 Feb 2018 10:34:27 -0800 (PST) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.2.30.149 with HTTP; Tue, 13 Feb 2018 10:34:26 -0800 (PST) In-Reply-To: <20180213140208.GA1180@albert.catwhisker.org> References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> <20180212145430.r5ygphq3yskm7gxi@vzakharov> <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> <20180213140208.GA1180@albert.catwhisker.org> From: Conrad Meyer Date: Tue, 13 Feb 2018 10:34:26 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive To: David Wolfskill , freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 18:34:35 -0000 On Tue, Feb 13, 2018 at 6:02 AM, David Wolfskill wrote: > On Tue, Feb 13, 2018 at 12:48:19PM +0300, Vladimir Zakharov wrote: >> .... >> > > It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. >> > > At least, removing it fixes build for me. > > FWIW, I have never specified WITH_AUTO_OBJ -- and I do encounter the > "Variable OBJTOP is recursive" during the "make install kernel" phase > unless I take evasive action (patches). FYI, it is on by default since r325520. Best, Conrad From owner-freebsd-current@freebsd.org Tue Feb 13 21:49:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D993EF03E56 for ; Tue, 13 Feb 2018 21:49:58 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 550F873AF1 for ; Tue, 13 Feb 2018 21:49:58 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.208] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 3d1833e3 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Tue, 13 Feb 2018 13:49:15 -0800 (PST) To: FreeBSD Current From: Pete Wright Subject: New ACPI Errors Message-ID: <58d889fa-a9c5-5108-c838-01f4904950cd@nomadlogic.org> Date: Tue, 13 Feb 2018 13:49:50 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 21:49:59 -0000 Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xfffff8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) I noticed this starting from a CURRENT build i installed two weeks ago, and still see it from a world/kernel i built last night.  two questions: 1) has anyone else noticed this? 2) is this something to worry about? i can help debug the issue but am not sure where to start poking. thanks! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Tue Feb 13 22:42:38 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FEC6F07AB3 for ; Tue, 13 Feb 2018 22:42:38 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp05.smtpout.orange.fr [80.12.242.127]) by mx1.freebsd.org (Postfix) with ESMTP id 31CA376544 for ; Tue, 13 Feb 2018 22:42:37 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from localhost ([86.222.35.125]) by mwinf5d10 with ME id ANaz1x01A2hzvBJ03Nb0uB; Tue, 13 Feb 2018 23:35:00 +0100 X-ME-Helo: localhost X-ME-Auth: Y2xidWlzc29uQHdhbmFkb28uZnI= X-ME-Date: Tue, 13 Feb 2018 23:35:00 +0100 X-ME-IP: 86.222.35.125 Subject: Re: New ACPI Errors To: freebsd-current@freebsd.org References: <58d889fa-a9c5-5108-c838-01f4904950cd@nomadlogic.org> From: Claude Buisson Message-ID: <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> Date: Tue, 13 Feb 2018 23:34:59 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <58d889fa-a9c5-5108-c838-01f4904950cd@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 22:42:38 -0000 On 02/13/2018 22:49, Pete Wright wrote: > Hello, > I have started seeing a lot of these messages spam my system log: > > ACPI Error: No pointer back to namespace node in package > 0xfffff8000f79a080 (20180209/dsargs-472) > ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, > AE_AML_INTERNAL (20180209/psparse-677) > ACPI Error: Method parse/execution failed \134_SB.AC._PSR, > AE_AML_INTERNAL (20180209/psparse-677) > > I noticed this starting from a CURRENT build i installed two weeks ago, > and still see it from a world/kernel i built last night.  two questions: > 1) has anyone else noticed this? > 2) is this something to worry about? > > i can help debug the issue but am not sure where to start poking. > > thanks! > -pete > Here I have ACPI Error: No pointer back to namespace node in package 0xfffff8000171f700 (20180209/dsargs-472) ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] (20180209/dswexec-606) ACPI Error: Method parse/execution failed \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) with svn 329142 on a Lenovo ThinkCentre M83 ACPI APIC Table: Claude Buisson From owner-freebsd-current@freebsd.org Wed Feb 14 02:11:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27150F17934 for ; Wed, 14 Feb 2018 02:11:37 +0000 (UTC) (envelope-from pkelsey@gmail.com) Received: from mail-pg0-x22b.google.com (mail-pg0-x22b.google.com [IPv6:2607:f8b0:400e:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BEFB7E485; Wed, 14 Feb 2018 02:11:36 +0000 (UTC) (envelope-from pkelsey@gmail.com) Received: by mail-pg0-x22b.google.com with SMTP id j9so1359649pgv.3; Tue, 13 Feb 2018 18:11:36 -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:to:cc; bh=l1mUVJTFWW8C98SekH3ffduQkzJmZzr55vNjsP2G02c=; b=YCrfYvAAT6dl3BA38xuULp1Qcz2ESllZa2VCVqwrDn/uAZDYmtOyPGPNwKawiA25kh yXhQXmCwfO3dhfM3M7QRH6e5TkFpu5PsOYNzIHtqv6k4tm2INRGU77DuaP43llQ0e1mR Cz9qP/rZQ+KPAy7cVUyYx1KiA2NesQ2hUAPgi9qnw3n+Vz0GVR+Hax3LvKyR5x0sfB8J If6MpIs1Qgh5CgifXA80hWEVtyZYRabG8mFUKheAZdXN54C0RmvVXzA7/HJJmIGOSSIk 9F+YwOKg52dMeMNrc+g04fIDxOZDzlcauuUT3ZRpOcDEJy0J21ER0BjbTsBqy5FC/RYE L4JA== 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=l1mUVJTFWW8C98SekH3ffduQkzJmZzr55vNjsP2G02c=; b=B9YMmuHnw2HZEsfeCUY5NzqPBleD7O70o+e5Nicy0wQ5oC41IjUUdRZWs9OJxhp0jR 8yxlINPzkIoQ2uhW0mWFhz+nxIO0wXFCSTHBxaMQmlcecqQzSToEQ5wZofTw3nvAvwqD 7oSTyYawfakuyyRaw3D7chkUPzsye2ens+R5z8i5F5XPMfkH4o95gpTPlhuWoUk09CC5 /7c4LsqBy82Vjf8uErjYoCE8X2IpVLCLvEvJ8Fw+EqpR2wiKpsBFKcZ8HegH3wT84hdb AWCqBNL/cu7sGWADfwiWl6rqkL9zpHsxYkArgNueuBdzzvPtEc6SnEBYELHJ7CzvR1Cu Cgbw== X-Gm-Message-State: APf1xPAooW4N8Pi2p3ygAd7CjObvpogTEscFUj/sICh4oP1hhxpNyXtn GwObPY67d9GRKSSm6dQoaCbO38ccFFX/UBpHK/w= X-Google-Smtp-Source: AH8x225vaUPz5iRAyurXLBNJHil6NpcnIZ/TJ9B/WNWcNIxpcrkvjBgO9E807DG303UmBSrHjGbo9Bo6hY+WTDHCPCI= X-Received: by 10.98.51.70 with SMTP id z67mr3244138pfz.2.1518574295264; Tue, 13 Feb 2018 18:11:35 -0800 (PST) MIME-Version: 1.0 Sender: pkelsey@gmail.com Received: by 10.236.190.6 with HTTP; Tue, 13 Feb 2018 18:11:34 -0800 (PST) In-Reply-To: <1868530.6C5Wu4I1lN@ralph.baldwin.cx> References: <1e2f43fd-85da-6629-62d1-6e96790278e5@digiware.nl> <201802101846.w1AIkX4Y000167@hergotha.csail.mit.edu> <1868530.6C5Wu4I1lN@ralph.baldwin.cx> From: Patrick Kelsey Date: Tue, 13 Feb 2018 21:11:34 -0500 X-Google-Sender-Auth: 9BZJTmG6L5x1cfdOiXRG4gzS0SA Message-ID: Subject: Re: posix_fallocate on ZFS To: John Baldwin Cc: freebsd-current , Garrett Wollman , asomers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 02:11:37 -0000 On Mon, Feb 12, 2018 at 12:04 PM, John Baldwin wrote: > On Saturday, February 10, 2018 01:46:33 PM Garrett Wollman wrote: > > In article > > , > > asomers@freebsd.org writes: > > > > >On Sat, Feb 10, 2018 at 10:28 AM, Willem Jan Withagen > > >wrote: > > > > >> Is there any expectation that this is going to fixed in any near > future? > > > > >No. It's fundamentally impossible to support posix_fallocate on a COW > > >filesystem like ZFS. Ceph should be taught to ignore an EINVAL result, > > >since the system call is merely advisory. > > > > I don't think it's true that this is _fundamentally_ impossible. What > > the standard requires would in essence be a per-object refreservation. > > ZFS supports refreservation, obviously, but not on a per-object basis. > > Furthermore, there are mechanisms to preallocate blocks for things > > like dumps. So it *could* be done (as in, the concept is there), but > > it may not be practical. (And ultimately, there are ways in which the > > administrator might manage the system that would defeat the desired > > effect, but that's out of the standard's scope.) Given the semantic > > mismatch, though, I suspect it's unreasonable to expect anyone to > > prioritize implementation of such a feature. > > I don't think posix_fallocate() can be compatible with COW. Suppose you > do reserve a fixed set of blocks. That ensures the first write has a > place to write, but not if you overwrite one of those blocks. You'd have > to reserve another block to maintain the reservation each time you wrote > to a block, or you'd have to have a way to mark a file as not COW. The > first case isn't really any better than not using posix_fallocate() in the > first place as you are still requiring writes to allocate blocks, and the > second seems a bit fraught with peril as well if the application is > expecting the non-COW'd file to be in sync with other files in the system > since presumably non-COW'd files couldn't be snapshotted, etc. > > I think Garrett's assessment that it is not fundamentally impossible, but may not be felt to be worth implementing in any given file system for practical reasons, is correct. I say this having designed/implemented a COW file system that was driven by customer pressure to do things that at first pass one might declare represented an architectural contradiction, but upon further reflection were entirely possible to do given sufficient willingness to invest the effort and accept the accompanying trade-offs, additional knobs to turn, etc. In this case (posix_fallocate() + COW + snapshots), it could be implemented with a per-object allocator that normally keeps at least one extra block beyond the reservation requirement on hand, plus a snapshot operation that in order to succeed has to be able to provision the local allocators of all fallocated objects with enough additional blocks to maintain the no-fail write guarantee post-snapshot. -Patrick From owner-freebsd-current@freebsd.org Wed Feb 14 08:31:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 737E3F0C591 for ; Wed, 14 Feb 2018 08:31:59 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 142206AF76 for ; Wed, 14 Feb 2018 08:31:58 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-18bc70d5.06-431-73746f70.cust.bredbandsbolaget.se ([213.112.188.24] helo=sigyn.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1elsTs-000C8d-OI; Wed, 14 Feb 2018 09:31:56 +0100 Received: from gw.bright-group.se ([193.12.143.142] helo=[192.168.30.20]) by sigyn.alvermark.net with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1elsTr-000FJp-UF; Wed, 14 Feb 2018 09:31:55 +0100 Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> From: Jakob Alvermark Message-ID: Date: Wed, 14 Feb 2018 09:31:55 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 08:31:59 -0000 Yes, it seems to be working. Thanks! Jakob On 02/13/18 13:50, Hans Petter Selasky wrote: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB audio, snd_uaudio.ko was loaded by devd before. >> > > Hi, > > This is a known issue. > > Can you try the attached patch? > > Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and > /etc/rc.d/devmatch only. > > --HPS From owner-freebsd-current@freebsd.org Wed Feb 14 08:42:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC998F0D2F6 for ; Wed, 14 Feb 2018 08:42:07 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BB776B5EC; Wed, 14 Feb 2018 08:42:07 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: by mail-lf0-x231.google.com with SMTP id f137so28356577lfe.4; Wed, 14 Feb 2018 00:42:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=YEbhaysC1V6naFAoYaT6R36oodcI7ayJ04qF+jeLLdE=; b=UJbJBWH/I9Cbj5t2oUkzRg/eLYTBOerDl/kjqJUFggG7NZplY7OohRZ00MroxR82HS m+xTePipIzcjEk+tZ3gfZvvjMsXuQ2XtD4KMbOMDlQDEkk6Dg2nCTetJF+49mV24Bhdc nEhIxYDIGajBy95e+KPwqgUwWij3C5Dz9Fo+RUG8rIEwxYluvlqEbpJEtGHlKyhh2Pff EBr9SeVRnu/VxSg8AHqVzqwKDD0ZkZ6ynNAloyro+vQEQ4fL25rvDuInu+6IPrbGxZnc XOzE9fWRoJCK8EWKdMAqsbQ7jRVx0SiMFumS2RGjIj8Uh7j+51DptWvDZ6QWCx9l8e2L nOlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=YEbhaysC1V6naFAoYaT6R36oodcI7ayJ04qF+jeLLdE=; b=Nx5fOA0ehyKswf1YIfUa21sx0fOXdOQ86+8CXqkvGsFeY4vi0hfQVwpXl6eSore++6 bAvGxnWgh0uEtOcSs872db7fmYsiZS2XwNucQuGz4Ux/QTJ3uWpqxPMjXAk69yN0o7hf cTutx27j/p/V+WHHzLpqG11Ktn3ImZFq7iO7NTBZPh2tl0jwPZfRnnFZ7eBxrje+pEGK FQCHBBJKIqyp8LJE8gw1X2Ij9Xc4Q2ViAu8w8WFCgAcUNxGQZNuEwG5LeYich7wG4ipC dzGAqW2m1I7ntFVMiOifDah7PLrA1+KKDy/mvps0n8Skv2JvLyH95VI9ik3lmMKQKlX4 jN7Q== X-Gm-Message-State: APf1xPAHICtldgum7CbOBByZrS8waK9Ghsim0h44aAgcvEg+zyuRHQw4 cTdhmP786p/ZEhL238NSVuc/J7HL X-Google-Smtp-Source: AH8x225E+rJ22+2vv9uOi4Pi9kAebrFR4M2NfnI5LVTjXB+es7xhyDyGd9HlVtpGk7r+ReOBS1jLew== X-Received: by 10.46.85.17 with SMTP id j17mr2981375ljb.55.1518597724841; Wed, 14 Feb 2018 00:42:04 -0800 (PST) Received: from localhost ([81.19.73.153]) by smtp.gmail.com with ESMTPSA id p12sm2422199ljb.95.2018.02.14.00.42.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Feb 2018 00:42:04 -0800 (PST) Date: Wed, 14 Feb 2018 11:42:03 +0300 From: Vladimir Zakharov To: Bryan Drewery Cc: David Wolfskill , freebsd-current@freebsd.org Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive Message-ID: <20180214084203.665x74r2bhummvb6@vzakharov> References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> <20180212145430.r5ygphq3yskm7gxi@vzakharov> <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 12.0-CURRENT amd64 X-PGP-Key: http://vzakharov.ru/pubkey.asc User-Agent: NeoMutt/20171215 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 08:42:08 -0000 On Tue, Feb 13, 2018, Bryan Drewery wrote: > On 2/13/2018 1:48 AM, Vladimir Zakharov wrote: > > On Mon, Feb 12, 2018, Bryan Drewery wrote: > >> On 2/12/2018 6:54 AM, Vladimir Zakharov wrote: > >>> Hello, Bryan! > >>> > >>> On Fri, Feb 09, 2018, Bryan Drewery wrote: > >>>> On 2/1/2018 1:10 AM, Vladimir Zakharov wrote: > >>>>> Hello! > >>>>> > >>>>> For some time (about a week) building and installing kernel fails with > >>>>> the error "Variable OBJTOP is recursive." when going to build/install > >>>>> module from ports. > >>>>> > >>>>> Last successful build was at r328426. Next build at r328527 failed and > >>>>> still broken at r328649. > >>>>> > >>>>> Without PORTS_MODULES building and installing kernel succeeds. Another > >>>>> workaround: ignore error and build/install module directly from ports. > >>>>> ... > >>>> > >>>> For some reason I cannot recreate this issue. > >>> > >>> It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. > >>> At least, removing it fixes build for me. > >>> > >>> Build successful with the following settings: > >>> # cat /etc/src-env.conf > >>> WITH_META_MODE= > >>> #WITH_AUTO_OBJ= > >>> > >> > >> Please try this patch (requires a buildkernel). > >> > >> https://people.freebsd.org/~bdrewery/patches/kernel-portsmodules.diff > >> > > > > Fixed partly: > > | buildkernel | installkernel | > > r329196 | OK | FAIL(*) | > > r329169 + patch | OK | OK | > > r329196 + WITH_AUTO_OBJ | FAIL | | > > r329169 + WITH_AUTO_OBJ + patch | FAIL | | > > > > (*) - same error "Variable OBJTOP is recursive". > > > > Thanks, r329232 should fix it. Not yet. 'installkernel' still fails (see below). Can be fixed either by explicit setting WITHOUT_AUTO_OBJ in /etc/src-env.conf or by applying previous patch (s/build/stage/ in kern.post.mk:89). # svn info Path: . Working Copy Root Path: /usr/src URL: https://svn.freebsd.org/base/head Relative URL: ^/head Repository Root: https://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 329259 Node Kind: directory Schedule: normal Last Changed Author: eadler Last Changed Rev: 329259 Last Changed Date: 2018-02-14 10:59:30 +0300 (Wed, 14 Feb 2018) # cat /etc/src-env.conf WITH_META_MODE= #WITH_AUTO_OBJ= # env | grep MAKE MAKEOBJDIRPREFIX=/home/obj # make -j 4 buildkernel && make installkernel ... ===> Ports module graphics/drm-next-kmod (all) cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env -u CC -u CXX -u CPP -u MAKESYSPATH -u MAKEOBJDIR MAKEFLAGS="-j 4 -J 15,16 -j 4 -J 15,16 -D NO_MODULES_OBJ .MAKE.LEVEL.ENV=MAKELEVEL KERNEL=kernel TARGET=amd64 TARGET_ARCH=amd64" SYSDIR=/usr/src/sys PATH=/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/home/obj/usr/src/amd64.amd64/tmp/legacy/bin:/home/obj/usr/src/amd64.amd64/tmp/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin SRC_BASE=/usr/src OSVERSION=1200058 WRKDIRPREFIX=/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B clean build ===> Cleaning for drm-next-kmod-g20180117 ===> License BSD2CLAUSE MIT GPLv2 accepted by the user ===> drm-next-kmod-g20180117 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by drm-next-kmod-g20180117 for building ===> Extracting for drm-next-kmod-g20180117 => SHA256 Checksum OK for FreeBSDDesktop-kms-drm-g20180117-622fdd1_GH0.tar.gz. ===> Patching for drm-next-kmod-g20180117 ===> drm-next-kmod-g20180117 depends on file: /usr/local/bin/ccache - found ===> Configuring for drm-next-kmod-g20180117 ===> Building for drm-next-kmod-g20180117 [Creating objdir obj...] ... -------------------------------------------------------------- >>> Kernel build for GENERIC-NODEBUG completed on Wed Feb 14 11:09:45 MSK 2018 -------------------------------------------------------------- -------------------------------------------------------------- >>> Installing kernel GENERIC-NODEBUG on Wed Feb 14 11:09:45 MSK 2018 -------------------------------------------------------------- ... kldxref /boot/kernel ===> Ports module graphics/drm-next-kmod (install) cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env -u CC -u CXX -u CPP -u MAKESYSPATH -u MAKEOBJDIR MAKEFLAGS=".MAKE.LEVEL.ENV=MAKELEVEL KERNEL=kernel MK_AUTO_OBJ=no TARGET=amd64 TARGET_ARCH=amd64" SYSDIR=/usr/src/sys PATH=/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/home/obj/usr/src/amd64.amd64/tmp/legacy/bin:/home/obj/usr/src/amd64.amd64/tmp/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin SRC_BASE=/usr/src OSVERSION=1200058 WRKDIRPREFIX=/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B deinstall reinstall ===> Deinstalling for drm-next-kmod ===> drm-next-kmod not installed, skipping ===> Staging for drm-next-kmod-g20180117 ===> drm-next-kmod-g20180117 depends on package: gpu-firmware-kmod>=g20170403 - found ===> Generating temporary packing list ===> drm (install) install -T release -o root -g wheel -m 555 drm.ko /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/home/ports/graphics/drm-next-kmod/work/stage/boot/modules/ install: drm.ko: No such file or directory *** Error code 71 Stop. make[7]: stopped in /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/home/ports/graphics/drm-next-kmod/work/kms-drm-622fdd1/drm *** Error code 1 Stop. make[6]: stopped in /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG/home/ports/graphics/drm-next-kmod/work/kms-drm-622fdd1 *** Error code 1 Stop. make[5]: stopped in /home/ports/graphics/drm-next-kmod *** Error code 1 Stop. make[4]: stopped in /home/ports/graphics/drm-next-kmod *** Error code 1 Stop. make[3]: stopped in /home/ports/graphics/drm-next-kmod *** Error code 1 Stop. make[2]: stopped in /home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG *** Error code 1 Stop. make[1]: stopped in /usr/src *** Error code 1 Stop. -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra From owner-freebsd-current@freebsd.org Wed Feb 14 13:02:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE383F20B51 for ; Wed, 14 Feb 2018 13:02:24 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 497CD75FA6 for ; Wed, 14 Feb 2018 13:02:24 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 08AF0F20B4A; Wed, 14 Feb 2018 13:02:24 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFB1AF20B48 for ; Wed, 14 Feb 2018 13:02:23 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 2D64275FA0 for ; Wed, 14 Feb 2018 13:02:22 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w1ED2Kbm042257 for ; Wed, 14 Feb 2018 13:02:20 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w1ED2K93042256 for current@freebsd.org; Wed, 14 Feb 2018 05:02:20 -0800 (PST) (envelope-from david) Date: Wed, 14 Feb 2018 05:02:20 -0800 From: David Wolfskill To: current@freebsd.org Subject: Crash during boot [g_part_wither()?] @r329259 Message-ID: <20180214130220.GS1180@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="K90HjsLT/gE7/naG" Content-Disposition: inline User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 13:02:24 -0000 --K90HjsLT/gE7/naG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I got one of these on each of my laptop and build machine; details beelow are from the build machine (which has a serial console and runs a vanilla GENERC kernel). Previous (successful) builld was r329197 (for both machines), yesterday. Copy/paste from serial console: =2E.. da1: Serial Number 20100818841300000 da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da1: quirks=3D0x2 ugen0.3: at usbus0 da1: Delete methods: ukbd0 on uhub1 ukbd0: on = usbus0 pass8 at umass-sim0 bus 0 scbus6 target 0 lun 2 kbd2 at ukbd0 kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000pass8: Removable Direct Access SCSI device pass8: Serial Number 20100818841300000 pass8: 40.000MB/s transfersrandom: harvesting attach, 8 bytes (4 bits) from= ukbd0 da2 at umass-sim0 bus 0 scbus6 target 0 lun 2 da2: Removable Direct Access SCSI device da2: Serial Number 20100818841300000 da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da2: quirks=3D0x2 da2: Delete methods: (probe0:umass-sim0:0:0:3): Down reving Protocol Version from 2 to 0? Fatal trap 12: page fault while in kernel mode pass9 at umass-sim0 bus 0 scbus6 target 0 lun 3 cpuid =3D 4; apic id =3D 04 fault virtual address =3D 0x78 pass9: Removable Direct Access SCSI device fault code =3D supervisor write data, page not present pass9: Serial Number 20100818841300000 ugen0.4: at usbus0 pass9: 40.000MB/s transfersinstruction pointer =3D 0x20:0xffffffff80a20c87 stack pointer =3D 0x28:0xfffffe0000428a10 da3 at umass-sim0 bus 0 scbus6 target 0 lun 3 da3: Removable Direct Access SCSI device da3: Serial Number 20100818841300000 da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present da3: quirks=3D0x2 frame pointer =3D 0x28:0xfffffe0000428a30 da3: Delete methods: code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 13 (g_event) [ thread pid 13 tid 100044 ] Stopped at g_part_wither+0x37: movq $0,offset+0x40(%rdi) db> bt Tracing pid 13 tid 100044 td 0xfffff800039d2000 g_part_wither() at g_part_wither+0x37/frame 0xfffffe0000428a30 g_run_events() at g_run_events+0x344/frame 0xfffffe0000428a70 fork_exit() at fork_exit+0x84/frame 0xfffffe0000428ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000428ab0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- db>=20 (This is still using the Forth loader, FWIW.) On the laptop, I tried issuing the "panic" command (within ddb), and got a core file, but the result appears to be a 'panic: from debugger', and the stack trace doesn't reflect the above, so it's not clear to me that that was a useful thing for me to have done. Is there some poking I can do to this to shed more light? Peace, david --=20 David H. Wolfskill david@catwhisker.org The circus around that memo helps confirm that Mr. Trump is unfit for offic= e. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --K90HjsLT/gE7/naG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqEM1tfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hfbVAgAgkmEjZbZTwlCrKT79X+lBccaGgInpOGDDxX1BiNhwZqqJ8chhDzI+H1b I2L53aNfXmw42kthCIgCBSmbSg3RE0P5JI8Nw4DlKwmj+clbI7XQYFiZGVcrch4i vzVX3mQfzFvCtWNXCdtC05DGnZz2gFf9NsunPYCnFGqGHeDBCV1pG1pPdA8FYULz xZT5hNfgxhjE5yE/VaDxpdBAYIiB0MoJjoTKmbLZZK5O57Eu5H8im1zCh67ulApl 9jCnnxRvptoBe3X0/8OaL6Z7KzOP0udFXatghcME0j/MvnDOcrlfr5/d6s+p5rqy ych22ZCpFcI5kII7T6QaxFJZ8bmwkQ== =Yh1P -----END PGP SIGNATURE----- --K90HjsLT/gE7/naG-- From owner-freebsd-current@freebsd.org Wed Feb 14 13:50:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5506EF23ECC for ; Wed, 14 Feb 2018 13:50:41 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 9035A78849 for ; Wed, 14 Feb 2018 13:50:40 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w1EDoa5j043857; Wed, 14 Feb 2018 13:50:36 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w1EDoaZ5043856; Wed, 14 Feb 2018 05:50:36 -0800 (PST) (envelope-from david) Date: Wed, 14 Feb 2018 05:50:36 -0800 From: David Wolfskill To: Warner Losh Cc: FreeBSD Current Subject: Re: LUA boot loader coming very soon Message-ID: <20180214135036.GA1180@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Warner Losh , FreeBSD Current References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="IchZQccUbQrk8obU" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 13:50:41 -0000 --IchZQccUbQrk8obU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 12, 2018 at 08:27:27AM -0700, Warner Losh wrote: > ... > So please give it a spin and give me any feedback, documentation updates > and/or bug fixes. I'm especially interested in reviews from people that > have embedded Lua in other projects or experts in Lua that can improve the > robustness of the menu code. > .... I was able to build, install, and (start to -- not loader's fault) boot my laptop; I have placed screenshots at . Some notes: * For loader_1_lua.jpg, I had (reflexively) already hit "v" to boot verbosely, so "Verbose :On" does NOT reflect the default. On the other hand, "ACPI :off" DOES reflect the default, which is opposite from the Forth loader (ref. loader_1_4th.jpg); I suspect that this warrants changing. * The lower left corner of the box seems to have an odd artifact for the Lua loader. I haven't looked, but suspect it will be easy to fix. Peace, david --=20 David H. Wolfskill david@catwhisker.org The circus around that memo helps confirm that Mr. Trump is unfit for offic= e. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --IchZQccUbQrk8obU Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqEPqxfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hdrXwf/VsD3Wy9w5FHuNiFCQsJtjazQQmtOr+EqH+juK7julVEYp+COfa3Bc7qR eQRHIlW+eMWJnjubUyFsDw2VV3J3Q32jXsBMR+Li9lmS5K4bjfxdNJRScbOPSl/Z +vPRHmWRInBMYEWxii6KLIwI89ds3KRO5fYZ3kBu1RsoOJW8uEe3cJmhx24Drr35 XMtW2R91v+xLG76cbVHTQboJN0bwbwfHeJzhABmL95X0roYreRQPMAShlp4CPYjb 3Pg1ubtoXYO3L8Eb7cuiNKVDQn4EqFbfUwwz/CvmLSKmU7WyH3ttgmPgOSaiT6DG 0iNX4sOTiJGBs1X15Oad8kiTUdzidg== =aJ96 -----END PGP SIGNATURE----- --IchZQccUbQrk8obU-- From owner-freebsd-current@freebsd.org Wed Feb 14 14:10:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B3FE7F015C8 for ; Wed, 14 Feb 2018 14:10:03 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F319E798A4 for ; Wed, 14 Feb 2018 14:10:02 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: by mailman.ysv.freebsd.org (Postfix) id 913C5F015BD; Wed, 14 Feb 2018 14:10:02 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E01EF015B1 for ; Wed, 14 Feb 2018 14:10:01 +0000 (UTC) (envelope-from cy.schubert@cschubert.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 1F5AC798A1 for ; Wed, 14 Feb 2018 14:10:00 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with ESMTPA id lxkpePe7n7GjalxkreM8xW; Wed, 14 Feb 2018 07:09:54 -0700 X-Authority-Analysis: v=2.3 cv=I59Luuog c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=Op4juWPpsa0A:10 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=JAf30KXuAAAA:8 a=KR32T9nSSsj_g8fHR4UA:9 a=MuIghYXqWu8fO9fa:21 a=VWVQLHGR46v3rawv:21 a=CjuIK1q_8ugA:10 a=vCTPE5yUGL8uW2fFCucA:9 a=_9vfjgWZw51dLhTh:21 a=hiyTQwxHeQeIX12E:21 a=iIOIlKF2bl53ehJ_:21 a=_W_S_7VecoQA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=GEL62FyrTCmHtEug2d3R:22 Received: from [25.171.85.17] (S0106002401cb186f.gv.shawcable.net [96.50.22.10]) by spqr.komquats.com (Postfix) with ESMTPSA id 94ECBA2A; Wed, 14 Feb 2018 06:09:47 -0800 (PST) MIME-Version: 1.0 From: Cy Schubert Subject: RE: Crash during boot [g_part_wither()?] @r329259 Date: Wed, 14 Feb 2018 06:09:51 -0800 To: David Wolfskill , "current@freebsd.org" Message-Id: <20180214140947.94ECBA2A@spqr.komquats.com> X-CMAE-Envelope: MS4wfO9PR7xKe05hTcLsILgrgo6qaJW2oh1hAXgiIAreHurGGeYH+uFBf8ow0uc/WxgfANJd8deatybw4qbYUxVZy7GRyouth2p4XXAGn9T1MLbNERL4MKFN wnlqecXksmCAg7aNTTYx2IxERWEpHJftbAO8RlrtP6XW0kOHe8Eu8etvWki/0gWD8D/BdXD/E+QSolWAcnq9XieU6xBQ/hbxjT0= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 14:10:04 -0000 Try reverting this https://svnweb.freebsd.org/changeset/base/329225 for now= . --- 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: David Wolfskill Sent: 14/02/2018 05:04 To: current@freebsd.org Subject: Crash during boot [g_part_wither()?] @r329259 I got one of these on each of my laptop and build machine; details beelow are from the build machine (which has a serial console and runs a vanilla GENERC kernel). Previous (successful) builld was r329197 (for both machines), yesterday. Copy/paste from serial console: ... da1: Serial Number 20100818841300000 da1: 40.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present da1: quirks=3D0x2 ugen0.3: at usbus0 da1: Delete methods: ukbd0 on uhub1 ukbd0: on = usbus0 pass8 at umass-sim0 bus 0 scbus6 target 0 lun 2 kbd2 at ukbd0 kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000pass8: Removable Direct Access SCSI device pass8: Serial Number 20100818841300000 pass8: 40.000MB/s transfersrandom: harvesting attach, 8 bytes (4 bits) from= ukbd0 da2 at umass-sim0 bus 0 scbus6 target 0 lun 2 da2: Removable Direct Access SCSI device da2: Serial Number 20100818841300000 da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da2: quirks=3D0x2 da2: Delete methods: (probe0:umass-sim0:0:0:3): Down reving Protocol Version from 2 to 0? Fatal trap 12: page fault while in kernel mode pass9 at umass-sim0 bus 0 scbus6 target 0 lun 3 cpuid =3D 4; apic id =3D 04 fault virtual address =3D 0x78 pass9: Removable Direct Access SCSI device fault code =3D supervisor write data, page not present pass9: Serial Number 20100818841300000 ugen0.4: at usbus0 pass9: 40.000MB/s transfersinstruction pointer =3D 0x20:0xffffffff80a20c87 stack pointer =3D 0x28:0xfffffe0000428a10 da3 at umass-sim0 bus 0 scbus6 target 0 lun 3 da3: Removable Direct Access SCSI device da3: Serial Number 20100818841300000 da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present da3: quirks=3D0x2 frame pointer =3D 0x28:0xfffffe0000428a30 da3: Delete methods: code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 13 (g_event) [ thread pid 13 tid 100044 ] Stopped at g_part_wither+0x37: movq $0,offset+0x40(%rdi) db> bt Tracing pid 13 tid 100044 td 0xfffff800039d2000 g_part_wither() at g_part_wither+0x37/frame 0xfffffe0000428a30 g_run_events() at g_run_events+0x344/frame 0xfffffe0000428a70 fork_exit() at fork_exit+0x84/frame 0xfffffe0000428ab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000428ab0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- db>=20 (This is still using the Forth loader, FWIW.) On the laptop, I tried issuing the "panic" command (within ddb), and got a core file, but the result appears to be a 'panic: from debugger', and the stack trace doesn't reflect the above, so it's not clear to me that that was a useful thing for me to have done. Is there some poking I can do to this to shed more light? Peace, david --=20 David H. Wolfskill david@catwhisker.org The circus around that memo helps confirm that Mr. Trump is unfit for offic= e. See http://www.catwhisker.org/~david/publickey.gpg for my public key. From owner-freebsd-current@freebsd.org Wed Feb 14 14:49:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF75BF044BE for ; Wed, 14 Feb 2018 14:49:28 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4D6337B7E7 for ; Wed, 14 Feb 2018 14:49:28 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 076B9F044AD; Wed, 14 Feb 2018 14:49:28 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7B33F044A8 for ; Wed, 14 Feb 2018 14:49:27 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 421577B7E2 for ; Wed, 14 Feb 2018 14:49:27 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w1EEnMXQ045498; Wed, 14 Feb 2018 14:49:22 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w1EEnMlZ045497; Wed, 14 Feb 2018 06:49:22 -0800 (PST) (envelope-from david) Date: Wed, 14 Feb 2018 06:49:22 -0800 From: David Wolfskill To: Cy Schubert Cc: "current@freebsd.org" Subject: Re: Crash during boot [g_part_wither()?] @r329259 Message-ID: <20180214144922.GK1180@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Cy Schubert , "current@freebsd.org" References: <20180214140947.94ECBA2A@spqr.komquats.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="o0dA3wbhdegQN8Av" Content-Disposition: inline In-Reply-To: <20180214140947.94ECBA2A@spqr.komquats.com> User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 14:49:28 -0000 --o0dA3wbhdegQN8Av Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 14, 2018 at 06:09:51AM -0800, Cy Schubert wrote: > Try reverting this https://svnweb.freebsd.org/changeset/base/329225 for n= ow. > .... Aye; thanks: after 'svn merge -c -329225 ^/head /usr/src' & a rebuild/install, the boot completes: FreeBSD freebeast.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #104 r3= 29259M/329260:1200058: Wed Feb 14 06:40:10 PST 2018 root@freebeast.catw= hisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 Thanks! Peace, david --=20 David H. Wolfskill david@catwhisker.org The circus around that memo helps confirm that Mr. Trump is unfit for offic= e. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --o0dA3wbhdegQN8Av Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqETHJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hdedAgAyZDnU8kR3ecKTCrHcIit8kHK1Fvep2BMA4QD2jJRkYl+G9TUQu/l6N3+ 9Yr8boZfJuZckCWvm0D5admck17Hc3BOBBwidHNjtCHOz4qF1UcIIpgyxUbmGswY /oMRmwQPlv47nVcNWalE2IhzQS/TEqtQVg6GEbMBbJ6tANy5tm/tMf7tdoJ3sWff UhZ7tsLt55b1+FhJiucFOci3H124GHtf7fyjxDZVONEzjx7uknLnnOPYsMY9Xgbk sCoiQFtFUgNpurvsvq1MZCXcWq/3SqUFDyVYylUdVjKF44+JARohlknZAbCCZZ/z 2e3wpVuGv5ZKcStTimMbjFEQ6kQeMA== =O38z -----END PGP SIGNATURE----- --o0dA3wbhdegQN8Av-- From owner-freebsd-current@freebsd.org Wed Feb 14 15:12:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 386B8F05FF8 for ; Wed, 14 Feb 2018 15:12:08 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 BE2977CDBB for ; Wed, 14 Feb 2018 15:12:07 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w1EFC4CN046192; Wed, 14 Feb 2018 15:12:04 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w1EFC4cu046191; Wed, 14 Feb 2018 07:12:04 -0800 (PST) (envelope-from david) Date: Wed, 14 Feb 2018 07:12:04 -0800 From: David Wolfskill To: Warner Losh , FreeBSD Current Subject: Re: LUA boot loader coming very soon Message-ID: <20180214151204.GM1180@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Warner Losh , FreeBSD Current References: <20180214135036.GA1180@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8UxdFs2YhOorwgUI" Content-Disposition: inline In-Reply-To: <20180214135036.GA1180@albert.catwhisker.org> User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 15:12:08 -0000 --8UxdFs2YhOorwgUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Also, after reverting r329225, I was able to build & boot the build machine with the Lua loader... but I didn't even see any way of interacting with it on the serial console. (I do get that opportunity with the Forth loader.) Peace, david --=20 David H. Wolfskill david@catwhisker.org The circus around that memo helps confirm that Mr. Trump is unfit for offic= e. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --8UxdFs2YhOorwgUI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqEUcRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hdEMQf/fE+MluuoPSrDU472BQ/Dfb5nNMyBT10pFKxYZ4+/e1+9JCiEkwB5ve0Z 5R5Yy9/6uoWQETcz2jIqzVOyp9+t3DhNOw7+nY+/sAJBl2oGLtT16nlqmhNunDoV 9knjyBg+jT+eAhT++FrjEkC7EFu5AoxXcVMPVXUYIo07UP5FMxpLB7j1AHILtt+S /JWlsSpIkHL/KwjLaqTW7aSOnlNiTh6ok02hzghSJZCu7P5CrQxaVjL+kdhYHq8N es03jCCmSH9RYz9odad8mn8Pq+QjNzTclwGVZh0QZvma3VEQGXtgBlJ17B4TcfBz IJA2E+CHByF/+3XrVWCY89ximDrOOQ== =sXqk -----END PGP SIGNATURE----- --8UxdFs2YhOorwgUI-- From owner-freebsd-current@freebsd.org Wed Feb 14 15:12:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A847F060E1 for ; Wed, 14 Feb 2018 15:12:41 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2229A7CF53 for ; Wed, 14 Feb 2018 15:12:41 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id D7676F060E0; Wed, 14 Feb 2018 15:12:40 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C4EF5F060DE for ; Wed, 14 Feb 2018 15:12:40 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 304747CF4C for ; Wed, 14 Feb 2018 15:12:40 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id 37so11031264lfs.7 for ; Wed, 14 Feb 2018 07:12:40 -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:to; bh=kL/CUiHBoHK22PfFmMQHxF1lkjhgnE0xDChqDkaceuo=; b=g/urUyzMF3iTwPhsji9YnoObgIj47c4vcyrIcPoIX/cRflZP5vxbflxSfI1f4vE/6i 2QwS4XKeq28sigxfjrUjQxY4xoADlhfTd8zRQaDP0G2l95TzzQn7nztC/dhTthKhRb5d 6MY/uWhYMv9MDKQyqC0iQo6Ea5ix7Z5jc3ZTQozKZISRs3hWHwuNpGHwT8+28AsJRbkV B+qSY75qy9RWK7yMJAjs1fZFrVRYj/7/T4omsLia2cs1z9MTqV0aTl5r/IF5C7KduIs4 HILkktRzoijVzNtWng3avq2SzCzDwBuFUO10fyoLl6OhJvF17QsUcIvJdbja47ao56r6 urGA== 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; bh=kL/CUiHBoHK22PfFmMQHxF1lkjhgnE0xDChqDkaceuo=; b=ku4kTI/8CvYm6CsrUnWOKp29EGklEvTSteT2QPiEGtR4yXmdFrHlAMiL2JIJgitkjH I3wWHL83MFzwAZZVlmJcIC2ZCnc9Za/yAMQFruzbmI/xNbF30C6cF9zUvJVOzHKRJM3+ GPiuYikhvLKPNZEnVZ8x0Z8zpjbEqsmAQAIwY64K5WLOkasHZhColcbo9SHXfzvxWBQe NE7EDP6rtx4RbuHPmwwTNrR7c4JacapsQDJGuI6TMUSjDjnM+xNRYOAtaiBzlk0RkM+h sICW5e7iZaL01ufom8dIhFOcD6W9jpXbVwvia5Y0dJ3ypxRfn07sN34yfXREs53UU3z5 4rCw== X-Gm-Message-State: APf1xPCDh92SqS67QDuoCB9M+bWgq5fdE8++hg6Y1LUXyUnsxssqtJj1 YSv7aejOpTwLOcOYvBoTYT8Ywbdescmhj+9CbfE= X-Google-Smtp-Source: AH8x224LTynIk8T4dQU4ieU9ti1r3P+EnxVUuZX6QsKw+qAcX7dugfkxwOwvRsrTZE3ScIcJXwMGawgkKuP3JBQPQsg= X-Received: by 10.25.79.19 with SMTP id d19mr3649471lfb.59.1518621158759; Wed, 14 Feb 2018 07:12:38 -0800 (PST) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.46.75.1 with HTTP; Wed, 14 Feb 2018 07:12:38 -0800 (PST) In-Reply-To: <20180214144922.GK1180@albert.catwhisker.org> References: <20180214140947.94ECBA2A@spqr.komquats.com> <20180214144922.GK1180@albert.catwhisker.org> From: Justin Hibbits Date: Wed, 14 Feb 2018 09:12:38 -0600 X-Google-Sender-Auth: fMdSs5SZIFxNN7bDCm-d-olU14E Message-ID: Subject: Re: Crash during boot [g_part_wither()?] @r329259 To: David Wolfskill , Cy Schubert , "current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 15:12:41 -0000 On Wed, Feb 14, 2018 at 8:49 AM, David Wolfskill wrote: > On Wed, Feb 14, 2018 at 06:09:51AM -0800, Cy Schubert wrote: >> Try reverting this https://svnweb.freebsd.org/changeset/base/329225 for now. >> .... > > Aye; thanks: after 'svn merge -c -329225 ^/head /usr/src' & a > rebuild/install, the boot completes: > > FreeBSD freebeast.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #104 r329259M/329260:1200058: Wed Feb 14 06:40:10 PST 2018 root@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 > > Thanks! > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > The circus around that memo helps confirm that Mr. Trump is unfit for office. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. Hi David, Sorry, this was my fault. I didn't think the partition table could ever have NULL(incomplete?) entries, but I was wrong. Fixed with r329262. - Justin From owner-freebsd-current@freebsd.org Thu Feb 15 18:46:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31F08F1043A for ; Thu, 15 Feb 2018 18:46:07 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::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 BF03B694AF for ; Thu, 15 Feb 2018 18:46:06 +0000 (UTC) (envelope-from ian.freislich@capeaugusta.com) Received: by mail-ot0-x236.google.com with SMTP id m15so604578otf.12 for ; Thu, 15 Feb 2018 10:46:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=capeaugusta-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=ClRMrQHRD2w2F7xuAO2oDRuwc6ggn3MZYFXs36fWq/c=; b=u18eDgLLJ7iL2mNrOa8Kja0tBFXNCI96vqt6NqkK2D7LbquopCJ8LFOjJL5XcT8DNz 7GFAtvhCpPiCNiy5IKVg0iwRygSontDz25DfXjlquam715NJTAnI11IPGnhOG6HfOXxE ds7X77WfyD8X0Rrg+bc40CcwJ34ap30iFRt40rQCxhw1vf4UlSwQZtwsGfzN9hUIYU/8 M9Z79iGgMEQbyRgASBd48EbVXEQSuI4+FCAL/t0Qq3aB7Ckj81mGpbu8Cd9w9JUcKvcZ /Lg5uJ0so7Ms1SKZxYii+gMaIxD17tDP8l5131ikNeI6EV3nI6hXubh5GdHcxI7bun++ xvWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ClRMrQHRD2w2F7xuAO2oDRuwc6ggn3MZYFXs36fWq/c=; b=dqos1nxs41ocmltjqxsC6S0FI1vdrqHSB88lqa6Vk0wmwSjKiB10jCGaTxjP5DadPO MOky9ObcOdcGRHZ+sYqVbkA4rLEQfN4LtY8L3dOlrIdAYEwh1XxBWe8Km42naXTasiLq jqltI5ASILjwZPR8auvXskMFL0edl9IM9AdS7zPWn8BGBYqhi90I065uH7VQtIqVNl7R LX4xnzQ2bAW90TmzRBCOEIzlSgUsJw5UFWRbaMn+2CXbvyWVGeG5yc+VLoTci+qYyLYE fCVMT3HP7Xt50dLCTVNuoQiflTCFT1zhnTJCocbFy21zB7OakGg8PF0zDB4r+Fe1eN/1 XSWg== X-Gm-Message-State: APf1xPD0tH8KT+yEpzdoYJakkDo0Y7NR6rj3WGYjOSZDJPlFchyNXPac i1QuOU3aPgj7XgP90V9xbafXgzHWx4qszEjrM9xwXpITbgfoQb97Oig83n0jKaBXcYVbktcJlko Pt7cZc5DNm9RKaJpq7JZStY9V5Jjz5xThHT5M3+GeQTAWd+fbgFdJII0LdnWm9MMOXr27zfFUk0 KGrsbk+uRCR2s= X-Google-Smtp-Source: AH8x227u4h7p4mQTcA+d1/Pc2Q/n7CuccGd5L+g6bBQkiwuV5etxxzP+X0mp4vu204ILtI6hrsKHSA== X-Received: by 10.157.114.12 with SMTP id u12mr2418332otj.83.1518720365477; Thu, 15 Feb 2018 10:46:05 -0800 (PST) Received: from zen.clue.co.za (c-69-254-3-228.hsd1.ga.comcast.net. [69.254.3.228]) by smtp.gmail.com with ESMTPSA id f5sm1708000oig.48.2018.02.15.10.46.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Feb 2018 10:46:04 -0800 (PST) Subject: Re: buildkernel with PORTS_MODULES fails: Variable OBJTOP is recursive To: freebsd-current@freebsd.org References: <20180201091030.qmq4boyzvvvqkug6@vzakharov> <2e2d0a5d-b032-894b-b0a8-d2ab9163159c@FreeBSD.org> <20180212145430.r5ygphq3yskm7gxi@vzakharov> <20180213094819.ilc2xcbdnpvwsm7a@vzakharov> <20180214084203.665x74r2bhummvb6@vzakharov> From: Ian FREISLICH Message-ID: <3f842e89-c84a-07bd-3b06-d6f069ff07e8@capeaugusta.com> Date: Thu, 15 Feb 2018 13:46:03 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180214084203.665x74r2bhummvb6@vzakharov> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2018 18:46:07 -0000 On 02/14/18 03:42, Vladimir Zakharov wrote: > On Tue, Feb 13, 2018, Bryan Drewery wrote: >> On 2/13/2018 1:48 AM, Vladimir Zakharov wrote: >>> On Mon, Feb 12, 2018, Bryan Drewery wrote: >>>> On 2/12/2018 6:54 AM, Vladimir Zakharov wrote: >>>>> Hello, Bryan! >>>>> >>>>> On Fri, Feb 09, 2018, Bryan Drewery wrote: >>>>>> On 2/1/2018 1:10 AM, Vladimir Zakharov wrote: >>>>>>> Hello! >>>>>>> >>>>>>> For some time (about a week) building and installing kernel fails w= ith >>>>>>> the error "Variable OBJTOP is recursive." when going to build/insta= ll >>>>>>> module from ports. >>>>>>> >>>>>>> Last successful build was at r328426. Next build at r328527 failed = and >>>>>>> still broken at r328649. >>>>>>> >>>>>>> Without PORTS_MODULES building and installing kernel succeeds. Anot= her >>>>>>> workaround: ignore error and build/install module directly from por= ts. >>>>>>> ... >>>>>> For some reason I cannot recreate this issue. >>>>> It seems, setting WITH_AUTO_OBJ in /etc/src-env.conf causes an error. >>>>> At least, removing it fixes build for me. >>>>> >>>>> Build successful with the following settings: >>>>> # cat /etc/src-env.conf >>>>> WITH_META_MODE=3D >>>>> #WITH_AUTO_OBJ=3D >>>>> >>>> Please try this patch (requires a buildkernel). >>>> >>>> https://people.freebsd.org/~bdrewery/patches/kernel-portsmodules.diff >>>> >>> Fixed partly: >>> | buildkernel | installkernel | >>> r329196 | OK | FAIL(*) | >>> r329169 + patch | OK | OK | >>> r329196 + WITH_AUTO_OBJ | FAIL | | >>> r329169 + WITH_AUTO_OBJ + patch | FAIL | | >>> >>> (*) - same error "Variable OBJTOP is recursive". >>> >> Thanks, r329232 should fix it. > Not yet. 'installkernel' still fails (see below). Can be fixed either by > explicit setting WITHOUT_AUTO_OBJ in /etc/src-env.conf or by applying > previous patch (s/build/stage/ in kern.post.mk:89). > > # svn info > Path: . > Working Copy Root Path: /usr/src > URL: https://svn.freebsd.org/base/head > Relative URL: ^/head > Repository Root: https://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 329259 > Node Kind: directory > Schedule: normal > Last Changed Author: eadler > Last Changed Rev: 329259 > Last Changed Date: 2018-02-14 10:59:30 +0300 (Wed, 14 Feb 2018) > > # cat /etc/src-env.conf > WITH_META_MODE=3D > #WITH_AUTO_OBJ=3D > > # env | grep MAKE > MAKEOBJDIRPREFIX=3D/home/obj > > # make -j 4 buildkernel && make installkernel > ... > =3D=3D=3D> Ports module graphics/drm-next-kmod (all) > cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env -u CC -u CXX -u= CPP -u MAKESYSPATH -u MAKEOBJDIR MAKEFLAGS=3D"-j 4 -J 15,16 -j 4 -J 15,= 16 -D NO_MODULES_OBJ .MAKE.LEVEL.ENV=3DMAKELEVEL KERNEL=3Dkernel TARGET=3Da= md64 TARGET_ARCH=3Damd64" SYSDIR=3D/usr/src/sys PATH=3D/home/obj/usr/src/= amd64.amd64/tmp/legacy/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/legacy/us= r/bin:/home/obj/usr/src/amd64.amd64/tmp/legacy/bin:/home/obj/usr/src/amd64.= amd64/tmp/usr/sbin:/home/obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/us= r/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin SRC_BASE=3D/usr/src OSVERS= ION=3D1200058 WRKDIRPREFIX=3D/home/obj/usr/src/amd64.amd64/sys/GENERIC-NOD= EBUG make -B clean build > =3D=3D=3D> Cleaning for drm-next-kmod-g20180117 > =3D=3D=3D> License BSD2CLAUSE MIT GPLv2 accepted by the user > =3D=3D=3D> drm-next-kmod-g20180117 depends on file: /usr/local/sbin/pkg= - found > =3D=3D=3D> Fetching all distfiles required by drm-next-kmod-g20180117 for= building > =3D=3D=3D> Extracting for drm-next-kmod-g20180117 > =3D> SHA256 Checksum OK for FreeBSDDesktop-kms-drm-g20180117-622fdd1_GH0.= tar.gz. > =3D=3D=3D> Patching for drm-next-kmod-g20180117 > =3D=3D=3D> drm-next-kmod-g20180117 depends on file: /usr/local/bin/ccac= he - found > =3D=3D=3D> Configuring for drm-next-kmod-g20180117 > =3D=3D=3D> Building for drm-next-kmod-g20180117 > [Creating objdir obj...] > ... > -------------------------------------------------------------- >>>> Kernel build for GENERIC-NODEBUG completed on Wed Feb 14 11:09:45 MSK = 2018 > -------------------------------------------------------------- > -------------------------------------------------------------- >>>> Installing kernel GENERIC-NODEBUG on Wed Feb 14 11:09:45 MSK 2018 > -------------------------------------------------------------- > ... > kldxref /boot/kernel > =3D=3D=3D> Ports module graphics/drm-next-kmod (install) > cd ${PORTSDIR:-/usr/ports}/graphics/drm-next-kmod; env -u CC -u CXX -u= CPP -u MAKESYSPATH -u MAKEOBJDIR MAKEFLAGS=3D".MAKE.LEVEL.ENV=3DMAKELEV= EL KERNEL=3Dkernel MK_AUTO_OBJ=3Dno TARGET=3Damd64 TARGET_ARCH=3Damd64" SY= SDIR=3D/usr/src/sys PATH=3D/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/sb= in:/home/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/home/obj/usr/src/amd64= .amd64/tmp/legacy/bin:/home/obj/usr/src/amd64.amd64/tmp/usr/sbin:/home/obj/= usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bi= n:/usr/local/sbin SRC_BASE=3D/usr/src OSVERSION=3D1200058 WRKDIRPREFIX= =3D/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG make -B deinstall rein= stall > =3D=3D=3D> Deinstalling for drm-next-kmod > =3D=3D=3D> drm-next-kmod not installed, skipping > =3D=3D=3D> Staging for drm-next-kmod-g20180117 > =3D=3D=3D> drm-next-kmod-g20180117 depends on package: gpu-firmware-kmo= d>=3Dg20170403 - found > =3D=3D=3D> Generating temporary packing list > =3D=3D=3D> drm (install) > install -T release -o root -g wheel -m 555 drm.ko /home/obj/usr/src/amd= 64.amd64/sys/GENERIC-NODEBUG/home/ports/graphics/drm-next-kmod/work/stage/b= oot/modules/ > install: drm.ko: No such file or directory > *** Error code 1 I can confirm this.=C2=A0 I think the issue is with the drm-next-kmod port (virtualbox-ose-kmod works correctly when used in PORTS_MODULES)=C2=A0 It appears that staging for the port is not working in this context: [zen] /usr/obj/usr/src/amd64.amd64/sys/ZEN/usr/ports/graphics/drm-next-kmod # find . -name "*.ko" ./work/kms-drm-622fdd1/amd/amdgpu/amdgpu.ko ./work/kms-drm-622fdd1/amd/amdkfd/amdkfd.ko ./work/kms-drm-622fdd1/drm/drm.ko ./work/kms-drm-622fdd1/i915/i915kms.ko ./work/kms-drm-622fdd1/lindebugfs/debugfs.ko ./work/kms-drm-622fdd1/linuxkpi/linuxkpi_gplv2.ko ./work/kms-drm-622fdd1/radeon/radeonkms.ko compare with the port: [zen] /usr/ports/graphics/drm-next-kmod # find . -name "*.ko" ./work/kms-drm-622fdd1/amd/amdgpu/amdgpu.ko ./work/kms-drm-622fdd1/amd/amdkfd/amdkfd.ko ./work/kms-drm-622fdd1/drm/drm.ko ./work/kms-drm-622fdd1/i915/i915kms.ko ./work/kms-drm-622fdd1/lindebugfs/debugfs.ko ./work/kms-drm-622fdd1/linuxkpi/linuxkpi_gplv2.ko ./work/kms-drm-622fdd1/radeon/radeonkms.ko ./work/stage/boot/modules/drm.ko ./work/stage/boot/modules/amdgpu.ko ./work/stage/boot/modules/amdkfd.ko ./work/stage/boot/modules/i915kms.ko ./work/stage/boot/modules/radeonkms.ko ./work/stage/boot/modules/debugfs.ko ./work/stage/boot/modules/linuxkpi_gplv2.ko Ian --=20 From owner-freebsd-current@freebsd.org Thu Feb 15 21:37:38 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04A9AF1C875 for ; Thu, 15 Feb 2018 21:37:38 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 929C471C25; Thu, 15 Feb 2018 21:37:37 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Subject: Re: New ACPI Errors To: Claude Buisson , Pete Wright References: <58d889fa-a9c5-5108-c838-01f4904950cd@nomadlogic.org> <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> From: Jung-uk Kim Cc: FreeBSD-current Message-ID: <7bb2e69f-2666-e813-b683-a4f035b220d5@FreeBSD.org> Date: Thu, 15 Feb 2018 16:37:33 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="NAiBLF99yEmTSWoQ9YNFVFv4Cetzjtsv3" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2018 21:37:38 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NAiBLF99yEmTSWoQ9YNFVFv4Cetzjtsv3 Content-Type: multipart/mixed; boundary="DA8eagmrdLyAtTrpGBsMnce6KtJWrO4YL"; protected-headers="v1" From: Jung-uk Kim To: Claude Buisson , Pete Wright Cc: FreeBSD-current Message-ID: <7bb2e69f-2666-e813-b683-a4f035b220d5@FreeBSD.org> Subject: Re: New ACPI Errors References: <58d889fa-a9c5-5108-c838-01f4904950cd@nomadlogic.org> <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> In-Reply-To: <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> --DA8eagmrdLyAtTrpGBsMnce6KtJWrO4YL Content-Type: multipart/mixed; boundary="------------0638AF1F52AAF55565D07D10" Content-Language: en-US This is a multi-part message in MIME format. --------------0638AF1F52AAF55565D07D10 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 02/13/2018 17:34, Claude Buisson wrote: > On 02/13/2018 22:49, Pete Wright wrote: >> Hello, >> I have started seeing a lot of these messages spam my system log: >> >> ACPI Error: No pointer back to namespace node in package >> 0xfffff8000f79a080 (20180209/dsargs-472) >> ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, >> AE_AML_INTERNAL (20180209/psparse-677) >> ACPI Error: Method parse/execution failed \134_SB.AC._PSR, >> AE_AML_INTERNAL (20180209/psparse-677) >> >> I noticed this starting from a CURRENT build i installed two weeks >> ago, and still see it from a world/kernel i built last night.=C2=A0 tw= o >> questions: >> 1) has anyone else noticed this? >> 2) is this something to worry about? >> >> i can help debug the issue but am not sure where to start poking. >> >> thanks! >> -pete >> > Here I have >=20 > ACPI Error: No pointer back to namespace node in package > 0xfffff8000171f700 (20180209/dsargs-472) > ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName > unavailable] (20180209/dswexec-606) > ACPI Error: Method parse/execution failed > \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) >=20 > with svn 329142 on a Lenovo ThinkCentre M83 > ACPI APIC Table: >=20 > Claude Buisson I believe you can silence the errors with the attached patch. Please try it and let me know. Jung-uk Kim --------------0638AF1F52AAF55565D07D10 Content-Type: text/x-patch; name="acpi.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="acpi.diff" Index: sys/contrib/dev/acpica/include/platform/acfreebsd.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- sys/contrib/dev/acpica/include/platform/acfreebsd.h (revision 329340)= +++ sys/contrib/dev/acpica/include/platform/acfreebsd.h (working copy) @@ -166,6 +166,7 @@ =20 #define ACPI_UINTPTR_T uintptr_t =20 +#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS #define ACPI_USE_DO_WHILE_0 #define ACPI_USE_LOCAL_CACHE #define ACPI_USE_NATIVE_DIVIDE --------------0638AF1F52AAF55565D07D10-- --DA8eagmrdLyAtTrpGBsMnce6KtJWrO4YL-- --NAiBLF99yEmTSWoQ9YNFVFv4Cetzjtsv3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlqF/Z0ACgkQfJ+WJvzb 8Ub9MQf/ahZ4tJDFki+HxRFdjvny6jqCCTUBlarjzqAZZCxXTHWoKetuSKS4NhT1 UjvdttkH4t6MfHV75X4gduiLJAQqv4iiedtFVKsEl0OINVaUfHvOFC3Wx5OMoxID mjk0Ip4AuAXGXjwsV+kyn2tS6eCFJmr5zOgs9XI0zYJqRCqJ6Ynz/51vFxhZ6oVr kU1eCkmkI4gl7S02f4EwxCNAzJY6z1b+wjrpG/pN2046Edfs6f4kS22mXJiBsTqz KhED2Vp4rUyh8AoxKVqi5VDLCkfUzi9kOLRKRHycvTUDvY9NqwWEgXZeRumBbmrt NA5fDNpHfme0/vm3B247tVOKRibuDQ== =TLTz -----END PGP SIGNATURE----- --NAiBLF99yEmTSWoQ9YNFVFv4Cetzjtsv3-- From owner-freebsd-current@freebsd.org Thu Feb 15 23:56:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6FE0F00548 for ; Thu, 15 Feb 2018 23:56:42 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [45.63.28.37]) (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 617D277135 for ; Thu, 15 Feb 2018 23:56:42 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: by lauren.room52.net (Postfix) with ESMTPSA id D069C31221; Fri, 16 Feb 2018 10:48:51 +1100 (AEDT) Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , Jakob Alvermark , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> From: Lawrence Stewart Message-ID: <46e84f0b-e0f1-87ea-08f3-2f3d656fde44@freebsd.org> Date: Fri, 16 Feb 2018 10:48:48 +1100 User-Agent: Not your concern MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2018 23:56:43 -0000 On 13/02/2018 23:50, Hans Petter Selasky wrote: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB audio, snd_uaudio.ko was loaded by devd before. >> > > Hi, > > This is a known issue. > > Can you try the attached patch? > > Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and > /etc/rc.d/devmatch only. +1 for ums mouse breakage on recent upgrade from head 20180201 (Git 9e57d147a97) to head 20180215 (Git 81891e10182). Will build and test patch on the weekend, but given the 2 success reports already, I presume it will fix things for me too. I won't follow up to this thread again unless the patch doesn't work for me. Thanks Hans. Cheers, Lawrence From owner-freebsd-current@freebsd.org Fri Feb 16 06:12:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4F09F18EFC for ; Fri, 16 Feb 2018 06:12:53 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from mailer.gwdg.de (mailer.gwdg.de [134.76.10.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 856A987639 for ; Fri, 16 Feb 2018 06:12:53 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from [134.76.11.225] (helo=email.stud.uni-goettingen.de) by mailer.gwdg.de with esmtp (Exim 4.80) (envelope-from ) id 1emZGH-0005I7-KW; Fri, 16 Feb 2018 07:12:45 +0100 Received: from UM-EXCHT-A02.um.gwdg.de (134.76.9.211) by um-excht-s1.um.gwdg.de (134.76.9.213) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 16 Feb 2018 07:12:45 +0100 Received: from pc028.nfv.nw-fva.de (134.76.242.1) by UM-EXCHT-A02.um.gwdg.de (134.76.9.211) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 16 Feb 2018 07:12:45 +0100 Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> From: Rainer Hurling Message-ID: Date: Fri, 16 Feb 2018 07:12:40 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 7bit X-Spam-Level: - X-Virus-Scanned: (clean) by clamav X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 06:12:54 -0000 Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB audio, snd_uaudio.ko was loaded by devd before. >> > > Hi, > > This is a known issue. > > Can you try the attached patch? > > Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and > /etc/rc.d/devmatch only. > > --HPS Is there any chance to get this committed into base in the near future? Thanks for any answer, Rainer Hurling From owner-freebsd-current@freebsd.org Fri Feb 16 06:17:50 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C306F192FA for ; Fri, 16 Feb 2018 06:17:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D141878A7 for ; Fri, 16 Feb 2018 06:17:50 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x236.google.com with SMTP id t126so3163552iof.4 for ; Thu, 15 Feb 2018 22:17:50 -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=13JGKp4k3Ba80IzJ3+wwOAkAxrJbx02N2RuoWjpHzsg=; b=zXAf+2RWP85RQ+d3ROlOeyeX6VDe+XDDML4Og0AkOukRX0/hMq6zT8BSuY4Igu3sKT JBHOEc/b+ghloJTmiyfRShZ+OIXF/f+eNgqik0Ge6yyx7MisvDLYwoMZuZ4dO6HqisX0 dtksTpplGV5VgWQ8f42WqGY7xkpfFVJAm3SDKuQGArt79tDEJT9UWeKdncsL16dFnSKN ziAPY7pcNmFU24mjiqrbpL3nSfJrQXrkwj1QROfufsYUhyP6XsErYRPaR+LXC3PH7zi8 0k5qtraYwjBa/tEUuF7SM0V88WM5vkrWE1mIq1UBwHWtMSsXvTJOG8Kqc7wn0ztTmk/J P1YA== 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=13JGKp4k3Ba80IzJ3+wwOAkAxrJbx02N2RuoWjpHzsg=; b=CDQBP86U8oc9x7b8D1G+22lnNdNU0KwuUNr11/je1RFzr9U+RdT0mfQ1TQGK7pdTtu jrxFI+syzxdoKMN7cbq7wO8xAiZsuH+xZOLRAD5zMEzM3UvgtNfqKTdSubMBhORiUcah uKGbs6G+O6DaLuoGzl3wtOjPcox3oudYgoJerdHnAMYqilLCrDHkvVTYBVx2+oj6GmU7 HMu+Yvs73VXY81ISELJadsYW9yP1TRc9WrOAjDRXnMnPHUQ7PMQbdLZLjkH3RkiGEWDd GlCf/AVNFZTJffwxBOY6ckXdNpGPsieqJz/Ib5JQk2+rafrZNeqykCC4HB5WFoR+JWk3 LV3Q== X-Gm-Message-State: APf1xPCT7BbWSKcZaO7p4tmeiZGCzGqRsqWtkSYc02wwzeeRobNz6ZLU pxeTaZF4SMfUVpw1+FmyapxiNZyj1OIAfeuIIEcxfQ== X-Google-Smtp-Source: AH8x224g2WuUjkoHwKj4TImhUbtQTQKRrJhekcXVEs9uIZGD/9T/XMzcIK1RHASk4Mgn1h7nsGLMYr+DH7j94fyXrtk= X-Received: by 10.107.2.6 with SMTP id 6mr6766483ioc.117.1518761869092; Thu, 15 Feb 2018 22:17:49 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Thu, 15 Feb 2018 22:17:48 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:18a2:a4f7:170:8dd9] In-Reply-To: References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> From: Warner Losh Date: Thu, 15 Feb 2018 23:17:48 -0700 X-Google-Sender-Auth: zI1cyGgtXSlc--nLKhygycaiLBM Message-ID: Subject: Re: devd in r329188M don't start To: Rainer Hurling Cc: Hans Petter Selasky , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 06:17:50 -0000 On Thu, Feb 15, 2018 at 11:12 PM, Rainer Hurling wrote: > Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky: > >> On 02/13/18 10:47, Jakob Alvermark wrote: >> >>> +1 >>> >>> My USB mouse was working fine before the switch to devmatch. Now I have >>> to 'kldload ums' manually. >>> >>> Same for USB audio, snd_uaudio.ko was loaded by devd before. >>> >>> >> Hi, >> >> This is a known issue. >> >> Can you try the attached patch? >> >> Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and >> /etc/rc.d/devmatch only. >> >> --HPS >> > > > Is there any chance to get this committed into base in the near future? > Yes. Warner From owner-freebsd-current@freebsd.org Fri Feb 16 06:35:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E9FFF19E0C for ; Fri, 16 Feb 2018 06:35:16 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from mailer.gwdg.de (mailer.gwdg.de [134.76.10.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B940A6814E for ; Fri, 16 Feb 2018 06:35:15 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from [134.76.11.226] (helo=email.stud.uni-goettingen.de) by mailer.gwdg.de with esmtp (Exim 4.80) (envelope-from ) id 1emZc2-0000Yl-17; Fri, 16 Feb 2018 07:35:14 +0100 Received: from UM-EXCHT-A01.um.gwdg.de (134.76.9.210) by um-excht-s2.um.gwdg.de (134.76.9.214) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 16 Feb 2018 07:35:13 +0100 Received: from pc028.nfv.nw-fva.de (134.76.242.1) by UM-EXCHT-A01.um.gwdg.de (134.76.9.210) with Microsoft SMTP Server (TLS) id 14.3.382.0; Fri, 16 Feb 2018 07:35:09 +0100 Subject: Re: devd in r329188M don't start To: Warner Losh CC: Hans Petter Selasky , FreeBSD Current References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> From: Rainer Hurling Message-ID: <21f5b409-3126-6c1e-4da8-90835b11bd30@gwdg.de> Date: Fri, 16 Feb 2018 07:35:09 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 7bit X-Spam-Level: - X-Virus-Scanned: (clean) by clamav X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 06:35:16 -0000 Am 16.02.2018 um 07:17 schrieb Warner Losh: > > > On Thu, Feb 15, 2018 at 11:12 PM, Rainer Hurling > wrote: > > Am 13.02.2018 um 13:50 schrieb Hans Petter Selasky: > > On 02/13/18 10:47, Jakob Alvermark wrote: > > +1 > > My USB mouse was working fine before the switch to devmatch. > Now I have to 'kldload ums' manually. > > Same for USB audio, snd_uaudio.ko was loaded by devd before. > > > Hi, > > This is a known issue. > > Can you try the attached patch? > > Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and > /etc/rc.d/devmatch only. > > --HPS > > > > Is there any chance to get this committed into base in the near future? > > > Yes. > > Warner Nice, thanks :) From owner-freebsd-current@freebsd.org Fri Feb 16 14:13:27 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A47CF1740D for ; Fri, 16 Feb 2018 14:13:27 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CE48A7BA03; Fri, 16 Feb 2018 14:13:26 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1518790398; bh=62SDRb1HmZFau/49/fR4Nc9snMFEX1V9xqGf6s5 Jqtk=; b=ZZupbResfCbjbQbhBVCsySSSU4brKklugFLYjFcQya/Z1SyToF87OnW mOvBfRIL7ltj2DUQZySK7LXgmpwoIm9Dv/AacCkQV2XtZZ5OBGi7Y/X7KVs2xcXX FAw0K3hG9ht4LPzcanDKVKVFZaq149HboaN1/28qCiIQwFXEk1W4= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id B31BC3D4A5; Fri, 16 Feb 2018 09:13:18 -0500 (EST) To: freebsd-current , ae@freebsd.org From: Michael Butler Subject: panic on boot after SVN r328988 Openpgp: id=6F63E6399DCC8E3E94D60F0642FF6BAE0442D492; url=0442D492 Message-ID: Date: Fri, 16 Feb 2018 09:13:17 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 14:13:27 -0000 This is on a slow (and remote :-() i386 (kgdb) bt #0 0xc076bfe8 in doadump () #1 0xc076c008 in doadump () #2 0xc0d00ee0 in suspend_blocked () #3 0xcf607548 in ?? () #4 0xc076bd8b in kern_reboot () #5 0xc076c141 in vpanic () #6 0xc076c03b in panic () #7 0xc0ab5065 in trap_fatal () #8 0xc0ab4de0 in trap () #9 #10 0xc0991ff0 in dyn_lookup_ipv4_state () #11 0xc0992323 in ipfw_dyn_lookup_state () #12 0xc098e2b9 in ipfw_chk () #13 0xc09983b9 in ipfw_check_packet () #14 0xc0879cf8 in pfil_run_hooks () #15 0xc08983e4 in ip_input () #16 0xc0878e94 in netisr_dispatch_src () #17 0xc0879190 in netisr_dispatch () #18 0xc0860434 in ether_demux () #19 0xc08611c9 in ether_nh_input () #20 0xc0878e94 in netisr_dispatch_src () #21 0xc0879190 in netisr_dispatch () #22 0xc08607aa in ether_input () #23 0xc08574e9 in if_input () #24 0xc05b5bbe in fxp_intr_body () #25 0xc05b4137 in fxp_intr () #26 0xc0732da9 in intr_event_execute_handlers () #27 0xc073303f in ithread_loop () #28 0xc0730351 in fork_exit () #29 ipfw is compiled into the kernel not loaded as a module. The best I can do to capture where in the boot process it was comes from searching the vmcore file for strings .. [ .. ] <118>devmatch: Can't read linker hints file. <118>add host 127.0.0.1: gateway lo0 fib 0: route already in table <118>add net default: gateway 64.xx.xxx.x <118>Additional inet routing options: gateway=YES. <118>add host ::1: gateway lo0 fib 0: route already in table <118>add net fe80::: gateway ::1 <118>add net ff02::: gateway ::1 <118>add net ::ffff:0.0.0.0: gateway ::1 <118>add net ::0.0.0.0: gateway ::1 <118>add net default: gateway 2001:xxx:xxxx:xxx::x <118>Additional inet6 routing options: gateway=YES. <118>00600 allow ip6 from any to any via lo0 <118>00700 deny ip6 from any to ::1 <118>00800 deny ip6 from ::1 to any <118>00900 allow ip6 from :: to ff02::/16 ipv6-icmp <118>01000 allow ip6 from fe80::/10 to fe80::/10 ipv6-icmp <118>01100 allow ip6 from fe80::/10 to ff02::/16 ipv6-icmp <118>01200 allow ip6 from any to any proto ipv6-icmp ip6 icmp6types 1,2,135,136 <118>01300 allow ip6 from me6 to any <110>ipfw: 4900 Deny TCP 77.72.82.80:50823 202.xx.xxx.xx:7696 in via fxp0 <118>Firewall rules loaded. <5>bridge0: link state changed to DOWN <6>tap0: promiscuous mode enabled <110>ipfw: 4900 Deny TCP 77.72.85.24:57077 202.xx.xxx.xx:33970 in via fxp0 <118>Creating and/or trimming log files <110>ipfw: 4900 Deny TCP 5.188.11.111:59849 202.xx.xxx.xxx:7300 in via fxp0 <118>. <118>Starting syslogd. <110>ipfw: 4900 Deny TCP 5.188.11.25:51041 202.xx.xxx.xxx:20826 in via fxp0 <118>Setting date via ntp. Fatal trap 1: privileged instruction fault while in kernel mode instruction pointer = 0x20:0xc0991ff0 stack pointer = 0x28:0xcf607704 frame pointer = 0x28:0xcf607728 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (irq7: fxp0 fxp1) trap number = 1 panic: privileged instruction fault time = 1518744036 Uptime: 26s Physical memory: 499 MB Dumping 51 MB: From owner-freebsd-current@freebsd.org Fri Feb 16 14:32:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BBD43F18D62 for ; Fri, 16 Feb 2018 14:32:20 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward101o.mail.yandex.net (forward101o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::601]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E95867C896 for ; Fri, 16 Feb 2018 14:32:19 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback14j.mail.yandex.net (mxback14j.mail.yandex.net [IPv6:2a02:6b8:0:1619::90]) by forward101o.mail.yandex.net (Yandex) with ESMTP id AB3791343994; Fri, 16 Feb 2018 17:32:16 +0300 (MSK) Received: from smtp1o.mail.yandex.net (smtp1o.mail.yandex.net [2a02:6b8:0:1a2d::25]) by mxback14j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id dcWygWq2ds-WGJKGSX2; Fri, 16 Feb 2018 17:32:16 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1518791536; bh=9/c4tOkEyAhd3f5IWuuenK0OWFanCPQNrKy+gNv4VGQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=ugLzAy3r0XiOfWraT2Oyf31ZvczuNBkKlWX/1goKMOMKEA6DLZnRtgz6PyPpalncZ 9NvJnVXaxgAbdVnoxZx5FvfEuGmewPUGYCYsZb3JF7U1Z7TVeEuFyepgUv9f8i2TPM UGds+7wjVqSI/JDEfMyrBI0azMqk7MBebEt2bw/Y= Received: by smtp1o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 0Kh0nCWX9d-WFtKsOGN; Fri, 16 Feb 2018 17:32:15 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1518791535; bh=9/c4tOkEyAhd3f5IWuuenK0OWFanCPQNrKy+gNv4VGQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=qTMlzQyesQvDpNhtW2xLSCJYRj3aaE353EZMG/kKHfv6X5n1MDaIzpOH3V80LcXux teMLh0NUIJZDFeMtzYkhdaoja7pSw8qgpGF3ExdTo3vWWbcD3GjOyopUje+fX7NYH0 mqx0wM+5cCaJQxPZQGmD/85sGL02+I5W2d28w940= Authentication-Results: smtp1o.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: panic on boot after SVN r328988 To: Michael Butler , freebsd-current References: From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <1c1d7cd3-7236-b082-0a6d-288f2b807da1@yandex.ru> Date: Fri, 16 Feb 2018 17:31:30 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1JrGIMbhWqEKZuCSt14EojHC1McQ9Ii8w" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 14:32:21 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1JrGIMbhWqEKZuCSt14EojHC1McQ9Ii8w Content-Type: multipart/mixed; boundary="hXukPAXMNfEvrOyYDx4VmmwpBzTi5b2rr"; protected-headers="v1" From: "Andrey V. Elsukov" To: Michael Butler , freebsd-current Message-ID: <1c1d7cd3-7236-b082-0a6d-288f2b807da1@yandex.ru> Subject: Re: panic on boot after SVN r328988 References: In-Reply-To: --hXukPAXMNfEvrOyYDx4VmmwpBzTi5b2rr Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 16.02.2018 17:13, Michael Butler wrote: > ipfw is compiled into the kernel not loaded as a module. Hi, do you have some specific optimization flags in make.conf? Can you show the output of `head -40 /var/run/dmesg.boot`? --=20 WBR, Andrey V. Elsukov --hXukPAXMNfEvrOyYDx4VmmwpBzTi5b2rr-- --1JrGIMbhWqEKZuCSt14EojHC1McQ9Ii8w Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlqG60IACgkQAcXqBBDI oXroRQf/W09uVQxQHC6IoNSZDnULdI8QanfXw6f7tJqqSgr4wwRCqvjC0xDn9k3h ocUtl1okyoMMuOF1m4E7ESV3b/J+yKTwdut8H4Bt85CE8KNspAcaLnSJt3k4q1yT /vaIAhjK09bZinPXKrDaHw7WvbCr0j8Ik+Y+rpwoSjNZIViqgjs98ruuUaq7RTIb Kh5oKsyrBo3dQzOvQa8CQShIwDM645cB9OZtVbh/zrLlntx6uSYWnL+qYosSoPQm vALhi/vdYFrR0pKo7uda/NrApFXi1s9dttqWSQj6ZJyjS0Pim5uxFKqOYmzyKjWv 976LyFwErUIu275l0LP4KZwCPcwGow== =s5SM -----END PGP SIGNATURE----- --1JrGIMbhWqEKZuCSt14EojHC1McQ9Ii8w-- From owner-freebsd-current@freebsd.org Fri Feb 16 14:44:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC4C5F19F30 for ; Fri, 16 Feb 2018 14:44:13 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4B9047D374 for ; Fri, 16 Feb 2018 14:44:13 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject; s=201508; t= 1518792251; bh=M/HwyflNS5BW2p/4att5TAgnUT32lfTZrpa3M7GI+qY=; b=C N3pWueb2kac6sm+mtLx4Mw5QFoQM5NAqrHJz3hP4zdG3ufg8k3bmnzjVMeDgV72d 5YEVJ8EZUD7YAFkYrHo0javI/NekX8P2qhn0kP6x99k6ttMqHzGeYedtwXbk2naf gWFgiiabYdPcZUqY5IOWOiS5GnROxDyKwOBS4RzBpo= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id B0D4F3D7C3; Fri, 16 Feb 2018 09:44:11 -0500 (EST) Subject: Re: panic on boot after SVN r328988 To: "Andrey V. Elsukov" , freebsd-current References: <1c1d7cd3-7236-b082-0a6d-288f2b807da1@yandex.ru> From: Michael Butler Openpgp: id=6F63E6399DCC8E3E94D60F0642FF6BAE0442D492; url=0442D492 Message-ID: <5ff53b57-cdb5-4059-6209-9bf70101af99@protected-networks.net> Date: Fri, 16 Feb 2018 09:44:11 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1c1d7cd3-7236-b082-0a6d-288f2b807da1@yandex.ru> Content-Type: multipart/mixed; boundary="------------231F62C5E033CA4292E05E9E" Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 14:44:14 -0000 This is a multi-part message in MIME format. --------------231F62C5E033CA4292E05E9E Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 02/16/18 09:31, Andrey V. Elsukov wrote: > On 16.02.2018 17:13, Michael Butler wrote: >> ipfw is compiled into the kernel not loaded as a module. > > Hi, > > do you have some specific optimization flags in make.conf? > Can you show the output of `head -40 /var/run/dmesg.boot`? > The only relevant flags in /etc/make.conf are .. CPUTYPE?=pentium3 KERNCONF=SARAH NO_MODULES=YES Boot log from last night's failure attached, imb --------------231F62C5E033CA4292E05E9E Content-Type: text/plain; charset=UTF-8; name="dmesg.txt" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dmesg.txt" Q29weXJpZ2h0IChjKSAxOTkyLTIwMTggVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0 IChjKSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAx OTkzLCAxOTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlh LiBBbGwgcmlnaHRzIHJlc2VydmVkLgpGcmVlQlNEIGlzIGEgcmVnaXN0ZXJlZCB0cmFkZW1h cmsgb2YgVGhlIEZyZWVCU0QgRm91bmRhdGlvbi4KRnJlZUJTRCAxMi4wLUNVUlJFTlQgIzAg cjMyOTM0NDogVGh1IEZlYiAxNSAxOTowNzo0MCBFU1QgMjAxOAogICAgcm9vdEBzYXJhaC5w cm90ZWN0ZWQtbmV0d29ya3MubmV0Oi91c3Ivb2JqL3Vzci9zcmMvaTM4Ni5pMzg2L3N5cy9T QVJBSCBpMzg2CkZyZWVCU0QgY2xhbmcgdmVyc2lvbiA2LjAuMCAoYnJhbmNoZXMvcmVsZWFz ZV82MCAzMjQwOTApIChiYXNlZCBvbiBMTFZNIDYuMC4wKQpWVCh2Z2EpOiByZXNvbHV0aW9u IDY0MHg0ODAKQ1BVOiBJbnRlbCBQZW50aXVtIElJSSAoNzAxLjYxLU1IeiA2ODYtY2xhc3Mg Q1BVKQogIE9yaWdpbj0iR2VudWluZUludGVsIiAgSWQ9MHg2ODEgIEZhbWlseT0weDYgIE1v ZGVsPTB4OCAgU3RlcHBpbmc9MQogIEZlYXR1cmVzPTB4Mzg3ZjlmZjxGUFUsVk1FLERFLFBT RSxUU0MsTVNSLFBBRSxNQ0UsQ1g4LFNFUCxNVFJSLFBHRSxNQ0EsQ01PVixQQVQsUFNFMzYs UE4sTU1YLEZYU1IsU1NFPgpyZWFsIG1lbW9yeSAgPSA1MzY4NzA5MTIgKDUxMiBNQikKYXZh aWwgbWVtb3J5ID0gNTEyNDkxNTIwICg0ODggTUIpCnJhbmRvbTogdW5ibG9ja2luZyBkZXZp Y2UuClRpbWVjb3VudGVyICJUU0MiIGZyZXF1ZW5jeSA3MDE2MDc0MTYgSHogcXVhbGl0eSA4 MDAKcmFuZG9tOiBlbnRyb3B5IGRldmljZSBleHRlcm5hbCBpbnRlcmZhY2UKa2JkMSBhdCBr YmRtdXgwCkFDUEk6IE92ZXJyaWRpbmcgX09TIGRlZmluaXRpb24gd2l0aCAiTGludXgiCm5l eHVzMAp2dHZnYTA6IDxWVCBWR0EgZHJpdmVyPiBvbiBtb3RoZXJib2FyZApjcnlwdG9zb2Z0 MDogPHNvZnR3YXJlIGNyeXB0bz4gb24gbW90aGVyYm9hcmQKYWNwaTA6IDxJTlRFTCBUUjQ0 MEJYQT4gb24gbW90aGVyYm9hcmQKYWNwaTA6IFBvd2VyIEJ1dHRvbiAoZml4ZWQpCmNwdTA6 IDxBQ1BJIENQVT4gb24gYWNwaTAKYXR0aW1lcjA6IDxBVCB0aW1lcj4gcG9ydCAweDQwLTB4 NDMgaXJxIDAgb24gYWNwaTAKVGltZWNvdW50ZXIgImk4MjU0IiBmcmVxdWVuY3kgMTE5MzE4 MiBIeiBxdWFsaXR5IDAKRXZlbnQgdGltZXIgImk4MjU0IiBmcmVxdWVuY3kgMTE5MzE4MiBI eiBxdWFsaXR5IDEwMAphdHJ0YzA6IDxBVCByZWFsdGltZSBjbG9jaz4gcG9ydCAweDcwLTB4 NzEgaXJxIDggb24gYWNwaTAKYXRydGMwOiByZWdpc3RlcmVkIGFzIGEgdGltZS1vZi1kYXkg Y2xvY2ssIHJlc29sdXRpb24gMS4wMDAwMDBzCkV2ZW50IHRpbWVyICJSVEMiIGZyZXF1ZW5j eSAzMjc2OCBIeiBxdWFsaXR5IDAKVGltZWNvdW50ZXIgIkFDUEktc2FmZSIgZnJlcXVlbmN5 IDM1Nzk1NDUgSHogcXVhbGl0eSA4NTAKYWNwaV90aW1lcjA6IDwyNC1iaXQgdGltZXIgYXQg My41Nzk1NDVNSHo+IHBvcnQgMHg0MDgtMHg0MGIgb24gYWNwaTAKcGNpYjA6IDxBQ1BJIEhv c3QtUENJIGJyaWRnZT4gcG9ydCAweGNmOC0weGNmZiBvbiBhY3BpMApwY2liMDogTGVuZ3Ro IG1pc21hdGNoIGZvciAzIHJhbmdlOiAxODAwMCB2cyAxNTAwMApwY2kwOiA8QUNQSSBQQ0kg YnVzPiBvbiBwY2liMAppc2FiMDogPFBDSS1JU0EgYnJpZGdlPiBhdCBkZXZpY2UgNy4wIG9u IHBjaTAKaXNhMDogPElTQSBidXM+IG9uIGlzYWIwCmF0YXBjaTA6IDxJbnRlbCBQSUlYNCBV RE1BMzMgY29udHJvbGxlcj4gcG9ydCAweDFmMC0weDFmNywweDNmNiwweDE3MC0weDE3Nyww eDM3NiwweGZmYTAtMHhmZmFmIGF0IGRldmljZSA3LjEgb24gcGNpMAphdGEwOiA8QVRBIGNo YW5uZWw+IGF0IGNoYW5uZWwgMCBvbiBhdGFwY2kwCmF0YTE6IDxBVEEgY2hhbm5lbD4gYXQg Y2hhbm5lbCAxIG9uIGF0YXBjaTAKdWhjaTA6IDxJbnRlbCA4MjM3MUFCL0VCIChQSUlYNCkg VVNCIGNvbnRyb2xsZXI+IHBvcnQgMHhlZjgwLTB4ZWY5ZiBpcnEgNSBhdCBkZXZpY2UgNy4y IG9uIHBjaTAKdXNidXMwIG9uIHVoY2kwCmludHNtYjA6IDxJbnRlbCBQSUlYNCBTTUJVUyBJ bnRlcmZhY2U+IHBvcnQgMHg0NDAtMHg0NGYgYXQgZGV2aWNlIDcuMyBvbiBwY2kwCmludHNt YjA6IGludHIgSVJRIDkgZW5hYmxlZCByZXZpc2lvbiAwCnNtYnVzMDogPFN5c3RlbSBNYW5h Z2VtZW50IEJ1cz4gb24gaW50c21iMApzbWIwOiA8U01CdXMgZ2VuZXJpYyBJL08+IG9uIHNt YnVzMApmeHAwOiA8SW50ZWwgODI1NTkgUHJvLzEwMCBFdGhlcm5ldD4gcG9ydCAweGVmMDAt MHhlZjNmIG1lbSAweGZlYmZhMDAwLTB4ZmViZmFmZmYsMHhmZWEwMDAwMC0weGZlYWZmZmZm IGlycSA3IGF0IGRldmljZSAxMi4wIG9uIHBjaTAKbWlpYnVzMDogPE1JSSBidXM+IG9uIGZ4 cDAKaW5waHkwOiA8aTgyNTU1IDEwLzEwMCBtZWRpYSBpbnRlcmZhY2U+IFBIWSAxIG9uIG1p aWJ1czAKaW5waHkwOiAgMTBiYXNlVCwgMTBiYXNlVC1GRFgsIDEwMGJhc2VUWCwgMTAwYmFz ZVRYLUZEWCwgYXV0bywgYXV0by1mbG93CmZ4cDA6IEV0aGVybmV0IGFkZHJlc3M6IDAwOmQw OmI3OjlhOjg3OmU4CmZ4cDE6IDxJbnRlbCA4MjU1OSBQcm8vMTAwIEV0aGVybmV0PiBwb3J0 IDB4ZWU4MC0weGVlYmYgbWVtIDB4ZmViZjkwMDAtMHhmZWJmOWZmZiwweGZlODAwMDAwLTB4 ZmU4ZmZmZmYgaXJxIDcgYXQgZGV2aWNlIDEzLjAgb24gcGNpMAptaWlidXMxOiA8TUlJIGJ1 cz4gb24gZnhwMQppbnBoeTE6IDxpODI1NTUgMTAvMTAwIG1lZGlhIGludGVyZmFjZT4gUEhZ IDEgb24gbWlpYnVzMQppbnBoeTE6ICAxMGJhc2VULCAxMGJhc2VULUZEWCwgMTAwYmFzZVRY LCAxMDBiYXNlVFgtRkRYLCBhdXRvLCBhdXRvLWZsb3cKZnhwMTogRXRoZXJuZXQgYWRkcmVz czogMDA6ZDA6Yjc6OWE6ODc6ZTkKdmdhcGNpMDogPFZHQS1jb21wYXRpYmxlIGRpc3BsYXk+ IG1lbSAweGZjMDAwMDAwLTB4ZmNmZmZmZmYsMHhmZWJmYzAwMC0weGZlYmZmZmZmLDB4ZmUw MDAwMDAtMHhmZTdmZmZmZiBpcnEgMTEgYXQgZGV2aWNlIDE0LjAgb24gcGNpMAp2Z2FwY2kw OiBCb290IHZpZGVvIGRldmljZQphaGMwOiA8QWRhcHRlYyAyOTE2MEIgVWx0cmExNjAgU0NT SSBhZGFwdGVyPiBwb3J0IDB4ZTgwMC0weGU4ZmYgbWVtIDB4ZmViZmIwMDAtMHhmZWJmYmZm ZiBpcnEgMTAgYXQgZGV2aWNlIDE1LjAgb24gcGNpMAphaWM3ODkyOiBVbHRyYTE2MCBXaWRl IENoYW5uZWwgQSwgU0NTSSBJZD03LCAzMi8yNTMgU0NCcwphY3BpX2J1dHRvbjA6IDxTbGVl cCBCdXR0b24+IG9uIGFjcGkwCmF0a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVyIChpODA0 Mik+IHBvcnQgMHg2MCwweDY0IGlycSAxIG9uIGFjcGkwCmF0a2JkMDogPEFUIEtleWJvYXJk PiBpcnEgMSBvbiBhdGtiZGMwCmtiZDAgYXQgYXRrYmQwCmF0a2JkMDogW0dJQU5ULUxPQ0tF RF0KdWFydDA6IDwxNjU1MCBvciBjb21wYXRpYmxlPiBwb3J0IDB4M2Y4LTB4M2ZmIGlycSA0 IGZsYWdzIDB4MTAgb24gYWNwaTAKdWFydDE6IDwxNjU1MCBvciBjb21wYXRpYmxlPiBwb3J0 IDB4MmY4LTB4MmZmIGlycSAzIG9uIGFjcGkwCm9ybTA6IDxJU0EgT3B0aW9uIFJPTXM+IGF0 IGlvbWVtIDB4YzAwMDAtMHhjN2ZmZiwweGNkODAwLTB4Y2VmZmYsMHhjZjAwMC0weGQwN2Zm IHBucGlkIE9STTAwMDAgb24gaXNhMApUaW1lY291bnRlcnMgdGljayBldmVyeSAxLjAwMCBt c2VjCmlwZncyICgraXB2NikgaW5pdGlhbGl6ZWQsIGRpdmVydCBsb2FkYWJsZSwgbmF0IGxv YWRhYmxlLCBkZWZhdWx0IHRvIGRlbnksIGxvZ2dpbmcgdXNidXMwOiAxMk1icHMgRnVsbCBT cGVlZCBVU0IgdjEuMApkaXNhYmxlZAp1Z2VuMC4xOiA8SW50ZWwgVUhDSSByb290IEhVQj4g YXQgdXNidXMwCnVodWIwOiA8SW50ZWwgVUhDSSByb290IEhVQiwgY2xhc3MgOS8wLCByZXYg MS4wMC8xLjAwLCBhZGRyIDE+IG9uIHVzYnVzMAp1aHViMDogMiBwb3J0cyB3aXRoIDIgcmVt b3ZhYmxlLCBzZWxmIHBvd2VyZWQKZGEwIGF0IGFoYzAgYnVzIDAgc2NidXMyIHRhcmdldCAw IGx1biAwCmRhMDogPFFVQU5UVU0gQVRMQVNfVl8xOF9XTFMgMDIwMD4gRml4ZWQgRGlyZWN0 IEFjY2VzcyBTQ1NJLTMgZGV2aWNlCmRhMDogU2VyaWFsIE51bWJlciAxNDEwMTg4NTA5NDEK ZGEwOiAxNjAuMDAwTUIvcyB0cmFuc2ZlcnMgKDgwLjAwME1IeiBEVCwgb2Zmc2V0IDYzLCAx NmJpdCkKZGEwOiBDb21tYW5kIFF1ZXVlaW5nIGVuYWJsZWQKZGEwOiAxNzUxME1CICgzNTg2 MTM4OCA1MTIgYnl0ZSBzZWN0b3JzKQpkYTEgYXQgYWhjMCBidXMgMCBzY2J1czIgdGFyZ2V0 IDEgbHVuIDAKZGExOiA8UVVBTlRVTSBBVExBU19WXzE4X1dMUyAwMjAwPiBGaXhlZCBEaXJl Y3QgQWNjZXNzIFNDU0ktMyBkZXZpY2UKZGExOiBTZXJpYWwgTnVtYmVyIDE0MTAxODg1MDg0 MApkYTE6IDE2MC4wMDBNQi9zIHRyYW5zZmVycyAoODAuMDAwTUh6IERULCBvZmZzZXQgNjMs IDE2Yml0KQpkYTE6IENvbW1hbmQgUXVldWVpbmcgZW5hYmxlZApkYTE6IDE3NTEwTUIgKDM1 ODYxMzg4IDUxMiBieXRlIHNlY3RvcnMpCmNkMCBhdCBhdGExIGJ1cyAwIHNjYnVzMSB0YXJn ZXQgMCBsdW4gMApjZDA6IDxURUFDIENELTIyNEUgMS41QT4gUmVtb3ZhYmxlIENELVJPTSBT Q1NJIGRldmljZQpjZDA6IDE2LjcwME1CL3MgdHJhbnNmZXJzIChXRE1BMiwgQVRBUEkgMTJi eXRlcywgUElPIDY1NTM0Ynl0ZXMpCmNkMDogQXR0Cmh3cG1jOiBTT0ZULzE2LzY0LzB4Njc8 SU5ULFVTUixTWVMsUkVBLFdSST4gVFNDLzEvNjQvMHgyMDxSRUE+IFA2LzIvNDAvMHgxZmU8 VVNSLFNZUyxFREcsVEhSLFJFQSxXUkksSU5WLFFVQT4KVHJ5aW5nIHRvIG1vdW50IHJvb3Qg ZnJvbSB1ZnM6L2Rldi9taXJyb3IvZ20wczFhIFtyd10uLi4KR0VPTV9NSVJST1I6IENhbmNl bGxpbmcgdW5tYXBwZWQgYmVjYXVzZSBvZiBkYTFzMS4KR0VPTV9NSVJST1I6IENhbmNlbGxp bmcgdW5tYXBwZWQgYmVjYXVzZSBvZiBkYTBzMS4KR0VPTV9NSVJST1I6IERldmljZSBtaXJy b3IvZ20wczEgbGF1bmNoZWQgKDIvMikuCndhcm5pbmc6IHRvdGFsIGNvbmZpZ3VyZWQgc3dh cCAoMjg3ODIxIHBhZ2VzKSBleGNlZWRzIG1heGltdW0gcmVjb21tZW5kZWQgYW1vdW50ICgy NTEzMjggcGFnZXMpLgp3YXJuaW5nOiBpbmNyZWFzZSBrZXJuLm1heHN3em9uZSBvciByZWR1 Y2UgYW1vdW50IG9mIHN3YXAuCmJyaWRnZTA6IEV0aGVybmV0IGFkZHJlc3M6IDAyOjc3OjA1 OmI0OjcxOjAwCnRhcDA6IEV0aGVybmV0IGFkZHJlc3M6IDAwOmJkOjA5OjEyOmY3OjAwCmZ4 cDA6IE1pY3JvY29kZSBsb2FkZWQsIGludF9kZWxheTogMTAwMCB1c2VjICBidW5kbGVfbWF4 OiA2Cg== --------------231F62C5E033CA4292E05E9E-- From owner-freebsd-current@freebsd.org Fri Feb 16 15:06:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 999A9F1BEDE for ; Fri, 16 Feb 2018 15:06:36 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward106p.mail.yandex.net (forward106p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 192D37E77C for ; Fri, 16 Feb 2018 15:06:35 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback5g.mail.yandex.net (mxback5g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:166]) by forward106p.mail.yandex.net (Yandex) with ESMTP id 45E842D8541E; Fri, 16 Feb 2018 18:06:33 +0300 (MSK) Received: from smtp2j.mail.yandex.net (smtp2j.mail.yandex.net [2a02:6b8:0:801::ac]) by mxback5g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id BqoFdATy1k-6WQipItC; Fri, 16 Feb 2018 18:06:33 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1518793593; bh=xkaVAQYhcPi3MtCMk22Gffozp9pRTRGK673BGB3ePTM=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=kA1VyUi2yKSe2d9ZK6QGJX1b+Vsg3Iuu2Ei9r4cN4OBa+TiJFq19xqT734eSvNNtc z+O0Jwf3ymocRVhXkSH+x/p0uggDzkANvnhUigWzEhVJa7adTWwSrn5sm8XHpr6s5A P4j8psPi5DXvhksE0utBd+ocoSupOTFWQN9jpAlA= Received: by smtp2j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id LSGCwAFOXL-6Wx4GuAd; Fri, 16 Feb 2018 18:06:32 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1518793592; bh=xkaVAQYhcPi3MtCMk22Gffozp9pRTRGK673BGB3ePTM=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=O93zoKkdeibGyyh6Q6g8fsluDQq4YRdSvW7yPQRDNr29A687RhQmGMYZrnMTSugs9 htBaffukRLI7QAZTbiXD7SD3H/nOO8iqSrKioMD6CYlj594LuEGU6fJP44kZLcofzR yws4qBPIkTOtYsCC3b/gS2+gjl817u5gtIsYEApw= Authentication-Results: smtp2j.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: panic on boot after SVN r328988 To: Michael Butler , freebsd-current References: <1c1d7cd3-7236-b082-0a6d-288f2b807da1@yandex.ru> <5ff53b57-cdb5-4059-6209-9bf70101af99@protected-networks.net> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: <9559d716-762f-e484-1d98-9cc3e8491bd3@yandex.ru> Date: Fri, 16 Feb 2018 18:05:47 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <5ff53b57-cdb5-4059-6209-9bf70101af99@protected-networks.net> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="kjPV7weBU5i5VwIPmiS3lgtMEe2ADbqVf" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 15:06:36 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --kjPV7weBU5i5VwIPmiS3lgtMEe2ADbqVf Content-Type: multipart/mixed; boundary="90GVZE16gDb698xRrtQZHIruu1xIyZ6XC"; protected-headers="v1" From: "Andrey V. Elsukov" To: Michael Butler , freebsd-current Message-ID: <9559d716-762f-e484-1d98-9cc3e8491bd3@yandex.ru> Subject: Re: panic on boot after SVN r328988 References: <1c1d7cd3-7236-b082-0a6d-288f2b807da1@yandex.ru> <5ff53b57-cdb5-4059-6209-9bf70101af99@protected-networks.net> In-Reply-To: <5ff53b57-cdb5-4059-6209-9bf70101af99@protected-networks.net> --90GVZE16gDb698xRrtQZHIruu1xIyZ6XC Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 16.02.2018 17:44, Michael Butler wrote: >> do you have some specific optimization flags in make.conf? >> Can you show the output of `head -40 /var/run/dmesg.boot`? >> >=20 > The only relevant flags in /etc/make.conf are .. >=20 > CPUTYPE?=3Dpentium3 > KERNCONF=3DSARAH > NO_MODULES=3DYES >=20 > Boot log from last night's failure attached, Ok, it seems ConcurrencyKit was not tested with Pintium3. Can you show the output from kgdb: disassemble *0xc0991ff0 --=20 WBR, Andrey V. Elsukov --90GVZE16gDb698xRrtQZHIruu1xIyZ6XC-- --kjPV7weBU5i5VwIPmiS3lgtMEe2ADbqVf Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlqG80sACgkQAcXqBBDI oXoYGQf/TKovIdME+FcSk3/9mzDGw2Q+XH3QGmuoyX8WTvRPGcJspCMOjuqb/24M kJi9uZA5yZpVW75xUkVp76qbH0bZhwrlZhdPSKwJ2dzWoBBfrjY5ELN+Mh0cXkCu 3Bw0hUJVfS4qwnA4Dv9lJo4P+0YH1R6AqzjcKqzx8ucBgdE6/gkuP4osBe6MWQQn 19YpsVVF+0pYv9EQvcgPanKGkakmE9vTbsUpLK710nO5AQTLJjXoa8c3iD0ExO8Y uSkUc5W/sOwlSNKfs8RQGDqKOzOZ2zTxXTRCykbq8RGzrGzsShvlRwTOBVS98IzV Zxrdo09eVohhpd/OyXtLOfHw7XTZ7g== =Uhf6 -----END PGP SIGNATURE----- --kjPV7weBU5i5VwIPmiS3lgtMEe2ADbqVf-- From owner-freebsd-current@freebsd.org Fri Feb 16 15:13:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 03086F1C881 for ; Fri, 16 Feb 2018 15:13:10 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AC947F02D for ; Fri, 16 Feb 2018 15:13:09 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:in-reply-to :mime-version:user-agent:date:date:message-id:from:from :references:subject:subject; s=201508; t=1518793988; bh=hbilKimE uzr8+5bFSmjRu5Ky1hcTynLn81Os8trY6EY=; b=eSfRwFZV0Jlkc28mSYkbkkIt rtjXleegv5CFJnHHsSgC6pYdEpS1jgeRA6hAn58yyrLoTDPfl3cmuLn4zWa1CFUk 3vw9ydcZfcigyima9V7y9H9PaNUCo6Giuo1mPDkaRWRTLe1qQM+JYnJvKKkUd8Jc 81ARCFn6n6mfhxxbEpE= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id E186D177; Fri, 16 Feb 2018 10:13:07 -0500 (EST) Subject: Re: panic on boot after SVN r328988 To: "Andrey V. Elsukov" , freebsd-current References: <1c1d7cd3-7236-b082-0a6d-288f2b807da1@yandex.ru> <5ff53b57-cdb5-4059-6209-9bf70101af99@protected-networks.net> <9559d716-762f-e484-1d98-9cc3e8491bd3@yandex.ru> From: Michael Butler Openpgp: id=6F63E6399DCC8E3E94D60F0642FF6BAE0442D492; url=0442D492 Message-ID: <55855848-6d82-92a5-c71b-a695a0edf1e0@protected-networks.net> Date: Fri, 16 Feb 2018 10:13:07 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <9559d716-762f-e484-1d98-9cc3e8491bd3@yandex.ru> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 15:13:10 -0000 On 02/16/18 10:05, Andrey V. Elsukov wrote: > On 16.02.2018 17:44, Michael Butler wrote: >>> do you have some specific optimization flags in make.conf? >>> Can you show the output of `head -40 /var/run/dmesg.boot`? >>> >> >> The only relevant flags in /etc/make.conf are .. >> >> CPUTYPE?=pentium3 >> KERNCONF=SARAH >> NO_MODULES=YES >> >> Boot log from last night's failure attached, > > Ok, it seems ConcurrencyKit was not tested with Pintium3. > Can you show the output from kgdb: > > disassemble *0xc0991ff0 That'd do it .. :-( (kgdb) disassemble 0xc0991ff0 Dump of assembler code for function dyn_lookup_ipv4_state: 0xc0991fa0 <+0>: push %ebp 0xc0991fa1 <+1>: mov %esp,%ebp 0xc0991fa3 <+3>: push %ebx 0xc0991fa4 <+4>: push %edi 0xc0991fa5 <+5>: push %esi 0xc0991fa6 <+6>: sub $0x18,%esp 0xc0991fa9 <+9>: mov 0x10(%ebp),%edx 0xc0991fac <+12>: mov 0xc0d19dd4,%ecx 0xc0991fb2 <+18>: dec %ecx 0xc0991fb3 <+19>: and 0x4(%edx),%ecx 0xc0991fb6 <+22>: mov 0xc0d19dd8,%eax 0xc0991fbb <+27>: mov (%eax,%ecx,4),%eax 0xc0991fbe <+30>: mov %eax,0x8(%edx) 0xc0991fc1 <+33>: mov 0xc0d19ddc,%eax 0xc0991fc6 <+38>: mov (%eax,%ecx,4),%eax 0xc0991fc9 <+41>: mov %eax,-0x14(%ebp) 0xc0991fcc <+44>: mov 0xc0d19de0,%eax 0xc0991fd1 <+49>: mov (%eax,%ecx,4),%ebx 0xc0991fd4 <+52>: test %ebx,%ebx 0xc0991fd6 <+54>: je 0xc09920ba 0xc0991fdc <+60>: mov 0x8(%ebp),%edx 0xc0991fdf <+63>: mov %ecx,-0x10(%ebp) 0xc0991fe2 <+66>: data16 data16 data16 data16 nopw %cs:0x0(%eax,%eax,1) 0xc0991ff0 <+80>: lfence 0xc0991ff3 <+83>: mov %fs:0x58,%eax 0xc0991ff9 <+89>: mov %eax,-0x18(%ebp) 0xc0991ffc <+92>: mov %ebx,-0x3f409e80(%eax) 0xc0992002 <+98>: mov 0xc0d19ddc,%eax 0xc0992007 <+103>: mov (%eax,%ecx,4),%eax 0xc099200a <+106>: cmp %eax,-0x14(%ebp) 0xc099200d <+109>: jne 0xc099209d 0xc0992013 <+115>: movzbl 0x1(%ebx),%eax 0xc0992017 <+119>: cmp 0xd(%edx),%al 0xc099201a <+122>: jne 0xc0992090 0xc099201c <+124>: mov 0x10(%ebp),%eax 0xc099201f <+127>: movzwl 0x2(%eax),%eax 0xc0992023 <+131>: test %ax,%ax 0xc0992026 <+134>: je 0xc099202e 0xc0992028 <+136>: cmp %ax,0x2(%ebx) 0xc099202c <+140>: jne 0xc0992090 0xc099202e <+142>: movzwl 0x4(%ebx),%esi 0xc0992032 <+146>: movzwl 0xa(%edx),%edi 0xc0992036 <+150>: cmp %di,%si 0xc0992039 <+153>: jne 0xc0992063 From owner-freebsd-current@freebsd.org Fri Feb 16 17:52:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89EAAF03E3E for ; Fri, 16 Feb 2018 17:52:39 +0000 (UTC) (envelope-from mlfbsd@kanar.ci0.org) Received: from kanar.ci0.org (kanar.ci0.org [IPv6:2001:bc8:35e6::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sd-123398", Issuer "sd-123398" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0BBE068B96 for ; Fri, 16 Feb 2018 17:52:38 +0000 (UTC) (envelope-from mlfbsd@kanar.ci0.org) Received: from kanar.ci0.org (pluxor@localhost [127.0.0.1]) by kanar.ci0.org (8.15.2/8.15.2) with ESMTPS id w1GHqCOC072911 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 16 Feb 2018 18:52:12 +0100 (CET) (envelope-from mlfbsd@kanar.ci0.org) Received: (from mlfbsd@localhost) by kanar.ci0.org (8.15.2/8.15.2/Submit) id w1GHpuuQ072909; Fri, 16 Feb 2018 18:51:56 +0100 (CET) (envelope-from mlfbsd) Date: Fri, 16 Feb 2018 18:51:56 +0100 From: Olivier Houchard To: Michael Butler Cc: "Andrey V. Elsukov" , freebsd-current Subject: Re: panic on boot after SVN r328988 Message-ID: <20180216175156.GA71996@ci0.org> References: <1c1d7cd3-7236-b082-0a6d-288f2b807da1@yandex.ru> <5ff53b57-cdb5-4059-6209-9bf70101af99@protected-networks.net> <9559d716-762f-e484-1d98-9cc3e8491bd3@yandex.ru> <55855848-6d82-92a5-c71b-a695a0edf1e0@protected-networks.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55855848-6d82-92a5-c71b-a695a0edf1e0@protected-networks.net> User-Agent: Mutt/1.8.0 (2017-02-23) X-Mailman-Approved-At: Fri, 16 Feb 2018 18:16:20 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 17:52:39 -0000 Hi Michael, On Fri, Feb 16, 2018 at 10:13:07AM -0500, Michael Butler wrote: > On 02/16/18 10:05, Andrey V. Elsukov wrote: > > On 16.02.2018 17:44, Michael Butler wrote: > >>> do you have some specific optimization flags in make.conf? > >>> Can you show the output of `head -40 /var/run/dmesg.boot`? > >>> > >> > >> The only relevant flags in /etc/make.conf are .. > >> > >> CPUTYPE?=pentium3 > >> KERNCONF=SARAH > >> NO_MODULES=YES > >> > >> Boot log from last night's failure attached, > > > > Ok, it seems ConcurrencyKit was not tested with Pintium3. > > Can you show the output from kgdb: > > > > disassemble *0xc0991ff0 > > That'd do it .. :-( [...] Sorry about this. It should be fixed with r329388. Can you update and let me know how it goes ? Thanks ! Olivier From owner-freebsd-current@freebsd.org Fri Feb 16 21:54:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B170FF15E4E for ; Fri, 16 Feb 2018 21:54:53 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 12EC5746AD; Fri, 16 Feb 2018 21:54:52 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [172.24.42.2] (ec2-34-214-251-129.us-west-2.compute.amazonaws.com [34.214.251.129]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 47201628 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Fri, 16 Feb 2018 13:54:15 -0800 (PST) Subject: Re: New ACPI Errors To: Jung-uk Kim , Claude Buisson Cc: FreeBSD-current References: <58d889fa-a9c5-5108-c838-01f4904950cd@nomadlogic.org> <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> <7bb2e69f-2666-e813-b683-a4f035b220d5@FreeBSD.org> From: Pete Wright Message-ID: <17a0c5eb-38a7-1956-5b6e-9ac08c2593e6@nomadlogic.org> Date: Fri, 16 Feb 2018 13:54:50 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <7bb2e69f-2666-e813-b683-a4f035b220d5@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Feb 2018 21:54:53 -0000 On 02/15/2018 13:37, Jung-uk Kim wrote: > On 02/13/2018 17:34, Claude Buisson wrote: >> On 02/13/2018 22:49, Pete Wright wrote: >>> Hello, >>> I have started seeing a lot of these messages spam my system log: >>> >>> ACPI Error: No pointer back to namespace node in package >>> 0xfffff8000f79a080 (20180209/dsargs-472) >>> ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, >>> AE_AML_INTERNAL (20180209/psparse-677) >>> ACPI Error: Method parse/execution failed \134_SB.AC._PSR, >>> AE_AML_INTERNAL (20180209/psparse-677) >>> >>> I noticed this starting from a CURRENT build i installed two weeks >>> ago, and still see it from a world/kernel i built last night.  two >>> questions: >>> 1) has anyone else noticed this? >>> 2) is this something to worry about? >>> >>> i can help debug the issue but am not sure where to start poking. >>> >>> thanks! >>> -pete >>> >> Here I have >> >> ACPI Error: No pointer back to namespace node in package >> 0xfffff8000171f700 (20180209/dsargs-472) >> ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName >> unavailable] (20180209/dswexec-606) >> ACPI Error: Method parse/execution failed >> \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) >> >> with svn 329142 on a Lenovo ThinkCentre M83 >> ACPI APIC Table: >> >> Claude Buisson > I believe you can silence the errors with the attached patch. Please > try it and let me know. hrm still getting errors: Feb 16 13:49:45 runner kernel: ACPI Error: No pointer back to namespace node in package 0xfffff80003c8c080 (20180209/dsargs-472) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) here's my diff: diff --git a/sys/contrib/dev/acpica/include/platform/acfreebsd.h b/sys/contrib/dev/acpica/include/platform/acfreebsd.h index 905dffb7a40..df89399a369 100644 --- a/sys/contrib/dev/acpica/include/platform/acfreebsd.h +++ b/sys/contrib/dev/acpica/include/platform/acfreebsd.h @@ -166,6 +166,7 @@  #define ACPI_UINTPTR_T      uintptr_t +#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS  #define ACPI_USE_DO_WHILE_0  #define ACPI_USE_LOCAL_CACHE  #define ACPI_USE_NATIVE_DIVIDE -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Sat Feb 17 10:38:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66EE2F24D02 for ; Sat, 17 Feb 2018 10:38:26 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x243.google.com (mail-lf0-x243.google.com [IPv6:2a00:1450:4010:c07::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D945974014 for ; Sat, 17 Feb 2018 10:38:25 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x243.google.com with SMTP id v9so5203068lfa.11 for ; Sat, 17 Feb 2018 02:38:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=FC/SUDyB1C2q1FWmZAUht8zkBszM9ya6hTimbvWjLvg=; b=ZNvJaafHFlpVcFvMom6adR7G0npB5YV+mcrhK4Cpzmo0oNysP8MEli0UPtIExjR5og MxNYq4zW+0WbpRAglheNR27BMj4JjKS6mNvYxSkHSdX5CyTHpX0K/WitQd2JhiuFyw7X 38m92/obuqPWu0kTL8uY0IXi1EAvQTBnYIhPPFevpeLhBwSlmpJ5KwGKqbUbzAwQpJS+ g+fm7gX30rQ7MiYYeIr65RS4AZEfBMDj/FWMSAMXeR0gKLWEly4APYis2mNOkJ4L5nEH wIFvZUfrd7RoK9LwGJNnv1sTeBIO8fg+YzvFzbBiHy9XxW+OWPM1RkTvS20mXZzbASYJ cl/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=FC/SUDyB1C2q1FWmZAUht8zkBszM9ya6hTimbvWjLvg=; b=pn+thig29nsO0Kluh2YLKP9Ssvmzk3TsqXJjf7io05Uv4seeEwSfht11VkLQU/J+td vKx0nS6UuwrOfb6vybLqMqgAhbt0Co6MJgb2WUQUnA0HT/Rf0mZMlbup9GHtX+mWZS84 g8p9unzd1FV5UVbDyLNflg3lp/IRWJtzHUVXmuIvqZ2JG/adWrut8g9xI0OoZNw5fRyZ +LXn+dmT7M6992IywoKgzTzm4teFCDOiAE8MgE2AN+Cd7TvVaxdJjPf4yQNZpRWwQUZk MzVVSzh1CaQsOZDx/dV6uKI1vLGDnE0g5ZQKeDZtWCFzI5mESe6E3MXLOOdeEwivC7nD 5bfg== X-Gm-Message-State: APf1xPDwWz8jZzZHnIMhZJRfToCdcmtA8okI243T9kDJpPOdDwLHIZN7 lNYeBTOtfk5oqFcfRv48eQitng== X-Google-Smtp-Source: AH8x226yoAl1n54VhEJz+0abYWdDmQYh1VE/MZzmGzMirG9+OstzZgxGgJ1TjCkE45bVW7YW5HF8mQ== X-Received: by 10.25.35.132 with SMTP id j126mr5816088lfj.130.1518863904268; Sat, 17 Feb 2018 02:38:24 -0800 (PST) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id s72sm4095094lfk.3.2018.02.17.02.38.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Feb 2018 02:38:22 -0800 (PST) Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> From: "Alex V. Petrov" Message-ID: <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> Date: Sat, 17 Feb 2018 17:38:20 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 10:38:26 -0000 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: on boot multilines: devmatch: Malformed NOMATCH string: ''?'' mouse don't start 13.02.2018 19:50, Hans Petter Selasky пишет: > On 02/13/18 10:47, Jakob Alvermark wrote: >> +1 >> >> My USB mouse was working fine before the switch to devmatch. Now I >> have to 'kldload ums' manually. >> >> Same for USB audio, snd_uaudio.ko was loaded by devd before. >> > > Hi, > > This is a known issue. > > Can you try the attached patch? > > Rebuild devmatch(8) and reinstall /etc/devd/devmatch.conf and > /etc/rc.d/devmatch only. > > --HPS > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- ----- Alex. From owner-freebsd-current@freebsd.org Sat Feb 17 12:03:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD9E9F0635D for ; Sat, 17 Feb 2018 12:03:59 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 DF65079E41; Sat, 17 Feb 2018 12:03:58 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 8646626027E; Sat, 17 Feb 2018 13:03:57 +0100 (CET) To: Warner Losh , FreeBSD Current From: Hans Petter Selasky Subject: panic in daprobedone: Unholding 4 with cnt = 0 Message-ID: Date: Sat, 17 Feb 2018 13:01:00 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 12:03:59 -0000 I've started to hit this panic with USB mass storage, before even the device has become in-use: panic: Unholding 4 with cnt = 0 Backtrace: vpanic() panic() daprobedone() dadone() xpt_done_process() xpt_done_td() fork_exit() fork_trampoline() db> > static inline void > da_periph_unhold(struct cam_periph *periph, da_ref_token token) > { > int cnt; > struct da_softc *softc = periph->softc; > > token_sanity(token); > DA_PERIPH_PRINT(periph, "Unholding device %s (%d)\n", > da_ref_text[token], token); > cnt = atomic_fetchadd_int(&softc->ref_flags[token], -1); > if (cnt != 1) > panic("Unholding %d with cnt = %d", token, cnt); > cam_periph_unhold(periph); > } From owner-freebsd-current@freebsd.org Sat Feb 17 12:16:38 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47416F07910 for ; Sat, 17 Feb 2018 12:16:38 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B4F497AC07 for ; Sat, 17 Feb 2018 12:16:37 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: by mailman.ysv.freebsd.org (Postfix) id 74224F0790F; Sat, 17 Feb 2018 12:16:37 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 503C2F0790D for ; Sat, 17 Feb 2018 12:16:37 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nsstlmta10p.bpe.bigpond.com (nsstlmta10p.bpe.bigpond.com [203.38.21.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Openwave Messaging Inc." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CEB1A7ABFF; Sat, 17 Feb 2018 12:16:32 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from smtp.telstra.com ([10.10.24.4]) by nsstlfep10p-svc.bpe.nexus.telstra.com.au with ESMTP id <20180217121622.VTTG21928.nsstlfep10p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com>; Sat, 17 Feb 2018 23:16:22 +1100 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtfedrgedugdegtdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfupfevtfgpvffgnffuvfftteenuceurghilhhouhhtmecufedttdenucenucfjughrpefhtggguffkfffvofesmhdtmherhhdtvdenucfhrhhomheptehnughrvgifucftvghilhhlhicuoegrrhgvihhllhihsegsihhgphhonhgurdhnvghtrdgruheqnecuffhomhgrihhnpegrtgdqrhdrnhhunecukfhppeduvdegrdduledtrdegtddrudekvdenucfrrghrrghmpehhvghlohepghhhrghnrghmihgrrdgrtgdqrhdrnhhupdhinhgvthepuddvgedrudeltddrgedtrddukedvpdhmrghilhhfrhhomhepoegrrhgvihhllhihsegsihhgphhonhgurdhnvghtrdgr X-RG-VS-CLASS: clean X-Authentication-Info: Submitted using ID areilly@bigpond.net.au Received: from ghanamia.ac-r.nu (124.190.40.182) by smtp.telstra.com (9.0.019.22-1) (authenticated as areilly@bigpond.net.au) id 5A6144360B53867C; Sat, 17 Feb 2018 23:16:22 +1100 From: Andrew Reilly Content-Type: multipart/mixed; boundary="Apple-Mail=_7A6A6105-CFEA-4690-ACC8-825D00238CE5" Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Since last week (today) current on my Ryzen box is unstable Message-Id: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> Date: Sat, 17 Feb 2018 23:16:21 +1100 Cc: current@freebsd.org, kib@freebsd.org To: avg@freebsd.org X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 12:16:38 -0000 --Apple-Mail=_7A6A6105-CFEA-4690-ACC8-825D00238CE5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi, I do a weekly build to track changes, on 12-current since I gave my = fileserver this new Ryzen motherboard a few months ago. I switched to = current because there was some badness in 11-stable that I attributed to = new processor twitchiness (wouldn't reboot, temperature sensors not = working.) A month or so of 12- has been lovely, for the most part. Today's rebuild has given me uptimes of below an hour, usually. The box = will stay up in single user mode long enough to rebuild world/kernel, = but multi-user it is panicking at = /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:1592 The backtrace shows that it gets to this panic from a sendfile() = syscall. The line above is in the middle of a big edit that's part of = svn revision 329363. The tripping assertion seems to suggest that = m->valid !=3D 0, for whatever that's worth. Anything that I should be trying? On a side-note, the new devmatch workings are giving me 43 boot warnings = about "Malformed NOMATCH string: ''?'', and devmatch_enable=3D"NO" in = /etc/rc.conf doesn't seem to help, and the new matching is very very = keen to load cc_vegas.ko, a lot. Here's the output of devmatch -v, in = case that helps: $ devmatch -v Searching acpi bus at handle=3D\_PR_.P008 for pnpinfo _HID=3Dnone = _UID=3D0 Searching acpi bus at handle=3D\_PR_.P009 for pnpinfo _HID=3Dnone = _UID=3D0 Searching acpi bus at handle=3D\_PR_.P00A for pnpinfo _HID=3Dnone = _UID=3D0 Searching acpi bus at handle=3D\_PR_.P00B for pnpinfo _HID=3Dnone = _UID=3D0 Searching acpi bus at handle=3D\_PR_.P00C for pnpinfo _HID=3Dnone = _UID=3D0 Searching acpi bus at handle=3D\_PR_.P00D for pnpinfo _HID=3Dnone = _UID=3D0 Searching acpi bus at handle=3D\_PR_.P00E for pnpinfo _HID=3Dnone = _UID=3D0 Searching acpi bus at handle=3D\_PR_.P00F for pnpinfo _HID=3Dnone = _UID=3D0 Searching pci bus at slot=3D0 function=3D2 dbsf=3Dpci0:0:0:2 = handle=3D\_SB_.PCI0.IOMA for pnpinfo vendor=3D0x1022 device=3D0x1451 = subvendor=3D0x1022 subdevice=3D0x1451 class=3D0x080600 Searching pci bus at slot=3D0 function=3D0 dbsf=3Dpci0:9:0:0 for = pnpinfo vendor=3D0x8086 device=3D0x24fb subvendor=3D0x8086 = subdevice=3D0x2110 class=3D0x028000 Searching pci bus at slot=3D0 function=3D1 dbsf=3Dpci0:11:0:1 for = pnpinfo vendor=3D0x1002 device=3D0xaab0 subvendor=3D0x174b = subdevice=3D0xaab0 class=3D0x040300 Searching pci bus at slot=3D0 function=3D0 dbsf=3Dpci0:17:0:0 for = pnpinfo vendor=3D0x1022 device=3D0x145a subvendor=3D0x1022 = subdevice=3D0x145a class=3D0x130000 Searching pci bus at slot=3D0 function=3D2 dbsf=3Dpci0:17:0:2 = handle=3D\_SB_.PCI0.GP17.APSP for pnpinfo vendor=3D0x1022 device=3D0x1456 = subvendor=3D0x1022 subdevice=3D0x1456 class=3D0x108000 cc_vegas.ko Searching pci bus at slot=3D0 function=3D0 dbsf=3Dpci0:18:0:0 for = pnpinfo vendor=3D0x1022 device=3D0x1455 subvendor=3D0x1022 = subdevice=3D0x1455 class=3D0x130000 Searching acpi bus at handle=3D\_SB_.PCI0.SBRG.PIC_ for pnpinfo = _HID=3DPNP0000 _UID=3D0 Searching acpi bus at handle=3D\_SB_.PCI0.SBRG.SPKR for pnpinfo = _HID=3DPNP0800 _UID=3D0 Searching acpi bus at handle=3D\_SB_.GPIO for pnpinfo _HID=3DAMDI0030 = _UID=3D0 Searching acpi bus at handle=3D\_SB_.PTIO for pnpinfo _HID=3DAMDIF030 = _UID=3D0 Searching acpi bus at handle=3D\AOD_ for pnpinfo _HID=3DPNP0C14 _UID=3D0 I can't tell if this is related to the zfs problem or not. As far as = I'm aware, cc_vegas.ko was not loaded into the kernel before today. FWIW uname -a says: FreeBSD Zen.ac-r.nu 12.0-CURRENT FreeBSD 12.0-CURRENT #6 r329450: Sat = Feb 17 22:36:19 AEDT 2018 = root@:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 I'll attach the dmesg.boot from the boot that I had to do while = composing this message... Cheers, Andrew --Apple-Mail=_7A6A6105-CFEA-4690-ACC8-825D00238CE5 Content-Disposition: attachment; filename=dmesg.boot Content-Type: application/octet-stream; x-unix-mode=0644; name="dmesg.boot" Content-Transfer-Encoding: 7bit Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT #6 r329450: Sat Feb 17 22:36:19 AEDT 2018 root@:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 FreeBSD clang version 6.0.0 (branches/release_60 325330) (based on LLVM 6.0.0) WARNING: WITNESS option enabled, expect reduced performance. VT(vga): resolution 640x480 CPU: AMD Ryzen 7 1700 Eight-Core Processor (2994.46-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 Features=0x178bfbff Features2=0x7ed8320b AMD Features=0x2e500800 AMD Features2=0x35c233ff Structured Extended Features=0x209c01a9 XSAVE Features=0xf AMD Extended Feature Extensions ID EBX=0x7 SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 33274941440 (31733 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 2 cache groups x 4 core(s) random: unblocking device. Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20180209/tbfadt-796) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-55 on motherboard SMP: AP CPU #6 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! Timecounter "TSC-low" frequency 1497229665 Hz quality 1000 random: entropy device external interface [ath_hal] loaded module_register_init: MOD_LOAD (vesa, 0xffffffff80ffe3e0, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" kbd1 at kbdmux0 netmap: loaded module nexus0 vtvga0: on motherboard cryptosoft0: on motherboard aesni0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 on acpi0 atrtc0: registered as a time-of-day clock, resolution 1.000000s Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 350 Event timer "HPET1" frequency 14318180 Hz quality 350 Event timer "HPET2" frequency 14318180 Hz quality 350 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 amdsmn0: on hostb0 amdtemp0: on hostb0 pci0: at device 0.2 (no driver attached) pcib1: at device 1.1 on pci0 pci1: on pcib1 nvme0: mem 0xfe900000-0xfe903fff irq 24 at device 0.0 on pci1 pcib2: at device 1.3 on pci0 pci2: on pcib2 xhci0: mem 0xfe6a0000-0xfe6a7fff irq 32 at device 0.0 on pci2 xhci0: 32 bytes context size, 64-bit DMA usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 ahci0: mem 0xfe680000-0xfe69ffff irq 33 at device 0.1 on pci2 ahci0: AHCI v1.31 with 8 6Gbps ports, Port Multiplier supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 pcib3: irq 34 at device 0.2 on pci2 pci3: on pcib3 pcib4: irq 32 at device 0.0 on pci3 pci4: on pcib4 pcib5: irq 33 at device 1.0 on pci3 pci5: on pcib5 pcib6: irq 32 at device 4.0 on pci3 pci6: on pcib6 pcib7: irq 33 at device 5.0 on pci3 pci7: on pcib7 pcib8: irq 34 at device 6.0 on pci3 pci8: on pcib8 pci8: at device 0.0 (no driver attached) pcib9: irq 35 at device 7.0 on pci3 pci9: on pcib9 igb0: port 0xf000-0xf01f mem 0xfe400000-0xfe41ffff,0xfe420000-0xfe423fff irq 32 at device 0.0 on pci9 igb0: attach_pre capping queues at 2 igb0: using 1024 tx descriptors and 1024 rx descriptors igb0: msix_init qsets capped at 2 igb0: pxm cpus: 8 queue msgs: 4 admincnt: 1 igb0: using 2 rx queues 2 tx queues igb0: Using MSIX interrupts with 3 vectors igb0: allocated for 2 tx_queues igb0: allocated for 2 rx_queues igb0: Ethernet address: 70:85:c2:59:38:4e igb0: netmap queues/slots: TX 2/1024, RX 2/1024 pcib10: at device 3.1 on pci0 pci10: on pcib10 vgapci0: port 0xe000-0xe0ff mem 0xe0000000-0xefffffff,0xfe800000-0xfe83ffff irq 54 at device 0.0 on pci10 vgapci0: Boot video device hdac0: mem 0xfe860000-0xfe863fff irq 55 at device 0.1 on pci10 hdac0: hdac_get_capabilities: Invalid corb size (0) device_attach: hdac0 attach returned 6 pcib11: at device 7.1 on pci0 pci11: on pcib11 pci11: at device 0.0 (no driver attached) pci11: at device 0.2 (no driver attached) xhci1: mem 0xfe100000-0xfe1fffff irq 37 at device 0.3 on pci11 xhci1: 64 bytes context size, 64-bit DMA usbus1 on xhci1 usbus1: 5.0Gbps Super Speed USB v3.0 pcib12: at device 8.1 on pci0 pci12: on pcib12 pci12: at device 0.0 (no driver attached) ahci1: mem 0xfe708000-0xfe708fff irq 42 at device 0.2 on pci12 ahci1: AHCI v1.31 with 1 6Gbps ports, Port Multiplier supported with FBS ahcich8: at channel 0 on ahci1 hdac0: mem 0xfe700000-0xfe707fff irq 43 at device 0.3 on pci12 isab0: at device 20.3 on pci0 isa0: on isab0 acpi_button0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem 0xc0000-0xcffff pnpid ORM0000 on isa0 hwpstate0: on cpu0 ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec ugen0.1: <0x1022 XHCI root HUB> at usbus0 uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 nvd0: NVMe namespace nvd0: 228936MB (468862128 512 byte sectors) hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 20,22,21 and 24,26 on hdaa0 pcm1: at nid 27 and 25 on hdaa0 pcm2: at nid 30 on hdaa0 ugen1.1: <0x1022 XHCI root HUB> at usbus1 uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA8-ACS SATA 3.x device ada0: Serial Number PK1334PEHWZT7S ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 3815447MB (7814037168 512 byte sectors) ada1 at ahcich1 bus 0 scbus1 target 0 lun 0 ada1: ATA8-ACS SATA 3.x device ada1: Serial Number PK1334PEHZBWXS ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 3815447MB (7814037168 512 byte sectors) ada2 at ahcich4 bus 0 scbus2 target 0 lun 0 ada2: ATA8-ACS SATA 3.x device ada2: Serial Number PK1334PEHYSZ6S ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 3815447MB (7814037168 512 byte sectors) ada3 at ahcich5 bus 0 scbus3 target 0 lun 0 ada3: ATA8-ACS SATA 3.x device ada3: Serial Number PK1334PEHZDA1S ada3: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada3: Command Queueing enabled ada3: 3815447MB (7814037168 512 byte sectors) WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from zfs:root [rw]... Root mount waiting for: usbus1 usbus0 uhub1: 8 ports with 8 removable, self powered uhub0: 22 ports with 22 removable, self powered Root mount waiting for: usbus1 usbus0 ugen0.2: at usbus0 ubt0 on uhub0 ubt0: on usbus0 ugen1.2: at usbus1 umass0 on uhub1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x0100 umass0:5:0: Attached to scbus5 da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 da0: Fixed Direct Access SPC-4 SCSI device da0: Serial Number 1153000117AD da0: 400.000MB/s transfers da0: 5723166MB (1465130646 4096 byte sectors) da0: quirks=0x2 Root mount waiting for: usbus0 ugen0.3: at usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 Link state changed to up igb0: link state changed to UP --Apple-Mail=_7A6A6105-CFEA-4690-ACC8-825D00238CE5-- From owner-freebsd-current@freebsd.org Sat Feb 17 12:45:55 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70362F0A1EE for ; Sat, 17 Feb 2018 12:45:55 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0EBA97C2BB for ; Sat, 17 Feb 2018 12:45:55 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id C3B4EF0A1EC; Sat, 17 Feb 2018 12:45:54 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B187BF0A1EB for ; Sat, 17 Feb 2018 12:45:54 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 4BD9F7C2B8; Sat, 17 Feb 2018 12:45:54 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 410EA26027E; Sat, 17 Feb 2018 13:45:52 +0100 (CET) Subject: Re: Since last week (today) current on my Ryzen box is unstable To: Andrew Reilly , avg@freebsd.org Cc: current@freebsd.org, kib@freebsd.org References: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> From: Hans Petter Selasky Message-ID: Date: Sat, 17 Feb 2018 13:42:55 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> Content-Type: multipart/mixed; boundary="------------91046396B63DE7E74028EF2C" Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 12:45:55 -0000 This is a multi-part message in MIME format. --------------91046396B63DE7E74028EF2C Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 02/17/18 13:16, Andrew Reilly wrote: > On a side-note, the new devmatch workings are giving me 43 boot warnings about "Malformed NOMATCH string: ''?'', and devmatch_enable="NO" in /etc/rc.conf doesn't seem to help, and the new matching is very very keen to load cc_vegas.ko, a lot. Here's the output of devmatch -v, in case that helps: Hi, Does the attached patch solve the devmatch issue? Just apply it directly on /etc and reboot. --HPS --------------91046396B63DE7E74028EF2C Content-Type: text/x-patch; name="devmatch.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="devmatch.diff" Index: etc/devd/devmatch.conf =================================================================== --- etc/devd/devmatch.conf (revision 329447) +++ etc/devd/devmatch.conf (working copy) @@ -9,7 +9,7 @@ # # Generic NOMATCH event nomatch 100 { - action "service devmatch start '?$_'"; + action "/etc/rc.d/devmatch start '?$_'"; }; # Add the following to devd.conf to prevent this from running: Index: etc/rc.d/devmatch =================================================================== --- etc/rc.d/devmatch (revision 329447) +++ etc/rc.d/devmatch (working copy) @@ -37,7 +37,7 @@ start_cmd="${name}_start" stop_cmd=':' -[ -n "$2" ] && one_nomatch="-p '$2'" +[ -n "$2" ] && one_nomatch=-p "$2" devmatch_start() { --------------91046396B63DE7E74028EF2C-- From owner-freebsd-current@freebsd.org Sat Feb 17 13:09:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 200ECF0BD37 for ; Sat, 17 Feb 2018 13:09:05 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AE8BE7CF20 for ; Sat, 17 Feb 2018 13:09:04 +0000 (UTC) (envelope-from hps@selasky.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6869AF0BD2B; Sat, 17 Feb 2018 13:09:04 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54740F0BD29 for ; Sat, 17 Feb 2018 13:09:04 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 E158E7CF1D; Sat, 17 Feb 2018 13:09:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id B45AB26027E; Sat, 17 Feb 2018 14:08:59 +0100 (CET) Subject: Re: Since last week (today) current on my Ryzen box is unstable From: Hans Petter Selasky To: Andrew Reilly , avg@freebsd.org Cc: current@freebsd.org, kib@freebsd.org References: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> Message-ID: Date: Sat, 17 Feb 2018 14:06:03 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------9603A69FABAC7864CD02A28F" Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 13:09:05 -0000 This is a multi-part message in MIME format. --------------9603A69FABAC7864CD02A28F Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit On 02/17/18 13:42, Hans Petter Selasky wrote: > On 02/17/18 13:16, Andrew Reilly wrote: >> On a side-note, the new devmatch workings are giving me 43 boot >> warnings about "Malformed NOMATCH string: ''?'', and >> devmatch_enable="NO" in /etc/rc.conf doesn't seem to help, and the new >> matching is very very keen to load cc_vegas.ko, a lot.  Here's the >> output of devmatch -v, in case that helps: > > Hi, > > Does the attached patch solve the devmatch issue? Just apply it directly > on /etc and reboot. > > --HPS > Please find updated patch attached. --HPS --------------9603A69FABAC7864CD02A28F Content-Type: text/x-patch; name="devmatch.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="devmatch.diff" Index: etc/devd/devmatch.conf =================================================================== --- etc/devd/devmatch.conf (revision 329447) +++ etc/devd/devmatch.conf (working copy) @@ -9,7 +9,7 @@ # # Generic NOMATCH event nomatch 100 { - action "service devmatch start '?$_'"; + action "/etc/rc.d/devmatch start '?$_'"; }; # Add the following to devd.conf to prevent this from running: Index: etc/rc.d/devmatch =================================================================== --- etc/rc.d/devmatch (revision 329447) +++ etc/rc.d/devmatch (working copy) @@ -37,13 +37,17 @@ start_cmd="${name}_start" stop_cmd=':' -[ -n "$2" ] && one_nomatch="-p '$2'" +one_nomatch=$2 devmatch_start() { local x - x=$(devmatch ${one_nomatch} | sort -u) + if [ -n "$one_nomatch" ]; then + x=$(devmatch -p "${one_nomatch}" | sort -u) + else + x=$(devmatch | sort -u) + fi [ -n "$x" ] || return --------------9603A69FABAC7864CD02A28F-- From owner-freebsd-current@freebsd.org Sat Feb 17 13:34:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A78FF0E197 for ; Sat, 17 Feb 2018 13:34:06 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 16D517E51B for ; Sat, 17 Feb 2018 13:34:06 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 09D1826027E; Sat, 17 Feb 2018 14:34:04 +0100 (CET) Subject: Re: devd in r329188M don't start To: "Alex V. Petrov" , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> From: Hans Petter Selasky Message-ID: Date: Sat, 17 Feb 2018 14:31:08 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 13:34:06 -0000 On 02/17/18 11:38, Alex V. Petrov wrote: > 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: > on boot multilines: > > devmatch: Malformed NOMATCH string: ''?'' > Can you try these two patches: https://svnweb.freebsd.org/changeset/base/329455 https://svnweb.freebsd.org/changeset/base/329456 Obviously USB attaching was not tested before submitting. --HPS From owner-freebsd-current@freebsd.org Sat Feb 17 13:51:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFA9EF0F76F for ; Sat, 17 Feb 2018 13:51:40 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 255BA7F246 for ; Sat, 17 Feb 2018 13:51:40 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x234.google.com with SMTP id 70so1576147lfw.2 for ; Sat, 17 Feb 2018 05:51:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=+8TamPzs9nEt8HYiQDwyX/Tgqh58M953ZV+fWzJD1kc=; b=eeHgeQZprdKo6U5SwGc2ljimCv1aJVEwg6gMyrPHq8u6DdlUn082UwtOBT6sAniCCi /qwF0UHtFCH/RFgwzKUu4ZlSx500hWXVgcMrTd9TF4ksrgFiA39M2P0pVckg7+7RK+Z2 dR2dnXS+CPnjd0AZ3HP8Q5U2s3VD4uCj8xsYQxWxEIgDpnZJ6Br8d8QKpAkRawb+Hmyl fO4H5zeeSsFL3TVrrNTLHaSmqg6VHwpyTyOL7yAs6DA7HNFkJJo2Q7EHuJLUOAMLTj7u XvQzSjLXiLlRlSO6Ap9t7v8eOfhNfoG0o7eg337A9/7S31MfuQrt45WYtzIfvfnCRrMy 7sIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+8TamPzs9nEt8HYiQDwyX/Tgqh58M953ZV+fWzJD1kc=; b=LnZfacIXUYs4YgwW+aXE65VQEa1KqKmOBnkc703nHwe5nYRQSjQYTLcyT8SOq6akRO 4U3kESVDY+HEYervJkYirgO1hyotd3hvPrpJqkSW8U1Dki8y7PJM8TfMm9Jud2S3R4X8 kakIrOutfl1mDb9YHIGqnqXZy2g4IpbjmGqdyeKABE+D5Mob5uvBCfFzrS2NeXg6SPur CqPfVrE0ZBe1LaaTCvDqjniVmF7kmKSeyZXjBfzKWOfUJh7RYS44W4MUJmSFHevEILfx fXRHyTl8CrNW8cttH/+6fKS8QtGvmokuszp/mkjwb/3IZvHTQfQ/+L67TR4WOuEAH3EH ll1g== X-Gm-Message-State: APf1xPDyPKYApEnV+zht9unGi9lRMu00Qckx1o+ADiJlAP70PAP+hSzz jsRz7SgagYTKd4AC9M+HxyFkVA== X-Google-Smtp-Source: AH8x226yxs/w3TCHlvVRKJfP2ppd9OojQhx11mSLGH9HWqfPTy/z4aUoFhx2apqiZm/xdEhGm1T5vQ== X-Received: by 10.46.43.3 with SMTP id q3mr5980187lje.130.1518875497784; Sat, 17 Feb 2018 05:51:37 -0800 (PST) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id d28sm1242302ljf.74.2018.02.17.05.51.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Feb 2018 05:51:36 -0800 (PST) Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> From: "Alex V. Petrov" Message-ID: Date: Sat, 17 Feb 2018 20:51:35 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 13:51:41 -0000 devmatch: Malformed NOMATCH string: ''?'' persists 17.02.2018 20:31, Hans Petter Selasky пишет: > On 02/17/18 11:38, Alex V. Petrov wrote: >> 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: >> on boot multilines: >> >> devmatch: Malformed NOMATCH string: ''?'' >> > > Can you try these two patches: > > https://svnweb.freebsd.org/changeset/base/329455 > https://svnweb.freebsd.org/changeset/base/329456 > > Obviously USB attaching was not tested before submitting. > > --HPS > > -- ----- Alex. From owner-freebsd-current@freebsd.org Sat Feb 17 13:57:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8F3F4F101C3; Sat, 17 Feb 2018 13:57:51 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 017FC7F7E8; Sat, 17 Feb 2018 13:57:50 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id 9e8bb61a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sat, 17 Feb 2018 13:51:07 +0000 (UTC) Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update To: Hans Petter Selasky , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> From: Greg V Message-ID: <90712e46-15a9-6107-b0f8-c64ac333c7e1@unrelenting.technology> Date: Sat, 17 Feb 2018 16:51:04 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 13:57:51 -0000 On 01/20/2018 12:18, Hans Petter Selasky wrote: > On 01/20/18 00:17, Greg V via freebsd-net wrote: >> >> On 01/19/2018 12:54, Hans Petter Selasky wrote: >>> On 01/18/18 14:11, Greg V wrote: >>>> Hi. I've upgraded CURRENT from December 19 >>>> (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) >>>> to today >>>> (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) >>>> and my Mellanox ConnectX-2 network card stopped working: >>>> >>>> mlx4_core0: mem >>>> 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff irq 32 at device 0.0 on >>>> pci7 >>>> mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) >>>> mlx4_core: Initializing mlx4_core >>>> mlx4_core0: command 0xffa failed: fw status = 0x1 >>>> mlx4_core0: Failed to map EQ context memory, aborting >>>> device_attach: mlx4_core0 attach returned 12 >>>> >>>> >>>> Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually >>>> does work fine! >>>> >>>> Reverting all mlx4 changes between then and now (no big changes, >>>> mostly just the 1 << 31 thing from D13858) and rebuilding the mlx4 >>>> module with CC=clang50 does not help. >>>> >>>> What happened?! Upgraded CURRENT again today, the problem went away :) From owner-freebsd-current@freebsd.org Sat Feb 17 14:21:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3283F123F4 for ; Sat, 17 Feb 2018 14:21:26 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 61E11809DE for ; Sat, 17 Feb 2018 14:21:26 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 10B6726027E; Sat, 17 Feb 2018 15:21:25 +0100 (CET) Subject: Re: devd in r329188M don't start To: "Alex V. Petrov" , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> From: Hans Petter Selasky Message-ID: <014c8376-939f-3b8e-d8a1-0d08407e8a5d@selasky.org> Date: Sat, 17 Feb 2018 15:18:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 14:21:26 -0000 On 02/17/18 14:51, Alex V. Petrov wrote: > devmatch: Malformed NOMATCH string: ''?'' persists > > Did you reinstall /etc ? --HPS From owner-freebsd-current@freebsd.org Sat Feb 17 14:22:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F1C5F125C6 for ; Sat, 17 Feb 2018 14:22:10 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::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 D1A9380ACC for ; Sat, 17 Feb 2018 14:22:09 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id h78so7633809lfg.6 for ; Sat, 17 Feb 2018 06:22:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=dB7eP91kDFqyuZJAeKQJIOS2fF9cxnUNw6TFKSdVPU0=; b=njuSUI0+K+M5q7gtqtDAXnugkc1oa+pc4MAkVFP/0JtWMQoxPbsi3wvG4Ok8wjO1ts Z7TPu06SXYpHFMbYf8Ym12UkZa2Qg/yWb6CGJ3tL6h4tLzEgxJxPEQ1O23iS3kB8//gs ZTGjMlqXjrqCNRchug3jVXxjOe6/S4TaIRv5f1+/2h1oR42gZx+H49KUO3BNimYRXroT q6FvFJ9BKZXJ3HuHcX+yMzIaJuq/hi0Vn5BBiqAb8TcpYOpg641PloxWxQQXPPj4DFas mtZ4Mb6pfWQZDI13GPMm/X0xB3NFO8dUQd+hFtv7ipgBF1HYuQMH7L1o7jJJoWsGJ/Ew Gilg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=dB7eP91kDFqyuZJAeKQJIOS2fF9cxnUNw6TFKSdVPU0=; b=aTpcCv2Vec96WeSipggRtlWz35NtqJpzIxtECUXJVDuHdULZvZyUdFgKnAD5bnNsQa BAgainFqSa/jQP2D0wwR+5NOk4ByNRFzpxR9ZuKg3xgozPV8n0qet06QY/M61yjsV++a NpSceu9TzlxPA5/NQYwfjs2FHXuHEkNjCn5bUDVine1rwmvKMGb5diRsVgQLKLCuLCqr YkIoT+MUcfTwHo0QDJVpX8XpDyaYqw7LF/0ksQLm12+HDFZknIH7e4ETrI/M1t+cqNk6 G7UdmKOegsg/01oavUWJtTYLrZosL6PwM7hIPsRY03WxPpX/Tftl+diwmOA6RmTZr8GD uQDg== X-Gm-Message-State: APf1xPDoqg1BRC+bZ1zV/aZfavamMbG8tYXdqc6pKQb234K15BqKQYha sdefn9FfkY31jIet6HmTKy/lEA== X-Google-Smtp-Source: AH8x227R2QChk8yK26c+x5vOPOmCegndxFzev7LcbzxXSerolHMMS9uzV77K1wjZF5pGYZDMbi2/5w== X-Received: by 10.25.123.18 with SMTP id w18mr3120347lfc.104.1518877328274; Sat, 17 Feb 2018 06:22:08 -0800 (PST) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id x13sm1158495ljd.6.2018.02.17.06.22.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Feb 2018 06:22:07 -0800 (PST) Subject: Re: devd in r329188M don't start To: Hans Petter Selasky , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> <014c8376-939f-3b8e-d8a1-0d08407e8a5d@selasky.org> From: "Alex V. Petrov" Message-ID: Date: Sat, 17 Feb 2018 21:22:06 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <014c8376-939f-3b8e-d8a1-0d08407e8a5d@selasky.org> Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 14:22:10 -0000 Sorry, prev msg this only afrer one patch. Now is all OK. 17.02.2018 21:18, Hans Petter Selasky пишет: > On 02/17/18 14:51, Alex V. Petrov wrote: >> devmatch: Malformed NOMATCH string: ''?'' persists >> >> > > Did you reinstall /etc ? > > --HPS > > -- ----- Alex. From owner-freebsd-current@freebsd.org Sat Feb 17 14:22:26 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5039CF12683; Sat, 17 Feb 2018 14:22:26 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 E6A7A80C92; Sat, 17 Feb 2018 14:22:25 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 7B8CD26027E; Sat, 17 Feb 2018 15:22:24 +0100 (CET) Subject: Re: mlx4 weird error "Failed to map EQ context memory" after update To: Greg V , freebsd-net@freebsd.org, freebsd-current@freebsd.org References: <48f48a42-9115-8d97-5093-0e7173b36533@unrelenting.technology> <90712e46-15a9-6107-b0f8-c64ac333c7e1@unrelenting.technology> From: Hans Petter Selasky Message-ID: <1ab033e3-114f-eeed-47e5-3b144240f2cc@selasky.org> Date: Sat, 17 Feb 2018 15:19:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <90712e46-15a9-6107-b0f8-c64ac333c7e1@unrelenting.technology> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 14:22:26 -0000 On 02/17/18 14:51, Greg V wrote: > On 01/20/2018 12:18, Hans Petter Selasky wrote: >> On 01/20/18 00:17, Greg V via freebsd-net wrote: >>> >>> On 01/19/2018 12:54, Hans Petter Selasky wrote: >>>> On 01/18/18 14:11, Greg V wrote: >>>>> Hi. I've upgraded CURRENT from December 19 >>>>> (https://github.com/freebsd/freebsd/commit/fd53ccf393f4f8ac1948e97eca108) >>>>> to today >>>>> (https://github.com/freebsd/freebsd/commit/391a83c86bb91ae3840cf37b7de478f42cc97e2a) >>>>> and my Mellanox ConnectX-2 network card stopped working: >>>>> >>>>> mlx4_core0: mem >>>>> 0xfe100000-0xfe1fffff,0xf0800000-0xf0ffffff irq 32 at device 0.0 on >>>>> pci7 >>>>> mlx4_core: Mellanox ConnectX core driver v3.4.1 (October 2017) >>>>> mlx4_core: Initializing mlx4_core >>>>> mlx4_core0: command 0xffa failed: fw status = 0x1 >>>>> mlx4_core0: Failed to map EQ context memory, aborting >>>>> device_attach: mlx4_core0 attach returned 12 >>>>> >>>>> >>>>> Loading the OLD mlx4.ko and mlx4en.ko on the NEW kernel actually >>>>> does work fine! >>>>> >>>>> Reverting all mlx4 changes between then and now (no big changes, >>>>> mostly just the 1 << 31 thing from D13858) and rebuilding the mlx4 >>>>> module with CC=clang50 does not help. >>>>> >>>>> What happened?! > Upgraded CURRENT again today, the problem went away :) OK, nice to know. --HPS From owner-freebsd-current@freebsd.org Sat Feb 17 14:35:45 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D0E3F13A3E for ; Sat, 17 Feb 2018 14:35:45 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 374B981A6D for ; Sat, 17 Feb 2018 14:35:45 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 2EF8D26027E; Sat, 17 Feb 2018 15:35:44 +0100 (CET) Subject: Re: devd in r329188M don't start To: "Alex V. Petrov" , freebsd-current@freebsd.org References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> <014c8376-939f-3b8e-d8a1-0d08407e8a5d@selasky.org> From: Hans Petter Selasky Message-ID: Date: Sat, 17 Feb 2018 15:32:47 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 14:35:45 -0000 On 02/17/18 15:22, Alex V. Petrov wrote: > Sorry, prev msg this only afrer one patch. > Now is all OK. > There is one more, but not so important: https://svnweb.freebsd.org/changeset/base/329458 Thank for your testing! --HPS From owner-freebsd-current@freebsd.org Sat Feb 17 14:47:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1DF0AF14ABF for ; Sat, 17 Feb 2018 14:47:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A6C8B825D3 for ; Sat, 17 Feb 2018 14:47:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x234.google.com with SMTP id t126so7037572iof.4 for ; Sat, 17 Feb 2018 06:47:15 -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=/WPCRZotgTSrXYNYyNuT2Y05htFSDzrMnqpa2sUJBTA=; b=GBBADpRadizGYK6gfGjE0TRzYPMvg4n6c77Qi5cnA25i2P4OVIznaOJCVfJEzSk9ll R4q+P031JFj1ifKpyCQWJBB/zhlNoikJcFiY+K8ym2ddJ6GYnjqtcNB4xxUZbw0yR71z lmlUxZK7naStvuwLG7vZYHszTShtroWvBCxTaK3dKLisRhWRUOFVhbQwJ284kwZ/2RP6 TTHVYoGuADiqzHxVjGkB60/O68pck5Xi7gyOhTUoSZtb5rr+T1KZDBhbyZEyaplGs6jM VTmKyn9bPSGiY+1VH8WD/5+ZZtPtB3MxjhRnFYfzjeEKfoNdJI3oSnEv+eEM+3lsC+jf rvKA== 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=/WPCRZotgTSrXYNYyNuT2Y05htFSDzrMnqpa2sUJBTA=; b=AfJPf8JkdQS0W8mhqVNyYUQFKMDgcqvI3bBYuYsFjA+zSrnehD957bXLgV9zsffRBm lny1FdHH5ou3P0afRSMzOkZZvcYy7kJxAlOKmmh63EGR08ff/bDT44AplPeM1QUauj/u gwe+Socggc5F+MalUaup1IVQH1q0HuC+v0ggfjHmKHcOKyer7RFPKggL5uBt+xIyfpAF 8vZujVuIeyor6ZxbFVOlmMxG/JKQCe5PREnNWnXB3ln1qw3txRJG8R2IvUDDMG1t8w0k oT/D8WfPy9pIn50MLsKeyEU9nDNxPoPQW5a637VSynRo3IOwha9UM+jWVYoAbLrWOVSN XtDA== X-Gm-Message-State: APf1xPDvocW3mUYGHaEni96Oz9sCKawK/S7D6SgmbIxxR8TRqNT1dIyk 1rteG3/l1zwN8bVWUXMRjz+C9S7M32l9fDO2XZnXAQ== X-Google-Smtp-Source: AH8x225KEMmB6w1lJhGynYW0EqpYbM5c2lvacojB/lfKft94P0ddVLjNkh4CrnyZAUMsAf93dFi7kABYUDsT7+hqqZ0= X-Received: by 10.107.2.6 with SMTP id 6mr12593625ioc.117.1518878834877; Sat, 17 Feb 2018 06:47:14 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Sat, 17 Feb 2018 06:47:14 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: References: From: Warner Losh Date: Sat, 17 Feb 2018 07:47:14 -0700 X-Google-Sender-Auth: PgwR9KUXoLlmmx6oullJHxTmMOA Message-ID: Subject: Re: panic in daprobedone: Unholding 4 with cnt = 0 To: Hans Petter Selasky Cc: Warner Losh , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 14:47:16 -0000 That's interesting. What did you do to get there? There's some code path that's unholding the periph without first holding it. I've been trying to find a scenario. Warner On Sat, Feb 17, 2018 at 5:01 AM, Hans Petter Selasky wrote: > I've started to hit this panic with USB mass storage, before even the > device has become in-use: > > panic: Unholding 4 with cnt = 0 > > Backtrace: > > vpanic() > panic() > daprobedone() > dadone() > xpt_done_process() > xpt_done_td() > fork_exit() > fork_trampoline() > > db> > > > static inline void >> da_periph_unhold(struct cam_periph *periph, da_ref_token token) >> { >> int cnt; >> struct da_softc *softc = periph->softc; >> >> token_sanity(token); >> DA_PERIPH_PRINT(periph, "Unholding device %s (%d)\n", >> da_ref_text[token], token); >> cnt = atomic_fetchadd_int(&softc->ref_flags[token], -1); >> if (cnt != 1) >> panic("Unholding %d with cnt = %d", token, cnt); >> cam_periph_unhold(periph); >> } >> > From owner-freebsd-current@freebsd.org Sat Feb 17 14:58:15 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DFA4F15A24 for ; Sat, 17 Feb 2018 14:58:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0E7EF82EAD for ; Sat, 17 Feb 2018 14:58:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22e.google.com with SMTP id t22so7086205iob.3 for ; Sat, 17 Feb 2018 06:58:15 -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=Ag4Wh4lZ7f0mJnrSDO78D2AFNzJf4wO/aYU4uonGQoM=; b=rT7+U/TFz3BgiXq77uBSfyuDHWgggUDb0ihDdGKf1v8CmRtFyU+ZNSQKFi/fbcj9CB nA3tLjYp39FFnkzmKs3GSB0I7gkmxTBxs68Tgeg/KqsnO4rP8iSBb5twphjtM1uDjM3g 6XY+043Ra9VckMx/jWGJAbmDwjERDEthhYLAQiwSAGXcE8WI6rkfsCiLb1bmEnCz38Q8 aliAloFbp02Xd16+SALttESlPqMTmAYqB5H+xH7dbmIbM0KyalLT3O9InN/aJt0GaGMg Nt+4iYMvN0q3xvc5Mcl3F00A9q7aUxTovIQc+WRiqlUZOyTwcBMeld+zkFj4qu0sQWfx nNeA== 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=Ag4Wh4lZ7f0mJnrSDO78D2AFNzJf4wO/aYU4uonGQoM=; b=nik2K6/MqUB++h8Fx5D2d+GmqYu2lE6YNO4xXbxW0sbQSn++Fh99QnUmAF893dj9sv +VDjVLm5lO/pwO7mJji48SglBMBMKnRsS54rcA++3dMLEfXUc6WNnw8FQk/v34Tduq53 QyR3VGh57V+W+kpxbJrGGMDc4j49V446So6v6JvjeunkAQ8acBTqzhfV7EOqsnkUZOuS gVEqT3K1ea/AdyX+6mkxRN3Dx1EBBd9WRaYDMCSsEx9iwldMeqA7fzvtTVT669qe/Qsw Y85EUuxeIMgam4mGrZAUldzP25fo2RORuJXVLuPH8HIMMeq2qB1lPRXkcZUVx9bLZoWo BALw== X-Gm-Message-State: APf1xPCQmOC6wk+ukkMNl5Xoy5yw5ahaOo1OG23hprWIsSK3UTIV/Q37 UUFzoyjx/jC7BQfImXUE2DIBOTq6cZfyjStTsienzQ== X-Google-Smtp-Source: AH8x224PwJcuLPq4pYB/CBPnRK56yF+4A2byPw2RQs+2/mvcPapTTWNziOyCYABM3GUp1ucHR+3DgFWeeZNWWveXxbg= X-Received: by 10.107.175.77 with SMTP id y74mr12920498ioe.37.1518879494331; Sat, 17 Feb 2018 06:58:14 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Sat, 17 Feb 2018 06:58:13 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> From: Warner Losh Date: Sat, 17 Feb 2018 07:58:13 -0700 X-Google-Sender-Auth: 4pXyv_ggY312tm_RsfleIdCW6QQ Message-ID: Subject: Re: devd in r329188M don't start To: Hans Petter Selasky Cc: "Alex V. Petrov" , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 14:58:15 -0000 On Sat, Feb 17, 2018 at 6:31 AM, Hans Petter Selasky wrote: > On 02/17/18 11:38, Alex V. Petrov wrote: > >> 12.0-CURRENT #12 r329446M: Sat Feb 17 17:11:05 +07 2018: >> on boot multilines: >> >> devmatch: Malformed NOMATCH string: ''?'' >> >> > Can you try these two patches: > > https://svnweb.freebsd.org/changeset/base/329455 > https://svnweb.freebsd.org/changeset/base/329456 > > Obviously USB attaching was not tested before submitting. USB WAS ABSOLUTELY TESTED. I rebooted my machine several times, unloaded drivers, etc. It all just worked for me. Please don't make snide comments like this, along with drive by commits to devmatch without even discussing the problems with me. It's really pissing me off. Warner From owner-freebsd-current@freebsd.org Sat Feb 17 15:01:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13946F15ED6 for ; Sat, 17 Feb 2018 15:01:35 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9DA8883453 for ; Sat, 17 Feb 2018 15:01:34 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5E057F15ED3; Sat, 17 Feb 2018 15:01:34 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4CE65F15ED1 for ; Sat, 17 Feb 2018 15:01:34 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f66.google.com (mail-lf0-f66.google.com [209.85.215.66]) (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 D19B783443; Sat, 17 Feb 2018 15:01:33 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f66.google.com with SMTP id v9so5700190lfa.11; Sat, 17 Feb 2018 07:01:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=5Vy0GLiXCdbmCx7NUkoL75GmT4++SkX39yXxXkCaDLI=; b=fnBoyPiKQ7D7qfKW+aVndg0D3/I0sU5VJaXU2CZ/eIFZc/dNBnuy+AJCjxXFldjnIX bTy5jJ/pUb51adO1fmXJVi1TTe5gAIUROFT3EKUzKFcsQDR0kVsIUbWfRcbLAubOuRMU aZD63aMOHdABLZo1nV6oRoyUtKtbbkHcFA3kfgdgDm4haIo3uaTCZfpIJi/TUGzsPmW1 dx7FLLGDlSMk4+3zOJmDI5aN6O85pw2cdJVZWx2z5ikAnC3moyyGevOnAQIPzF0AuIae zmz3wpTIqDvXjMrt5VinHgUI5JFO56lBcaY4QF2/sHb59dISeAWE4acgUPkg1ZbkqI0t aZKQ== X-Gm-Message-State: APf1xPB8ftRX9wRe1npLFeHuqyUpBT+vpV0OcgbffdyTc25jr8LjMEJ1 63S9iOeMmZogpuuZvrVo94UlSDXK X-Google-Smtp-Source: AH8x227eFCjwcEaoQ3Ofo85chFGqemuYH0ECNOpDqmcF3b8OgqH3FoM37nPc5pv7o+vJYY5S5La7IA== X-Received: by 10.46.1.149 with SMTP id f21mr6030632lji.56.1518878386405; Sat, 17 Feb 2018 06:39:46 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id z4sm3925954ljz.20.2018.02.17.06.39.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Feb 2018 06:39:44 -0800 (PST) Subject: Re: Since last week (today) current on my Ryzen box is unstable To: Andrew Reilly Cc: current@freebsd.org, kib@freebsd.org References: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> From: Andriy Gapon Message-ID: Date: Sat, 17 Feb 2018 16:39:43 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 15:01:35 -0000 On 17/02/2018 14:16, Andrew Reilly wrote: > Today's rebuild has given me uptimes of below an hour, usually. The box will > stay up in single user mode long enough to rebuild world/kernel, but > multi-user it is panicking at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:1592 > > The backtrace shows that it gets to this panic from a sendfile() syscall. > The line above is in the middle of a big edit that's part of svn revision > 329363. The tripping assertion seems to suggest that m->valid != 0, for > whatever that's worth. The panic message and the backtrace would be a good start, but a crash dump is probably what's really needed to analyze the issue. -- Andriy Gapon From owner-freebsd-current@freebsd.org Sat Feb 17 15:07:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56689F16A7E for ; Sat, 17 Feb 2018 15:07:54 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 E764383D53; Sat, 17 Feb 2018 15:07:53 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id D514C26027E; Sat, 17 Feb 2018 16:07:52 +0100 (CET) Subject: Re: panic in daprobedone: Unholding 4 with cnt = 0 To: Warner Losh Cc: Warner Losh , FreeBSD Current References: From: Hans Petter Selasky Message-ID: <56adf14f-54d0-2669-cb12-139f06a370b5@selasky.org> Date: Sat, 17 Feb 2018 16:04:56 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 15:07:54 -0000 On 02/17/18 15:47, Warner Losh wrote: > That's interesting. What did you do to get there? There's some code path > that's unholding the periph without first holding it. I've been trying to > find a scenario. > I just booted into single user mode with a multi-card USB reader attached. Seems like some kind of race. Doesn't happen during normal boot. --HPS From owner-freebsd-current@freebsd.org Sat Feb 17 15:09:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2CC4F16C96 for ; Sat, 17 Feb 2018 15:09:23 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 8158883E4D for ; Sat, 17 Feb 2018 15:09:23 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 0E52B26027E; Sat, 17 Feb 2018 16:09:22 +0100 (CET) Subject: Re: devd in r329188M don't start To: Warner Losh Cc: "Alex V. Petrov" , FreeBSD Current References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> From: Hans Petter Selasky Message-ID: <21715430-dab3-b8ea-c831-54edbf69e495@selasky.org> Date: Sat, 17 Feb 2018 16:06:25 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 15:09:24 -0000 On 02/17/18 15:58, Warner Losh wrote: > USB WAS ABSOLUTELY TESTED. I rebooted my machine several times, unloaded > drivers, etc. It all just worked for me. > > Please don't make snide comments like this, along with drive by commits to > devmatch without even discussing the problems with me. It's really pissing > me off. Are you using a different shell then? It did not work for me, and several others. Did you also check you've removed the old /etc/devd/usb.conf ?? And did you check no errors were in the console? --HPS From owner-freebsd-current@freebsd.org Sat Feb 17 15:15:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2763F17763 for ; Sat, 17 Feb 2018 15:15:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 509FB845FD for ; Sat, 17 Feb 2018 15:15:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x232.google.com with SMTP id l12so1350579ioc.10 for ; Sat, 17 Feb 2018 07:15:41 -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=aN+fQpNDtJgLfAExUZY5I7xbFmQXPAFk/5KCKVyxlTQ=; b=yDuP2oaM3NGEqxQGJruyO8YgxCb91nQa3AXc4Xpz0XtVoKWk2Hz55VomeNmFcjnpcp N9AvnFkm4WIK4MZJZhKV6zFdvxgfme/D4Fs56UYWM5a0EBlZgkjdh/PpO4+TiQ9fr/dL NArG7Mb5kfbYpSbuSLfXL/PHnX51GtDuScf9Q7l7K+HmVrdCmPMsR53pk7upnrK0ASOM sJAhsXfBlOZ0Q5x2VkU29DBbns8+J2FGPg/ZIxt9DinALJKNGwMJuZvvrHuMMMctQUJw izDpmn3+QMu1xenEtWNK8F1+wd25qTT4BJmyEwInG0dFyPCx4Q+f4OBaG2uM9mMtkwVA SrNQ== 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=aN+fQpNDtJgLfAExUZY5I7xbFmQXPAFk/5KCKVyxlTQ=; b=iqaCMW8Y2g4qqAs0OLvJcFCHv47vHk6pDIWKVI7Ga6PmsHRq7eOHWJQM/HALZcb7A3 ORqf5AJmgT17+Rb7OPI2PMCgSpIQjAPubrG5752oYJxKn4J0SQcb8iNKeSN7ARt/iypa Uh9eClWouNPr9gPJ6q4UR/AEtrJGI2vqtIQlS0n+qCdX6gHVE6Pw3XkePDjO44xl6ecq LFsMee0miCDm/J4bFf6XpJpttrpMqFUxV/JB7UvNJDyU7jM6ZqS8T81VLI/higdgzZSl eekRndWQYDKmBeOnyHzJ4tRJ+tk5B6VMoJSyVErTG4ENchnjuKWhkOvS4nGUIeCXf8lc IyBw== X-Gm-Message-State: APf1xPB3L4AAE5zw0GNwHQsi5eyLtXtKzfhlaLia7q1fqW9sCmSPXSgx u8HR0PWrk6GbA5mHgvtXuhio9XR/IeCZy8KQqhgPOQ== X-Google-Smtp-Source: AH8x225dU4o8i0i4KgfmaMMjfWXNxPr2dKAE27wyeOc4a5zXu7nxaxSoEzjHKiLZyRgtHr8vW77YCoVdsb8HwFAMh/g= X-Received: by 10.107.2.6 with SMTP id 6mr12694569ioc.117.1518880540655; Sat, 17 Feb 2018 07:15:40 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Sat, 17 Feb 2018 07:15:39 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <56adf14f-54d0-2669-cb12-139f06a370b5@selasky.org> References: <56adf14f-54d0-2669-cb12-139f06a370b5@selasky.org> From: Warner Losh Date: Sat, 17 Feb 2018 08:15:39 -0700 X-Google-Sender-Auth: uQ1g52uxHVEogD9x0PJueG1_AB8 Message-ID: Subject: Re: panic in daprobedone: Unholding 4 with cnt = 0 To: Hans Petter Selasky Cc: Warner Losh , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 15:15:42 -0000 On Sat, Feb 17, 2018 at 8:04 AM, Hans Petter Selasky wrote: > On 02/17/18 15:47, Warner Losh wrote: > >> That's interesting. What did you do to get there? There's some code path >> that's unholding the periph without first holding it. I've been trying to >> find a scenario. >> >> > I just booted into single user mode with a multi-card USB reader attached. > Seems like some kind of race. Doesn't happen during normal boot. I've done that with my systems here... If you can reliably reproduce it, booting a kernel with 'options DA_TRACK_REFS=2' in the kernel config and send me the output? Warner From owner-freebsd-current@freebsd.org Sat Feb 17 15:17:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D2F1F17A51 for ; Sat, 17 Feb 2018 15:17:39 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B1E7C847E8 for ; Sat, 17 Feb 2018 15:17:38 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x233.google.com with SMTP id d13so7095553iog.5 for ; Sat, 17 Feb 2018 07:17:38 -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=6gxuqfHA8xxB+ezStnCvE+7Gt+FOG4LNeeuT5cOJxeo=; b=FVXVmkJvUWfd6erW913w79cueHOJRRCgXoY7hrQTh8g1ALCtlvmwGaEN6BMqYVO6ig 3txB9rdmr7w+gGtQhK2dfMYEPBBYsB2xqVgFVyDF0GFngaqbQ1UybI3plXMbfy6NvwGK wr1zOZZsr30JMODywqXVYkx3J3DgjVF51wtlRsVaVrc3VRLlYUqYFM6CL3JHTM2P3q50 ELgAdYlHqwDSH9pAhBczCsX8C33d1A1Hwke8cwvQKKQbob3xGFwbugbAFULVCXw20Fue I3nDe0kY4/Qjpe8tHqIzTAqRTQShY5XVWpKGu2z5N74+3SwFV0Gf6/WREuz0jlXTGkUp 9Egw== 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=6gxuqfHA8xxB+ezStnCvE+7Gt+FOG4LNeeuT5cOJxeo=; b=HolHRXWNep4eZhCdV8lZr7autRpDGfRPxzk3EIlnUfmaK90EE4S6luTxb0s5I20jxH PRy3Vbg+zfBmchkKx5PSWSpOT7qNoZU/aRHtK/jIen3R6ylnRfOLwPHWk0OT4LxvkrDQ pyZPTmgWcCGxkXrZONk/6zdjYLK9S9D83YiNKqGXWaSRbSKQ1l1HDgyIbM9hWAa7wTWB PtAkb8r53RmGVBnCx0WLxo+LaRQwbNCVSQ5ZjKFdA+faAs2YHOyj928S/I/RcnQjKA+x 4m09LSQ6bHtvrhDoVULHfyf5CVmcjIZqzVgoGXRa8g7ba/bkVnnJLc+HhjLi4ulOk5gC /NmA== X-Gm-Message-State: APf1xPAWHaXaA3+JbBeKuPU8q3bwHuf5Fjt7R/0JVaG3Qb6alcMODu4v h3ZOj/nHzbr+5jEGTw7PTpNT2q3uT5mR3pJgND2v3g== X-Google-Smtp-Source: AH8x226lM8zoOrVjI+mBoX+y3CKjpwTgpDXYMcxQEdnVsT767VWfuGPL8IrGoMh4WLR7rqEn+j5tXNUHVgMO/xqyo6U= X-Received: by 10.107.175.77 with SMTP id y74mr12998815ioe.37.1518880657832; Sat, 17 Feb 2018 07:17:37 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.201.67 with HTTP; Sat, 17 Feb 2018 07:17:37 -0800 (PST) X-Originating-IP: [50.253.99.174] In-Reply-To: <21715430-dab3-b8ea-c831-54edbf69e495@selasky.org> References: <6dda893b-e1a1-6e13-98f8-3c73d29fe936@gmail.com> <66467b7f-299c-83c8-798e-562d7fa39b8e@gmail.com> <4913dc5a-e3a9-01da-8f23-6f62d03d2cc7@selasky.org> <5fa0ef16-7689-91a2-a43b-1dd319d8b745@gmail.com> <3b1dbc5d-bc44-c896-0728-9e2e2a767b00@gmail.com> <21715430-dab3-b8ea-c831-54edbf69e495@selasky.org> From: Warner Losh Date: Sat, 17 Feb 2018 08:17:37 -0700 X-Google-Sender-Auth: mM2K229GlG4Qqcb8CMVLfO4zfCc Message-ID: Subject: Re: devd in r329188M don't start To: Hans Petter Selasky Cc: "Alex V. Petrov" , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 15:17:39 -0000 On Sat, Feb 17, 2018 at 8:06 AM, Hans Petter Selasky wrote: > On 02/17/18 15:58, Warner Losh wrote: > >> USB WAS ABSOLUTELY TESTED. I rebooted my machine several times, unloaded >> drivers, etc. It all just worked for me. >> >> Please don't make snide comments like this, along with drive by commits to >> devmatch without even discussing the problems with me. It's really pissing >> me off. >> > > Are you using a different shell then? It did not work for me, and several > others. Did you also check you've removed the old /etc/devd/usb.conf ?? And > did you check no errors were in the console? Yes. I did check there were no error... It just worked... However, I have a pruned set of .ko's in the test setup which likely lead to not noticing the multiple-module issue. It was a mistake to not check before removing the old usb.conf. You are right, I should have done that. Warner From owner-freebsd-current@freebsd.org Sat Feb 17 16:23:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB87BF1D3E7 for ; Sat, 17 Feb 2018 16:23:33 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 62BA787B17; Sat, 17 Feb 2018 16:23:33 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 60BB826027E; Sat, 17 Feb 2018 17:23:31 +0100 (CET) Subject: Re: panic in daprobedone: Unholding 4 with cnt = 0 To: Warner Losh Cc: Warner Losh , FreeBSD Current References: <56adf14f-54d0-2669-cb12-139f06a370b5@selasky.org> From: Hans Petter Selasky Message-ID: Date: Sat, 17 Feb 2018 17:20:34 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 16:23:34 -0000 On 02/17/18 16:15, Warner Losh wrote: > I've done that with my systems here... > > If you can reliably reproduce it, booting a kernel with 'options > DA_TRACK_REFS=2' in the kernel config and send me the output? > > Warner I have a reproduction. I'll send you the photo off-list. --HPS From owner-freebsd-current@freebsd.org Sat Feb 17 21:26:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA614F11044 for ; Sat, 17 Feb 2018 21:26:38 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5B28D6D793 for ; Sat, 17 Feb 2018 21:26:38 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: by mailman.ysv.freebsd.org (Postfix) id 19FCFF1103E; Sat, 17 Feb 2018 21:26:38 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 074C1F1103D for ; Sat, 17 Feb 2018 21:26:38 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nsstlmta36p.bpe.bigpond.com (nsstlmta36p.bpe.bigpond.com [203.38.21.36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "", Issuer "Openwave Messaging Inc." (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 433C06D78D; Sat, 17 Feb 2018 21:26:30 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from smtp.telstra.com ([10.10.24.4]) by nsstlfep08p-svc.bpe.nexus.telstra.com.au with ESMTP id <20180217205203.CMRD8842.nsstlfep08p-svc.bpe.nexus.telstra.com.au@smtp.telstra.com>; Sun, 18 Feb 2018 07:52:03 +1100 X-RG-Spam: Unknown X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtfedrgedugddugeefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuuffpveftpgfvgffnuffvtfetnecuuegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheptehnughrvgifucftvghilhhlhicuoegrrhgvihhllhihsegsihhgphhonhgurdhnvghtrdgruheqnecukfhppeduvdegrdduledtrdegtddrudekvdenucfrrghrrghmpehhvghlohepghhhrghnrghmihgrrdgrtgdqrhdrnhhupdhinhgvthepuddvgedrudeltddrgedtrddukedvpdhmrghilhhfrhhomhepoegrrhgvihhllhihsegsihhgphhonhgurdhnvghtrdgruheqnecuvehluhhsthgvrhfu X-RG-VS-CLASS: clean X-Authentication-Info: Submitted using ID areilly@bigpond.net.au Received: from ghanamia.ac-r.nu (124.190.40.182) by smtp.telstra.com (9.0.019.22-1) (authenticated as areilly@bigpond.net.au) id 5A6144360B674EA6; Sun, 18 Feb 2018 07:52:03 +1100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Since last week (today) current on my Ryzen box is unstable From: Andrew Reilly In-Reply-To: Date: Sun, 18 Feb 2018 07:52:03 +1100 Cc: Andriy Gapon , current@freebsd.org, kib@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> To: Hans Petter Selasky X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 21:26:39 -0000 I've applied the patch, and the boot process is quiet now, but it's = still loading cc_vegas.ko, seemingly in response to seeing this device: = (from pciconf -l -v) none4@pci0:17:0:2: class=3D0x108000 card=3D0x14561022 = chip=3D0x14561022 rev=3D0x00 hdr=3D0x00 vendor =3D 'Advanced Micro Devices, Inc. [AMD]' device =3D 'Family 17h (Models 00h-0fh) Platform Security = Processor' class =3D encrypt/decrypt (from devmatch -v) Searching pci bus at slot=3D0 function=3D2 dbsf=3Dpci0:17:0:2 = handle=3D\_SB_.PCI0.GP17.APSP for pnpinfo vendor=3D0x1022 device=3D0x1456 = subvendor=3D0x1022 subdevice=3D0x1456 class=3D0x108000 cc_vegas.ko The output above suggests that there isn't a driver attached to that = device anyway, though. Cheers, Andrew Reilly > On 18 Feb 2018, at 00:06 , Hans Petter Selasky = wrote: >=20 > On 02/17/18 13:42, Hans Petter Selasky wrote: >> On 02/17/18 13:16, Andrew Reilly wrote: >>> On a side-note, the new devmatch workings are giving me 43 boot = warnings about "Malformed NOMATCH string: ''?'', and = devmatch_enable=3D"NO" in /etc/rc.conf doesn't seem to help, and the new = matching is very very keen to load cc_vegas.ko, a lot. Here's the = output of devmatch -v, in case that helps: >> Hi, >> Does the attached patch solve the devmatch issue? Just apply it = directly on /etc and reboot. >> --HPS >=20 > Please find updated patch attached. >=20 > --HPS >=20 > From owner-freebsd-current@freebsd.org Sat Feb 17 20:36:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F4C0F0CB7D for ; Sat, 17 Feb 2018 20:36:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DC59C6B1F7 for ; Sat, 17 Feb 2018 20:36:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9D651F0CB6C; Sat, 17 Feb 2018 20:36:47 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62EA6F0CB6A for ; Sat, 17 Feb 2018 20:36:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0228F6B1F0 for ; Sat, 17 Feb 2018 20:36:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 478251D84E for ; Sat, 17 Feb 2018 20:36:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w1HKakGo053346 for ; Sat, 17 Feb 2018 20:36:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w1HKakR9053345 for current@FreeBSD.org; Sat, 17 Feb 2018 20:36:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: current@FreeBSD.org Subject: [Bug 218849] Remove rc.conf jail configuration via jail_* variables Date: Sat, 17 Feb 2018 20:36:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: jtkoerting@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable9- mfc-stable10- mfc-stable11- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Mailman-Approved-At: Sat, 17 Feb 2018 21:44:09 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 20:36:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218849 jtkoerting@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jtkoerting@gmail.com --- Comment #31 from jtkoerting@gmail.com --- (In reply to Thomas Steen Rasmussen / Tykling from comment #25) I must admit it looks like exactly this. If you take a look at the first versions of qjail, you can see, that the 'Author' Joe Barbish just stole the main code from ezjail and even forgot to remove all occurances of the patte= rn 'ezjail' in the code he redistributed under his own name (https://sourceforge.net/projects/qjail/files/qjail-1.0.tar.bz2/download) -= of course you can find tons of other portions of the original ezjail code (https://lists.freebsd.org/pipermail/freebsd-jail/2013-March/002120.html), = but that is just funny: [xxx qjail-1.0.tar]# grep -R 'ezjail' * qjail.conf.sample:# This is the default location where ezjail archives its jails to Stealing code and than making such an effort to ruin the original authors w= ork? Shame on you, script kiddie! As the most relevant people already stated here: There is no reason to remo= ve that bits, that will in return doing harm to ezjail users, without removing= any risks or problems from the base. period. So the responsible FreeBSD people should close this 'bug' as there is no evident reason for this, except the personal intention of Joe Barbish. Peop= le like him shouldn't get to much attention and at least no support from a community of real coders. I'm doing this job since the late eighties and might be a little blue, but claiming others code/work as your own is nothing an opensource community sh= ould accept or tolerate. Keeping this as an open 'bug' implies that. Not a good sign. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-current@freebsd.org Sat Feb 17 22:54:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8C27F185FC for ; Sat, 17 Feb 2018 22:54:32 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 72156718DF for ; Sat, 17 Feb 2018 22:54:32 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 31EC6F185FB; Sat, 17 Feb 2018 22:54:32 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D234F185FA for ; Sat, 17 Feb 2018 22:54:32 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) (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 7125D718DB; Sat, 17 Feb 2018 22:54:31 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f49.google.com with SMTP id f137so8518412lfe.4; Sat, 17 Feb 2018 14:54:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CPTDu4Tj1fwEjD9oFgG3ZD+nLLXSLBZT26qAdyeK+NI=; b=WuGKSuqIeRii9n8OMHUzXR/1J5pp6ranIO6WV33cqETwggWkWzl1mBwQSPMJx4s3uD pz3GmILp7G7ucSRhFoqRvpCzGNdtfmzUZDZrS9C4A/s5E6QhpeBd6kpTFlQEiGU7jSKc NUuBt9q/FtvP2DyQ+NkpyhH57VCLq2z67QR2JLioj2oA44US9dp3bxL6UsSnS2Gz7wTJ YPTLY1PK7AVVYeguNoJZWp8Fxge6vxetpCJrORwITMQYXjwgAk9xwmVJcezrrS91YjGZ cJFlcGHaU52tbg+WjsqZclqxT+GgXCPRfSysf8sr+FXWYBbjs6lQERTRqRD/OTD2EdDm RtTA== X-Gm-Message-State: APf1xPCmikcyJIBw+7kgSATxLiYg2pBu1YdKc34y8fP6wN3nLKjXnpTp Dv+WVL0C77TAExbPD9G+vHIUSbkw X-Google-Smtp-Source: AH8x227JeRWLRoalUjnFR79CLI9r0jMccdVulL8u99ext9RJ0UDVjCv79TjJYs8r5J0gj4JQJOYnPg== X-Received: by 10.25.147.219 with SMTP id w88mr7059140lfk.58.1518908063766; Sat, 17 Feb 2018 14:54:23 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id b13sm4327549lfb.27.2018.02.17.14.54.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 17 Feb 2018 14:54:23 -0800 (PST) Subject: Re: Since last week (today) current on my Ryzen box is unstable To: Andrew Reilly , kib@freebsd.org, Gleb Smirnoff Cc: current@freebsd.org References: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> From: Andriy Gapon Message-ID: Date: Sun, 18 Feb 2018 00:54:21 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Feb 2018 22:54:33 -0000 On 17/02/2018 14:16, Andrew Reilly wrote: > Today's rebuild has given me uptimes of below an hour, usually. The box will stay up in single user mode long enough to rebuild world/kernel, but multi-user it is panicking at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:1592 > > The backtrace shows that it gets to this panic from a sendfile() syscall. The line above is in the middle of a big edit that's part of svn revision 329363. The tripping assertion seems to suggest that m->valid != 0, for whatever that's worth. I am doing a bit of an offline investigation with Andrew and it seems that the actual panic message is this: panic: vm_page_assert_xbusied: page 0xfffff807ebbd8f98 not exclusive busy @ /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dmu.c:1592 The stack is this: vpanic() at vpanic/frame 0xfffffe00b3c36390 dmu_read_pages() at dmu_read_pages+0x535/frame 0xfffffe00b3c36460 zfs_freebsd_getpages() at zfs_freebsd_getpages+0x24c/frame 0xfffffe00b3c36510 VOP_GETPAGES_APV() at VOP_GETPAGES_APV+0xd9/frame 0xfffffe00b3c36540 vop_stdgetpages_async() at vop_stdgetpages_async+0x49/frame 0xfffffe00b3c36590 VOP_GETPAGES_ASYNC_APV() at VOP_GETPAGES_ASYNC_APV+0xd9/frame 0xfffffe00b3c365c0 vnode_pager_getpages_async() at vnode_pager_getpages_async+0x81/frame 0xfffffe00b3c36650 vn_sendfile() at vn_sendfile+0xe70/frame 0xfffffe00b3c368e0 sendfile() at sendfile+0x149/frame 0xfffffe00b3c36980 amd64_syscall() at amd64_syscall+0x79b/frame 0xfffffe00b3c36ab0 fast_syscall_common() at fast_syscall_common+0x101/frame 0x7fffffffdb00 I looked at sendfile_swapin() code and it seems that it uses the pager API in an undocumented way. Specifically, it inserts bogus_page into the array of requested pages. For starters, bogus_page is not busied and VOP_GETPAGES is documented to have all requested pages exclusively busied. Second, I always had an impression that bogus_page is an implementation detail of the unified buffer / page cache and that other code need not be aware of it. So, my opinion is that the sendfile code uses a "clever hack" that happens to work with the buffer cache based filesystems, but that that hack is a bug. So, I'd prefer that the problem is fixed in that code. But I am open to being convinced that all VOP_GETPAGES implementations, including that in ZFS, must be made aware of bogus_page. Or, at least, that they should not verify that the requested pages are busied. -- Andriy Gapon