From owner-freebsd-current@freebsd.org Sun Jul 9 08:03:04 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69472DAD6D8 for ; Sun, 9 Jul 2017 08:03:04 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::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 00E637CC31 for ; Sun, 9 Jul 2017 08:03:04 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id 77so98705101wrb.1 for ; Sun, 09 Jul 2017 01:03:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=NwG+M/GxnqVIj+TtY8QcgL2UTddPvHitX5Zm/YX7dJE=; b=Fo1GJ5nzYLN1jsywhMlRmpAQPQGVmxs1dz2FBdhpgF7J3KCxa4ncT6ZnoyBJcTtB9/ Yt8BAvEjiRi3E1dNe3Q984lGWQ0nzIekIeqfzXnOhlWyyL9A3GspYfOWrel29/YI5Gg1 yT1S2e2+aO+mHykVsAjiXA4I6VeaU/UrWGAJvuCUpw/D/zUal5mQGiUbyRnZIcm8ueUH N4nV5pE9uIsseotunFbKhGmuk+vEaPZuIxeKMSRKZY+ojP0WbltlivWyj5kZSMC0Uvag dOzCBXb4uVLX93sdT3TadSGwj3W2K9h+afC0ShSumvJZwKO1nbz0+2MKJx9D80enwzTG DgLg== 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=NwG+M/GxnqVIj+TtY8QcgL2UTddPvHitX5Zm/YX7dJE=; b=czfaqQlhDXeXPbCxvhSMMxaXprHzFUA/DmTQHFeuBzNqrOvsvIbr7Kc8/upm53an/4 hjS4c8f3w3OW+2jvqD/qwjsun/AIS39Tz+V0O36ur28KYHMDT1OADU/7dVAAYoDP6QA2 oWiuqCUV4HcmZT8twnXoCiHOUka9zrulID3cA9dvXA+9zSf/Yp5LXh7h5quiri5GvNn2 FsJMgizgC5Yf0sxOkndV7GDNTu2CwXO8HtGIFLkxmCKNqNki8TpoaWDmKuCKMyuk2Y40 4nIT2lV/D8435CJ2pkhUmyNl6jL+KgRtPDp1ZqOlcSisXd2ROmm/YIsJwS8xXmgLSQ9M E0aA== X-Gm-Message-State: AIVw112LgRjIpj8qdACSxa4JYIIKM+fZE4mCae98/VqLqivKHKw5y/Va tRb+ECh1R4oaASc5BN1iJGNpZeDNag== X-Received: by 10.223.177.213 with SMTP id r21mr4423721wra.119.1499587382091; Sun, 09 Jul 2017 01:03:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.154.193 with HTTP; Sun, 9 Jul 2017 01:03:01 -0700 (PDT) From: Johannes Lundberg Date: Sun, 9 Jul 2017 10:03:01 +0200 Message-ID: Subject: Getting PID of socket client To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 08:03:04 -0000 Hi Without altering the client code (i.e. adding sendmsg(credentials)), is there anyway of getting the client PID (or path to binary) using the file descriptor returned by accept() on the server side? Similar to Linux's getsockopt with SO_PEERCRED option. Thanks! From owner-freebsd-current@freebsd.org Sun Jul 9 08:40:20 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B299EDADC16 for ; Sun, 9 Jul 2017 08:40:20 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::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 4D6147D531 for ; Sun, 9 Jul 2017 08:40:20 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x22e.google.com with SMTP id c11so99414720wrc.3 for ; Sun, 09 Jul 2017 01:40:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=28JalXDUcYqZHx8tV/VkYmkaUpPmdmvXAYEp3jm6eGY=; b=EwaasLP+VbN/Xg29j3JvFOaOwr38oF1c0CFRowkkjEjEH3gpDWYaZWEIg3RIWG4pkB HSlTfhwlKTEmT72e2i+JfQXIRL+10in4Tfxcb2tQiijSNsxTZ9ID4QNmoEwEL+NYYcw6 jzbG6xt+wYrHkyAi03OyduM93iaewUbsuNHAT/ZF2noCX4qL8+0ZpymDlVdFXajeA8qE 9mk7MgRCx7A0RePdM/1lmY9DbIUkDTTylg2UUfXviZBjMVL1CTf9pFun1k4w58LPvv1L 3i8fIQCSuSa2bM/MQF3rWGNzIxN5a7ED0qVF23G2+FWMQgDX6PY8JDqBBgf2Y/oVF3C7 xBkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=28JalXDUcYqZHx8tV/VkYmkaUpPmdmvXAYEp3jm6eGY=; b=JwXCD+rTLsYzOFEo1ghgq2WaQc/Tv8U8dW1/7/sXeHmoEmy0GjL2X2SyAmJRNhGyHQ r06HBq+AokerDcdTcbW18W51NEr0HrWxO61lnJa8XN3VdLq2dk9Usv5zoB7OBNjYMIr6 4UYzFeeo/PtYUhQq4rEBmwwRJ/St0rFJY8avIqguXxi8zSi+qjg7oWHz/XA8r7FuT2RZ 8EOv4ufzoXN/9c3XqZoZTJd52L6Tk8bAuBo+vWwYHxRZSCy9a3vdV8uIzl1iFhCTD56m d3o0Uvdqe6uRipBNu8OXgp8C8yM6zcuZC9e26bGNQGelrqp6X6/3gizBWPXyY4TS+qPP 25EQ== X-Gm-Message-State: AIVw111Ldse+d8snAvkdvzcdKoDIvhYTRZsPaHm+MNFy5Xz87o5LFWGG 5kgIG8tY0nLpvddWkNewRYTN86vqnNty X-Received: by 10.223.171.181 with SMTP id s50mr4863773wrc.129.1499589618697; Sun, 09 Jul 2017 01:40:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.154.193 with HTTP; Sun, 9 Jul 2017 01:40:18 -0700 (PDT) In-Reply-To: References: From: Johannes Lundberg Date: Sun, 9 Jul 2017 10:40:18 +0200 Message-ID: Subject: Re: Getting PID of socket client To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 08:40:20 -0000 follow-up Seems like at least OpenBSD implemented SO_PEERCRED which returns a struct sockpeercred. /* Read using getsockopt() with SOL_SOCKET, SO_PEERCRED */ struct sockpeercred { uid_t uid; /* effective user id */ gid_t gid; /* effective group id */ pid_t pid; }; If not anyone is oppose to this or know some other secret API that provides similar functionality, I can see if I can put together a patch for this very useful API. On Sun, Jul 9, 2017 at 10:03 AM, Johannes Lundberg wrote: > Hi > > Without altering the client code (i.e. adding sendmsg(credentials)), is > there anyway of getting the client PID (or path to binary) using the file > descriptor returned by accept() on the server side? > > Similar to Linux's getsockopt with SO_PEERCRED option. > > Thanks! > > From owner-freebsd-current@freebsd.org Sun Jul 9 09:47:24 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D00AEDAEA4C for ; Sun, 9 Jul 2017 09:47:24 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 2C3137ECC8 for ; Sun, 9 Jul 2017 09:47:23 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from walrus.pepperland ([81.217.71.61]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MB1C4-1dMPZ92XuW-009vRB; Sun, 09 Jul 2017 11:47:15 +0200 Subject: Re: Getting PID of socket client To: Johannes Lundberg , freebsd-current References: From: Stefan Ehmann Message-ID: Date: Sun, 9 Jul 2017 11:47:14 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 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-Provags-ID: V03:K0:Vi8wFS0jkUnZ8SssDSdsTm2wxRk4DZMizBbFtXbxdAQeSmc9S4j 9ke5H0TFKxXGUwWNSW+0YU1wX9AYeiAevqE4t60bjqa8IBvhulJoqxafmpe3vRT+AtctDT1 ZOOMZFXXQ6rRMxZqISGGkvexoyYhEDNrM7NFhlJ3lZ4aVNVLM8feNBw6kxugCTDV9A34elB PLs+Yv+RlxSZuUqCciimA== X-UI-Out-Filterresults: notjunk:1;V01:K0:axHOzCSzM/g=:kElE03lrzlWXIbtEPpgXRa 4zWxR8ASOqE36jJcbPmUjBel8YX8skRjUVRyIwgvrKFv0D0bjuebybE3pLJ55Xtvx4oMHP0TG KoVRI3Za1jEYKhOuQMlu8LI32sYZciccebXcZ6stWuctFke4VAFfTov2nkdU+cWcjvCnr8UHD CaVUflIlDagi9PyQzWz2L9t1G0E6wDpxI+nJtHVd1fY7GQTNp2w5ocPbWbEP8oNWTdlzV3h3Q Ow2W2DCr2sHAMMk4iBKbe08UIwR0IpbepcWrocYcPa9LeQYjHoAPWnVnvRG/r7cGGVot975j4 u7YTQiNoYrqxXuc5DAojRKdMPdKtehbzyQM2Jyxo1wdVACUhKZgR8aereWz0U7QKPtUrq467A ByizReGJ8LhAYTQ5I+0XT7Wrf2a3ZRBZr7eNXGVRhwRVbrf3Y6dlLaW2dyq12X7Nth8s9gexE LnVZuk0n06HGhuT5MGkIlK1YHr+EnR8qhMI4FfVehDDj1a8aY3H8xPXFGOZzb3rLXnVor/Vsp Vj4FngqlHclFMWFgqKlI3TgczUH+khNBVGX5ty3WK4Ey9cJjS3ebf3bc5IGBQu/PO4gyHPo53 CSkaf53phKPUid+97GYU7eubK+ncaTbPP0BQX8AeSzBzG2xevCoZBTd3pHhFr+V0/WTmGsAAv 1+U62DbmTGbCxnq7w0iqZ+4VGn42XcAo6pmE0t5sWFe6FPm8booPinUB8ev97nq3X9fdGu5KR WxL+ePVMqA5oHlWfXWBZXskVtyZw3QMsov5qNUFPz4JNhskq2+BQ0pnJi61iIxO137QjX/eSr D9dn+x2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 09:47:24 -0000 On 09.07.2017 10:03, Johannes Lundberg wrote: > Hi > > Without altering the client code (i.e. adding sendmsg(credentials)), is > there anyway of getting the client PID (or path to binary) using the file > descriptor returned by accept() on the server side? > > Similar to Linux's getsockopt with SO_PEERCRED option. You want the LOCAL_CREDS socket option from unix(4). There's also a FreeBSD sample in the UNIX network programming book. Source is available from http://unpbook.com/src.html With the following two changes it seems to work for me: unixstrserv02.c: set LOCAL_CREDS readcred.c: disable CONTROL_LEN check $ ./unixstrserv02 PID of sender = 1001 real user ID = 1001 real group ID = 1001 effective user ID = 1001 3 groups: 0 5 920 From owner-freebsd-current@freebsd.org Sun Jul 9 09:52:39 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 319A4DAEC35 for ; Sun, 9 Jul 2017 09:52:39 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::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 D703A7F079 for ; Sun, 9 Jul 2017 09:52:38 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x22a.google.com with SMTP id 77so100664839wrb.1 for ; Sun, 09 Jul 2017 02:52:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=74f7uDC5k03b4DeUBSEIyXBw0OlHnVTtS5YH/XmyzBU=; b=HhmstPwsT7e8WQ+NTujRFJSF7gRRnndCRbkpWxqmj571vhBp+cNnytFREtWXJdgG5g e7uhOdEY0+ahIJyqPQ8WtTJRp2CuHrYn3Uh/oN+badR5Ck9vM1ekU90JCKMuw/1oozLn ompEn+poxnCQ4Cx+PXK/MRYghkh76az2JIBV0U7n3W2vH3gMllSgs85Pu+0VL45+nKJe Kfx0ZanyfJPzJ9osEAW6n18a/+ovqvzeNm6Zw2wpnfg4jRlyrz41FdFo3WeVXvN694G3 fxBtgmOb9Fd7vuyWCBwYxxf/dZgJXAlY20rptGIOI5DOWXTVtrF3RbemFIL2/2erLRg0 8+Pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=74f7uDC5k03b4DeUBSEIyXBw0OlHnVTtS5YH/XmyzBU=; b=ekDyvn8F+BIYybQcuELk2VjViR/Ugrmd39bI5kJZNdWmdN3+mWh6FjrVc9GDBPl6LJ bZ6io0iDXBkVSFyCNKFRQOU0u3LWHCiIJElMUUyVWhXKi4YfnE9g0iFS9N1HNZxKLw09 QyWCHprcY8jjB7EA7aomrVNJmBjUpO3VTtfSNnIP+SlIuwCDzHOw1tTuq416QvaE0k94 McfXlNXPIEsxW84Ad940sSYjnPwMIDREKOsDUmoZj3lZauTDfqkjx0DuiSwLx4oJbb/w Z3CWhCoyQaseD/hGzoGtkC2A229Xsl8m4lV6iAsNfiBHqERI3Jk5gGpy7vdncUZC9Imb EOEg== X-Gm-Message-State: AIVw112Kez4immcedSnN/s/YLj05M4UTVaErLrc/eD05IG+vBvGY03iw w/c61VfRIDMmOP2kOUmhJRSgKeEOWg== X-Received: by 10.28.4.141 with SMTP id 135mr4329784wme.21.1499593957342; Sun, 09 Jul 2017 02:52:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.154.193 with HTTP; Sun, 9 Jul 2017 02:52:36 -0700 (PDT) In-Reply-To: References: From: Johannes Lundberg Date: Sun, 9 Jul 2017 11:52:36 +0200 Message-ID: Subject: Re: Getting PID of socket client To: Stefan Ehmann Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 09:52:39 -0000 Hi Yeah I forgot to mention the LOCAL_CREDS. It does not return the PID of the client process but i guess it could be expanded to include that instead of adding another option for that. On Sun, Jul 9, 2017 at 11:47 AM, Stefan Ehmann wrote: > On 09.07.2017 10:03, Johannes Lundberg wrote: > >> Hi >> >> Without altering the client code (i.e. adding sendmsg(credentials)), is >> there anyway of getting the client PID (or path to binary) using the file >> descriptor returned by accept() on the server side? >> >> Similar to Linux's getsockopt with SO_PEERCRED option. >> > > You want the LOCAL_CREDS socket option from unix(4). > > There's also a FreeBSD sample in the UNIX network programming book. Source > is available from http://unpbook.com/src.html > > With the following two changes it seems to work for me: > unixstrserv02.c: set LOCAL_CREDS > readcred.c: disable CONTROL_LEN check > > $ ./unixstrserv02 > PID of sender = 1001 > real user ID = 1001 > real group ID = 1001 > effective user ID = 1001 > 3 groups: 0 5 920 > From owner-freebsd-current@freebsd.org Sun Jul 9 10:02:32 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A19D6DAF0A8 for ; Sun, 9 Jul 2017 10:02:32 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward14o.cmail.yandex.net (forward14o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::1e4]) (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 5EE027F5EA for ; Sun, 9 Jul 2017 10:02:32 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp1m.mail.yandex.net (smtp1m.mail.yandex.net [77.88.61.132]) by forward14o.cmail.yandex.net (Yandex) with ESMTP id E17E92155E for ; Sun, 9 Jul 2017 13:02:27 +0300 (MSK) Received: from smtp1m.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1m.mail.yandex.net (Yandex) with ESMTP id C26A363C0BCA for ; Sun, 9 Jul 2017 13:02:27 +0300 (MSK) Received: by smtp1m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id pnv3lixKaq-2QnGmiiE; Sun, 09 Jul 2017 13:02:26 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1499594546; bh=z2X43zln/WQBYzTG6zueonbA/spAoxRKaxVE88uJGKw=; h=To:From:Subject:Message-ID:Date; b=jn9tOJKTEklWssRYXIHODfPt/DpCGRPEAcfDZpUp9zeu72VLmqg+lCsvizowFKnJp 5SxPxBcpgaap2HPbb17IizgO4VN33E3gWxfaCY3W8l34U3fA2WmcXtMWFMnXJh0msf 0pkbJnT76TXi/Dli/V470krqvgwvh4EbhMzxqkWI= Authentication-Results: smtp1m.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0 To: freebsd-current@FreeBSD.org From: Boris Samorodov Subject: [bhyve] FreeBSD guest, Handbook, vmrun.sh Message-ID: Date: Sun, 9 Jul 2017 13:02:26 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 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.23 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: Sun, 09 Jul 2017 10:02:32 -0000 Hi All, I try to create a FreeBSD guest as per TH, section "21.7.2. Creating a FreeBSD Guest". All is good up until the last command at the section. When I try to launch the installed client, I get: ----- # sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d guest.img guestname Launching virtual machine "guestname" ... Installation CDROM image "./release.iso" is not readable % uname -a FreeBSD latt.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r320821: Sun Jul 9 07:10:56 MSK 2017 bsam@builder.bsnet:/usr/obj/usr/src/sys/PKG64X amd64 ----- Is it a bug at vmrun.sh or documentation? -- WBR, bsam From owner-freebsd-current@freebsd.org Sun Jul 9 13:26:09 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A2C8DB21D4 for ; Sun, 9 Jul 2017 13:26:09 +0000 (UTC) (envelope-from shoesoft@gmx.net) 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 665C38454E for ; Sun, 9 Jul 2017 13:26:07 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from walrus.pepperland ([81.217.71.61]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M20Jj-1dnuph3hkJ-00u5En; Sun, 09 Jul 2017 15:25:58 +0200 Subject: Re: Getting PID of socket client To: Johannes Lundberg Cc: freebsd-current References: From: Stefan Ehmann Message-ID: <684e8346-c4a8-a0c5-cb2a-cd5159d2af1c@gmx.net> Date: Sun, 9 Jul 2017 15:25:57 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 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-Provags-ID: V03:K0:DPz+6BbMuqz2Y/10aD5cktzl0A6KnsHaMIacAZy/bMiEl107sYX F/8+GALvrm0WC3/Frr8fwiS2ArznJJIGOMtsVDqY7tgBhp6qvNcWjkx48pOJYhoHkGYdixA GC0XmX1FeXFqzd6LTc5lzVANraioivrShzpmZ+q8C7IPqjjCFoKIEb8ejZHMUS9HHUysYXm TRu3Y3cYy2ZdYqcKOUz0g== X-UI-Out-Filterresults: notjunk:1;V01:K0:l1Pfydvv2dw=:rmlrFsaz78OziTMZqyJq2n TiActv1rFf02COh6p9utlHZPI7nwWhdfrnfLz98+1qacCS+390zj9wXR8yPqwiFCk/tBitmn3 xxl12EIj7mHHECi4dxeAn4hQytWtvFnVRLEw2oAEUkQeFFFjrRglgwuN5iEO+RRg5mNAVtFhK 4L2iyYD6NDrN6DeAynyXTIZG/ywEnvHvfpwZLqLNLTmomEi0tmYMLDdPbQWqgwZP+6vp/88h7 U6iZG4kV0TBSVqGESGIAXbG2Kk4pAiTQeo7b19Jqy/MqlR9uym+8bdz1biAO48MBJvJdnMKsd 8mtn3Re3pDrKeLuxGMkyQI0fkbX03I+LFeJ9PYYxBLWxStnydeZ/EIhmiNSgG/49PFZPletTb WuKZe0axmM7WKo9D9tXCkGFGlnK5CfEP0HIeguUDHXughAgaPsb1P+bgtLEvrfDGuHCjiHQ1+ 5THfRxB8SwPq3nu7Dn6FIcWfDXsXulOTaWrVL6bA3D5MsAbDs2HDOy2bSxBMwkGh9kek5XWAo cStddw+0ixOPsip1HZxqlZVhvu/OqAODOyMuQmrunuz3UHsZ3AmUgtFe6JuuBSzpKwk/ZX0/o 8whEYrRYYOwh+vVLE2Sgi1lovWVHTtra9GbSUKKn429yJDVeflSaki7p4j8RUfjvkX+7add0k iiJUuU2kvjyvvw4zJU0nJTYFn4rFGxr013B/jAJFmU+/FQqjfuB/XULT8Ew5GT3RQdfZxe4yL ZUQVTXyUklPKvWaoycnJLFq66hqCTk72d3osrTFh4YFdh54X6u9gqIst19cZIsNYAXSDmf7W0 McL4k5R X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 13:26:09 -0000 On 09.07.2017 11:52, Johannes Lundberg wrote: > Hi > > Yeah I forgot to mention the LOCAL_CREDS. > It does not return the PID of the client process but i guess it could be > expanded to include that instead of adding another option for that. I was only skimming the man page. Didn't see that cmsgcred contains the PID, but sockcred does not. Of course the PID in my sample output is also wrong (the UID is printed instead of the PID): > $ ./unixstrserv02 > PID of sender = 1001 Don't why the structs are not compatible, maybe because: "The process ID cmcred_pid should not be looked up (such as via the KERN_PROC_PID sysctl) for making security decisions. The sending process could have exited and its process ID already been reused for a new process." According to the commit log LOCAL_CREDS was obtained from NetBSD but I didn't investigate further. From owner-freebsd-current@freebsd.org Sun Jul 9 14:07:19 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72271DB2A8D for ; Sun, 9 Jul 2017 14:07:19 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDB9494E for ; Sun, 9 Jul 2017 14:07:18 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x235.google.com with SMTP id k67so105252384wrc.2 for ; Sun, 09 Jul 2017 07:07:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=s6cb7l07gAj3Ri1rDYO+W8dxyz+dBYfVhlq7TeQjX/M=; b=laU8/QGJy/1q8JR5iB1DZcodB5TPU6mRQWPwN7dlatSY7UkKw/po93D6LtcnuG+1vH cziOzzZJ4q9YlyvDiEzu4gQBpdYRn1r9BjR9gTYnYzESUSGZGLfr6gZ/5BWJ40FdjNlO o7pm4QfTllqe+6q3HP6GATtAq5vzODlKUS2AP4AHqf7j2IL5ni9k+USGgioZox5WqgBB uvMLIrqq7VpnC0yua6RwkN3DmEI5xx/nRUA2MHCUjaDwfhn6ugj9KY/DM+yWsqx2m5IQ qwYH23tpqxD47VDWeojjKuVnvTKrumXakJkOLpjY2dqzmESFU4MbkA8kDHMEGYpU3RnN lQGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=s6cb7l07gAj3Ri1rDYO+W8dxyz+dBYfVhlq7TeQjX/M=; b=tMCMDcmHZ5GijLWT7ca1pLYC8f8v/CLWyt+UqhqvYYr2yEeCRAYB6r/vv1BdrBkOnN JDrVsfWVbV32+ID4fXZeP4iWufWttWSgWe6+rCQIt3QhG1IFo217ZEdBt4Cq4wR1D0IP jtKCw9EgGXOCB7MjYlqhH39DzaAmJJggYCaw634eRCXD8gwivyIOdjwlGlzmNnX2ghBK mrReE8wcl6MSnxtd+KA2VuB6F2FOh6MFqOIcnZKw9f4VmSJWbUFnM7nbUc8qHapL86Qf dxU7XMb5mYAFajrFj1k8Y0G7+8qlSiEFnm++4/1S+lnGVQhEwxurRGRVYbHJLWZm4Wt+ JnGw== X-Gm-Message-State: AIVw112Ar4xnofY+dmmP+jNlR3i0vBCGn6QSfCpp3I11SuU3ZOtU1yct /5/RrWuenb1ILfPX400V7GPGGqPBOg== X-Received: by 10.28.17.11 with SMTP id 11mr4381730wmr.109.1499609237276; Sun, 09 Jul 2017 07:07:17 -0700 (PDT) MIME-Version: 1.0 References: <684e8346-c4a8-a0c5-cb2a-cd5159d2af1c@gmx.net> In-Reply-To: <684e8346-c4a8-a0c5-cb2a-cd5159d2af1c@gmx.net> From: Johannes Lundberg Date: Sun, 09 Jul 2017 14:07:06 +0000 Message-ID: Subject: Re: Getting PID of socket client To: Stefan Ehmann Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 14:07:19 -0000 That code gets the child's pid from the fork command. That's is not available in my case (Wayland client connects to Wayland server via unix socket). I can understand the security issue.. hmm will dig further tomorrow.. Thanks for the info! On Sun, 9 Jul 2017 at 15:26, Stefan Ehmann wrote: > On 09.07.2017 11:52, Johannes Lundberg wrote: > > Hi > > > > Yeah I forgot to mention the LOCAL_CREDS. > > It does not return the PID of the client process but i guess it could be > > expanded to include that instead of adding another option for that. > > I was only skimming the man page. Didn't see that cmsgcred contains the > PID, but sockcred does not. Of course the PID in my sample output is > also wrong (the UID is printed instead of the PID): > > > $ ./unixstrserv02 > > PID of sender = 1001 > > Don't why the structs are not compatible, maybe because: > "The process ID cmcred_pid should not be looked up (such as via the > KERN_PROC_PID sysctl) for making security decisions. The sending > process could have exited and its process ID already been reused for a > new process." > > According to the commit log LOCAL_CREDS was obtained from NetBSD but I > didn't investigate further. > From owner-freebsd-current@freebsd.org Sun Jul 9 14:43:21 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44887D87547 for ; Sun, 9 Jul 2017 14:43:21 +0000 (UTC) (envelope-from filippomore@yahoo.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 290041CF1 for ; Sun, 9 Jul 2017 14:43:21 +0000 (UTC) (envelope-from filippomore@yahoo.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2575FD87545; Sun, 9 Jul 2017 14:43:21 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25181D87544 for ; Sun, 9 Jul 2017 14:43:21 +0000 (UTC) (envelope-from filippomore@yahoo.com) Received: from sonic319-24.consmr.mail.ne1.yahoo.com (sonic319-24.consmr.mail.ne1.yahoo.com [66.163.188.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EA31F1CF0 for ; Sun, 9 Jul 2017 14:43:20 +0000 (UTC) (envelope-from filippomore@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1499611394; bh=ELJEV4IJqDZuYRYAVdwe3obekDxTv9WucXTJfLtwLJQ=; h=Date:From:To:Subject:References:From:Subject; b=UwpaqGimz+y7O6k7CrrWSFotDKsil0VSAzuSskKLEBb/IB0XI2IOV4dQ9z8h8OBULn96DA/PuXeVvq2mOkAYdvczl+jWOzznumScdg6m8Cg7qbx9flUSNhBHfFgMxn7++rPQJlVCgNTHvW/yIO95cxv3EO4Co+5Ybq4RRkZF2aRJOQXmfYYn6bLSb2vBnUiLJLXmTN0goWmoR/RD252DN7UgTIHTKbljGe6MjsTXZh7qRXC9sdQvuakZL+zp/bO3RMw/shhwW/r5wEI96h0qcgwh7WFUyTbWMCUC/NjDGovNeJDfOf9jlXpFcql22ffwCq29jgXJAxIQ4BrV2m6e7w== X-YMail-OSG: 3Hm94S4VRDtX4O7bahaAQHAz4HfEabFmnzRBOcLeOpVtMKzv Received: from sonic.gate.mail.ne1.yahoo.com by sonic319.consmr.mail.ne1.yahoo.com with HTTP; Sun, 9 Jul 2017 14:43:14 +0000 Date: Sun, 9 Jul 2017 14:43:13 +0000 (UTC) From: Filippo Moretti To: Current Message-ID: <1482174535.1601586.1499611393763@mail.yahoo.com> Subject: Problem with make installworld et alii MIME-Version: 1.0 References: <1482174535.1601586.1499611393763.ref@mail.yahoo.com> X-Mailer: WebService/1.1.10014 YMailNorrin Mozilla/5.0 (X11; FreeBSD i386; rv:54.0) Gecko/20100101 Firefox/54.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 14:43:21 -0000 FreeBSD sting 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320360: Mon Jun 26 15:4= 9:29 UTC 2017=C2=A0=C2=A0=C2=A0=C2=A0 root@releng3.nyi.freebsd.org:/usr/obj= /usr/src/sys/GENERIC=C2=A0=C2=A0i386After compiling world and kernel I cann= ot make install world with the following error:Fatal error cannot allocate = read line in initial thread at line 392 in file /use/src/lib/libthr/thread/= thr_init.c (errorno=3D12)PID 42315 (cc) uid 0: exited on signal 6 (core dum= ped) make:=C2=A0 "/usr/src/share/mk/bsd.compiler.mk" line 145 : Unable to determ= ine compiler type for CC=3Dcc . Consider settingCOMPILER_TYPE This is the report of the crash I experienced with my custom kernel while r= unning xinit (all the operations in console mode worked).I can succesfully = start X using GENERIC.My kernel Worked fine until I reinstalled this snapsh= ot. Jul=C2=A0=C2=A08 08:41:53 sting kernel:=20 Jul=C2=A0=C2=A08 08:41:53 sting kernel:=20 Jul=C2=A0=C2=A08 08:41:53 sting kernel: Fatal trap 12: page fault while in = kernel mode Jul=C2=A0=C2=A08 08:41:53 sting kernel: cpuid =3D 1; apic id =3D 01 Jul=C2=A0=C2=A08 08:41:53 sting kernel: fault virtual address=C2=A0=C2=A0= =C2=A0=C2=A0 =3D 0xa4c8c67d Jul=C2=A0=C2=A08 08:41:53 sting kernel: fault code=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=3D= supervisor read, page not present Jul=C2=A0=C2=A08 08:41:53 sting kernel: instruction pointer=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 =3D 0x20:0xc7f86218 Jul=C2=A0=C2=A08 08:41:53 sting kernel: stack pointer=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 0x28:0xf0b828e0 Jul=C2=A0=C2=A08 08:41:53 sting kernel: frame pointer=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 0x28:0xf0b8290c Jul=C2=A0=C2=A08 08:41:53 sting kernel: code segment=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=3D base 0x0= , limit 0xfffff, type 0x1b Jul=C2=A0=C2=A08 08:41:53 sting kernel: =3D DPL 0, pres 1, def32 1, gran 1 Jul=C2=A0=C2=A08 08:41:53 sting kernel: processor eflags=C2=A0=C2=A0=3D int= errupt enabled, resume, IOPL =3D 0 Jul=C2=A0=C2=A08 08:41:53 sting kernel: current process=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 798 (Xorg) Jul=C2=A0=C2=A08 08:41:53 sting kernel: trap number=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =3D 12 Jul=C2=A0=C2=A08 08:41:53 sting kernel: panic: page fault Jul=C2=A0=C2=A08 08:41:53 sting kernel: cpuid =3D 1 Jul=C2=A0=C2=A08 08:41:53 sting kernel: time =3D 1499495998 Jul=C2=A0=C2=A08 08:41:53 sting kernel: KDB: stack backtrace: Jul=C2=A0=C2=A08 08:41:53 sting kernel: #0 0xc07d92df at kdb_backtrace+0x4f Jul=C2=A0=C2=A08 08:41:53 sting kernel: #1 0xc079ad33 at vpanic+0x133 Jul=C2=A0=C2=A08 08:41:53 sting kernel: #2 0xc079abfb at panic+0x1b Jul=C2=A0=C2=A08 08:41:53 sting kernel: #3 0xc0a7a73e at trap_fatal+0x31e Jul=C2=A0=C2=A08 08:41:53 sting kernel: #4 0xc0a7a783 at trap_pfault+0x33 Jul=C2=A0=C2=A08 08:41:53 sting kernel: #5 0xc0a79e8e at trap+0x2be Jul=C2=A0=C2=A08 08:41:53 sting kernel: #6 0xc0a68d6a at calltrap+0x6 Jul=C2=A0=C2=A08 08:41:53 sting kernel: #7 0xc0823df8 at unp_connect2+0x88 Jul=C2=A0=C2=A08 08:41:53 sting kernel: #8 0xc0823a9b at unp_connectat+0x40= b Jul=C2=A0=C2=A08 08:41:53 sting kernel: #9 0xc0821000 at uipc_connect+0x40 Jul=C2=A0=C2=A08 08:41:53 sting kernel: #10 0xc081dac6 at kern_connectat+0x= 116 Jul=C2=A0=C2=A08 08:41:53 sting kernel: #11 0xc081d999 at sys_connect+0x99 Jul=C2=A0=C2=A08 08:41:53 sting kernel: #12 0xc0a7b104 at syscall+0x5b4 Jul=C2=A0=C2=A08 08:41:53 sting kernel: #13 0xc0a68dee at Xint0x80_syscall+= 0x2e Jul=C2=A0=C2=A08 08:41:53 sting kernel: Uptime: 2m10s Jul=C2=A0=C2=A08 08:41:53 sting kernel: Physical memory: 2929 MB Jul=C2=A0=C2=A08 08:41:53 sting kernel: Dumping 109 MB: 94 78 62 46 30 14 Jul=C2=A0=C2=A08 08:41:53 sting kernel: Dump complete Jul=C2=A0=C2=A08 08:41:53 sting kernel: Automatic reboot in 15 seconds - pr= ess a key on the console to abort Jul=C2=A0=C2=A08 08:41:53 sting kernel: --> Press a key on the console to r= eboot, Jul=C2=A0=C2=A08 08:41:53 sting kernel: --> or switch off the system now. Jul=C2=A0=C2=A08 08:41:53 sting kernel: Rebooting... Jul=C2=A0=C2=A08 08:41:53 sting kernel: cpu_reset: Restarting BSP Jul=C2=A0=C2=A08 08:41:53 sting kernel: cpu_reset_proxy: Stopped CPU 1 I also get these messages in console Jul=C2=A0=C2=A08 08:45:31 sting kernel: 1st 0xc6114bb8 bufwait (bufwait) @ = /usr/src/sys/kern/vfs_bio.c:3539 Jul=C2=A0=C2=A08 08:45:31 sting kernel: 2nd 0xd0391800 dirhash (dirhash) @ = /usr/src/sys/ufs/ufs/ufs_dirhash.c:281 Jul=C2=A0=C2=A08 08:45:31 sting kernel: stack backtrace: Jul=C2=A0=C2=A08 08:45:31 sting kernel: #0 0xc0cbbbd1 at witness_debugger+0= x81 Jul=C2=A0=C2=A08 08:45:31 sting kernel: #1 0xc0cbbaf1 at witness_checkorder= +0xd11 Jul=C2=A0=C2=A08 08:45:31 sting kernel: #2 0xc0c60154 at _sx_xlock+0x64 Jul=C2=A0=C2=A08 08:45:31 sting kernel: #3 0xc0f5d3b0 at ufsdirhash_add+0x4= 0 Jul=C2=A0=C2=A08 08:45:31 sting kernel: #4 0xc0f6010a at ufs_direnter+0x47a Jul=C2=A0=C2=A08 08:45:31 sting kernel: #5 0xc0f6a07f at ufs_makeinode+0x5a= f Jul=C2=A0=C2=A08 08:45:31 sting kernel: #6 0xc0f695a6 at ufs_symlink+0x36 Jul=C2=A0=C2=A08 08:45:31 sting kernel: #7 0xc123be43 at VOP_SYMLINK_APV+0x= d3 Jul=C2=A0=C2=A08 08:45:31 sting kernel: #8 0xc0d301a4 at kern_symlinkat+0x2= 74 Jul=C2=A0=C2=A08 08:45:31 sting kernel: #9 0xc0d2ff21 at sys_symlink+0x31 Jul=C2=A0=C2=A08 08:45:31 sting kernel: #10 0xc120719e at syscall+0x6de Jul=C2=A0=C2=A08 08:45:31 sting kernel: #11 0xc11f2bee at Xint0x80_syscall+= 0x2e Jul=C2=A0=C2=A08 08:46:07 sting kernel: lock order reversal: Jul=C2=A0=C2=A08 08:46:07 sting kernel: 1st 0xd18c9914 ufs (ufs) @ /usr/src= /sys/kern/vfs_syscalls.c:3362 Jul=C2=A0=C2=A08 08:46:07 sting kernel: 2nd 0xc6114bb8 bufwait (bufwait) @ = /usr/src/sys/ufs/ffs/ffs_vnops.c:280 Jul=C2=A0=C2=A08 08:46:07 sting kernel: 3rd 0xd1af3c68 ufs (ufs) @ /usr/src= /sys/kern/vfs_subr.c:2602 Jul=C2=A0=C2=A08 08:46:07 sting kernel: stack backtrace: Jul=C2=A0=C2=A08 08:46:07 sting kernel: #0 0xc0cbbbd1 at witness_debugger+0= x81 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #1 0xc0cbbaf1 at witness_checkorder= +0xd11 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #2 0xc0c2b2cc at __lockmgr_args+0x7= 9c Jul=C2=A0=C2=A08 08:46:07 sting kernel: #3 0xc0f577e7 at ffs_lock+0x87 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #4 0xc123c627 at VOP_LOCK1_APV+0xd7 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #5 0xc0d37ea3 at _vn_lock+0x63 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #6 0xc0d24c51 at vget+0x81 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #7 0xc0d1655d at vfs_hash_get+0xcd Jul=C2=A0=C2=A08 08:46:07 sting kernel: #8 0xc0f52a44 at ffs_vgetf+0x44 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #9 0xc0f48a7a at softdep_sync_buf+0= xbba Jul=C2=A0=C2=A08 08:46:07 sting kernel: #10 0xc0f585df at ffs_syncvnode+0x2= df Jul=C2=A0=C2=A08 08:46:07 sting kernel: #11 0xc0f57984 at ffs_fdatasync+0x2= 4 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #12 0xc123fe87 at VOP_FDATASYNC_APV= +0xd7 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #13 0xc0d34075 at kern_fsync+0x225 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #14 0xc0d34152 at sys_fdatasync+0x2= 2 Jul=C2=A0=C2=A08 08:46:07 sting kernel: #15 0xc120719e at syscall+0x6de Jul=C2=A0=C2=A08 08:46:07 sting kernel: #16 0xc11f2bee at Xint0x80_syscall+= 0x2e sincerelyFilippo From owner-freebsd-current@freebsd.org Sun Jul 9 14:49:55 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52C2CD87797 for ; Sun, 9 Jul 2017 14:49:55 +0000 (UTC) (envelope-from imb@protected-networks.net) 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 360611ECF for ; Sun, 9 Jul 2017 14:49:55 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: by mailman.ysv.freebsd.org (Postfix) id 32303D87795; Sun, 9 Jul 2017 14:49:55 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31B8FD87794 for ; Sun, 9 Jul 2017 14:49:55 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (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 D1D271ECE for ; Sun, 9 Jul 2017 14:49:54 +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=1499611786; bh=+7GE6hIh EOITSVebrqeA0jQWylU+yJdZMMXKnJOppCY=; b=CH9YgvGP5941qq8L5pfo5x0t ttrEBgiOYgZIIWXiKU+7CrKgUik5VxYM4g+oU5uQbHpp+gv8dNtVzrsghij9kBdK 5PfnKQsL5JbETzC1pakpnfUyMU0LpvuhuHkznWThfI8iN15UyCMociCfnLQuXuQS trP+4H9cQZs542nKb9o= 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 559451AAAE; Sun, 9 Jul 2017 10:49:46 -0400 (EDT) Subject: Re: Problem with make installworld et alii To: Filippo Moretti , Current References: <1482174535.1601586.1499611393763.ref@mail.yahoo.com> <1482174535.1601586.1499611393763@mail.yahoo.com> From: Michael Butler Message-ID: <77dd8283-b427-df31-3021-335ddf254d84@protected-networks.net> Date: Sun, 9 Jul 2017 10:49:45 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1482174535.1601586.1499611393763@mail.yahoo.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.23 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: Sun, 09 Jul 2017 14:49:55 -0000 You need to a build newer than SVN r320652 to fix this .. On 07/09/17 10:43, Filippo Moretti wrote: > FreeBSD sting 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320360: Mon Jun 26 15:49:29 UTC 2017 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386After compiling world and kernel I cannot make install world with the following error:Fatal error cannot allocate read line in initial thread at line 392 in file /use/src/lib/libthr/thread/thr_init.c (errorno=12)PID 42315 (cc) uid 0: exited on signal 6 (core dumped) > make: "/usr/src/share/mk/bsd.compiler.mk" line 145 : Unable to determine compiler type for CC=cc . Consider settingCOMPILER_TYPE > > > > > > This is the report of the crash I experienced with my custom kernel while running xinit (all the operations in console mode worked).I can succesfully start X using GENERIC.My kernel Worked fine until I reinstalled this snapshot. > > > Jul 8 08:41:53 sting kernel: > Jul 8 08:41:53 sting kernel: > Jul 8 08:41:53 sting kernel: Fatal trap 12: page fault while in kernel mode > Jul 8 08:41:53 sting kernel: cpuid = 1; apic id = 01 > Jul 8 08:41:53 sting kernel: fault virtual address = 0xa4c8c67d > Jul 8 08:41:53 sting kernel: fault code = supervisor read, page not present > Jul 8 08:41:53 sting kernel: instruction pointer = 0x20:0xc7f86218 > Jul 8 08:41:53 sting kernel: stack pointer = 0x28:0xf0b828e0 > Jul 8 08:41:53 sting kernel: frame pointer = 0x28:0xf0b8290c > Jul 8 08:41:53 sting kernel: code segment = base 0x0, limit 0xfffff, type 0x1b > Jul 8 08:41:53 sting kernel: = DPL 0, pres 1, def32 1, gran 1 > Jul 8 08:41:53 sting kernel: processor eflags = interrupt enabled, resume, IOPL = 0 > Jul 8 08:41:53 sting kernel: current process = 798 (Xorg) > Jul 8 08:41:53 sting kernel: trap number = 12 > Jul 8 08:41:53 sting kernel: panic: page fault > Jul 8 08:41:53 sting kernel: cpuid = 1 > Jul 8 08:41:53 sting kernel: time = 1499495998 > Jul 8 08:41:53 sting kernel: KDB: stack backtrace: > Jul 8 08:41:53 sting kernel: #0 0xc07d92df at kdb_backtrace+0x4f > Jul 8 08:41:53 sting kernel: #1 0xc079ad33 at vpanic+0x133 > Jul 8 08:41:53 sting kernel: #2 0xc079abfb at panic+0x1b > Jul 8 08:41:53 sting kernel: #3 0xc0a7a73e at trap_fatal+0x31e > Jul 8 08:41:53 sting kernel: #4 0xc0a7a783 at trap_pfault+0x33 > Jul 8 08:41:53 sting kernel: #5 0xc0a79e8e at trap+0x2be > Jul 8 08:41:53 sting kernel: #6 0xc0a68d6a at calltrap+0x6 > Jul 8 08:41:53 sting kernel: #7 0xc0823df8 at unp_connect2+0x88 > Jul 8 08:41:53 sting kernel: #8 0xc0823a9b at unp_connectat+0x40b > Jul 8 08:41:53 sting kernel: #9 0xc0821000 at uipc_connect+0x40 > Jul 8 08:41:53 sting kernel: #10 0xc081dac6 at kern_connectat+0x116 > Jul 8 08:41:53 sting kernel: #11 0xc081d999 at sys_connect+0x99 > Jul 8 08:41:53 sting kernel: #12 0xc0a7b104 at syscall+0x5b4 > Jul 8 08:41:53 sting kernel: #13 0xc0a68dee at Xint0x80_syscall+0x2e > Jul 8 08:41:53 sting kernel: Uptime: 2m10s > Jul 8 08:41:53 sting kernel: Physical memory: 2929 MB > Jul 8 08:41:53 sting kernel: Dumping 109 MB: 94 78 62 46 30 14 > Jul 8 08:41:53 sting kernel: Dump complete > Jul 8 08:41:53 sting kernel: Automatic reboot in 15 seconds - press a key on the console to abort > Jul 8 08:41:53 sting kernel: --> Press a key on the console to reboot, > Jul 8 08:41:53 sting kernel: --> or switch off the system now. > Jul 8 08:41:53 sting kernel: Rebooting... > Jul 8 08:41:53 sting kernel: cpu_reset: Restarting BSP > Jul 8 08:41:53 sting kernel: cpu_reset_proxy: Stopped CPU 1 > I also get these messages in console > > Jul 8 08:45:31 sting kernel: 1st 0xc6114bb8 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3539 > Jul 8 08:45:31 sting kernel: 2nd 0xd0391800 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:281 > Jul 8 08:45:31 sting kernel: stack backtrace: > Jul 8 08:45:31 sting kernel: #0 0xc0cbbbd1 at witness_debugger+0x81 > Jul 8 08:45:31 sting kernel: #1 0xc0cbbaf1 at witness_checkorder+0xd11 > Jul 8 08:45:31 sting kernel: #2 0xc0c60154 at _sx_xlock+0x64 > Jul 8 08:45:31 sting kernel: #3 0xc0f5d3b0 at ufsdirhash_add+0x40 > Jul 8 08:45:31 sting kernel: #4 0xc0f6010a at ufs_direnter+0x47a > Jul 8 08:45:31 sting kernel: #5 0xc0f6a07f at ufs_makeinode+0x5af > Jul 8 08:45:31 sting kernel: #6 0xc0f695a6 at ufs_symlink+0x36 > Jul 8 08:45:31 sting kernel: #7 0xc123be43 at VOP_SYMLINK_APV+0xd3 > Jul 8 08:45:31 sting kernel: #8 0xc0d301a4 at kern_symlinkat+0x274 > Jul 8 08:45:31 sting kernel: #9 0xc0d2ff21 at sys_symlink+0x31 > Jul 8 08:45:31 sting kernel: #10 0xc120719e at syscall+0x6de > Jul 8 08:45:31 sting kernel: #11 0xc11f2bee at Xint0x80_syscall+0x2e > Jul 8 08:46:07 sting kernel: lock order reversal: > Jul 8 08:46:07 sting kernel: 1st 0xd18c9914 ufs (ufs) @ /usr/src/sys/kern/vfs_syscalls.c:3362 > Jul 8 08:46:07 sting kernel: 2nd 0xc6114bb8 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:280 > Jul 8 08:46:07 sting kernel: 3rd 0xd1af3c68 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2602 > Jul 8 08:46:07 sting kernel: stack backtrace: > Jul 8 08:46:07 sting kernel: #0 0xc0cbbbd1 at witness_debugger+0x81 > Jul 8 08:46:07 sting kernel: #1 0xc0cbbaf1 at witness_checkorder+0xd11 > Jul 8 08:46:07 sting kernel: #2 0xc0c2b2cc at __lockmgr_args+0x79c > Jul 8 08:46:07 sting kernel: #3 0xc0f577e7 at ffs_lock+0x87 > Jul 8 08:46:07 sting kernel: #4 0xc123c627 at VOP_LOCK1_APV+0xd7 > Jul 8 08:46:07 sting kernel: #5 0xc0d37ea3 at _vn_lock+0x63 > Jul 8 08:46:07 sting kernel: #6 0xc0d24c51 at vget+0x81 > Jul 8 08:46:07 sting kernel: #7 0xc0d1655d at vfs_hash_get+0xcd > Jul 8 08:46:07 sting kernel: #8 0xc0f52a44 at ffs_vgetf+0x44 > Jul 8 08:46:07 sting kernel: #9 0xc0f48a7a at softdep_sync_buf+0xbba > Jul 8 08:46:07 sting kernel: #10 0xc0f585df at ffs_syncvnode+0x2df > Jul 8 08:46:07 sting kernel: #11 0xc0f57984 at ffs_fdatasync+0x24 > Jul 8 08:46:07 sting kernel: #12 0xc123fe87 at VOP_FDATASYNC_APV+0xd7 > Jul 8 08:46:07 sting kernel: #13 0xc0d34075 at kern_fsync+0x225 > Jul 8 08:46:07 sting kernel: #14 0xc0d34152 at sys_fdatasync+0x22 > Jul 8 08:46:07 sting kernel: #15 0xc120719e at syscall+0x6de > Jul 8 08:46:07 sting kernel: #16 0xc11f2bee at Xint0x80_syscall+0x2e > sincerelyFilippo > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > 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 Sun Jul 9 15:37:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86131D8D39E for ; Sun, 9 Jul 2017 15:37:33 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (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 30654341A for ; Sun, 9 Jul 2017 15:37:32 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190e-865ff70000000a57-f2-59624db4bcc8 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id DE.42.02647.4BD42695; Sun, 9 Jul 2017 11:37:24 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id v69FbNBB005439; Sun, 9 Jul 2017 11:37:23 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v69FbI4d030143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 9 Jul 2017 11:37:21 -0400 Date: Sun, 9 Jul 2017 10:37:18 -0500 From: Benjamin Kaduk To: Boris Samorodov Cc: freebsd-current@FreeBSD.org Subject: Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh Message-ID: <20170709153718.GM80947@kduck.kaduk.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrCIsWRmVeSWpSXmKPExsUixCmqrLvFNynS4FCXmcXfZ+eZLea8+cDk wOQx49N8Fo8nM1+xBTBFcdmkpOZklqUW6dslcGUsW8VSsJ+z4vilhewNjOfYuxg5OSQETCRu N65g62Lk4hASWMwk0dH5ngUkISSwgVFi/qcgiMQVJonJXStZQRIsAioSh5o2s4HYbAJqEutX XGMGsUWA4ifObwCbyiwgL/FraxOQzcEhLGAm0bJZEiTMC7Ts6IvXrBDzbSSe/T3AChEXlDg5 8wkLRKuWxI1/L5lAWpkFpCWW/+MACXMK2Eo8eNcKNl1UQFni7+F7LBMYBWYh6Z6FpHsWQvcC RuZVjLIpuVW6uYmZOcWpybrFyYl5ealFusZ6uZkleqkppZsYwQEqybeDcVKD9yFGAQ5GJR7e BbKJkUKsiWXFlbmHGCU5mJREecV6EyKF+JLyUyozEosz4otKc1KLDzFKcDArifCW2SRFCvGm JFZWpRblw6SkOViUxHnFNRojhATSE0tSs1NTC1KLYLIyHBxKErwzfIAaBYtS01Mr0jJzShDS TBycIMN5gIaf+AB0C29xQWJucWY6RP4Uoy7Hnb4NX5iEWPLy81KlxHltQAYJgBRllObBzQEl Fons/TWvGMWB3hLmXQxSxQNMSnCTXgEtYQJawlaXALKkJBEhJdXAaLsiRtphz/buWbf1CkJT biwOtLGa0c/n3tap/Utq++mCwogF3zfeeBm5KIdnyRy1T+FJmVEJFsaP+TeUxSw61M2efnyt iRrnFv/nTKvEZ+Ulzs4+2peUfq6wQZCn69VTl98ZTMkBGuek7UQ0rs1Xy2CaH25aJh1Z+llo y4rGi6U9mr4Gj5mVWIozEg21mIuKEwGlUJsmBwMAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 15:37:33 -0000 On Sun, Jul 09, 2017 at 01:02:26PM +0300, Boris Samorodov wrote: > Hi All, > > I try to create a FreeBSD guest as per TH, section "21.7.2. Creating > a FreeBSD Guest". All is good up until the last command at the section. > When I try to launch the installed client, I get: > ----- > # sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d > guest.img guestname > Launching virtual machine "guestname" ... > Installation CDROM image "./release.iso" is not readable > > % uname -a > FreeBSD latt.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r320821: Sun > Jul 9 07:10:56 MSK 2017 > bsam@builder.bsnet:/usr/obj/usr/src/sys/PKG64X amd64 > ----- > > Is it a bug at vmrun.sh or documentation? Documentation looks okay, as -I is documented during the install stage, and is not supposed to be needed during normal operation. The quoted error message from vmrun.sh happens when it thinks you need to install on the given filesystem image (if [ $force_install -eq 1 -o $need_install -eq 1 ];) so it might be worth checking that your guest.img contains a valid FFS filesystem on it. (Hmm, maybe you used ZFS and vmrun.sh isn't prepared to handle that?) -Ben From owner-freebsd-current@freebsd.org Sun Jul 9 15:48:35 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93B7ED8D8A2 for ; Sun, 9 Jul 2017 15:48:35 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward2m.cmail.yandex.net (forward2m.cmail.yandex.net [IPv6:2a02:6b8:b030::19]) (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 500E43A83; Sun, 9 Jul 2017 15:48:35 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp1m.mail.yandex.net (smtp1m.mail.yandex.net [IPv6:2a02:6b8:0:2519::121]) by forward2m.cmail.yandex.net (Yandex) with ESMTP id E5E14210C6; Sun, 9 Jul 2017 18:48:23 +0300 (MSK) Received: from smtp1m.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1m.mail.yandex.net (Yandex) with ESMTP id 582B363C0491; Sun, 9 Jul 2017 18:48:22 +0300 (MSK) Received: by smtp1m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id sz3Cz3vANd-mMnacc1L; Sun, 09 Jul 2017 18:48:22 +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=passap.ru; s=mail; t=1499615302; bh=uAzPzYEs+N9VdVrizYM+OKC5Kwf/LJSILuwqXBxEGgg=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=VI2+75NfhUOjChC4H5HSKXpW1+S345+JCa18LlWWLkzImvriSQiUbKBFWth9CGfph SQzCt6ZwGet/nUmc6nBau36zwqZm5FIIdirMCe0xDYHeCMC95J8ocA91sgk7D2BAyE 0NvYImuxeyiv16BnIYccB92zfVhkotGe7Ec0O+F0= Authentication-Results: smtp1m.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh To: Benjamin Kaduk Cc: freebsd-current@FreeBSD.org References: <20170709153718.GM80947@kduck.kaduk.org> From: Boris Samorodov Message-ID: <0d526def-9e14-078a-5933-ab97cd643e8c@passap.ru> Date: Sun, 9 Jul 2017 18:48:22 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170709153718.GM80947@kduck.kaduk.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.23 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: Sun, 09 Jul 2017 15:48:35 -0000 09.07.2017 18:37, Benjamin Kaduk пишет: > On Sun, Jul 09, 2017 at 01:02:26PM +0300, Boris Samorodov wrote: >> Hi All, >> >> I try to create a FreeBSD guest as per TH, section "21.7.2. Creating >> a FreeBSD Guest". All is good up until the last command at the section. >> When I try to launch the installed client, I get: >> ----- >> # sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d >> guest.img guestname >> Launching virtual machine "guestname" ... >> Installation CDROM image "./release.iso" is not readable >> >> % uname -a >> FreeBSD latt.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r320821: Sun >> Jul 9 07:10:56 MSK 2017 >> bsam@builder.bsnet:/usr/obj/usr/src/sys/PKG64X amd64 >> ----- >> >> Is it a bug at vmrun.sh or documentation? > > Documentation looks okay, as -I is documented during > the install stage, and is not supposed to be needed during > normal operation. > > The quoted error message from vmrun.sh happens when it thinks you > need to install on the given filesystem image > (if [ $force_install -eq 1 -o $need_install -eq 1 ];) > so it might be worth checking that your guest.img contains a valid > FFS filesystem on it. (Hmm, maybe you used ZFS and vmrun.sh isn't > prepared to handle that?) Yes, I used AutoZFS installer function to install FreeBSD. -- WBR, bsam From owner-freebsd-current@freebsd.org Sun Jul 9 15:58:15 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C9B9D8DC3A for ; Sun, 9 Jul 2017 15:58:15 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward5h.cmail.yandex.net (forward5h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::15]) (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 0F83C3EFF; Sun, 9 Jul 2017 15:58:15 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp1o.mail.yandex.net (smtp1o.mail.yandex.net [37.140.190.26]) by forward5h.cmail.yandex.net (Yandex) with ESMTP id 2826620C65; Sun, 9 Jul 2017 18:58:11 +0300 (MSK) Received: from smtp1o.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1o.mail.yandex.net (Yandex) with ESMTP id 747BE1300AB3; Sun, 9 Jul 2017 18:58:09 +0300 (MSK) Received: by smtp1o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 8tkDj9RiOl-w9Ba9qDx; Sun, 09 Jul 2017 18:58:09 +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=passap.ru; s=mail; t=1499615889; bh=QqTEjGuqWuX/MH362vlDkKzIK7R+c/26GLvuzJ8iWD4=; h=Subject:From:To:Cc:References:Message-ID:Date:In-Reply-To; b=gcAD//QwAejxMTbq1VyFm1H3vob9gX8WYyRWEpCK776/ONydj7BTBOuBDcLk9rFAp P9nDqxyUykCah4d5WUcKHFZAnrMNS5wsu6I6JkyEcAqRbPPV+y2aC+/V5tRmgeHByz F69W72unyBpz91XW2Fs8B9xPSwqC8PYeCsFzNkAY= Authentication-Results: smtp1o.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh From: Boris Samorodov To: Benjamin Kaduk Cc: freebsd-current@FreeBSD.org References: <20170709153718.GM80947@kduck.kaduk.org> <0d526def-9e14-078a-5933-ab97cd643e8c@passap.ru> Message-ID: <8ac4e8a3-35c9-0054-0e5f-c663b80fd97b@passap.ru> Date: Sun, 9 Jul 2017 18:58:09 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <0d526def-9e14-078a-5933-ab97cd643e8c@passap.ru> 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.23 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: Sun, 09 Jul 2017 15:58:15 -0000 09.07.2017 18:48, Boris Samorodov пишет: > 09.07.2017 18:37, Benjamin Kaduk пишет: >> On Sun, Jul 09, 2017 at 01:02:26PM +0300, Boris Samorodov wrote: >>> Hi All, >>> >>> I try to create a FreeBSD guest as per TH, section "21.7.2. Creating >>> a FreeBSD Guest". All is good up until the last command at the section. >>> When I try to launch the installed client, I get: >>> ----- >>> # sh /usr/share/examples/bhyve/vmrun.sh -c 4 -m 1024M -t tap0 -d >>> guest.img guestname >>> Launching virtual machine "guestname" ... >>> Installation CDROM image "./release.iso" is not readable >>> >>> % uname -a >>> FreeBSD latt.bsnet 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r320821: Sun >>> Jul 9 07:10:56 MSK 2017 >>> bsam@builder.bsnet:/usr/obj/usr/src/sys/PKG64X amd64 >>> ----- >>> >>> Is it a bug at vmrun.sh or documentation? >> >> Documentation looks okay, as -I is documented during >> the install stage, and is not supposed to be needed during >> normal operation. >> >> The quoted error message from vmrun.sh happens when it thinks you >> need to install on the given filesystem image >> (if [ $force_install -eq 1 -o $need_install -eq 1 ];) >> so it might be worth checking that your guest.img contains a valid >> FFS filesystem on it. (Hmm, maybe you used ZFS and vmrun.sh isn't >> prepared to handle that?) > > Yes, I used AutoZFS installer function to install FreeBSD. ----- % sudo mdconfig -f quest.img mdo0 % gpart show md0 => 40 16777136 md0 GPT (8.0G) 40 1024 1 freebsd-boot (512K) 1064 984 - free - (492K) 2048 4194304 2 freebsd-swap (2.0G) 4196352 12578816 3 freebsd-zfs (6.0G) 16775168 2008 - free - (1.0M) ----- So, that seems the same bug as at my previous email: https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066514.html -- WBR, bsam From owner-freebsd-current@freebsd.org Sun Jul 9 16:13:58 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C14DAD900FD for ; Sun, 9 Jul 2017 16:13:58 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 6E745645A0 for ; Sun, 9 Jul 2017 16:13:57 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074423-dd5ff70000000c44-84-5962550d410d Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id 09.11.03140.D0552695; Sun, 9 Jul 2017 12:08:46 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v69G8jtj025135; Sun, 9 Jul 2017 12:08:45 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v69G8fcc004193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 9 Jul 2017 12:08:44 -0400 Date: Sun, 9 Jul 2017 11:08:42 -0500 From: Benjamin Kaduk To: Boris Samorodov Cc: freebsd-current@FreeBSD.org Subject: Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh Message-ID: <20170709160841.GN80947@kduck.kaduk.org> References: <20170709153718.GM80947@kduck.kaduk.org> <0d526def-9e14-078a-5933-ab97cd643e8c@passap.ru> <8ac4e8a3-35c9-0054-0e5f-c663b80fd97b@passap.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8ac4e8a3-35c9-0054-0e5f-c663b80fd97b@passap.ru> User-Agent: Mutt/1.7.1 (2016-10-04) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42IRYrdT0eULTYo0WLja0uLvs/PMFnPefGBy YPKY8Wk+i8eTma/YApiiuGxSUnMyy1KL9O0SuDJm3utlLPjMWzHv/leWBsZ1XF2MnBwSAiYS J/dfYO1i5OIQEljMJHFg20VGkISQwAZGiaedbBCJK0wSW6YtYAVJsAioSBzd/x7MZhNQk1i/ 4hoziC0CFD9xfgM7iM0sIC/xa2sTkM3BISxgJtGyWRIkzAu07OLvHnaImWcZJa68eMQGkRCU ODnzCQtEr7rEn3mXmEF6mQWkJZb/44AZ2bx1NtgqTgFbiX+z1jKB2KICyhJ/D99jmcAoOAvJ pFlIJs1CmDQLyaQFjCyrGGVTcqt0cxMzc4pTk3WLkxPz8lKLdM30cjNL9FJTSjcxgoPaRXkH 48s+70OMAhyMSjy8C2QTI4VYE8uKK3MPMUpyMCmJ8or1JkQK8SXlp1RmJBZnxBeV5qQWH2KU 4GBWEuEts0mKFOJNSaysSi3Kh0lJc7AoifOKazRGCAmkJ5akZqemFqQWwWRlODiUJHhXBAM1 ChalpqdWpGXmlCCkmTg4QYbzAA0/8QHoFt7igsTc4sx0iPwpRl2OO30bvjAJseTl56VKifNK ggwSACnKKM2DmwNKRhLZ+2teMYoDvSXMyxcEVMUDTGRwk14BLWECWsJWlwCypCQRISXVwGiw u3T3ldWrtmto/jlnp8hVLtBYMflq+re3nTUL33Oy3vhR4WMmXBE2yXjDbCW2IM/jf2YbvD75 5MXkNM6M517rzC1idt3lV7xQ5a596+K5K75tjIcbeG34Tzazh8v8mn4zpLNTws/+/5dA86i4 my8Zr3xsClwlmnzytLRF/dzjl5l372BUTlBiKc5INNRiLipOBAD/atUeIQMAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 16:13:58 -0000 On Sun, Jul 09, 2017 at 06:58:09PM +0300, Boris Samorodov wrote: > 09.07.2017 18:48, Boris Samorodov пишет: > > 09.07.2017 18:37, Benjamin Kaduk пишет: > >> > >> Documentation looks okay, as -I is documented during > >> the install stage, and is not supposed to be needed during > >> normal operation. > >> > >> The quoted error message from vmrun.sh happens when it thinks you > >> need to install on the given filesystem image > >> (if [ $force_install -eq 1 -o $need_install -eq 1 ];) > >> so it might be worth checking that your guest.img contains a valid > >> FFS filesystem on it. (Hmm, maybe you used ZFS and vmrun.sh isn't > >> prepared to handle that?) > > > > Yes, I used AutoZFS installer function to install FreeBSD. > > ----- > % sudo mdconfig -f quest.img > mdo0 > > % gpart show md0 > => 40 16777136 md0 GPT (8.0G) > 40 1024 1 freebsd-boot (512K) > 1064 984 - free - (492K) > 2048 4194304 2 freebsd-swap (2.0G) > 4196352 12578816 3 freebsd-zfs (6.0G) > 16775168 2008 - free - (1.0M) > ----- > > So, that seems the same bug as at my previous email: > https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066514.html Is it? I refer to this part of vmrun.sh: file -s ${first_diskdev} | grep "boot sector" > /dev/null rc=$? if [ $rc -ne 0 ]; then file -s ${first_diskdev} | grep ": Unix Fast File sys" > /dev/null rc=$? fi if [ $rc -ne 0 ]; then need_install=1 else need_install=0 fi Which is not expected to be particularly robust. (BTW, I think there is not agreement as to whether vmrun.sh should be used in general use, or alternate solutions for VM managemnet.) -Ben From owner-freebsd-current@freebsd.org Sun Jul 9 16:38:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7ACF7D905D8 for ; Sun, 9 Jul 2017 16:38:38 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward3h.cmail.yandex.net (forward3h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::13]) (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 36BA864D11; Sun, 9 Jul 2017 16:38:38 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp2j.mail.yandex.net (smtp2j.mail.yandex.net [IPv6:2a02:6b8:0:801::ac]) by forward3h.cmail.yandex.net (Yandex) with ESMTP id 42B1B20CB5; Sun, 9 Jul 2017 19:38:27 +0300 (MSK) Received: from smtp2j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2j.mail.yandex.net (Yandex) with ESMTP id 8326F3EC0E93; Sun, 9 Jul 2017 19:38:25 +0300 (MSK) Received: by smtp2j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 00RDUqbno1-cPW0F73e; Sun, 09 Jul 2017 19:38:25 +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=passap.ru; s=mail; t=1499618305; bh=XKFtJDVj6N3lM4LWu/JwbOFGPXCU3jUAo4VQhSurMEE=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=By6+z87B3pnAdJVOiwsKU79m6WG2GmZzKcfOZQbpHX3f7RHpAkrGDdH8Ej4AbVlle KYq8ciJ2m2vdCq4acgUge7tsdez3mB8aLv9CestD9ku+SJgR7J/De7dK5k6dpwhCGE idsnMV3ztNnpK+2i35C3ZqbEZ129l+76VdJMutAM= Authentication-Results: smtp2j.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh To: Benjamin Kaduk Cc: freebsd-current@FreeBSD.org References: <20170709153718.GM80947@kduck.kaduk.org> <0d526def-9e14-078a-5933-ab97cd643e8c@passap.ru> <8ac4e8a3-35c9-0054-0e5f-c663b80fd97b@passap.ru> <20170709160841.GN80947@kduck.kaduk.org> From: Boris Samorodov Message-ID: <7b73ab2d-0f6f-f11a-b37f-23f148af8277@passap.ru> Date: Sun, 9 Jul 2017 19:38:25 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170709160841.GN80947@kduck.kaduk.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 16:38:38 -0000 09.07.2017 19:08, Benjamin Kaduk пишет: > On Sun, Jul 09, 2017 at 06:58:09PM +0300, Boris Samorodov wrote: >> 09.07.2017 18:48, Boris Samorodov пишет: >>> 09.07.2017 18:37, Benjamin Kaduk пишет: >>>> >>>> Documentation looks okay, as -I is documented during >>>> the install stage, and is not supposed to be needed during >>>> normal operation. >>>> >>>> The quoted error message from vmrun.sh happens when it thinks you >>>> need to install on the given filesystem image >>>> (if [ $force_install -eq 1 -o $need_install -eq 1 ];) >>>> so it might be worth checking that your guest.img contains a valid >>>> FFS filesystem on it. (Hmm, maybe you used ZFS and vmrun.sh isn't >>>> prepared to handle that?) >>> >>> Yes, I used AutoZFS installer function to install FreeBSD. >> >> ----- >> % sudo mdconfig -f quest.img >> mdo0 >> >> % gpart show md0 >> => 40 16777136 md0 GPT (8.0G) >> 40 1024 1 freebsd-boot (512K) >> 1064 984 - free - (492K) >> 2048 4194304 2 freebsd-swap (2.0G) >> 4196352 12578816 3 freebsd-zfs (6.0G) >> 16775168 2008 - free - (1.0M) >> ----- >> >> So, that seems the same bug as at my previous email: >> https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066514.html > > Is it? I refer to this part of vmrun.sh: > > file -s ${first_diskdev} | grep "boot sector" > /dev/null > rc=$? > if [ $rc -ne 0 ]; then > file -s ${first_diskdev} | grep ": Unix Fast File sys" > /dev/null > rc=$? > fi > if [ $rc -ne 0 ]; then > need_install=1 > else > need_install=0 > fi > > Which is not expected to be particularly robust. > (BTW, I think there is not agreement as to whether vmrun.sh should > be used in general use, or alternate solutions for VM managemnet.) OK, normal bhyveload/bhyve ended up at a successful boot. Benjamin, thank you for your comments and help! -- WBR, bsam From owner-freebsd-current@freebsd.org Sun Jul 9 16:53:07 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 106A3D90A68 for ; Sun, 9 Jul 2017 16:53:07 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (xvm-110-62.dc2.ghst.net [46.226.110.62]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "theravensnest.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7DF46551A for ; Sun, 9 Jul 2017 16:53:05 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.1.65] (host86-147-116-38.range86-147.btcentralplus.com [86.147.116.38]) (authenticated bits=0) by theravensnest.org (8.15.2/8.15.2) with ESMTPSA id v69GhRMK006492 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 9 Jul 2017 16:43:28 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: d60e724c-75b0-4b63-9702-f4a9d2bf6793: Host host86-147-116-38.range86-147.btcentralplus.com [86.147.116.38] claimed to be [192.168.1.65] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Getting PID of socket client From: David Chisnall In-Reply-To: <684e8346-c4a8-a0c5-cb2a-cd5159d2af1c@gmx.net> Date: Sun, 9 Jul 2017 17:43:22 +0100 Cc: Johannes Lundberg , freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: References: <684e8346-c4a8-a0c5-cb2a-cd5159d2af1c@gmx.net> To: Stefan Ehmann X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 16:53:07 -0000 On 9 Jul 2017, at 14:25, Stefan Ehmann wrote: >=20 > Don't why the structs are not compatible, maybe because: > "The process ID cmcred_pid should not be looked up (such as via the > KERN_PROC_PID sysctl) for making security decisions. The sending = process could have exited and its process ID already been reused for a = new process." Note that having the kernel provide a process descriptor instead of a = PID would allow the userspace process to have race-free access to the = PID. David From owner-freebsd-current@freebsd.org Sun Jul 9 18:40:17 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 174DED929D9 for ; Sun, 9 Jul 2017 18:40:17 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward1m.cmail.yandex.net (forward1m.cmail.yandex.net [IPv6:2a02:6b8:b030::18]) (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 C7F7E683E7 for ; Sun, 9 Jul 2017 18:40:16 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [77.88.29.85]) by forward1m.cmail.yandex.net (Yandex) with ESMTP id 5AFC720DA6 for ; Sun, 9 Jul 2017 21:40:13 +0300 (MSK) Received: from smtp2p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2p.mail.yandex.net (Yandex) with ESMTP id 4188F1A80058 for ; Sun, 9 Jul 2017 21:40:12 +0300 (MSK) Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id NtJmECYIvU-eClOJb5o; Sun, 09 Jul 2017 21:40:12 +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=passap.ru; s=mail; t=1499625612; bh=u3s/iNmaXrJVgt/gK9KEX9wTXzev/3mQI234Hr0vdQs=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=ZI7aRQ6o1wcWYLV1JMu5G8xnaxuWT2bFWtGZngl/3vhUbPrbeM3eiY5jw7kZeLpDt 2VOOS2BAxplRk6Mm6qqODPf6qAuTAw+MbP/+bHsuozZIhz7MjpkHrl3HNzUSCltIai mMGJMrdF0BxH7KYFI6ZNXMLzHFVSHoEJNyNeNnt0= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0 Subject: [SOLVED] [memstick install] auto-zfs error To: freebsd-current@freebsd.org References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> From: Boris Samorodov Message-ID: Date: Sun, 9 Jul 2017 21:40:11 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> 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.23 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: Sun, 09 Jul 2017 18:40:17 -0000 08.07.2017 18:56, Boris Samorodov пишет: > Hi All, > > I tied to install a new FreeBSD-amd-12 system from official USB > installation memstick.img. Auto-UFS (GPT) installs fine and the system > boots fine. However, ZFS-Auto install succeeds, but is not loaded. > At the very beginning it gives something like "gpt sector XXXX error, > gpt sector 1 error, can't find zroot..." > > Is it a known error / should I give more (precise) errors? > > I tried two recent images with the same result: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img It turned out GPT and zfs are not usable at this machine. MBR / ZFS works fine. I'll stick with that. -- WBR, bsam From owner-freebsd-current@freebsd.org Sun Jul 9 18:59:07 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D806D92E71 for ; Sun, 9 Jul 2017 18:59:07 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward5o.cmail.yandex.net (forward5o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::28a]) (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 C214368BA6; Sun, 9 Jul 2017 18:59:06 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [77.88.29.86]) by forward5o.cmail.yandex.net (Yandex) with ESMTP id CB18B20D3A; Sun, 9 Jul 2017 21:59:03 +0300 (MSK) Received: from smtp3p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp3p.mail.yandex.net (Yandex) with ESMTP id 0D1BE132007F; Sun, 9 Jul 2017 21:59:02 +0300 (MSK) Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id Qo9DBakYJt-x1ximiKc; Sun, 09 Jul 2017 21:59:01 +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=passap.ru; s=mail; t=1499626741; bh=gsqiwKVdu6M1ZNCSvaMQcI7tPRc1wyqHwe6ifk92zTo=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=pmbiH35D+TvBqjETd3HqLcMe6nkuYYueg+UBwMhU7aBaYzGw6qXZgl8lNQv0UGd2/ q5eXU02PDYuTKfPuWMYzcom1WOZGQHyN9PwO9a1ng2guAi60SjlGaA2lBLNZJOHaot lR4hO2r6e4WJqAN0DRFRJvdMLr8DbA45aJ0epN1w= Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: [bhyve] FreeBSD guest, Handbook, vmrun.sh To: Benjamin Kaduk Cc: freebsd-current@FreeBSD.org References: <20170709153718.GM80947@kduck.kaduk.org> <0d526def-9e14-078a-5933-ab97cd643e8c@passap.ru> <8ac4e8a3-35c9-0054-0e5f-c663b80fd97b@passap.ru> <20170709160841.GN80947@kduck.kaduk.org> From: Boris Samorodov Message-ID: <7e5f7abe-3903-c680-f349-3b3bdc61ae6f@passap.ru> Date: Sun, 9 Jul 2017 21:59:01 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170709160841.GN80947@kduck.kaduk.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.23 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: Sun, 09 Jul 2017 18:59:07 -0000 09.07.2017 19:08, Benjamin Kaduk пишет: > (BTW, I think there is not agreement as to whether vmrun.sh should > be used in general use, or alternate solutions for VM managemnet.) As a side note: I used the process written at TH... -- WBR, bsam From owner-freebsd-current@freebsd.org Sun Jul 9 19:57:28 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7910AD93F26; Sun, 9 Jul 2017 19:57:28 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670069.outbound.protection.outlook.com [40.107.67.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 24CB06E0CF; Sun, 9 Jul 2017 19:57:24 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.13; Sun, 9 Jul 2017 19:57:22 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.1240.020; Sun, 9 Jul 2017 19:57:22 +0000 From: Rick Macklem To: "freebsd-current@freebsd.org" CC: "rc@freebsd.org" Subject: small patch for /etc/rc.d/nfsd, bugfix or POLA violation? Thread-Topic: small patch for /etc/rc.d/nfsd, bugfix or POLA violation? Thread-Index: AQHS+OwyOXcv/ziVcEC7Kot52D/l2w== Date: Sun, 9 Jul 2017 19:57:22 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTXPR01MB0189; 7:BVH6jFEjJMYrTGiSKidWOIWKFL5hK19NKXYBIm/lIuJL5kyPDTm1BBpcs7Pcwj6SjrgeQOg5j7GIalGAjG+vc0hGkpMxuzFk539mrX1u75P1ZS+2yDvLohJ7RKifSax0d35x5qfMIrcsicc+eGf0Qhz10tp9FjLnL5iDYHYtKC5EXczdbB/AY6bCpFsnWX1FNOeKp4HVatF1cKhnUxcyeN6AMcbR1znafzsWwuj9RlRIk4nQqdxuwu13pqoR2Qi2Nw1wgDvfIFrzNkHEnyQgNCvn8w4oTDFg0DFY+Bp/WUdDETANhDQRjJOyUWRsoJ7f3PCrTZ3MV3Dnr+bast7jhS+i+fps6jrPhS1QpxoMGysVSxr7NDtyCGr31eQv/eTBejKqXVg/xPyB1q+/xfTOiRg5i3shHAZWu1JN8HckBplz8tXvGkWqabXUXZqJzJzH5808V8/3BkdlovYura++z9c6jEzoshNgKnOIS1M4U/YDx5frxcGz7CgIYmjp3sacrsxIjOLbERVJFdIfOmuDjM/JSGeVn2W4DWkoF9NebVdGCziVWYLa7X9fP632S3eePnNS2Fcz+Si7OvWJbfL4dxSR3rUBSgH/VrxAYl+dmdcxf3/GA2XUNZtkyqBKWpzPs4dFCHaCXE2ZK6kJ0CO1KrdL20FA4VBxiqaAwU13OV0PE1+IqB/j9vEhCYcTqjq45SfU5S9QEfxAQG538MBP030RMPhFJ27wl3bTdyxMqGaRr5JJ14jblLWSVnCYkjuK8or9xJKt28z1PAgkzaxpBa4FUU/AMo/If+c9b2APEoA= x-ms-office365-filtering-correlation-id: 42bb23d9-ee6b-4ef4-559f-08d4c704b6e3 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(49563074)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:YTXPR01MB0189; x-ms-traffictypediagnostic: YTXPR01MB0189: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(236129657087228)(788757137089)(247924648384137); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(102415395)(6040450)(2401047)(2017060910075)(5005006)(8121501046)(100000703101)(100105400095)(3002001)(10201501046)(93006095)(93001095)(6041248)(20161123562025)(20161123558100)(20161123564025)(20161123560025)(201703131423075)(201702281528075)(201702281529075)(201703061421075)(201703061406153)(20161123555025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:YTXPR01MB0189; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:YTXPR01MB0189; x-forefront-prvs: 03630A6A4A x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39840400002)(39450400003)(39850400002)(39400400002)(39410400002)(77096006)(54356999)(2906002)(99936001)(50986999)(86362001)(74482002)(2351001)(6506006)(305945005)(74316002)(6436002)(25786009)(5640700003)(55016002)(450100002)(8676002)(81166006)(8936002)(4326008)(9686003)(14454004)(2900100001)(478600001)(7696004)(38730400002)(110136004)(102836003)(6916009)(33656002)(53936002)(2501003)(5890100001)(189998001)(3280700002)(5660300001)(3660700001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0189; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/mixed; boundary="_002_YTXPR01MB0189F5614497D4FA96A7579ADDA80YTXPR01MB0189CANP_" MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2017 19:57:22.7293 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0189 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 19:57:28 -0000 --_002_YTXPR01MB0189F5614497D4FA96A7579ADDA80YTXPR01MB0189CANP_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, The attached one line patch to /etc/rc.d/nfsd modifies the script so that i= t does not force the nfsuserd to be run when nfsv4_server_enable is set. (nfsuserd can still be enabled via nfsuserd_enable=3D"YES" is /etc/rc.conf.= ) Here's why I think this patch might be appropriate... (a) - The original RFC for NFSv4 (RFC3530) essentially required Owners and Owner_groups to be specified as @ and this required the nfsuserd daemon to be running. (b) - RFC7530, which replace RFC3530, allows a Owner/Owner_group string to = be the uid/gid number in a string when using AUTH_SYS. This simplifies confi= guration for an all AUTH_SYS/POSIX environment (most NFS uses, I suspect?). To make the server do (b), two things need to be done: 1 - set vfs.nfsd.enable_stringtouid=3D1 2 - set vfs.nfsd.enable_uidtostring=3D1 (for head, I don't know if it will = be MFC'd?) OR - never run nfsuserd after booting (killing it off after it has been runn= ing is not sufficient) =20 Given the above, it would seem that /etc/rc.d/nfsd should not force running= of the nfsuserd daemon, due to changes in the protocol. However, this will result in a POLA violation, in that after the patch, nfs= userd won't start when booting, unless nfsuserd_enable=3D"YES" is added to /etc/rc.conf= . So, what do people think about this patch? rick= --_002_YTXPR01MB0189F5614497D4FA96A7579ADDA80YTXPR01MB0189CANP_ Content-Type: application/octet-stream; name="nfsd-rcd.patch" Content-Description: nfsd-rcd.patch Content-Disposition: attachment; filename="nfsd-rcd.patch"; size=372; creation-date="Sun, 09 Jul 2017 19:57:16 GMT"; modification-date="Sun, 09 Jul 2017 19:57:16 GMT" Content-Transfer-Encoding: base64 LS0tIG5mc2Quc2F2CTIwMTctMDctMDkgMTU6MzM6MDguNDE2MzgzMDAwIC0wNDAwCisrKyBuZnNk CTIwMTctMDctMDkgMTU6MzM6NDIuNTc3MDU3MDAwIC0wNDAwCkBAIC0zMyw4ICszMyw3IEBAIG5m c2RfcHJlY21kKCkKIAkJc3lzY3RsIHZmcy5uZnNkLm5mc19wcml2cG9ydD0wID4gL2Rldi9udWxs CiAJZmkKIAotCWlmIGNoZWNreWVzbm8gbmZzdjRfc2VydmVyX2VuYWJsZSB8fCBcCi0JICAgIGNo ZWNreWVzbm8gbmZzX3NlcnZlcl9tYW5hZ2VnaWRzOyB0aGVuCisJaWYgY2hlY2t5ZXNubyBuZnNf c2VydmVyX21hbmFnZWdpZHM7IHRoZW4KIAkJZm9yY2VfZGVwZW5kIG5mc3VzZXJkIHx8IGVyciAx ICJDYW5ub3QgcnVuIG5mc3VzZXJkIgogCWZpCiAK --_002_YTXPR01MB0189F5614497D4FA96A7579ADDA80YTXPR01MB0189CANP_-- From owner-freebsd-current@freebsd.org Sun Jul 9 20:32:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EFFAD948FF; Sun, 9 Jul 2017 20:32:38 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) (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 109376EEFA; Sun, 9 Jul 2017 20:32:37 +0000 (UTC) (envelope-from cy.schubert@komquats.com) Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with SMTP id UIsVd0XvEM9gtUIsWdh2xb; Sun, 09 Jul 2017 14:32:29 -0600 X-Authority-Analysis: v=2.2 cv=a+JAzQaF c=1 sm=1 tr=0 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17 a=kj9zAlcOel0A:10 a=G3gG6ho9WtcA:10 a=UqCG9HQmAAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=1j0icQxtbOdNwcB9JegA:9 a=S2FHIams8PM9pwU0:21 a=aiMRPD2nugAZN8cm:21 a=CjuIK1q_8ugA:10 a=XqhbnV00hwtEhPrFMTfD:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 52784CA; Sun, 9 Jul 2017 13:32:27 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id v69KVB9F045630; Sun, 9 Jul 2017 13:31:11 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.14.8/Submit) with ESMTP id v69KVBSn045623; Sun, 9 Jul 2017 13:31:11 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201707092031.v69KVBSn045623@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Rick Macklem cc: "freebsd-current@freebsd.org" , "rc@freebsd.org" Subject: Re: small patch for /etc/rc.d/nfsd, bugfix or POLA violation? In-Reply-To: Message from Rick Macklem of "Sun, 09 Jul 2017 19:57:22 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 09 Jul 2017 13:31:11 -0700 X-CMAE-Envelope: MS4wfO/nfrEOXZzR3pUONkxqGoMOQsPeRZYCX+U3l3esqw9pIvR2dAE+Up5hDz3LWhKV8ElkzDpdifUedWEx0BadHOicQiZQeussC79dvAHRYcjUVZf5XVTq 1MD5sozLTGe09ZEuW7savf0wZNPN35+heoIurjQFz70DtHGcZd1xBSmBOX9n7ypNpt3oCo2MG3uY8ylEfbJ4jhjnyESMxex7fB0UWVtJfx52LUsYrJc6Gy11 UVR0mq+Y2XawyERd/194Eg== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 20:32:38 -0000 In message , Rick Macklem writes: > --_002_YTXPR01MB0189F5614497D4FA96A7579ADDA80YTXPR01MB0189CANP_ > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Hi, > > The attached one line patch to /etc/rc.d/nfsd modifies the script so that i= > t > does not force the nfsuserd to be run when nfsv4_server_enable is set. > (nfsuserd can still be enabled via nfsuserd_enable=3D"YES" is /etc/rc.conf.= > ) > > Here's why I think this patch might be appropriate... > (a) - The original RFC for NFSv4 (RFC3530) essentially required Owners and > Owner_groups to be specified as @ and this required > the nfsuserd daemon to be running. > (b) - RFC7530, which replace RFC3530, allows a Owner/Owner_group string to = > be > the uid/gid number in a string when using AUTH_SYS. This simplifies confi= > guration > for an all AUTH_SYS/POSIX environment (most NFS uses, I suspect?). > > To make the server do (b), two things need to be done: > 1 - set vfs.nfsd.enable_stringtouid=3D1 > 2 - set vfs.nfsd.enable_uidtostring=3D1 (for head, I don't know if it will = > be MFC'd?) > OR > - never run nfsuserd after booting (killing it off after it has been runn= > ing is not > sufficient) > =20 > Given the above, it would seem that /etc/rc.d/nfsd should not force running= > of > the nfsuserd daemon, due to changes in the protocol. > > However, this will result in a POLA violation, in that after the patch, nfs= > userd won't > start when booting, unless nfsuserd_enable=3D"YES" is added to /etc/rc.conf= > . > > So, what do people think about this patch? rick= How about a warning message + an UPDATING entry + no MFC? And, relnotes = yes to say we now support RFC7530 in 12.0? -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Sun Jul 9 21:02:41 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10D67D95C10 for ; Sun, 9 Jul 2017 21:02:41 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mailout.stack.nl (mailout05.stack.nl [IPv6:2001:610:1108:5010::202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout.stack.nl", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CEA6B70653; Sun, 9 Jul 2017 21:02:40 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mailout.stack.nl (Postfix) with ESMTP id 7D90A69; Sun, 9 Jul 2017 23:02:38 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 65D0528497; Sun, 9 Jul 2017 23:02:38 +0200 (CEST) Date: Sun, 9 Jul 2017 23:02:38 +0200 From: Jilles Tjoelker To: David Chisnall Cc: Stefan Ehmann , Johannes Lundberg , freebsd-current Subject: Re: Getting PID of socket client Message-ID: <20170709210238.GA51240@stack.nl> References: <684e8346-c4a8-a0c5-cb2a-cd5159d2af1c@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 21:02:41 -0000 On Sun, Jul 09, 2017 at 05:43:22PM +0100, David Chisnall wrote: > On 9 Jul 2017, at 14:25, Stefan Ehmann wrote: > > Don't why the structs are not compatible, maybe because: > > "The process ID cmcred_pid should not be looked up (such as via the > > KERN_PROC_PID sysctl) for making security decisions. The sending > > process could have exited and its process ID already been reused for > > a new process." > Note that having the kernel provide a process descriptor instead of a > PID would allow the userspace process to have race-free access to the > PID. This is an interesting idea, but would require quite a few changes. First, current process descriptors act as an artificial parent process, suppressing the normal SIGCHLD to the parent and not being matched by a wildcard waitpid() or similar function. A new kind of process descriptor would have to be added which leaves this behaviour unchanged and could exist in parallel with a process descriptor from pdfork(). Second, pdgetpid() makes no guarantees whether the process ID still exists. It should not make them either for this case, since this would allow another user to hold onto process slots for RLIMIT_NPROC. The only solution would be to add variants of the necessary calls that take a process descriptor instead of a process ID. -- Jilles Tjoelker From owner-freebsd-current@freebsd.org Sun Jul 9 21:21:31 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 669F2D9628A for ; Sun, 9 Jul 2017 21:21:31 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mailout.stack.nl (mailout05.stack.nl [IPv6:2001:610:1108:5010::202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout.stack.nl", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 31C58710CF for ; Sun, 9 Jul 2017 21:21:31 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mailout.stack.nl (Postfix) with ESMTP id 887A469; Sun, 9 Jul 2017 23:21:22 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 732A928497; Sun, 9 Jul 2017 23:21:22 +0200 (CEST) Date: Sun, 9 Jul 2017 23:21:22 +0200 From: Jilles Tjoelker To: Johannes Lundberg Cc: Stefan Ehmann , freebsd-current Subject: Re: Getting PID of socket client Message-ID: <20170709212122.GB51240@stack.nl> References: <684e8346-c4a8-a0c5-cb2a-cd5159d2af1c@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 09 Jul 2017 21:21:31 -0000 On Sun, Jul 09, 2017 at 02:07:06PM +0000, Johannes Lundberg wrote: > That code gets the child's pid from the fork command. That's is not > available in my case (Wayland client connects to Wayland server via unix > socket). > I can understand the security issue.. hmm will dig further tomorrow.. It seems like what Wayland wants is not a security feature, but a feature to prevent people from building things that will not work in a future more secure world. In this future world, operations like making a screenshot would be privileged. Even if the PID race is solved, it remains trivial to fake the check (for example, fork a process that sends the initial message and then immediately execs a "privileged" binary, or use ptrace to attach to a "privileged" binary or launch a new copy of a "privileged" binary). With regard to security, it would be equivalent to have the client send the name of its binary to the server. Putting this into a low-level Wayland library would deter people from faking the check to do things that will not work in the future more secure world. I don't know how invasive this would be, though. One possible implementation of the future more secure world would be per-application UIDs a la Android. Another one would be Capsicum-sandboxed applications where applications receive their Wayland sockets pre-connected by code that tells the Wayland server the application identity. -- Jilles Tjoelker From owner-freebsd-current@freebsd.org Mon Jul 10 02:15:25 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37915D9AFEF for ; Mon, 10 Jul 2017 02:15:25 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::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 ED1E577BD0 for ; Mon, 10 Jul 2017 02:15:24 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qt0-x22f.google.com with SMTP id 32so62236037qtv.1 for ; Sun, 09 Jul 2017 19:15:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=to:from:subject:message-id:date:user-agent:mime-version; bh=QRiWTknuCN32wYFnGF2rSxv2akfzFPKzR7Uw/XpmV5o=; b=Jm2874hHi24xp25Nu+vX1AApgiPKyfkxol9CfnUbjEh/1kGfIPVZrM0giDK61aNUo1 jfyrJzhIXftqlISdJOH/zuuOf+8i2nN5IiCeLOYktFlFKlR2FnxwsDzahtVDn9wVrB3o 9UpI6mzv2EGO8undVQXE0rXLSCE1NHMA//zGc= 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; bh=QRiWTknuCN32wYFnGF2rSxv2akfzFPKzR7Uw/XpmV5o=; b=gGWi7+4C/QTHvrUJvP1GPNzC99fI8+/KjeqVaAJY+5xXqI0WuMy9DIVX1ygigfBAit wxUW7mPL+zQuhThKJbR7JT4UNGJbmrYvKVKcJ83O05Xeh4afJvw7bE75HI5WNhlDIzvR WVgOOl9JZw6Pk3MHabHb51AqkYetZe06KrWyLHTU46LXddhRU3Bz59rzxptn+1YujPVA FzSdiRRYn60pTupHYlmTmif82sskXu/nvr0IvOJzbTpDY2UIKsOwdamuUniaimObOMR1 fuh73E9O09n8OOxu57iaEG4eaqxvsn1qq0wIjbyRc3UDddg/i9tso4QU/7ey2Sqb9DQl e0+A== X-Gm-Message-State: AIVw1109uRWdMO7MqVGB8JfCjLRhPAtTtFXSxS/vpzZbu3aw+DcqnjxB ZKLhAl2JdlIMdWGBuMA= X-Received: by 10.200.43.208 with SMTP id n16mr1514464qtn.190.1499652923157; Sun, 09 Jul 2017 19:15:23 -0700 (PDT) Received: from ?IPv6:2804:54:19ef:cc00:d576:4783:d01d:7f6b? ([2804:54:19ef:cc00:d576:4783:d01d:7f6b]) by smtp.googlemail.com with ESMTPSA id a1sm7455169qkg.54.2017.07.09.19.15.21 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Jul 2017 19:15:22 -0700 (PDT) To: freebsd-current From: =?UTF-8?B?T3RhY8OtbGlv?= Subject: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730 Message-ID: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> Date: Sun, 9 Jul 2017 23:15:18 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 02:15:25 -0000 Dears I'm the maintainer of xosview and I'm debugging rather weird behavior from it in the latest FreeBSD 12 revisions (12.0-CURRENT #0 r320730 AMD64) . The problem is occurring on the lines responsible for collecting statistics about paging. These lines follow: If (pageinfo) { Pageinfo [0] = (uint64_t) vm.v_vnodepgsin + (uint64_t) vm.v_swappgsin; Pageinfo [1] = (uint64_t) vm.v_vnodepgsout + (uint64_t) vm.v_swappgsout; } This code works on FreeBSD 11 and until a short time ago it works at 12. But now it returns extremely large values ​​when interpreted as 64-bit values. A debugging has shown that for this sysctl call the following values ​​are returned in the terminal: sysctl vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout Vm.stats.vm.v_vnodepgsin: 47432 Vm.stats.vm.v_swappgsin: 0 Vm.stats.vm.v_vnodepgsout: 19 Vm.stats.vm.v_swappgsout: 0 While the code returns things like: Pageinf [0] = 34359785800; Pageinfo [1] = 140733193388051 Pageinf [0] = 34359785800; Pageinfo [1] = 2678138638516092947 After some tests I found that if I change the code to use a typecast to (uint32_t) then Xosview works correctly.: If (pageinfo) { Pageinfo [0] = (uint32_t) ((uint64_t) vm.v_vnodepgsin + (uint64_t) vm.v_swappgsin); Pageinfo [1] = (uint32_t) ((uint64_t) vm.v_vnodepgsout + (uint64_t) vm.v_swappgsout); } For me, it seems that some code in the kernel is storing values ​​as 32 bits where it should be 64 bits. Is this behavior correct? []'s -Otacílio From owner-freebsd-current@freebsd.org Mon Jul 10 05:51:59 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9809FD9E45F for ; Mon, 10 Jul 2017 05:51:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F10E7CD69 for ; Mon, 10 Jul 2017 05:51:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v6A5pqUm007686 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Jul 2017 08:51:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v6A5pqUm007686 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v6A5ppQO007685; Mon, 10 Jul 2017 08:51:51 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 10 Jul 2017 08:51:51 +0300 From: Konstantin Belousov To: Otac??lio Cc: freebsd-current Subject: Re: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730 Message-ID: <20170710055151.GL1935@kib.kiev.ua> References: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> User-Agent: Mutt/1.8.3 (2017-05-23) 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.23 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, 10 Jul 2017 05:51:59 -0000 On Sun, Jul 09, 2017 at 11:15:18PM -0300, Otac??lio wrote: > Dears > > I'm the maintainer of xosview and I'm debugging rather weird behavior > from it in the latest FreeBSD 12 revisions (12.0-CURRENT #0 r320730 > AMD64) . The problem is occurring on the lines responsible for > collecting statistics about paging. These lines follow: > > If (pageinfo) { > Pageinfo [0] = (uint64_t) vm.v_vnodepgsin + (uint64_t) vm.v_swappgsin; Why these casts are needed ? What is the type of vm.v_vnodepgsin ? > Pageinfo [1] = (uint64_t) vm.v_vnodepgsout + (uint64_t) vm.v_swappgsout; > } > > This code works on FreeBSD 11 and until a short time ago it works at 12. > But now it returns extremely large values ??????when interpreted as 64-bit > values. A debugging has shown that for this sysctl call the following > values ??????are returned in the terminal: > sysctl vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin > vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout > Vm.stats.vm.v_vnodepgsin: 47432 > Vm.stats.vm.v_swappgsin: 0 > Vm.stats.vm.v_vnodepgsout: 19 > Vm.stats.vm.v_swappgsout: 0 > > While the code returns things like: > > Pageinf [0] = 34359785800; Pageinfo [1] = 140733193388051 > Pageinf [0] = 34359785800; Pageinfo [1] = 2678138638516092947 > > After some tests I found that if I change the code to use a typecast to > (uint32_t) then Xosview works correctly.: > If (pageinfo) { > Pageinfo [0] = (uint32_t) ((uint64_t) vm.v_vnodepgsin + (uint64_t) > vm.v_swappgsin); > Pageinfo [1] = (uint32_t) ((uint64_t) vm.v_vnodepgsout + (uint64_t) > vm.v_swappgsout); > } > > For me, it seems that some code in the kernel is storing values ??????as 32 > bits where it should be 64 bits. Is this behavior correct? Show the _exact_ code fragment that reads the MIBs values. From owner-freebsd-current@freebsd.org Mon Jul 10 07:12:42 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23F2BD9FA1B for ; Mon, 10 Jul 2017 07:12:42 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (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 C89277EBB0 for ; Mon, 10 Jul 2017 07:12:41 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-21-125.dz.commufa.jp [124.18.21.125]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id v6A6elGe030946; Mon, 10 Jul 2017 15:40:47 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 10 Jul 2017 15:40:46 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: otacilio.neto@bsd.com.br Subject: Re: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730 Message-Id: <20170710154046.58c3d7b14a227a20bea3e55b@dec.sakura.ne.jp> In-Reply-To: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> References: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> Organization: Junchoon corps X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 07:12:42 -0000 Hi. Members v_swappgsin and v_vnodepgsin are declared on sys/sys/vmmeter.h as u_int on stable/11@r320798 [1] counter_u64_t on head@r320861 [2] respectively. Diggin in further, on head@r320861, counter_u64_t is typedef'ed as uint64_t * at line 32 of sys/sys/counter.h [3] like below. typedef uint64_t *counter_u64_t; So they're "pointers" on head, while "values" on stable/11. So, as you're on head, it seems you're casting "pointers (addresses)" to uint64_t "value". It could be huge and non-expected values. Your code would work as expected on stable/11. [1] https://svnweb.freebsd.org/base/stable/11/sys/sys/vmmeter.h?annotate=320610 [2] https://svnweb.freebsd.org/base/head/sys/sys/vmmeter.h?annotate=317061 [3] https://svnweb.freebsd.org/base/head/sys/sys/counter.h?annotate=309745 On Sun, 9 Jul 2017 23:15:18 -0300 Otac$B".(Blio wrote: > Dears > > I'm the maintainer of xosview and I'm debugging rather weird behavior > from it in the latest FreeBSD 12 revisions (12.0-CURRENT #0 r320730 > AMD64) . The problem is occurring on the lines responsible for > collecting statistics about paging. These lines follow: > > If (pageinfo) { > Pageinfo [0] = (uint64_t) vm.v_vnodepgsin + (uint64_t) vm.v_swappgsin; > Pageinfo [1] = (uint64_t) vm.v_vnodepgsout + (uint64_t) vm.v_swappgsout; > } > > This code works on FreeBSD 11 and until a short time ago it works at 12. > But now it returns extremely large values $B".".(Bwhen interpreted as 64-bit > values. A debugging has shown that for this sysctl call the following > values $B".".(Bare returned in the terminal: > sysctl vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin > vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout > Vm.stats.vm.v_vnodepgsin: 47432 > Vm.stats.vm.v_swappgsin: 0 > Vm.stats.vm.v_vnodepgsout: 19 > Vm.stats.vm.v_swappgsout: 0 > > While the code returns things like: > > Pageinf [0] = 34359785800; Pageinfo [1] = 140733193388051 > Pageinf [0] = 34359785800; Pageinfo [1] = 2678138638516092947 > > After some tests I found that if I change the code to use a typecast to > (uint32_t) then Xosview works correctly.: > If (pageinfo) { > Pageinfo [0] = (uint32_t) ((uint64_t) vm.v_vnodepgsin + (uint64_t) > vm.v_swappgsin); > Pageinfo [1] = (uint32_t) ((uint64_t) vm.v_vnodepgsout + (uint64_t) > vm.v_swappgsout); > } > > For me, it seems that some code in the kernel is storing values $B".".(Bas 32 > bits where it should be 64 bits. Is this behavior correct? > > []'s > > -Otac$B".(Blio > _______________________________________________ > 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" > > -- Tomoaki AOKI From owner-freebsd-current@freebsd.org Mon Jul 10 07:18:19 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42409D9FC29 for ; Mon, 10 Jul 2017 07:18:19 +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 D89EE7EE75 for ; Mon, 10 Jul 2017 07:18:18 +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 v6A7I74I026613 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Jul 2017 10:18:07 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v6A7I74I026613 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v6A7I7l6026612; Mon, 10 Jul 2017 10:18:07 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 10 Jul 2017 10:18:07 +0300 From: Konstantin Belousov To: Tomoaki AOKI Cc: freebsd-current@freebsd.org, otacilio.neto@bsd.com.br Subject: Re: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730 Message-ID: <20170710071807.GO1935@kib.kiev.ua> References: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> <20170710154046.58c3d7b14a227a20bea3e55b@dec.sakura.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170710154046.58c3d7b14a227a20bea3e55b@dec.sakura.ne.jp> User-Agent: Mutt/1.8.3 (2017-05-23) 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.23 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, 10 Jul 2017 07:18:19 -0000 On Mon, Jul 10, 2017 at 03:40:46PM +0900, Tomoaki AOKI wrote: > Hi. > > Members v_swappgsin and v_vnodepgsin are declared on sys/sys/vmmeter.h > as > > u_int on stable/11@r320798 [1] > counter_u64_t on head@r320861 [2] > > respectively. > > Diggin in further, on head@r320861, counter_u64_t is typedef'ed as > uint64_t * at line 32 of sys/sys/counter.h [3] like below. > > typedef uint64_t *counter_u64_t; > > So they're "pointers" on head, while "values" on stable/11. > > So, as you're on head, it seems you're casting "pointers (addresses)" to > uint64_t "value". It could be huge and non-expected values. > Your code would work as expected on stable/11. What ? counter_u64_t in userspace in nonsense. Whole struct vmmeter is useless in userspace, it is not exported by the sysctls and is only used in kernel. Sysctl MIBs export individual counters which should be used with appropriate type, but besides native uint64_t, 32bit requests are also supported. This is why I asked about the type of the vm.v_something and asked for the explicit fragment of the code which reads the MIBs. > > [1] > https://svnweb.freebsd.org/base/stable/11/sys/sys/vmmeter.h?annotate=320610 > > [2] > https://svnweb.freebsd.org/base/head/sys/sys/vmmeter.h?annotate=317061 > > [3] > https://svnweb.freebsd.org/base/head/sys/sys/counter.h?annotate=309745 > > > On Sun, 9 Jul 2017 23:15:18 -0300 > Otac?$B".lio wrote: > > > Dears > > > > I'm the maintainer of xosview and I'm debugging rather weird behavior > > from it in the latest FreeBSD 12 revisions (12.0-CURRENT #0 r320730 > > AMD64) . The problem is occurring on the lines responsible for > > collecting statistics about paging. These lines follow: > > > > If (pageinfo) { > > Pageinfo [0] = (uint64_t) vm.v_vnodepgsin + (uint64_t) vm.v_swappgsin; > > Pageinfo [1] = (uint64_t) vm.v_vnodepgsout + (uint64_t) vm.v_swappgsout; > > } > > > > This code works on FreeBSD 11 and until a short time ago it works at 12. > > But now it returns extremely large values ?$B".".when interpreted as 64-bit > > values. A debugging has shown that for this sysctl call the following > > values ?$B".".are returned in the terminal: > > sysctl vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin > > vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout > > Vm.stats.vm.v_vnodepgsin: 47432 > > Vm.stats.vm.v_swappgsin: 0 > > Vm.stats.vm.v_vnodepgsout: 19 > > Vm.stats.vm.v_swappgsout: 0 > > > > While the code returns things like: > > > > Pageinf [0] = 34359785800; Pageinfo [1] = 140733193388051 > > Pageinf [0] = 34359785800; Pageinfo [1] = 2678138638516092947 > > > > After some tests I found that if I change the code to use a typecast to > > (uint32_t) then Xosview works correctly.: > > If (pageinfo) { > > Pageinfo [0] = (uint32_t) ((uint64_t) vm.v_vnodepgsin + (uint64_t) > > vm.v_swappgsin); > > Pageinfo [1] = (uint32_t) ((uint64_t) vm.v_vnodepgsout + (uint64_t) > > vm.v_swappgsout); > > } > > > > For me, it seems that some code in the kernel is storing values ?$B".".as 32 > > bits where it should be 64 bits. Is this behavior correct? > > > > []'s > > > > -Otac?$B".lio > > _______________________________________________ > > 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" > > > > > > > -- > Tomoaki AOKI > _______________________________________________ > 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 Jul 10 09:45:35 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CB2EDA2711 for ; Mon, 10 Jul 2017 09:45:35 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (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 5A0C282BFF for ; Mon, 10 Jul 2017 09:45:35 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-21-125.dz.commufa.jp [124.18.21.125]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id v6A9jT9W033161; Mon, 10 Jul 2017 18:45:29 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Mon, 10 Jul 2017 18:45:28 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Cc: Konstantin Belousov , otacilio.neto@bsd.com.br Subject: Re: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730 Message-Id: <20170710184528.8677740bc55681e331c2fbea@dec.sakura.ne.jp> In-Reply-To: <20170710071807.GO1935@kib.kiev.ua> References: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> <20170710154046.58c3d7b14a227a20bea3e55b@dec.sakura.ne.jp> <20170710071807.GO1935@kib.kiev.ua> Organization: Junchoon corps X-Mailer: Sylpheed 3.6.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 09:45:35 -0000 Hm, for example, sysutils/lsof (userspace app) depends on kernel source, and I thought the one Otacilio mentioned is something like it. Anyway, we should wait for Otacilio's response. ;-) On Mon, 10 Jul 2017 10:18:07 +0300 Konstantin Belousov wrote: > On Mon, Jul 10, 2017 at 03:40:46PM +0900, Tomoaki AOKI wrote: > > Hi. > > > > Members v_swappgsin and v_vnodepgsin are declared on sys/sys/vmmeter.h > > as > > > > u_int on stable/11@r320798 [1] > > counter_u64_t on head@r320861 [2] > > > > respectively. > > > > Diggin in further, on head@r320861, counter_u64_t is typedef'ed as > > uint64_t * at line 32 of sys/sys/counter.h [3] like below. > > > > typedef uint64_t *counter_u64_t; > > > > So they're "pointers" on head, while "values" on stable/11. > > > > So, as you're on head, it seems you're casting "pointers (addresses)" to > > uint64_t "value". It could be huge and non-expected values. > > Your code would work as expected on stable/11. > > What ? counter_u64_t in userspace in nonsense. > > Whole struct vmmeter is useless in userspace, it is not exported by the > sysctls and is only used in kernel. Sysctl MIBs export individual > counters which should be used with appropriate type, but besides native > uint64_t, 32bit requests are also supported. > > This is why I asked about the type of the vm.v_something and asked for > the explicit fragment of the code which reads the MIBs. > > > > > [1] > > https://svnweb.freebsd.org/base/stable/11/sys/sys/vmmeter.h?annotate=320610 > > > > [2] > > https://svnweb.freebsd.org/base/head/sys/sys/vmmeter.h?annotate=317061 > > > > [3] > > https://svnweb.freebsd.org/base/head/sys/sys/counter.h?annotate=309745 > > > > > > On Sun, 9 Jul 2017 23:15:18 -0300 > > Otac?$B".lio wrote: > > > > > Dears > > > > > > I'm the maintainer of xosview and I'm debugging rather weird behavior > > > from it in the latest FreeBSD 12 revisions (12.0-CURRENT #0 r320730 > > > AMD64) . The problem is occurring on the lines responsible for > > > collecting statistics about paging. These lines follow: > > > > > > If (pageinfo) { > > > Pageinfo [0] = (uint64_t) vm.v_vnodepgsin + (uint64_t) vm.v_swappgsin; > > > Pageinfo [1] = (uint64_t) vm.v_vnodepgsout + (uint64_t) vm.v_swappgsout; > > > } > > > > > > This code works on FreeBSD 11 and until a short time ago it works at 12. > > > But now it returns extremely large values ?$B".".when interpreted as 64-bit > > > values. A debugging has shown that for this sysctl call the following > > > values ?$B".".are returned in the terminal: > > > sysctl vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin > > > vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout > > > Vm.stats.vm.v_vnodepgsin: 47432 > > > Vm.stats.vm.v_swappgsin: 0 > > > Vm.stats.vm.v_vnodepgsout: 19 > > > Vm.stats.vm.v_swappgsout: 0 > > > > > > While the code returns things like: > > > > > > Pageinf [0] = 34359785800; Pageinfo [1] = 140733193388051 > > > Pageinf [0] = 34359785800; Pageinfo [1] = 2678138638516092947 > > > > > > After some tests I found that if I change the code to use a typecast to > > > (uint32_t) then Xosview works correctly.: > > > If (pageinfo) { > > > Pageinfo [0] = (uint32_t) ((uint64_t) vm.v_vnodepgsin + (uint64_t) > > > vm.v_swappgsin); > > > Pageinfo [1] = (uint32_t) ((uint64_t) vm.v_vnodepgsout + (uint64_t) > > > vm.v_swappgsout); > > > } > > > > > > For me, it seems that some code in the kernel is storing values ?$B".".as 32 > > > bits where it should be 64 bits. Is this behavior correct? > > > > > > []'s > > > > > > -Otac?$B".lio > > > _______________________________________________ > > > 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" > > > > > > > > > > > > -- > > Tomoaki AOKI > > _______________________________________________ > > 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" > _______________________________________________ > 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" > -- Tomoaki AOKI From owner-freebsd-current@freebsd.org Mon Jul 10 09:49:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EF98DA2875 for ; Mon, 10 Jul 2017 09:49:33 +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 04ACC82DA3 for ; Mon, 10 Jul 2017 09:49:32 +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 v6A9nM8C060106 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Jul 2017 12:49:23 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v6A9nM8C060106 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v6A9nMAq060105; Mon, 10 Jul 2017 12:49:22 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 10 Jul 2017 12:49:22 +0300 From: Konstantin Belousov To: Tomoaki AOKI Cc: freebsd-current@freebsd.org, otacilio.neto@bsd.com.br Subject: Re: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730 Message-ID: <20170710094922.GQ1935@kib.kiev.ua> References: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> <20170710154046.58c3d7b14a227a20bea3e55b@dec.sakura.ne.jp> <20170710071807.GO1935@kib.kiev.ua> <20170710184528.8677740bc55681e331c2fbea@dec.sakura.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170710184528.8677740bc55681e331c2fbea@dec.sakura.ne.jp> User-Agent: Mutt/1.8.3 (2017-05-23) 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.23 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, 10 Jul 2017 09:49:33 -0000 On Mon, Jul 10, 2017 at 06:45:28PM +0900, Tomoaki AOKI wrote: > Hm, for example, sysutils/lsof (userspace app) depends on kernel > source, and I thought the one Otacilio mentioned is something like it. lsof purpose is to dig into a kernel memory to gather information about the process state and opened files. To do this, lsof authors have to use internal kernel data structures. The library which is discussed in the thread uses public interfaces, but then tries to pack the returned data into internal kernel structure. If this is true, then the breakage is on the library side. From owner-freebsd-current@freebsd.org Mon Jul 10 11:51:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8DD1DA4A51 for ; Mon, 10 Jul 2017 11:51:16 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id C2697135A for ; Mon, 10 Jul 2017 11:51:16 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id C1C61DA4A4F; Mon, 10 Jul 2017 11:51:16 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C16DEDA4A4D for ; Mon, 10 Jul 2017 11:51:16 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.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 75A751359 for ; Mon, 10 Jul 2017 11:51:15 +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 v6ABp9NY019739 for ; Mon, 10 Jul 2017 11:51:09 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v6ABp90C019738 for current@freebsd.org; Mon, 10 Jul 2017 04:51:09 -0700 (PDT) (envelope-from david) Date: Mon, 10 Jul 2017 04:51:09 -0700 From: David Wolfskill To: current@freebsd.org Subject: Panic on boot after upgrade from r320827 -> r320869 Message-ID: <20170710115109.GD1177@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="dZH1BijwiAv2CwKz" Content-Disposition: inline User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 11:51:16 -0000 --dZH1BijwiAv2CwKz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Pnic occurred prior to mounting file systems; I was able to boot =66rom the r320827 (as "kernel.old") OK. I was not able to get a dump. Both the laptop and the build machine panicked, but the build machine's keyboard was unresponsive and its serial console isn't funtioning at the moment (because of unrelated issues involving the machine to which said console is connected). The laptop doesn't have a serial console, but its keyboard was working. I grabbed a few screenshots; for the build machine, there's just the one, but for the laptop, I managed to get a backtrace and 6 screenshots (including the backtrace). Please see for the screenshots: Index of /~david/FreeBSD/head/r320869 Icon Name Last modified Size Description[PARENTDIR] Parent Directory - =20 [IMG] freebeast_1.jpg 2017-07-10 11:36 260K =20 [IMG] laptop_1.jpg 2017-07-10 11:36 253K =20 [IMG] laptop_2.jpg 2017-07-10 11:36 242K =20 [IMG] laptop_3.jpg 2017-07-10 11:36 259K =20 [IMG] laptop_4.jpg 2017-07-10 11:36 245K =20 [IMG] laptop_5.jpg 2017-07-10 11:36 158K =20 [IMG] laptop_6.jpg 2017-07-10 11:36 140K =20 Also, I have links to yesterday's verbose dmesg.boot files for each machine at . I'm happy to experiment.... Peace, david --=20 David H. Wolfskill david@catwhisker.org POTUS impeachment requires Congress buy-in. First, fix Congress, THEN impe= ach. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --dZH1BijwiAv2CwKz Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZY2otXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XNvQIAMOxO+UjuLJdq2Z5vMS2+Qa/ 4j2u80Mkr/fDFzguY/cv7cYpEmdGg5IIFeGBfvfJ0pPMf/C/bXVDosMVHmi1+DTg frKz0OWdj2pPFGOQtEo3Blxdf+TTF06iv/jEqhydFytNCC9DwK2uqmoTXtL+dG8q vvql4TjDlTIdyS9+tf7D/t/fyLkTqRNY7bkSHn4gBRQ+7N3AK4T/KiSBXmUO/4XL SS2oZVMjX2FfVpwflHaZHOqRiFUQWSfTz9K73fmE55jSAQzDnYUsKSaNlsUO9/50 YJpjzwAw76CBH6WOe26Koh1CUXm/SlOEUO8XHDB3jy8scxlTMr9rH1fptCrvjwY= =9Ibs -----END PGP SIGNATURE----- --dZH1BijwiAv2CwKz-- From owner-freebsd-current@freebsd.org Mon Jul 10 13:51:50 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A477FDA8D5D for ; Mon, 10 Jul 2017 13:51:50 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6413365766 for ; Mon, 10 Jul 2017 13:51:49 +0000 (UTC) (envelope-from otacilio.neto@bsd.com.br) Received: by mail-qk0-x231.google.com with SMTP id 16so73834666qkg.2 for ; Mon, 10 Jul 2017 06:51:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=3LaFIACulUqP+Gk5+tayOIIBBadB6xL6S/vSBUV3wK0=; b=ckqZ0BF/J5+Gf+tyAmxFt0M4dONuzZ3SAy1wKudhYN20FEVGTCiE5UYjYUHgJh4LTS Ii35cw1hq37XPuuX5Oqwdk5bCksWQUH48kEFVwMYzQ7nLQGTqvuw/7spxYumBm6WWuOb ysWuDFBcJk977pDEwy0MMbKxJCm9upj5afgiY= 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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=3LaFIACulUqP+Gk5+tayOIIBBadB6xL6S/vSBUV3wK0=; b=sZQOP4+rCAdjKyuUVHDv8LRaSISx5S6jWEAhVBfy/1bJ/dbEj5GxJ+IV+ToRs9EM1j JL8C6LEYDywdCuXq+AdN6JszvQrpjfNYFGSlxprhs+6VVuiK10uZQb8//Cd7fHHFVjHd igkqM5PUlX/qq8Y7Q6Mg3aM/iuLJXDp9mPDFNhvakFF3DcwCy2RKyV9ur+sIjYTeyXzF MIf92NX9l9bpb0ss2LmbCm+ubbJzg17MjY98JaS4CSD0eLfGj4TONertRfCvuS5UrrCX chjCHRFL8FLyZtiLwZYZu9y2VQUyfu+f3+Ra6PIV8qF10ltX5H+0ZW6QZawbV0TmFZac avag== X-Gm-Message-State: AIVw112MLNBYdDuq5P4pMhtLrcbZ7xCXYj2ILoJhcoyVEYZwV3/iTd1c fSB5yQFVfLQdYaSu+I0= X-Received: by 10.55.19.13 with SMTP id d13mr3927291qkh.214.1499694708593; Mon, 10 Jul 2017 06:51:48 -0700 (PDT) Received: from [10.51.223.89] ([177.20.152.129]) by smtp.googlemail.com with ESMTPSA id j17sm8772907qta.49.2017.07.10.06.51.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Jul 2017 06:51:47 -0700 (PDT) Subject: Re: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730 To: Konstantin Belousov , Tomoaki AOKI References: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> <20170710154046.58c3d7b14a227a20bea3e55b@dec.sakura.ne.jp> <20170710071807.GO1935@kib.kiev.ua> <20170710184528.8677740bc55681e331c2fbea@dec.sakura.ne.jp> <20170710094922.GQ1935@kib.kiev.ua> Cc: freebsd-current@freebsd.org From: =?UTF-8?B?T3RhY8OtbGlv?= Message-ID: Date: Mon, 10 Jul 2017 10:51:43 -0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170710094922.GQ1935@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 13:51:50 -0000 Em 10/07/2017 06:49, Konstantin Belousov escreveu: > On Mon, Jul 10, 2017 at 06:45:28PM +0900, Tomoaki AOKI wrote: >> Hm, for example, sysutils/lsof (userspace app) depends on kernel >> source, and I thought the one Otacilio mentioned is something like it. > lsof purpose is to dig into a kernel memory to gather information about > the process state and opened files. To do this, lsof authors have to use > internal kernel data structures. > > The library which is discussed in the thread uses public interfaces, > but then tries to pack the returned data into internal kernel structure. > If this is true, then the breakage is on the library side. Hello This following simple program behaves in the same manner that xosview. It shows corrects answers for pages_in and pages_out on FreeBSD 11 amd64 and FreeBSD10.3 i386. On FreeBSD 12 r320730 it shows the error answer that I related previously. If the lines pageinfo[0] = (uint64_t)vm.v_vnodepgsin + (uint64_t)vm.v_swappgsin; pageinfo[1] = (uint64_t)vm.v_vnodepgsout + (uint64_t)vm.v_swappgsout; are patched to pageinfo[0] = (uint32_t)((uint64_t)vm.v_vnodepgsin + (uint64_t)vm.v_swappgsin); pageinfo[1] = (uint32_t)((uint64_t)vm.v_vnodepgsout + (uint64_t)vm.v_swappgsout); The program works on all FreeBSD version. My doubt is why now this type cast (uint32_t) is necessary? []'s -Otacilio #include #include #include #define _WANT_VMMETER #include /* meminfo[5] = { active, inactive, wired, cached, free } */ /* pageinfo[2] = { pages_in, pages_out } */ void BSDGetPageStats(uint64_t *meminfo, uint64_t *pageinfo) { struct vmmeter vm; size_t size = sizeof(unsigned int); #define GET_VM_STATS(name) sysctlbyname("vm.stats.vm." #name, &vm.name, &size, NULL, 0) GET_VM_STATS(v_active_count); GET_VM_STATS(v_inactive_count); GET_VM_STATS(v_wire_count); GET_VM_STATS(v_free_count); GET_VM_STATS(v_page_size); GET_VM_STATS(v_vnodepgsin); GET_VM_STATS(v_vnodepgsout); GET_VM_STATS(v_swappgsin); GET_VM_STATS(v_swappgsout); if (meminfo) { meminfo[0] = (uint64_t)vm.v_active_count * vm.v_page_size; meminfo[1] = (uint64_t)vm.v_inactive_count * vm.v_page_size; meminfo[2] = (uint64_t)vm.v_wire_count * vm.v_page_size; meminfo[4] = (uint64_t)vm.v_free_count * vm.v_page_size; } if (pageinfo) { pageinfo[0] = (uint64_t)vm.v_vnodepgsin + (uint64_t)vm.v_swappgsin; pageinfo[1] = (uint64_t)vm.v_vnodepgsout + (uint64_t)vm.v_swappgsout; } } int main(int argc, char **argv){ uint64_t meminfo[5]; uint64_t pageinfo[2]; BSDGetPageStats(meminfo, pageinfo); printf("active memory = %lu bytes\n", meminfo[0]); printf("inactive memory = %lu bytes\n", meminfo[1]); printf("wired memory = %lu bytes\n", meminfo[2]); printf("cached memory = %lu bytes\n", meminfo[3]); printf("free memory = %lu bytes\n", meminfo[4]); printf("\npages_in = %lu bytes\n", pageinfo[0]); printf("pages_out = %lu bytes\n", pageinfo[1]); return 0; } From owner-freebsd-current@freebsd.org Mon Jul 10 14:12:53 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97CE2DA94A9 for ; Mon, 10 Jul 2017 14:12:53 +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 2555866351 for ; Mon, 10 Jul 2017 14:12:52 +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 v6AECbfZ018599 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Jul 2017 17:12:37 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v6AECbfZ018599 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v6AECbJK018598; Mon, 10 Jul 2017 17:12:37 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 10 Jul 2017 17:12:37 +0300 From: Konstantin Belousov To: Otac??lio Cc: Tomoaki AOKI , freebsd-current@freebsd.org Subject: Re: type of vm.stats.vm.v_vnodepgsin vm.stats.vm.v_swappgsin, vm.stats.vm.v_vnodepgsout vm.stats.vm.v_swappgsout on AMD64 r320730 Message-ID: <20170710141237.GS1935@kib.kiev.ua> References: <1c37db96-7cd2-91c9-011c-967a32a97f05@bsd.com.br> <20170710154046.58c3d7b14a227a20bea3e55b@dec.sakura.ne.jp> <20170710071807.GO1935@kib.kiev.ua> <20170710184528.8677740bc55681e331c2fbea@dec.sakura.ne.jp> <20170710094922.GQ1935@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-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.23 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, 10 Jul 2017 14:12:53 -0000 On Mon, Jul 10, 2017 at 10:51:43AM -0300, Otac??lio wrote: > Em 10/07/2017 06:49, Konstantin Belousov escreveu: > > On Mon, Jul 10, 2017 at 06:45:28PM +0900, Tomoaki AOKI wrote: > >> Hm, for example, sysutils/lsof (userspace app) depends on kernel > >> source, and I thought the one Otacilio mentioned is something like it. > > lsof purpose is to dig into a kernel memory to gather information about > > the process state and opened files. To do this, lsof authors have to use > > internal kernel data structures. > > > > The library which is discussed in the thread uses public interfaces, > > but then tries to pack the returned data into internal kernel structure. > > If this is true, then the breakage is on the library side. > > Hello > > This following simple program behaves in the same manner that xosview. > It shows corrects answers for pages_in and pages_out on FreeBSD 11 amd64 > and FreeBSD10.3 i386. On FreeBSD 12 r320730 it shows the error answer > that I related previously. If the lines > > pageinfo[0] = (uint64_t)vm.v_vnodepgsin + (uint64_t)vm.v_swappgsin; > pageinfo[1] = (uint64_t)vm.v_vnodepgsout + (uint64_t)vm.v_swappgsout; > > are patched to > > pageinfo[0] = (uint32_t)((uint64_t)vm.v_vnodepgsin + > (uint64_t)vm.v_swappgsin); > pageinfo[1] = (uint32_t)((uint64_t)vm.v_vnodepgsout + > (uint64_t)vm.v_swappgsout); > > The program works on all FreeBSD version. My doubt is why now this type > cast (uint32_t) is necessary? > > []'s > > -Otacilio > > #include > #include > #include > > #define _WANT_VMMETER > > #include > > /* meminfo[5] = { active, inactive, wired, cached, free } */ > /* pageinfo[2] = { pages_in, pages_out } */ > void BSDGetPageStats(uint64_t *meminfo, uint64_t *pageinfo) { > struct vmmeter vm; > size_t size = sizeof(unsigned int); > #define GET_VM_STATS(name) sysctlbyname("vm.stats.vm." #name, > &vm.name, &size, NULL, 0) Use of struct vmmeter is wrong, as discussed. The structure is for kernel internal interfaces. The behaviour changed because the structure member was of type uint32_t but become a pointer. You initialize the size of the storage to receive MIB value to sizeof(int), which leaves half of the pointer storage not filled. Stop using vmmeter, use correct types for the MIBs values, and pass correct size to sysctl(3) call. > GET_VM_STATS(v_active_count); > GET_VM_STATS(v_inactive_count); > GET_VM_STATS(v_wire_count); > GET_VM_STATS(v_free_count); > GET_VM_STATS(v_page_size); > GET_VM_STATS(v_vnodepgsin); > GET_VM_STATS(v_vnodepgsout); > GET_VM_STATS(v_swappgsin); > GET_VM_STATS(v_swappgsout); > > if (meminfo) { > meminfo[0] = (uint64_t)vm.v_active_count * vm.v_page_size; > meminfo[1] = (uint64_t)vm.v_inactive_count * vm.v_page_size; > meminfo[2] = (uint64_t)vm.v_wire_count * vm.v_page_size; > meminfo[4] = (uint64_t)vm.v_free_count * vm.v_page_size; > } > if (pageinfo) { > pageinfo[0] = (uint64_t)vm.v_vnodepgsin + (uint64_t)vm.v_swappgsin; > pageinfo[1] = (uint64_t)vm.v_vnodepgsout + > (uint64_t)vm.v_swappgsout; > } > } > > int main(int argc, char **argv){ > uint64_t meminfo[5]; > uint64_t pageinfo[2]; > > BSDGetPageStats(meminfo, pageinfo); > > printf("active memory = %lu bytes\n", meminfo[0]); > printf("inactive memory = %lu bytes\n", meminfo[1]); > printf("wired memory = %lu bytes\n", meminfo[2]); > printf("cached memory = %lu bytes\n", meminfo[3]); > printf("free memory = %lu bytes\n", meminfo[4]); > > printf("\npages_in = %lu bytes\n", pageinfo[0]); > printf("pages_out = %lu bytes\n", pageinfo[1]); > return 0; > } From owner-freebsd-current@freebsd.org Mon Jul 10 18:06:03 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C451DADA5F for ; Mon, 10 Jul 2017 18:06:03 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC48D71EBA for ; Mon, 10 Jul 2017 18:06:02 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [192.168.1.10] (unknown [192.168.1.10]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 679B41360B for ; Mon, 10 Jul 2017 18:05:55 +0000 (UTC) Subject: Re: [SOLVED] [memstick install] auto-zfs error To: freebsd-current@freebsd.org References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> From: Allan Jude Message-ID: Date: Mon, 10 Jul 2017 14:05:49 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MP8J3Qu1l1gxboNx9nxstkn6LkVu6WFRj" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 18:06:03 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MP8J3Qu1l1gxboNx9nxstkn6LkVu6WFRj Content-Type: multipart/mixed; boundary="k8f8xqGbQJTR8MBtHEGh8jEoubTg1e1jj"; protected-headers="v1" From: Allan Jude To: freebsd-current@freebsd.org Message-ID: Subject: Re: [SOLVED] [memstick install] auto-zfs error References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> In-Reply-To: --k8f8xqGbQJTR8MBtHEGh8jEoubTg1e1jj Content-Type: text/plain; charset=utf-8 Content-Language: en-CA Content-Transfer-Encoding: quoted-printable On 2017-07-09 14:40, Boris Samorodov wrote: > 08.07.2017 18:56, Boris Samorodov =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> Hi All, >> >> I tied to install a new FreeBSD-amd-12 system from official USB >> installation memstick.img. Auto-UFS (GPT) installs fine and the system= >> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >> At the very beginning it gives something like "gpt sector XXXX error, >> gpt sector 1 error, can't find zroot..." >> >> Is it a known error / should I give more (precise) errors? >> >> I tried two recent images with the same result: >> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12= =2E0-CURRENT-amd64-20170703-r320599-memstick.img >> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12= =2E0-CURRENT-amd64-20170626-r320360-memstick.img >=20 > It turned out GPT and zfs are not usable at this machine. > MBR / ZFS works fine. >=20 > I'll stick with that. >=20 What type of machine is it? --=20 Allan Jude --k8f8xqGbQJTR8MBtHEGh8jEoubTg1e1jj-- --MP8J3Qu1l1gxboNx9nxstkn6LkVu6WFRj 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.0.16 (MingW32) iQIcBAEBAgAGBQJZY8IAAAoJEBmVNT4SmAt+LosQAIQUyPVdWoh2d3J3ODYycnww FEW03+1ViY6S8fk/fWcuekGE2gReAwUB/lTKQZsFZTY827qmj6KRtdmS7JVQe9+L pG0WAF2GGzHO5wh+HVaIzpdII9aUaza7ws62vm/wlUgt9d+1rk/OJ/ahjbAVPfOf lJFJrH2jrKhIP/1iwD9VuIQ6HOYOciNUDddC9ZqM0ufA+yEWzoqJ6685zWk43QnH CHnfJLXw3QIVgOBeIzcqyTUQEXE3+PU0vr0i0PWYfE3pXQ2FYQH1Ik0jRyrt40DY ZP+2Y56MzXq1rmzHcTiWhjQmEAvHKQYGJlzzMvTBjUQOsJ6jJRIFcaRvzQWG122q UHzE30lN4oYuYdiBuNrsEFlFuvmNtZ61fR7jp6qqBzyLsETOAS/2ArNCtzekktcE TWSCnjq6bZE0XBSNUzo3Jfmhseeygc37Pn/067ZIvZpLitkLnwa8VGbsxVLUi1Dg UkRDC8R2euj3XTB2FOkoHmtpxRU2gFh6UOEUV9oHKVP7MZyFL7TWnH1RmQ2bp+Qo OSYiDCEoWut4GoIoT0UgKBVQM79SOPqH3wZhy/bY0JFa6n5LNVPLMBjzXF6Dkb1J Q3y9bO2XrqXJsfWb4sduERUk0W8YlHOrYXQJ9z+RSOq/e0ll/8oS5ooQux5ZZw4C 48A4IsS3coiRvTeg3B2O =l/x2 -----END PGP SIGNATURE----- --MP8J3Qu1l1gxboNx9nxstkn6LkVu6WFRj-- From owner-freebsd-current@freebsd.org Mon Jul 10 18:25:12 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C114DAE2A5 for ; Mon, 10 Jul 2017 18:25:12 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward4h.cmail.yandex.net (forward4h.cmail.yandex.net [87.250.230.101]) (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 CC69872BAA for ; Mon, 10 Jul 2017 18:25:11 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp2j.mail.yandex.net (smtp2j.mail.yandex.net [95.108.130.60]) by forward4h.cmail.yandex.net (Yandex) with ESMTP id B1C9920B06 for ; Mon, 10 Jul 2017 21:25:01 +0300 (MSK) Received: from smtp2j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2j.mail.yandex.net (Yandex) with ESMTP id 944313EC0D20 for ; Mon, 10 Jul 2017 21:25:01 +0300 (MSK) Received: by smtp2j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id mJY39P8UVQ-P0t0ET48; Mon, 10 Jul 2017 21:25:00 +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=passap.ru; s=mail; t=1499711100; bh=lO079sBiMgXuH06ORcDmY1JyAIBei2GKOQIoNtDCM9A=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=lp7pvYr/qHhnA78cO1XADNefxvCzyFj0C8n/e7mKu6iPRnS5tzd2fB2JRsrEBFONi tSP/y1/kK88liXRzjOhphggmqx+6YO/xLsTxpFTaXKryEDlcSk2qHIzYuDdSZ512zJ Cfeyc2DdSpo682I7BlbtLbk5B/Z4m4qdXv3CMSO8= Authentication-Results: smtp2j.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0 Subject: Re: [SOLVED] [memstick install] auto-zfs error To: freebsd-current@freebsd.org References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> From: Boris Samorodov Message-ID: Date: Mon, 10 Jul 2017 21:24:59 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="MS1ELT9NvUCcxSpVJOE7LTVl6ojMxjbHe" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 18:25:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MS1ELT9NvUCcxSpVJOE7LTVl6ojMxjbHe Content-Type: multipart/mixed; boundary="h8i25bU8UwNCtklkNCn1p6LT84t32qgjT"; protected-headers="v1" From: Boris Samorodov To: freebsd-current@freebsd.org Message-ID: Subject: Re: [SOLVED] [memstick install] auto-zfs error References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> In-Reply-To: --h8i25bU8UwNCtklkNCn1p6LT84t32qgjT Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU Content-Transfer-Encoding: quoted-printable 10.07.2017 21:05, Allan Jude =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > On 2017-07-09 14:40, Boris Samorodov wrote: >> 08.07.2017 18:56, Boris Samorodov =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>> Hi All, >>> >>> I tied to install a new FreeBSD-amd-12 system from official USB >>> installation memstick.img. Auto-UFS (GPT) installs fine and the syste= m >>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>> At the very beginning it gives something like "gpt sector XXXX error,= >>> gpt sector 1 error, can't find zroot..." >>> >>> Is it a known error / should I give more (precise) errors? >>> >>> I tried two recent images with the same result: >>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-1= 2.0-CURRENT-amd64-20170703-r320599-memstick.img >>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-1= 2.0-CURRENT-amd64-20170626-r320360-memstick.img >> >> It turned out GPT and zfs are not usable at this machine. >> MBR / ZFS works fine. >> >> I'll stick with that. >=20 > What type of machine is it? It's a PC circa 2009 with MB ASUS P5QL/EPU: --- CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz K8-class CPU) Origin=3D"GenuineIntel" Id=3D0x1067a Family=3D0x6 Model=3D0x17 Step= ping=3D10 Features=3D0xbfebfbff Features2=3D0xc08e3bd AMD Features=3D0x20100800 AMD Features2=3D0x1 VT-x: HLT,PAUSE TSC: P-state invariant, performance statistics real memory =3D 4294967296 (4096 MB) avail memory =3D 3324891136 (3170 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) --- --=20 WBR, bsam --h8i25bU8UwNCtklkNCn1p6LT84t32qgjT-- --MS1ELT9NvUCcxSpVJOE7LTVl6ojMxjbHe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEiEg2cjwbwCvqC1Z0lg4gsDo/bSgFAlljxnwACgkQlg4gsDo/ bShynA/8DRX59SZJ54IgrA7jwgMDXVt+ZCsOUAxfBTPlvhpHDmSncs/jDIgPcv7W 3YZ6Vf5PXd5RziTgjXmN4Hom+uMIlVNmGr7Oh5pKXvZSfrzdP14GB6vhjsRN6DTc WOoXgPZCV8lqZtFrl3BbRbIvyVZHeRhqhnazgqi5KsD2Sw8nmgNTCbwI08qxeKo+ DKg++aiujlJiD06FGKvsLuWp8aBSDTAeHkz01+TZdL+F9WJkikvwY2Brr4giRBhN 2s3QLwcZLK2jY2Y0+F3AxbgG58sgSDEvrhlBBGCV69M+FOjt85QSpqsjW5+eTdCD cZewLVxxAcagbsPfCPD6Yq7Gs4WKKstXS2bZu11I3FVn603t4+ChN8Wcx0hmVYgr 9a/m0hUJplHlDt4wFhpsEraprFCEcdMaIiTCkkOwyjIzSWB8LkTXWwMHTzw/bcd1 Np9MUnYZQcRbj8i0Eqt3dakHE+Yz+GjLXPZ2/1n2Pbx4uU0rGhV/cU5plHEJxAtG s7P+8qb8Z6BpleYAtsWm2/ouGyzVLj8EiQO51yE4P441bghoDyQLUsMCMRa/AAs8 Sgv5oNcZmzdJgS8b2ShNUrYySFCtbu5FhmygGOBWtri3QXKi8T+kJBtrzAXZn8h2 5QuIW7TBMwtQ91cPj5qdVuaNouO76qV9U10KW9cxau7hIzVv+x8= =8kY4 -----END PGP SIGNATURE----- --MS1ELT9NvUCcxSpVJOE7LTVl6ojMxjbHe-- From owner-freebsd-current@freebsd.org Mon Jul 10 18:49:09 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DFA6DAE85F for ; Mon, 10 Jul 2017 18:49:09 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0D8B173C42 for ; Mon, 10 Jul 2017 18:49:09 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: by mailman.ysv.freebsd.org (Postfix) id 08C2FDAE85E; Mon, 10 Jul 2017 18:49:09 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 085E2DAE85D for ; Mon, 10 Jul 2017 18:49:09 +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 795A673C41 for ; Mon, 10 Jul 2017 18:49:07 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.179.232.149]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MTfZc-1d4CwA0GPI-00QV4U; Mon, 10 Jul 2017 20:48:54 +0200 Date: Mon, 10 Jul 2017 20:48:45 +0200 From: "O. Hartmann" To: David Wolfskill Cc: current@freebsd.org Subject: Re: Panic on boot after upgrade from r320827 -> r320869 Message-ID: <20170710204845.1daa4beb@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170710115109.GD1177@albert.catwhisker.org> References: <20170710115109.GD1177@albert.catwhisker.org> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/znkbnDwBH3_PqceIeJXoGeR"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:ftsok1bq4XMe8SS4xXffJfZ9z5RQwfn+XELbEH0754LeOx0pWGE FTV+3fT+g6VLNmXY4UeBNnbSaXWrFUS1y5YXzuxDuq/4DyWW3C+XLZcDGpFPwcx7KfxPTpz v0BIUxXrT/xjbmeUG7iX4XgJCdMTZFC7Fv2InBGuEg3cz8dwm8HF3hDfwmpQZUPbKQxQKDH Bri1hLxtM7u98sidVaMsA== X-UI-Out-Filterresults: notjunk:1;V01:K0:tX5layn0Ul4=:0AUm0CKFFJhhZAkqjWERZN MM5wVq57MK5cPei1p38EVwUur44B8NCDW8X28f1dQoHRWWxw5Ikr9Ps5Id+eXsxSrBUrheBEN mPb3a7+v9Ka6xsVMcunn45PlnO/h59UCz0kvJ/SG7y2W8S3JxZqvETnGCZJyjkczuR1Y6BU1R jFYlPzpgL3Xh011mbLQTY9cglbu7+c/jVz8Vlaff2vx1XIGnUY2wTzk0vK6BgZOTRpmL4t0Mq d0im4pSEvd7SHl1102GGmooSWHFG/EyVLHozDoP44RuqtYisPGOJ2Oc0itpUGFP+L4i6Qoo7T jKUWmLRWUcgsEm6Zdka6iL5O00moFqqT3jbJbB5gOj8QYeT9BhWkFjM9oHbyZ+1Ws4LUyVFCt grYMJXmJJIYW+IjTN/llq2GQtHIQXgb8WpSBv/uFCWGYiE+B3ZG0HUjAumIF17CygB7OXVDGU Mc95pNTFinyIAYXvP84vWcvKev9osa8IiBYduLHzHvaW7p3z65AWz7GDjwVzidb3jVJSa5MOy 8XLdWQqpNR9kiReyXbB/b5dtHQtjgN5Nat3Sp9Hkyf7xqOVPT8i+XIOqIIcibX2OajJ1vAIIP Fs/PIZkyoZJckTY+OzHq0onm4+liUS4PuE4TMOWF/dDNDJqP6r7Ywh36mSWADMnuifOsWU+jZ /bL75EGP65XF+rcBN0E2O1VBibbifLMssGfBBP9IlPlvVJABneX/UemSJA31GMr45Ob73MBTa /fIBYvx7d/7Y3ZXH7LqPD3zRaAMzdkKGrgdH8Wyg6+GpNr3W40KSmXVd1eM= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 18:49:09 -0000 --Sig_/znkbnDwBH3_PqceIeJXoGeR Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 10 Jul 2017 04:51:09 -0700 David Wolfskill schrieb: > Pnic occurred prior to mounting file systems; I was able to boot > from the r320827 (as "kernel.old") OK. I was not able to get a > dump. Both the laptop and the build machine panicked, but the build > machine's keyboard was unresponsive and its serial console isn't > funtioning at the moment (because of unrelated issues involving the > machine to which said console is connected). >=20 > The laptop doesn't have a serial console, but its keyboard was working. >=20 > I grabbed a few screenshots; for the build machine, there's just the > one, but for the laptop, I managed to get a backtrace and 6 screenshots > (including the backtrace). >=20 > Please see for > the screenshots: >=20 > Index of /~david/FreeBSD/head/r320869 >=20 > Icon Name Last modified Size > Description[PARENTDIR] Parent Directory - =20 > [IMG] freebeast_1.jpg 2017-07-10 11:36 260K =20 > [IMG] laptop_1.jpg 2017-07-10 11:36 253K =20 > [IMG] laptop_2.jpg 2017-07-10 11:36 242K =20 > [IMG] laptop_3.jpg 2017-07-10 11:36 259K =20 > [IMG] laptop_4.jpg 2017-07-10 11:36 245K =20 > [IMG] laptop_5.jpg 2017-07-10 11:36 158K =20 > [IMG] laptop_6.jpg 2017-07-10 11:36 140K =20 >=20 >=20 > Also, I have links to yesterday's verbose dmesg.boot files for each > machine at . >=20 > I'm happy to experiment.... >=20 > Peace, > david Hello David. I had the same with r320873. Either my box (a SSD/UFS2-off booting server r= unning CURRENT) ended up in a immediate panic and rebooted or it is stuck at=20 [...] mountroot: Waiting for device /dev/gpt/root ... Mounting from ufs:/dev/gpt/root failed with error 19 mountroot >: ? List of GEOM managed disk devices mountroot >: [...] I went back to r320843 as I identified r320844 to be the culprit in my case. I regret having not more information ... Kind regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/znkbnDwBH3_PqceIeJXoGeR Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWWPMDQAKCRDS528fyFhY lG1eAf0WHw6ZwM7Jf+vVYif8BhypjR0faKfBVa1Z7SYISHAJ7EFk3Xi8yb0O0H3F AqwjxU90Vz5RCZMDqZZ1/DIve0twAf9b2yjIkrxz4ft50qHCzQ3WfLFKYKM8JBdx EjIJX438QgC6Cx26kRmaFAeGgibgdBIeci+VY6ywuyPR8sywXb09 =9ZII -----END PGP SIGNATURE----- --Sig_/znkbnDwBH3_PqceIeJXoGeR-- From owner-freebsd-current@freebsd.org Mon Jul 10 19:53:27 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E68FDAFB36 for ; Mon, 10 Jul 2017 19:53:27 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward5o.cmail.yandex.net (forward5o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::28a]) (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 A3FB275ED0 for ; Mon, 10 Jul 2017 19:53:26 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [77.88.29.85]) by forward5o.cmail.yandex.net (Yandex) with ESMTP id 543DA206FA; Mon, 10 Jul 2017 22:53:14 +0300 (MSK) Received: from smtp2p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2p.mail.yandex.net (Yandex) with ESMTP id 2DCFA1A80086; Mon, 10 Jul 2017 22:53:12 +0300 (MSK) Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id XU99hzlwUH-rCs4V6T8; Mon, 10 Jul 2017 22:53:12 +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=passap.ru; s=mail; t=1499716392; bh=aMaaDWrI6lTu/vjMxlHtfxU4e/lIBGhXDMBSxJWG4H0=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=eFZwgw8S5q8AbFA+kl/tFvmTvMLFW07NHjh6s4GzliiZFz+XWDxKwKmTBE1mQ/w4X yuymY2HXfFgkpGm964BcuOop4RUcgQe7LXSCfHePurYh9jeQzQWjxR8wFhG/19sXEW aw6ZSoaWS8krqBYrPR3ZENMSByW/g6T8WArrlwpE= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: [SOLVED] [memstick install] auto-zfs error To: Toomas Soome Cc: freebsd-current@freebsd.org References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> From: Boris Samorodov Message-ID: Date: Mon, 10 Jul 2017 22:53:11 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> 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.23 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, 10 Jul 2017 19:53:27 -0000 10.07.2017 22:21, Toomas Soome пишет: > >> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >> >> 10.07.2017 21:05, Allan Jude пишет: >>> On 2017-07-09 14:40, Boris Samorodov wrote: >>>> 08.07.2017 18:56, Boris Samorodov пишет: >>>>> Hi All, >>>>> >>>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>>> installation memstick.img. Auto-UFS (GPT) installs fine and the system >>>>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>>>> At the very beginning it gives something like "gpt sector XXXX error, >>>>> gpt sector 1 error, can't find zroot..." >>>>> >>>>> Is it a known error / should I give more (precise) errors? >>>>> >>>>> I tried two recent images with the same result: >>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img >>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img >>>> >>>> It turned out GPT and zfs are not usable at this machine. >>>> MBR / ZFS works fine. >>>> >>>> I'll stick with that. >>> >>> What type of machine is it? >> >> It's a PC circa 2009 with MB ASUS P5QL/EPU: >> --- >> CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz >> K8-class CPU) >> Origin="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 >> >> >> Features=0xbfebfbff >> >> >> >> Features2=0xc08e3bd >> >> AMD Features=0x20100800 >> AMD Features2=0x1 >> VT-x: HLT,PAUSE >> TSC: P-state invariant, performance statistics >> real memory = 4294967296 (4096 MB) >> avail memory = 3324891136 (3170 MB) >> Event timer "LAPIC" quality 100 >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> FreeBSD/SMP: 1 package(s) x 2 core(s) >> --- >> >> -- >> WBR, bsam > > Of course it really can not be that the BIOS has something against combination of GPT+ZFS, but this combination may trigger some sort of bug/misbehavior. I have seen some pretty weird issues and have work in process to have a bit more fool proof approach, but I haven't had time yet to finalize it properly. Yep, UFS+GPT works fine here. Just for archieves: errors for ZFS + GPT --- gptzfsboot: error 128 lba 3907027040 gptzfsboot: error 128 lba 1 gptzfsboot: no zfs pools located, can't boot --- The disk is: --- 512 # sectorsize 2000397852160 # mediasize in bytes (1.8T) 3907027055 # mediasize in sectors 0 # stripesize 0 # stripeoffset 3876018 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. WD-WMAUR0112162 # Disk ident. Not_Zoned # Zone Mode --- UEFI is not available at the motherboard. > Namely, what I have found is that in some systems the INT13 ah=08 can result with unexpected results - error from command reported or disk count not reported etc - something not really expected. It also may have to do about what other devices are there. And also if the system has plain BIOS or BIOS emulated on UEFI. -- WBR, bsam From owner-freebsd-current@freebsd.org Mon Jul 10 20:21:17 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD065DB047B for ; Mon, 10 Jul 2017 20:21:17 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B20C076F55 for ; Mon, 10 Jul 2017 20:21:17 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OSW004002K4ND00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Mon, 10 Jul 2017 19:21:11 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1499714471; bh=vD6+i0hGVs3Mn0kWGBYuG1cduCxPEAbTG3fCTgUEcOA=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=wHXGmp8552mFXmL5VyUrkcOmaG0BzXHuS0UkTPiA6t4Ays17ckI9bz1gMTgKMaP4a pV8bz7JZGDmy3hPrHMtbBj8MO9WcVSLfdXM1Y7g9RNrobl0pn5d40hCfOwyc4bD1gN nIcOZpPFwej3+gPyCvwmgRxmevrYZ+rQzSBA4e2uv7vp+ifVtyZ49RGpfBi90IDi9u l0KsKIrPQZtPo/dc7J2nY5p9+aoiefUXetEAnt+ZTchMRBdmUv9T6g7BNwVye1gSRi snXG1Br4XAyEvyb74GNNcjt7Qmc93sZ53RazdBr5CFo20+wsyeorP+9/SkqRrBQwLr zjsNRFkCLLCIw== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OSW001PM338LE50@st13p35im-asmtp001.me.com>; Mon, 10 Jul 2017 19:21:11 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-07-10_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=52 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1707100340 From: Toomas Soome Message-id: <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [SOLVED] [memstick install] auto-zfs error Date: Mon, 10 Jul 2017 22:21:08 +0300 In-reply-to: Cc: freebsd-current@freebsd.org To: Boris Samorodov References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> X-Mailer: Apple Mail (2.3273) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 20:21:18 -0000 > On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >=20 > 10.07.2017 21:05, Allan Jude =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> On 2017-07-09 14:40, Boris Samorodov wrote: >>> 08.07.2017 18:56, Boris Samorodov =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>>> Hi All, >>>>=20 >>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>> installation memstick.img. Auto-UFS (GPT) installs fine and the = system >>>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>>> At the very beginning it gives something like "gpt sector XXXX = error, >>>> gpt sector 1 error, can't find zroot..." >>>>=20 >>>> Is it a known error / should I give more (precise) errors? >>>>=20 >>>> I tried two recent images with the same result: >>>> = ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-C= URRENT-amd64-20170703-r320599-memstick.img >>>> = ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-C= URRENT-amd64-20170626-r320360-memstick.img >>>=20 >>> It turned out GPT and zfs are not usable at this machine. >>> MBR / ZFS works fine. >>>=20 >>> I'll stick with that. >>=20 >> What type of machine is it? >=20 > It's a PC circa 2009 with MB ASUS P5QL/EPU: > --- > CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz > K8-class CPU) > Origin=3D"GenuineIntel" Id=3D0x1067a Family=3D0x6 Model=3D0x17 = Stepping=3D10 >=20 >=20 > = Features=3D0xbfebfbff >=20 >=20 >=20 > = Features2=3D0xc08e3bd >=20 > AMD Features=3D0x20100800 > AMD Features2=3D0x1 > VT-x: HLT,PAUSE > TSC: P-state invariant, performance statistics > real memory =3D 4294967296 (4096 MB) > avail memory =3D 3324891136 (3170 MB) > Event timer "LAPIC" quality 100 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > --- >=20 > --=20 > WBR, bsam Of course it really can not be that the BIOS has something against = combination of GPT+ZFS, but this combination may trigger some sort of = bug/misbehavior. I have seen some pretty weird issues and have work in = process to have a bit more fool proof approach, but I haven't had time = yet to finalize it properly. Namely, what I have found is that in some systems the INT13 ah=3D08 can = result with unexpected results - error from command reported or disk = count not reported etc - something not really expected. It also may have = to do about what other devices are there. And also if the system has = plain BIOS or BIOS emulated on UEFI. rgds, toomas From owner-freebsd-current@freebsd.org Mon Jul 10 21:02:51 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA023DB0C88 for ; Mon, 10 Jul 2017 21:02:51 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8088478057 for ; Mon, 10 Jul 2017 21:02:51 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OSW00J004F66R00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Mon, 10 Jul 2017 20:02:43 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1499716963; bh=GgZLkBdY5x4EG9pm9dyv3eP5r7tAEa+BkTpaLGx67oU=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=Iiuo0jRqGM+gsvAVTwYKrdp1qWJ+XYOd+Y5tXwinuKe5japa2rEmnmC+usbmRcSie uWWwHhEFbV3L0edaKVCWdP+1o4xGxdBiMeMHtaLabUDVRMm+ytjD/Y06OsdWySv3Hv eL5Q6BWKzUQ7nXXJGMlPbrtsih51nsc00JqA7tlFFZuqxI2115N06gbe7zxfsJhGbT cDVq6h7YEjUucgnOGl3TKuVIK9DllLAl/+vac1T/8xcAb6Ej4A+JS4MJt5WBJvbq12 l1xlNNCsZLbyECQ/Zhqw+9ebNuP79aubOn9rnEF/T1ncfx1QEHHUJBPoqgZjlUgBAl 5pFZPi5VmjTxw== Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OSW00KL050ENH00@st13p35im-asmtp002.me.com>; Mon, 10 Jul 2017 20:02:41 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-07-10_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=18 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1707100350 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [SOLVED] [memstick install] auto-zfs error From: Toomas Soome In-reply-to: Date: Mon, 10 Jul 2017 23:02:37 +0300 Cc: freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <88E064A9-D834-418B-BBFA-586104989DB0@me.com> References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> To: Boris Samorodov X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 21:02:51 -0000 > On 10. juuli 2017, at 22:53, Boris Samorodov wrote: >=20 > 10.07.2017 22:21, Toomas Soome =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>=20 >>> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >>>=20 >>> 10.07.2017 21:05, Allan Jude =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>>> On 2017-07-09 14:40, Boris Samorodov wrote: >>>>> 08.07.2017 18:56, Boris Samorodov =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>>>>> Hi All, >>>>>>=20 >>>>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>>>> installation memstick.img. Auto-UFS (GPT) installs fine and the = system >>>>>> boots fine. However, ZFS-Auto install succeeds, but is not = loaded. >>>>>> At the very beginning it gives something like "gpt sector XXXX = error, >>>>>> gpt sector 1 error, can't find zroot..." >>>>>>=20 >>>>>> Is it a known error / should I give more (precise) errors? >>>>>>=20 >>>>>> I tried two recent images with the same result: >>>>>> = ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-C= URRENT-amd64-20170703-r320599-memstick.img >>>>>> = ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-C= URRENT-amd64-20170626-r320360-memstick.img >>>>>=20 >>>>> It turned out GPT and zfs are not usable at this machine. >>>>> MBR / ZFS works fine. >>>>>=20 >>>>> I'll stick with that. >>>>=20 >>>> What type of machine is it? >>>=20 >>> It's a PC circa 2009 with MB ASUS P5QL/EPU: >>> --- >>> CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz >>> K8-class CPU) >>> Origin=3D"GenuineIntel" Id=3D0x1067a Family=3D0x6 Model=3D0x17 = Stepping=3D10 >>>=20 >>>=20 >>> = Features=3D0xbfebfbff >>>=20 >>>=20 >>>=20 >>> = Features2=3D0xc08e3bd >>>=20 >>> AMD Features=3D0x20100800 >>> AMD Features2=3D0x1 >>> VT-x: HLT,PAUSE >>> TSC: P-state invariant, performance statistics >>> real memory =3D 4294967296 (4096 MB) >>> avail memory =3D 3324891136 (3170 MB) >>> Event timer "LAPIC" quality 100 >>> ACPI APIC Table: >>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>> FreeBSD/SMP: 1 package(s) x 2 core(s) >>> --- >>>=20 >>> --=20 >>> WBR, bsam >>=20 >> Of course it really can not be that the BIOS has something against = combination of GPT+ZFS, but this combination may trigger some sort of = bug/misbehavior. I have seen some pretty weird issues and have work in = process to have a bit more fool proof approach, but I haven't had time = yet to finalize it properly. >=20 > Yep, UFS+GPT works fine here. >=20 > Just for archieves: errors for ZFS + GPT > --- > gptzfsboot: error 128 lba 3907027040 > gptzfsboot: error 128 lba 1 Hm, 128 is 0x80 =3D=3D Disk timeout. So it can be result from the = missing device (bad USB connection or missing floppy drive). What our = INT13 related code is currently missing, is the reset on error calls - = to try to get the IO system back to stable state. Or to be exact - the = reset is not always used. rgds, toomas > gptzfsboot: no zfs pools located, can't boot > --- >=20 > The disk is: > --- > 512 # sectorsize > 2000397852160 # mediasize in bytes (1.8T) > 3907027055 # mediasize in sectors > 0 # stripesize > 0 # stripeoffset > 3876018 # Cylinders according to firmware. > 16 # Heads according to firmware. > 63 # Sectors according to firmware. > WD-WMAUR0112162 # Disk ident. > Not_Zoned # Zone Mode > --- >=20 > UEFI is not available at the motherboard. >=20 >> Namely, what I have found is that in some systems the INT13 ah=3D08 = can result with unexpected results - error from command reported or disk = count not reported etc - something not really expected. It also may have = to do about what other devices are there. And also if the system has = plain BIOS or BIOS emulated on UEFI. >=20 > --=20 > WBR, bsam From owner-freebsd-current@freebsd.org Mon Jul 10 21:14:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C793FDB1171 for ; Mon, 10 Jul 2017 21:14:44 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8EA1B7859F for ; Mon, 10 Jul 2017 21:14:44 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1dUflR-00066H-Vu; Mon, 10 Jul 2017 22:58:42 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Toomas Soome" , "Boris Samorodov" Cc: freebsd-current@freebsd.org Subject: Re: [SOLVED] [memstick install] auto-zfs error References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> Date: Mon, 10 Jul 2017 22:58:37 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-As-Hash: bdb49c4ff80bd276e321aade33e76e02752072e2 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 9e5d90b7ad51a80bf663b69d2bb8c379 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 10 Jul 2017 21:14:44 -0000 On Mon, 10 Jul 2017 21:53:11 +0200, Boris Samorodov wro= te: > 10.07.2017 22:21, Toomas Soome =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> >>> On 10. juuli 2017, at 21:24, Boris Samorodov wrote:= >>> >>> 10.07.2017 21:05, Allan Jude =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>>> On 2017-07-09 14:40, Boris Samorodov wrote: >>>>> 08.07.2017 18:56, Boris Samorodov =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>>>>> Hi All, >>>>>> >>>>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>>>> installation memstick.img. Auto-UFS (GPT) installs fine and the = >>>>>> system >>>>>> boots fine. However, ZFS-Auto install succeeds, but is not loaded= . >>>>>> At the very beginning it gives something like "gpt sector XXXX = >>>>>> error, >>>>>> gpt sector 1 error, can't find zroot..." >>>>>> >>>>>> Is it a known error / should I give more (precise) errors? >>>>>> >>>>>> I tried two recent images with the same result: >>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeB= SD-12.0-CURRENT-amd64-20170703-r320599-memstick.img >>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeB= SD-12.0-CURRENT-amd64-20170626-r320360-memstick.img >>>>> >>>>> It turned out GPT and zfs are not usable at this machine. >>>>> MBR / ZFS works fine. >>>>> >>>>> I'll stick with that. >>>> >>>> What type of machine is it? >>> >>> It's a PC circa 2009 with MB ASUS P5QL/EPU: >>> --- >>> CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz >>> K8-class CPU) >>> Origin=3D"GenuineIntel" Id=3D0x1067a Family=3D0x6 Model=3D0x17 = Stepping=3D10 >>> >>> >>> Features=3D0xbfebfbff >>> >>> >>> >>> Features2=3D0xc08e3bd >>> >>> AMD Features=3D0x20100800 >>> AMD Features2=3D0x1 >>> VT-x: HLT,PAUSE >>> TSC: P-state invariant, performance statistics >>> real memory =3D 4294967296 (4096 MB) >>> avail memory =3D 3324891136 (3170 MB) >>> Event timer "LAPIC" quality 100 >>> ACPI APIC Table: >>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>> FreeBSD/SMP: 1 package(s) x 2 core(s) >>> --- >>> >>> -- >>> WBR, bsam >> >> Of course it really can not be that the BIOS has something against = >> combination of GPT+ZFS, but this combination may trigger some sort of= = >> bug/misbehavior. I have seen some pretty weird issues and have work i= n = >> process to have a bit more fool proof approach, but I haven't had tim= e = >> yet to finalize it properly. > > Yep, UFS+GPT works fine here. > > Just for archieves: errors for ZFS + GPT > --- > gptzfsboot: error 128 lba 3907027040 > gptzfsboot: error 128 lba 1 > gptzfsboot: no zfs pools located, can't boot > --- > > The disk is: > --- > 512 # sectorsize > 2000397852160 # mediasize in bytes (1.8T) > 3907027055 # mediasize in sectors > 0 # stripesize > 0 # stripeoffset > 3876018 # Cylinders according to firmware. > 16 # Heads according to firmware. > 63 # Sectors according to firmware. > WD-WMAUR0112162 # Disk ident. > Not_Zoned # Zone Mode > --- > > UEFI is not available at the motherboard. > >> Namely, what I have found is that in some systems the INT13 ah=3D08 c= an = >> result with unexpected results - error from command reported or disk = = >> count not reported etc - something not really expected. It also may = >> have to do about what other devices are there. And also if the system= = >> has plain BIOS or BIOS emulated on UEFI. > This looks similar to: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D144234 Please add your information if you think it is the same issue. Or try th= e = workaround and see if it helps. Regards, Ronald. From owner-freebsd-current@freebsd.org Mon Jul 10 22:15:30 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A0BCDB1E87 for ; Mon, 10 Jul 2017 22:15:30 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward1o.cmail.yandex.net (forward1o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::2a1]) (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 B0B5C7A0E5 for ; Mon, 10 Jul 2017 22:15:29 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp4j.mail.yandex.net (smtp4j.mail.yandex.net [5.45.198.129]) by forward1o.cmail.yandex.net (Yandex) with ESMTP id 6B63A21320; Tue, 11 Jul 2017 01:15:16 +0300 (MSK) Received: from smtp4j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp4j.mail.yandex.net (Yandex) with ESMTP id ECD45324112A; Tue, 11 Jul 2017 01:15:15 +0300 (MSK) Received: by smtp4j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id yV5WBh9lgF-FEXqm9DV; Tue, 11 Jul 2017 01:15:14 +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=passap.ru; s=mail; t=1499724914; bh=+hivCvijFdGFYMjyQeH55uEz6ITBKltrn4Gf1wkKSQI=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=YB6BvAJ9eF8Q/wivklCgyYK51NK5qKiJjmeoc3vgkB5tKy7H04ro1nTnvTQWMUuPh VBcNMb0YxpyaOnYs2qWyGnSl5RfTROo6gh2y47Ccee1eLthzQDssifM3GTqzLRQGdB lQAD5bDhuBHFQIGo+Q+JrautEk6bRiGJ1soQWZUQ= Authentication-Results: smtp4j.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0 Subject: Re: [SOLVED] [memstick install] auto-zfs error To: Toomas Soome Cc: freebsd-current@freebsd.org References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> <88E064A9-D834-418B-BBFA-586104989DB0@me.com> From: Boris Samorodov Message-ID: Date: Tue, 11 Jul 2017 01:15:14 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <88E064A9-D834-418B-BBFA-586104989DB0@me.com> 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.23 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, 10 Jul 2017 22:15:30 -0000 10.07.2017 23:02, Toomas Soome пишет: > >> On 10. juuli 2017, at 22:53, Boris Samorodov wrote: >> >> 10.07.2017 22:21, Toomas Soome пишет: >>> >>>> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >>>> >>>> 10.07.2017 21:05, Allan Jude пишет: >>>>> On 2017-07-09 14:40, Boris Samorodov wrote: >>>>>> 08.07.2017 18:56, Boris Samorodov пишет: >>>>>>> Hi All, >>>>>>> >>>>>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>>>>> installation memstick.img. Auto-UFS (GPT) installs fine and the system >>>>>>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>>>>>> At the very beginning it gives something like "gpt sector XXXX error, >>>>>>> gpt sector 1 error, can't find zroot..." >>>>>>> >>>>>>> Is it a known error / should I give more (precise) errors? >>>>>>> >>>>>>> I tried two recent images with the same result: >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img >>>>>> >>>>>> It turned out GPT and zfs are not usable at this machine. >>>>>> MBR / ZFS works fine. >>>>>> >>>>>> I'll stick with that. >>>>> >>>>> What type of machine is it? >>>> >>>> It's a PC circa 2009 with MB ASUS P5QL/EPU: >>>> --- >>>> CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz >>>> K8-class CPU) >>>> Origin="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 >>>> >>>> >>>> Features=0xbfebfbff >>>> >>>> >>>> >>>> Features2=0xc08e3bd >>>> >>>> AMD Features=0x20100800 >>>> AMD Features2=0x1 >>>> VT-x: HLT,PAUSE >>>> TSC: P-state invariant, performance statistics >>>> real memory = 4294967296 (4096 MB) >>>> avail memory = 3324891136 (3170 MB) >>>> Event timer "LAPIC" quality 100 >>>> ACPI APIC Table: >>>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>>> FreeBSD/SMP: 1 package(s) x 2 core(s) >>>> --- >>>> >>>> -- >>>> WBR, bsam >>> >>> Of course it really can not be that the BIOS has something against combination of GPT+ZFS, but this combination may trigger some sort of bug/misbehavior. I have seen some pretty weird issues and have work in process to have a bit more fool proof approach, but I haven't had time yet to finalize it properly. >> >> Yep, UFS+GPT works fine here. >> >> Just for archieves: errors for ZFS + GPT >> --- >> gptzfsboot: error 128 lba 3907027040 >> gptzfsboot: error 128 lba 1 > > Hm, 128 is 0x80 == Disk timeout. So it can be result from the missing device (bad USB connection or missing floppy drive). What our INT13 related code is currently missing, is the reset on error calls - to try to get the IO system back to stable state. Or to be exact - the reset is not always used. Actually, it's the same SATA cable/disk which works for UFS/ZFS. > rgds, > toomas > >> gptzfsboot: no zfs pools located, can't boot >> --- >> >> The disk is: >> --- >> 512 # sectorsize >> 2000397852160 # mediasize in bytes (1.8T) >> 3907027055 # mediasize in sectors >> 0 # stripesize >> 0 # stripeoffset >> 3876018 # Cylinders according to firmware. >> 16 # Heads according to firmware. >> 63 # Sectors according to firmware. >> WD-WMAUR0112162 # Disk ident. >> Not_Zoned # Zone Mode >> --- >> >> UEFI is not available at the motherboard. >> >>> Namely, what I have found is that in some systems the INT13 ah=08 can result with unexpected results - error from command reported or disk count not reported etc - something not really expected. It also may have to do about what other devices are there. And also if the system has plain BIOS or BIOS emulated on UEFI. >> -- WBR, bsam From owner-freebsd-current@freebsd.org Mon Jul 10 23:06:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B38F2DB2EC7 for ; Mon, 10 Jul 2017 23:06:22 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward5h.cmail.yandex.net (forward5h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::15]) (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 585367B8AA for ; Mon, 10 Jul 2017 23:06:22 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from smtp2p.mail.yandex.net (smtp2p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b6:7]) by forward5h.cmail.yandex.net (Yandex) with ESMTP id 37D3220FE4; Tue, 11 Jul 2017 02:06:18 +0300 (MSK) Received: from smtp2p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2p.mail.yandex.net (Yandex) with ESMTP id 6C4AF1A8003B; Tue, 11 Jul 2017 02:06:16 +0300 (MSK) Received: by smtp2p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id ffG7OZaxgz-6Gsegs3Z; Tue, 11 Jul 2017 02:06:16 +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=passap.ru; s=mail; t=1499727976; bh=A6NIZY09iuxh2X2Qncgmrfj0c/rEE2fHGGp3w3NCgSA=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=O2HQEoijv2S9GdkQTw/pYwPZIxsZTB3Z/SCYlOnmBg5qgz4jbCt2MTVKfzVW5QS0R b+xpGnhTdzWCSs6t3zvRISNBGDRMoruqpnZzQ7IlEaASDFG4/LyotfWRhcr6u+ocF9 5cem1aAPRQfAOoXvggq2cBoKnYdhAbIIl57vwams= Authentication-Results: smtp2p.mail.yandex.net; dkim=pass header.i=@passap.ru X-Yandex-Suid-Status: 1 0,1 0,1 0 Subject: Re: [SOLVED] [memstick install] auto-zfs error To: Ronald Klop , Toomas Soome Cc: freebsd-current@freebsd.org References: <3f6e5da8-f818-eef2-5384-912d6879cd8e@passap.ru> <5F653933-EA3A-4DAD-93F3-A3C8A7016A30@me.com> From: Boris Samorodov Message-ID: <277f7ce9-f939-0878-f954-4924596b6421@passap.ru> Date: Tue, 11 Jul 2017 02:06:16 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 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.23 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, 10 Jul 2017 23:06:22 -0000 10.07.2017 23:58, Ronald Klop пишет: > On Mon, 10 Jul 2017 21:53:11 +0200, Boris Samorodov wrote: > >> 10.07.2017 22:21, Toomas Soome пишет: >>> >>>> On 10. juuli 2017, at 21:24, Boris Samorodov wrote: >>>> >>>> 10.07.2017 21:05, Allan Jude пишет: >>>>> On 2017-07-09 14:40, Boris Samorodov wrote: >>>>>> 08.07.2017 18:56, Boris Samorodov пишет: >>>>>>> Hi All, >>>>>>> >>>>>>> I tied to install a new FreeBSD-amd-12 system from official USB >>>>>>> installation memstick.img. Auto-UFS (GPT) installs fine and the >>>>>>> system >>>>>>> boots fine. However, ZFS-Auto install succeeds, but is not loaded. >>>>>>> At the very beginning it gives something like "gpt sector XXXX >>>>>>> error, >>>>>>> gpt sector 1 error, can't find zroot..." >>>>>>> >>>>>>> Is it a known error / should I give more (precise) errors? >>>>>>> >>>>>>> I tried two recent images with the same result: >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170703-r320599-memstick.img >>>>>>> >>>>>>> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20170626-r320360-memstick.img >>>>>>> >>>>>> >>>>>> It turned out GPT and zfs are not usable at this machine. >>>>>> MBR / ZFS works fine. >>>>>> >>>>>> I'll stick with that. >>>>> >>>>> What type of machine is it? >>>> >>>> It's a PC circa 2009 with MB ASUS P5QL/EPU: >>>> --- >>>> CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.52-MHz >>>> K8-class CPU) >>>> Origin="GenuineIntel" Id=0x1067a Family=0x6 Model=0x17 Stepping=10 >>>> >>>> >>>> Features=0xbfebfbff >>>> >>>> >>>> >>>> >>>> Features2=0xc08e3bd >>>> >>>> >>>> AMD Features=0x20100800 >>>> AMD Features2=0x1 >>>> VT-x: HLT,PAUSE >>>> TSC: P-state invariant, performance statistics >>>> real memory = 4294967296 (4096 MB) >>>> avail memory = 3324891136 (3170 MB) >>>> Event timer "LAPIC" quality 100 >>>> ACPI APIC Table: >>>> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >>>> FreeBSD/SMP: 1 package(s) x 2 core(s) >>>> --- >>>> >>>> -- >>>> WBR, bsam >>> >>> Of course it really can not be that the BIOS has something against >>> combination of GPT+ZFS, but this combination may trigger some sort of >>> bug/misbehavior. I have seen some pretty weird issues and have work >>> in process to have a bit more fool proof approach, but I haven't had >>> time yet to finalize it properly. >> >> Yep, UFS+GPT works fine here. >> >> Just for archieves: errors for ZFS + GPT >> --- >> gptzfsboot: error 128 lba 3907027040 >> gptzfsboot: error 128 lba 1 >> gptzfsboot: no zfs pools located, can't boot >> --- >> >> The disk is: >> --- >> 512 # sectorsize >> 2000397852160 # mediasize in bytes (1.8T) >> 3907027055 # mediasize in sectors >> 0 # stripesize >> 0 # stripeoffset >> 3876018 # Cylinders according to firmware. >> 16 # Heads according to firmware. >> 63 # Sectors according to firmware. >> WD-WMAUR0112162 # Disk ident. >> Not_Zoned # Zone Mode >> --- >> >> UEFI is not available at the motherboard. >> >>> Namely, what I have found is that in some systems the INT13 ah=08 can >>> result with unexpected results - error from command reported or disk >>> count not reported etc - something not really expected. It also may >>> have to do about what other devices are there. And also if the system >>> has plain BIOS or BIOS emulated on UEFI. >> > > This looks similar to: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > Please add your information if you think it is the same issue. Or try > the workaround and see if it helps. Yes, the problem seems to be the same. A comment is added. Thank you for the link. -- WBR, bsam From owner-freebsd-current@freebsd.org Tue Jul 11 11:48:59 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1567FD9CCE6; Tue, 11 Jul 2017 11:48:59 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660078.outbound.protection.outlook.com [40.107.66.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA697709C1; Tue, 11 Jul 2017 11:48:57 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0191.CANPRD01.PROD.OUTLOOK.COM (10.165.218.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1240.13; Tue, 11 Jul 2017 11:48:55 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.1240.020; Tue, 11 Jul 2017 11:48:55 +0000 From: Rick Macklem To: Cy Schubert CC: "freebsd-current@freebsd.org" , "rc@freebsd.org" Subject: Re: small patch for /etc/rc.d/nfsd, bugfix or POLA violation? Thread-Topic: small patch for /etc/rc.d/nfsd, bugfix or POLA violation? Thread-Index: AQHS+PJNOXcv/ziVcEC7Kot52D/l26JOhC2z Date: Tue, 11 Jul 2017 11:48:55 +0000 Message-ID: References: Message from Rick Macklem of "Sun, 09 Jul 2017 19:57:22 -0000." , <201707092031.v69KVBSn045623@slippy.cwsent.com> In-Reply-To: <201707092031.v69KVBSn045623@slippy.cwsent.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: freebsd.org; dkim=none (message not signed) header.d=none;freebsd.org; dmarc=none action=none header.from=uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTXPR01MB0191; 7:aeEZOz9Qra6OLx8PhD9pKO2IvtllQ60ED6Hgw9URkgWoN67/KQgYm16rxqajgpHpST/PmDIPbMWCTh3G+lc/VmZ3tqrex//kVdsOI7emD2IiT587sUwjYaf3ijvmLmxSPXCvu/EqeI3uYvIBhSloIa0IreBgwZNmTDxfZGk/pMX9m86E7xq1UJldoM9aJyNIdp0AUVrgMrHQ7+m1/2C7eWrqUPUHqll0nxYVmK4GxEL+rncxddzg8W1h+nu7+YtLzOCCDkmOTftApEFu2ZrUXaaRCTcKGdB+2SmMcp69H11AHbq1hALlmJSJ9MBEH5wqUh3WCLqEcpGFfZ3Q+tEthCb/lXVvpKzx/rhx5dSHeNV5oDfTEScvLX/ST8+NHk8OESm0OtP3OLOriH0EZgH/8Z9x8KJIit22QGe0o8xz0jWC0w0lByDfbz0aIS3vWOX/2TbhTuJ11zV1TDdBTYA0jwbjXM1N/ChSeAXMsObXgYXM+WYsHFwmqH1rdxVb7JjWY3JZa5yQXhfRu+2y7pR52nh96VjFg28JZPZNPS6xWDhJfAQUWhGBB2L62qWqce4PTkGZyTmz76U7OKG10Olwvg357wd4X4ztEwatEq7FKqsoegJ4GYSh9K8TQeAwU0nH2gSx6Yvpt30Q0LqFvgEBMN4HuWksq9Mqp9F8oS8TaecDFiSnLvz+HOum7PUpE3boltAIL9KuXu2+K8th0rNiwUk57lbjMNMuQdcY1BLbnQsAi88evC5lhtqbN7cxxvyZBOFk8mlWR41xd34O7IsNzmyMQQkBX5eXbKCo29e92HQ= x-ms-office365-filtering-correlation-id: 27673176-10d6-4e88-04fe-08d4c852cf73 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:YTXPR01MB0191; x-ms-traffictypediagnostic: YTXPR01MB0191: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863)(133145235818549)(236129657087228)(788757137089)(247924648384137); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(2017060910075)(10201501046)(93006095)(93001095)(100000703101)(100105400095)(3002001)(6041248)(20161123555025)(201703131423075)(201702281528075)(201702281529075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(20161123564025)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:YTXPR01MB0191; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:YTXPR01MB0191; x-forefront-prvs: 0365C0E14B x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39850400002)(39410400002)(39400400002)(39450400003)(39840400002)(24454002)(77096006)(6506006)(478600001)(33656002)(50986999)(54356999)(102836003)(76176999)(54906002)(110136004)(6246003)(74482002)(74316002)(53936002)(7696004)(14454004)(55016002)(38730400002)(2906002)(5660300001)(2950100002)(189998001)(6916009)(9686003)(4326008)(305945005)(229853002)(25786009)(8936002)(6436002)(3280700002)(8676002)(5890100001)(81166006)(3660700001)(86362001)(299355004); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0191; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jul 2017 11:48:55.7971 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0191 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 11:48:59 -0000 Cy Schubert wrote: >Rick Macklem wrote: >> Hi, >> >> The attached one line patch to /etc/rc.d/nfsd modifies the script so tha= t i=3D >> t >> does not force the nfsuserd to be run when nfsv4_server_enable is set. >> (nfsuserd can still be enabled via nfsuserd_enable=3D3D"YES" is /etc/rc.= conf.=3D >> ) >> >> Here's why I think this patch might be appropriate... >> (a) - The original RFC for NFSv4 (RFC3530) essentially required Owners a= nd >> Owner_groups to be specified as @ and this required >> the nfsuserd daemon to be running. >> (b) - RFC7530, which replace RFC3530, allows a Owner/Owner_group string = to =3D >> be >> the uid/gid number in a string when using AUTH_SYS. This simplifies co= nfi=3D >> guration >> for an all AUTH_SYS/POSIX environment (most NFS uses, I suspect?). >> >> To make the server do (b), two things need to be done: >> 1 - set vfs.nfsd.enable_stringtouid=3D3D1 >> 2 - set vfs.nfsd.enable_uidtostring=3D3D1 (for head, I don't know if it = will =3D >> be MFC'd?) >> OR >> - never run nfsuserd after booting (killing it off after it has been r= unn=3D >> ing is not >> sufficient) >> =3D20 >> Given the above, it would seem that /etc/rc.d/nfsd should not force runn= ing=3D >> of >> the nfsuserd daemon, due to changes in the protocol. >> >> However, this will result in a POLA violation, in that after the patch, = nfs=3D >> userd won't >> start when booting, unless nfsuserd_enable=3D3D"YES" is added to /etc/rc= .conf=3D >> . >> >> So, what do people think about this patch? rick=3D > >How about a warning message + an UPDATING entry + no MFC? And, relnotes = =3D >yes to say we now support RFC7530 in 12.0? Sounds fine to me. I'll wait to see if there are more comments. Thanks, rick From owner-freebsd-current@freebsd.org Tue Jul 11 12:13:20 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3E44D9DDC5 for ; Tue, 11 Jul 2017 12:13:19 +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 DC61371757 for ; Tue, 11 Jul 2017 12:13:19 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id DB727D9DDBF; Tue, 11 Jul 2017 12:13:19 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D94F2D9DDBE for ; Tue, 11 Jul 2017 12:13:19 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.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 85EB971756; Tue, 11 Jul 2017 12:13:18 +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 v6BCDBaY037090; Tue, 11 Jul 2017 12:13:11 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v6BCDBTM037089; Tue, 11 Jul 2017 05:13:11 -0700 (PDT) (envelope-from david) Date: Tue, 11 Jul 2017 05:13:11 -0700 From: David Wolfskill To: current@freebsd.org Subject: Re: Panic on boot after upgrade from r320827 -> r320869 Message-ID: <20170711121311.GI1177@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org References: <20170710115109.GD1177@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="TEibalRXjoGf3jhD" Content-Disposition: inline In-Reply-To: <20170710115109.GD1177@albert.catwhisker.org> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 12:13:20 -0000 --TEibalRXjoGf3jhD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 10, 2017 at 04:51:09AM -0700, David Wolfskill wrote: > Pnic occurred prior to mounting file systems.... While O. Hartmann had written to indicate the he had identified r320844 as the culprit, and I had other reason to suspect it, I was a bit busy at work yesterday, and unable to determine this for myself empirically. I went ahead and updated my "head" sources to r320884 (without attempting to revert r320844), while running head @r320827. On reboot, I (again) had a panic on the laptop that looked similar to the one from yesterday (r320869). On the build machine, however, I encountered the "mountroot" issue that O. Hartmann had described. I have again created screenshots; they may be found in . For the laptop, the last of them shows the backtrace; the one previous shows the panic message. For the build machine ("freebeast"), the last shows that when I asked for a list of "valid disk boot devices," what was presented was an empty list. (I found a working keyboard for it.) The most recent verbnose dmesg.boot from a successful boot of the laptop (running head) may still be found at . For the build machine, it is . I believe that each of the machines has an MMC slot, but I also believe that in each case, it is empty. Is there anything else I might be able to do to help resolve this? Peace, david --=20 David H. Wolfskill david@catwhisker.org POTUS impeachment requires Congress buy-in. First, fix Congress, THEN impe= ach. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --TEibalRXjoGf3jhD Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZZMDXXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X3pwIAKK8aLdmQ7k75J1rx98nd1nj sZ2uXVw0YmOD+Qc8S3UsX2gnIc1rJWvyArs7IuzMAJ85Fecv14O0AKmezl6bm5A+ F+q5WdPAu89W/YsNQwqGkiHkmlk1w7fshvWU/PGZ+m4mt/i302VwuOv5E0jPJpVj VQtrEyMZb+iIoXHg8iWGiR4kVoRXaJ9EMoKtYCnlR0h01HG5xNk1+vBsBaeK9l4A Ncq0UWKlFLctt03my+QLFzgr5FWS6CFcYIVTEThNTLGsBsrjFL4C2B5EAGNtvZPV RWluouTpHoYmNLFBpTrlUCtqqrZs1XOpBsQ6qWc7L+8G+3gQSzYDIdU+Cq0/qoQ= =tu/2 -----END PGP SIGNATURE----- --TEibalRXjoGf3jhD-- From owner-freebsd-current@freebsd.org Tue Jul 11 13:05:24 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96938D9EECB; Tue, 11 Jul 2017 13:05:24 +0000 (UTC) (envelope-from gergely.czuczy@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) (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 57263730BF; Tue, 11 Jul 2017 13:05:20 +0000 (UTC) (envelope-from gergely.czuczy@harmless.hu) Received: from business-89-133-214-251.business.broadband.hu ([89.133.214.251] helo=[10.160.11.182]) by marvin.harmless.hu with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88 (FreeBSD)) (envelope-from ) id 1dUumH-0000Tj-Px; Tue, 11 Jul 2017 13:00:33 +0000 To: freebsd-current@freebsd.org, freebsd-mips@freebsd.org Cc: pkg@FreeBSD.org From: Gergely Czuczy Subject: strip: elf_strptr failed: Invalid argument Message-ID: Date: Tue, 11 Jul 2017 15:00:33 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 13:05:24 -0000 Hello, I'm trying to build packages on an rpi3, on a freshly build image (with crochet), and when it's trying to build pkg from ports, I'm getting the following error message: libtool: link: cc -D_BSD_SOURCE -I../libpkg -I../libpkg -I../compat -I../external/libucl/klib -I../external/uthash -I../external/expat/lib -DGITHASH=\"\" -O2 -pipe -Wno-error -fno-strict-aliasing -Wall -Wno-unused-function -D_BSD_SOURCE -DINET6=1 -Wl,--enable-new-dtags -o .libs/pkg pkg-add.o pkg-alias.o pkg-annotate.o pkg-audit.o pkg-autoremove.o pkg-backup.o pkg-check.o pkg-clean.o pkg-config.o pkg-convert.o pkg-create.o pkg-delete.o pkg-event.o pkg-fetch.o pkg-globals.o pkg-info.o pkg-install.o pkg-lock.o pkg-main.o pkg-plugins.o pkg-query.o pkg-register.o pkg-repo.o pkg-rquery.o pkg-search.o pkg-set.o pkg-shell.o pkg-shlib.o pkg-ssh.o pkg-stats.o pkg-update.o pkg-updating.o pkg-upgrade.o pkg-utils.o pkg-version.o pkg-which.o ../libpkg/.libs/libpkg.so ../compat/.libs/libbsd_compat.a -lutil -lssl -lcrypto -lm -lelf -ljail -larchive -lz -lbz2 -llzma -Wl,-rpath -Wl,/usr/local/lib /bin/mkdir -p '/usr/ports/ports-mgmt/pkg/work/stage/usr/local/etc' install -m 0644 pkg.conf.sample '/usr/ports/ports-mgmt/pkg/work/stage/usr/local/etc' /bin/mkdir -p '/usr/ports/ports-mgmt/pkg/work/stage/usr/local/sbin' STRIPPROG='strip' /bin/sh ../libtool --mode=install /bin/sh /usr/ports/ports-mgmt/pkg/work/pkg-1.10.1/install-sh -c -s pkg-static pkg '/usr/ports/ports-mgmt/pkg/work/stage/usr/local/sbin' libtool: install: /bin/sh /usr/ports/ports-mgmt/pkg/work/pkg-1.10.1/install-sh -c -s pkg-static /usr/ports/ports-mgmt/pkg/work/stage/usr/local/sbin/pkg-static strip: elf_strptr failed: Invalid argument *** Error code 1 Stop. make[5]: stopped in /usr/ports/ports-mgmt/pkg/work/pkg-1.10.1/src *** Error code 1 Strange part, it says it's stripped already: root@build:/usr/ports/ports-mgmt/pkg # file -s ./work/pkg-1.10.1/src/pkg-static ./work/pkg-1.10.1/src/pkg-static: ELF 64-bit LSB executable, ARM aarch64, version 1 (FreeBSD), statically linked, stripped However, trying to strip(1) manually reproduces the error: # strip ~/pkg-static.1 strip: elf_strptr failed: Invalid argument ktrace didn't reveal anything about the failing elf_strptr(3) call. The system is: FreeBSD build.aegir 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320657: Tue Jul 4 22:28:33 CEST 2017 aegir@marvin.harmless.hu:/tank/rpi3/crochet/work/obj/arm64.aarch64/tank/rpi3/src/sys/AEGIR arm64 Could someone please help me with this? I don't really know how to solve this, or where to start looking. Usually building pkg works out of box. Best regards, Gergely From owner-freebsd-current@freebsd.org Tue Jul 11 14:32:28 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4870DDA13D4 for ; Tue, 11 Jul 2017 14:32:28 +0000 (UTC) (envelope-from wlosh@bsdimp.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 23AE376376 for ; Tue, 11 Jul 2017 14:32:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 22F7ADA13D3; Tue, 11 Jul 2017 14:32:28 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22885DA13D1 for ; Tue, 11 Jul 2017 14:32:28 +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 E143176374 for ; Tue, 11 Jul 2017 14:32:27 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x233.google.com with SMTP id v202so64923159itb.0 for ; Tue, 11 Jul 2017 07:32:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=UPRjeFl87CFehb/Eupa3xG51PP8yeCc6oS1TARymGuQ=; b=xyzxFZG56uKCximy9B0rdpkiYckgFGoXbrMuxth0fmOgLrBpvSkzyIReCJ9MXAiUYk s/zXWEKNHSFvjy8QhqQ1nV4mOd6imCdQfZyExf4JOXw0ZGuDM2grHDSiwMq+3hUMgi2W LPUyCqRj5dxhVHrQPku4FUlP2YtfthucNHosSdNQt78Eij2IIo9kBWAcyjcLD8m2yEgq 0L/rd3IbBROrAmDhY3R8M4VmKHEOWOYcXl/wVpXQl/GECmIq60mKbvF8HqRHQskETvJ9 egAPMSomyw4Ur12DDQ7MBVm/8nNU/6uRcd+jqxDwyRPMmBIuYNUYU14CQNpDg2rF5U4S C3Hw== 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=UPRjeFl87CFehb/Eupa3xG51PP8yeCc6oS1TARymGuQ=; b=C0gGjeQ/7u8KQALtAK2spnq+kvhRz6XbmUJkpg353XnvCddax+cyJJlkgduoXQnHJr Y2RPI2JxJOybguV6kNtM9jujz3o5EQuaaEtOkPT98UQJ/RWYWu4ZwemjnNAexW5t4q3J 93w6ARMnkkhFd4bDjCJHIbDM0F0tLzCVqwnU+g/QL+X0lNZBXsPZTzhFvSU1pm5vm57A GRHBJQdkkk/q1clocP8hVpANX0S4UVnGaArseb91Ta5y75tmRfLzcfV64XeJerVExGf7 BM4dzcHvBSa22gA8bxnXIibyj2UkDKuCV1d0IjXxIxwZlNX1rEIWASIim0cWR/zzpSP2 ZW4g== X-Gm-Message-State: AIVw111+VhbTBU4qQQrd/Q2P6dy52plFkiBuVgFRiTMBaVmiPr4EgWvG p8OFIKSDZ+XNVvLgTMWmaDIPqR/9u5EH X-Received: by 10.36.120.1 with SMTP id p1mr17875839itc.20.1499783547102; Tue, 11 Jul 2017 07:32:27 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.212.167 with HTTP; Tue, 11 Jul 2017 07:32:26 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <20170711121311.GI1177@albert.catwhisker.org> References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> From: Warner Losh Date: Tue, 11 Jul 2017 08:32:26 -0600 X-Google-Sender-Auth: kFSbbM_xvRAbrtddjIe37-i8kaA Message-ID: Subject: Re: Panic on boot after upgrade from r320827 -> r320869 To: David Wolfskill , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 14:32:28 -0000 On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill wrote: > On Mon, Jul 10, 2017 at 04:51:09AM -0700, David Wolfskill wrote: > > Pnic occurred prior to mounting file systems.... > > While O. Hartmann had written to indicate the he had identified r320844 > as the culprit, and I had other reason to suspect it, I was a bit busy > at work yesterday, and unable to determine this for myself empirically. > > I went ahead and updated my "head" sources to r320884 (without > attempting to revert r320844), while running head @r320827. > > On reboot, I (again) had a panic on the laptop that looked similar > to the one from yesterday (r320869). > > On the build machine, however, I encountered the "mountroot" issue that > O. Hartmann had described. > > I have again created screenshots; they may be found in > . For the > laptop, the last of them shows the backtrace; the one previous shows > the panic message. For the build machine ("freebeast"), the last > shows that when I asked for a list of "valid disk boot devices," > what was presented was an empty list. (I found a working keyboard for > it.) > > The most recent verbnose dmesg.boot from a successful boot of the > laptop (running head) may still be found at > . > For the build machine, it is > . > > I believe that each of the machines has an MMC slot, but I also believe > that in each case, it is empty. > > Is there anything else I might be able to do to help resolve this? > Try building a kernel without sdhci in it. It's looking like the scans for ata devices are returning errors on the desktop machine you have, which shouldn't have been happening. Also, can you try a 100% clean build of GENERIC to make sure there's not a meta-mode bug? Warner From owner-freebsd-current@freebsd.org Tue Jul 11 15:06:38 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2CE0DA21B8 for ; Tue, 11 Jul 2017 15:06:38 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::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 936A6772D2 for ; Tue, 11 Jul 2017 15:06:38 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr0-x231.google.com with SMTP id c11so2966621wrc.3 for ; Tue, 11 Jul 2017 08:06:38 -0700 (PDT) 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-transfer-encoding:content-language; bh=tnWsTqb8oKTfoBlkrzT0anptIiEbUXJVDs+orUP6aac=; b=q+GgGBJMVfQs+95wHy+6JOg5mxB5xQsnVMqejOYEccyyCQOFQDuoXTZJRsSX5uA6jo YUQFPu+GmgYbVomR2Nw2K0CdVIzb64KXFb9OCAGU48GQFTunfBJ41jbeB0fazZgTlbm/ +EQJ1Ryada6JN8CiJMMfDnb6IP2jUDsE7fhEh6d3E7SrpCHbbWo0zXR9YVwRZq/OyJeY 9bD9yUqTBh41ONbKKp1s47Av0+ciz0hkD1U7gbzx0iqhL62NOUpBi9LXo/dOgniDtLUy JOr9nF5fv/L151IpgXCeG8vSUggw1AlqlbSx0Fb+0PvKygPiCXIDN7ST9GTsrI0Knqqi CR1g== 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-transfer-encoding:content-language; bh=tnWsTqb8oKTfoBlkrzT0anptIiEbUXJVDs+orUP6aac=; b=Gi9tgp+FaFmXI5pS60B+s/gZEW4j6hiIn5aXgBq2xpw6OElM4HYwMtXbDR+FKt4cYQ y9fbqyoymEqwooEoYW4wgeTajOFQxVE7Qw7Tg+4/+/9ayz320rvlN1a2fNJMQh0GqEkH Q75ZtQW7L2neVmszF7c+dP5m6MA6lKGVVfGomMLRmyD/j3vWgvTiuW/I6doCWv2GgQJL AWfLTg54k/UM3JWoFadZKkEYZJvruy4HQ4XEhGBrtIllKQhmIkXrvsQTdmbOMBhrwCuB TcmRcsfYmlpH6wmbxXo4f/e/2BUnnqgnmmQ7Az88dy7aBZgicCr4FdjVwb9PPSd3GQ81 JtUg== X-Gm-Message-State: AIVw11210YJPKQeL80f+N8lcCMEZYMEvSf/PBtLVRBSuEMXsFjzdR1xU oXNepW2p8hPj+VwWsCM= X-Received: by 10.223.151.44 with SMTP id r41mr225224wrb.6.1499785596625; Tue, 11 Jul 2017 08:06:36 -0700 (PDT) Received: from [193.62.187.15] ([193.62.187.15]) by smtp.gmail.com with ESMTPSA id 92sm169747wrb.55.2017.07.11.08.06.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jul 2017 08:06:34 -0700 (PDT) To: freebsd-current@freebsd.org From: Graham Perrin Subject: beadm activate, cp: /tmp/BE-.../boot/zfs/zpool.cache: No such file or directory Message-ID: <3c198c78-46fc-9c2c-041e-5efee251ece8@gmail.com> Date: Tue, 11 Jul 2017 15:18:09 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 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.23 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, 11 Jul 2017 15:06:39 -0000 UEFI, booted from GELI-encrypted ZFS. Whenever I attempt to activate a boot environment, activation fails. Instead, the environment is mounted. I tried both beadm and (below) beadm-devel. Thoughts? Is this, maybe, a known issue when booting r320599 from encrypted ZFS? Also: at boot time, the list of boot environments is empty. I might workaround, lszfs poolname/ROOT set vfs.root.mountfrom=zfs:poolname/ROOT/bename Thanks ---- # date ; uptime ; uname -a Tue Jul 11 09:15:42 BST 2017 9:15AM up 9 mins, 3 users, load averages: 0.26, 0.33, 0.19 FreeBSD momh167-gjp4-hpelitebook8570p-freebsd 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r320599: Mon Jul 3 15:34:15 UTC 2017 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 # pkg info beadm beadm-1.2.7_2 Name : beadm Version : 1.2.7_2 Installed on : Mon Jul 10 21:44:13 2017 BST Origin : sysutils/beadm Architecture : FreeBSD:12:amd64 Prefix : /usr/local Categories : sysutils Licenses : BSD2CLAUSE Maintainer : bdrewery@FreeBSD.org WWW : https://github.com/vermaden/beadm/ Comment : Solaris-like utility to manage Boot Environments on ZFS Annotations : repo_type : binary repository : FreeBSD Flat size : 30.6KiB Description : beadm is an Illumos/Solaris-like utility for FreeBSD to manage Boot Environments on ZFS filesystems. WWW: https://github.com/vermaden/beadm/ # pkg install beadm-devel Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating area51 repository catalogue... area51 repository is up to date. Updating poudriere repository catalogue... poudriere repository is up to date. Updating trueos-base repository catalogue... trueos-base repository is up to date. All repositories are up to date. Checking integrity... done (2 conflicting) - beadm-devel-1.2.99.20150924 [poudriere] conflicts with beadm-1.2.7_2 [installed] on /usr/local/sbin/beadm - beadm-devel-1.2.99.20150924 [FreeBSD] conflicts with beadm-1.2.7_2 [installed] on /usr/local/sbin/beadm Checking integrity... done (0 conflicting) The following 2 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: beadm-1.2.7_2 New packages to be INSTALLED: beadm-devel: 1.2.99.20150924 [poudriere] Number of packages to be removed: 1 Number of packages to be installed: 1 Proceed with this action? [y/N]: y [1/2] Deinstalling beadm-1.2.7_2... [1/2] Deleting files for beadm-1.2.7_2: 100% [2/2] Installing beadm-devel-1.2.99.20150924... [2/2] Extracting beadm-devel-1.2.99.20150924: 100% # beadm create 2017-07-11-09 Created successfully # beadm activate 2017-07-11-09 cp: /tmp/BE-2017-07-11-09.H0k1WFYJ/boot/zfs/zpool.cache: No such file or directory # beadm list BE Active Mountpoint Space Created default NR / 8.3G 2017-07-07 10:50 2017-07-11-09 - /tmp/BE-2017-07-11-09.H0k1WFYJ 8.0K 2017-07-11 09:16 # gpart show => 40 976773088 ada0 GPT (466G) 40 409600 1 efi (200M) 409640 2008 - free - (1.0M) 411648 4194304 2 freebsd-zfs (2.0G) 4605952 33554432 3 freebsd-swap (16G) 38160384 938612736 4 freebsd-zfs (448G) 976773120 8 - free - (4.0K) # mount hpelitebook8570p/ROOT/default on / (zfs, local, noatime, nfsv4acls) devfs on /dev (devfs, local, multilabel) procfs on /proc (procfs, local) bootpool on /bootpool (zfs, local, nfsv4acls) hpelitebook8570p on /hpelitebook8570p (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere on /hpelitebook8570p/poudriere (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/jails on /hpelitebook8570p/poudriere/jails (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/ports on /hpelitebook8570p/poudriere/ports (zfs, local, noatime, nfsv4acls) hpelitebook8570p/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls) hpelitebook8570p/usr/home on /usr/home (zfs, local, noatime, nfsv4acls) hpelitebook8570p/usr/home/grahamperrin on /usr/home/grahamperrin (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/data on /usr/local/poudriere/data (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/data/.m on /usr/local/poudriere/data/.m (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/data/cache on /usr/local/poudriere/data/cache (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/data/logs on /usr/local/poudriere/data/logs (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/data/packages on /usr/local/poudriere/data/packages (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/data/wrkdirs on /usr/local/poudriere/data/wrkdirs (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/jails/current on /usr/local/poudriere/jails/current (zfs, local, noatime, nfsv4acls) hpelitebook8570p/poudriere/ports/freebsd-ports-kde on /usr/local/poudriere/ports/freebsd-ports-kde (zfs, local, noatime, nfsv4acls) hpelitebook8570p/usr/ports on /usr/ports (zfs, local, noatime, nosuid, nfsv4acls) hpelitebook8570p/usr/src on /usr/src (zfs, local, noatime, nfsv4acls) hpelitebook8570p/var/VirtualBox on /var/VirtualBox (zfs, local, noatime, nfsv4acls) hpelitebook8570p/var/audit on /var/audit (zfs, local, noatime, noexec, nosuid, nfsv4acls) hpelitebook8570p/var/crash on /var/crash (zfs, local, noatime, noexec, nosuid, nfsv4acls) hpelitebook8570p/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls) hpelitebook8570p/var/mail on /var/mail (zfs, local, nfsv4acls) hpelitebook8570p/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls) linprocfs on /compat/linux/proc (linprocfs, local) tmpfs on /compat/linux/dev/shm (tmpfs, local) fdescfs on /dev/fd (fdescfs) hpelitebook8570p/ROOT/2017-07-11-09 on /tmp/BE-2017-07-11-09.H0k1WFYJ (zfs, local, noatime, nfsv4acls) # zfs list NAME USED AVAIL REFER MOUNTPOINT bootpool 135M 1.73G 133M /bootpool hpelitebook8570p 78.2G 352G 88K /hpelitebook8570p hpelitebook8570p/ROOT 8.27G 352G 88K none hpelitebook8570p/ROOT/2017-07-11-09 8K 352G 8.27G /tmp/BE-2017-07-11-09.H0k1WFYJ hpelitebook8570p/ROOT/default 8.27G 352G 8.27G / hpelitebook8570p/poudriere 3.62G 352G 88K /hpelitebook8570p/poudriere hpelitebook8570p/poudriere/data 732M 352G 96K /usr/local/poudriere/data hpelitebook8570p/poudriere/data/.m 88K 352G 88K /usr/local/poudriere/data/.m hpelitebook8570p/poudriere/data/cache 12.6M 352G 12.6M /usr/local/poudriere/data/cache hpelitebook8570p/poudriere/data/logs 42.8M 352G 42.8M /usr/local/poudriere/data/logs hpelitebook8570p/poudriere/data/packages 676M 352G 676M /usr/local/poudriere/data/packages hpelitebook8570p/poudriere/data/wrkdirs 88K 352G 88K /usr/local/poudriere/data/wrkdirs hpelitebook8570p/poudriere/jails 949M 352G 88K /hpelitebook8570p/poudriere/jails hpelitebook8570p/poudriere/jails/current 948M 352G 948M /usr/local/poudriere/jails/current hpelitebook8570p/poudriere/ports 1.98G 352G 88K /hpelitebook8570p/poudriere/ports hpelitebook8570p/poudriere/ports/freebsd-ports-kde 1.98G 352G 1.98G /usr/local/poudriere/ports/freebsd-ports-kde hpelitebook8570p/tmp 15.9M 352G 15.9M /tmp hpelitebook8570p/usr 66.2G 352G 88K /usr hpelitebook8570p/usr/home 64.3G 352G 547M /usr/home hpelitebook8570p/usr/home/grahamperrin 63.7G 352G 58.2G /usr/home/grahamperrin hpelitebook8570p/usr/ports 1.34G 352G 1.34G /usr/ports hpelitebook8570p/usr/src 638M 352G 638M /usr/src hpelitebook8570p/var 1.25M 352G 88K /var hpelitebook8570p/var/VirtualBox 88K 352G 88K /var/VirtualBox hpelitebook8570p/var/audit 88K 352G 88K /var/audit hpelitebook8570p/var/crash 88K 352G 88K /var/crash hpelitebook8570p/var/log 684K 352G 684K /var/log hpelitebook8570p/var/mail 152K 352G 152K /var/mail hpelitebook8570p/var/tmp 88K 352G 88K /var/tmp # From owner-freebsd-current@freebsd.org Tue Jul 11 15:31:37 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79DD2DA29F2 for ; Tue, 11 Jul 2017 15:31:37 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3689A7800F for ; Tue, 11 Jul 2017 15:31:36 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 2BB45139F5 for ; Tue, 11 Jul 2017 15:31:35 +0000 (UTC) Subject: Re: beadm activate, cp: /tmp/BE-.../boot/zfs/zpool.cache: No such file or directory To: freebsd-current@freebsd.org References: <3c198c78-46fc-9c2c-041e-5efee251ece8@gmail.com> From: Allan Jude Message-ID: <42d96984-e1dc-9bc1-41b4-f4bf39da4566@freebsd.org> Date: Tue, 11 Jul 2017 11:31:31 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <3c198c78-46fc-9c2c-041e-5efee251ece8@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="P9BXATPpLcAVCNJN6in1hXtAhuuRex0jX" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 15:31:37 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --P9BXATPpLcAVCNJN6in1hXtAhuuRex0jX Content-Type: multipart/mixed; boundary="UKBmHN8Nm1PJbPw2i9oWPAVcOm3lhGnIw"; protected-headers="v1" From: Allan Jude To: freebsd-current@freebsd.org Message-ID: <42d96984-e1dc-9bc1-41b4-f4bf39da4566@freebsd.org> Subject: Re: beadm activate, cp: /tmp/BE-.../boot/zfs/zpool.cache: No such file or directory References: <3c198c78-46fc-9c2c-041e-5efee251ece8@gmail.com> In-Reply-To: <3c198c78-46fc-9c2c-041e-5efee251ece8@gmail.com> --UKBmHN8Nm1PJbPw2i9oWPAVcOm3lhGnIw Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2017-07-11 10:18, Graham Perrin wrote: > UEFI, booted from GELI-encrypted ZFS. >=20 > Whenever I attempt to activate a boot environment, activation fails. > Instead, the environment is mounted. >=20 > I tried both beadm and (below) beadm-devel. >=20 > Thoughts? Is this, maybe, a known issue when booting r320599 from > encrypted ZFS? >=20 > Also: at boot time, the list of boot environments is empty. I might > workaround, >=20 > lszfs poolname/ROOT > set vfs.root.mountfrom=3Dzfs:poolname/ROOT/bename >=20 > Thanks >=20 > ---- >=20 > # date ; uptime ; uname -a > Tue Jul 11 09:15:42 BST 2017 > 9:15AM up 9 mins, 3 users, load averages: 0.26, 0.33, 0.19 > FreeBSD momh167-gjp4-hpelitebook8570p-freebsd 12.0-CURRENT FreeBSD > 12.0-CURRENT #0 r320599: Mon Jul 3 15:34:15 UTC 2017 > root@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > # pkg info beadm > beadm-1.2.7_2 > Name : beadm > Version : 1.2.7_2 > Installed on : Mon Jul 10 21:44:13 2017 BST > Origin : sysutils/beadm > Architecture : FreeBSD:12:amd64 > Prefix : /usr/local > Categories : sysutils > Licenses : BSD2CLAUSE > Maintainer : bdrewery@FreeBSD.org > WWW : https://github.com/vermaden/beadm/ > Comment : Solaris-like utility to manage Boot Environments on ZF= S > Annotations : > repo_type : binary > repository : FreeBSD > Flat size : 30.6KiB > Description : > beadm is an Illumos/Solaris-like utility for FreeBSD to manage > Boot Environments on ZFS filesystems. >=20 > WWW: https://github.com/vermaden/beadm/ > # pkg install beadm-devel > Updating FreeBSD repository catalogue... > FreeBSD repository is up to date. > Updating area51 repository catalogue... > area51 repository is up to date. > Updating poudriere repository catalogue... > poudriere repository is up to date. > Updating trueos-base repository catalogue... > trueos-base repository is up to date. > All repositories are up to date. > Checking integrity... done (2 conflicting) > - beadm-devel-1.2.99.20150924 [poudriere] conflicts with beadm-1.2.7_= 2 > [installed] on /usr/local/sbin/beadm > - beadm-devel-1.2.99.20150924 [FreeBSD] conflicts with beadm-1.2.7_2 > [installed] on /usr/local/sbin/beadm > Checking integrity... done (0 conflicting) > The following 2 package(s) will be affected (of 0 checked): >=20 > Installed packages to be REMOVED: > beadm-1.2.7_2 >=20 > New packages to be INSTALLED: > beadm-devel: 1.2.99.20150924 [poudriere] >=20 > Number of packages to be removed: 1 > Number of packages to be installed: 1 >=20 > Proceed with this action? [y/N]: y > [1/2] Deinstalling beadm-1.2.7_2... > [1/2] Deleting files for beadm-1.2.7_2: 100% > [2/2] Installing beadm-devel-1.2.99.20150924... > [2/2] Extracting beadm-devel-1.2.99.20150924: 100% > # beadm create 2017-07-11-09 > Created successfully > # beadm activate 2017-07-11-09 > cp: /tmp/BE-2017-07-11-09.H0k1WFYJ/boot/zfs/zpool.cache: No such file o= r > directory > # beadm list > BE Active Mountpoint Space Created > default NR / 8.3G 2017-07-07 1= 0:50 > 2017-07-11-09 - /tmp/BE-2017-07-11-09.H0k1WFYJ 8.0K 2017-07-11 0= 9:16 > # gpart show > =3D> 40 976773088 ada0 GPT (466G) > 40 409600 1 efi (200M) > 409640 2008 - free - (1.0M) > 411648 4194304 2 freebsd-zfs (2.0G) > 4605952 33554432 3 freebsd-swap (16G) > 38160384 938612736 4 freebsd-zfs (448G) > 976773120 8 - free - (4.0K) >=20 > # mount > hpelitebook8570p/ROOT/default on / (zfs, local, noatime, nfsv4acls) > devfs on /dev (devfs, local, multilabel) > procfs on /proc (procfs, local) > bootpool on /bootpool (zfs, local, nfsv4acls) > hpelitebook8570p on /hpelitebook8570p (zfs, local, noatime, nfsv4acls) > hpelitebook8570p/poudriere on /hpelitebook8570p/poudriere (zfs, local, > noatime, nfsv4acls) > hpelitebook8570p/poudriere/jails on /hpelitebook8570p/poudriere/jails > (zfs, local, noatime, nfsv4acls) > hpelitebook8570p/poudriere/ports on /hpelitebook8570p/poudriere/ports > (zfs, local, noatime, nfsv4acls) > hpelitebook8570p/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls) > hpelitebook8570p/usr/home on /usr/home (zfs, local, noatime, nfsv4acls)= > hpelitebook8570p/usr/home/grahamperrin on /usr/home/grahamperrin (zfs, > local, noatime, nfsv4acls) > hpelitebook8570p/poudriere/data on /usr/local/poudriere/data (zfs, > local, noatime, nfsv4acls) > hpelitebook8570p/poudriere/data/.m on /usr/local/poudriere/data/.m (zfs= , > local, noatime, nfsv4acls) > hpelitebook8570p/poudriere/data/cache on /usr/local/poudriere/data/cach= e > (zfs, local, noatime, nfsv4acls) > hpelitebook8570p/poudriere/data/logs on /usr/local/poudriere/data/logs > (zfs, local, noatime, nfsv4acls) > hpelitebook8570p/poudriere/data/packages on > /usr/local/poudriere/data/packages (zfs, local, noatime, nfsv4acls) > hpelitebook8570p/poudriere/data/wrkdirs on > /usr/local/poudriere/data/wrkdirs (zfs, local, noatime, nfsv4acls) > hpelitebook8570p/poudriere/jails/current on > /usr/local/poudriere/jails/current (zfs, local, noatime, nfsv4acls) > hpelitebook8570p/poudriere/ports/freebsd-ports-kde on > /usr/local/poudriere/ports/freebsd-ports-kde (zfs, local, noatime, > nfsv4acls) > hpelitebook8570p/usr/ports on /usr/ports (zfs, local, noatime, nosuid, > nfsv4acls) > hpelitebook8570p/usr/src on /usr/src (zfs, local, noatime, nfsv4acls) > hpelitebook8570p/var/VirtualBox on /var/VirtualBox (zfs, local, noatime= , > nfsv4acls) > hpelitebook8570p/var/audit on /var/audit (zfs, local, noatime, noexec, > nosuid, nfsv4acls) > hpelitebook8570p/var/crash on /var/crash (zfs, local, noatime, noexec, > nosuid, nfsv4acls) > hpelitebook8570p/var/log on /var/log (zfs, local, noatime, noexec, > nosuid, nfsv4acls) > hpelitebook8570p/var/mail on /var/mail (zfs, local, nfsv4acls) > hpelitebook8570p/var/tmp on /var/tmp (zfs, local, noatime, nosuid, > nfsv4acls) > linprocfs on /compat/linux/proc (linprocfs, local) > tmpfs on /compat/linux/dev/shm (tmpfs, local) > fdescfs on /dev/fd (fdescfs) > hpelitebook8570p/ROOT/2017-07-11-09 on /tmp/BE-2017-07-11-09.H0k1WFYJ > (zfs, local, noatime, nfsv4acls) > # zfs list > NAME USED AVAIL REFER = > MOUNTPOINT > bootpool 135M 1.73G 133M=20 > /bootpool > hpelitebook8570p 78.2G 352G 88K=20 > /hpelitebook8570p > hpelitebook8570p/ROOT 8.27G 352G 88K n= one > hpelitebook8570p/ROOT/2017-07-11-09 8K 352G 8.27G = > /tmp/BE-2017-07-11-09.H0k1WFYJ > hpelitebook8570p/ROOT/default 8.27G 352G 8.27G = / > hpelitebook8570p/poudriere 3.62G 352G 88K=20 > /hpelitebook8570p/poudriere > hpelitebook8570p/poudriere/data 732M 352G 96K=20 > /usr/local/poudriere/data > hpelitebook8570p/poudriere/data/.m 88K 352G 88K=20 > /usr/local/poudriere/data/.m > hpelitebook8570p/poudriere/data/cache 12.6M 352G 12.6M = > /usr/local/poudriere/data/cache > hpelitebook8570p/poudriere/data/logs 42.8M 352G 42.8M = > /usr/local/poudriere/data/logs > hpelitebook8570p/poudriere/data/packages 676M 352G 676M=20 > /usr/local/poudriere/data/packages > hpelitebook8570p/poudriere/data/wrkdirs 88K 352G 88K=20 > /usr/local/poudriere/data/wrkdirs > hpelitebook8570p/poudriere/jails 949M 352G 88K=20 > /hpelitebook8570p/poudriere/jails > hpelitebook8570p/poudriere/jails/current 948M 352G 948M=20 > /usr/local/poudriere/jails/current > hpelitebook8570p/poudriere/ports 1.98G 352G 88K=20 > /hpelitebook8570p/poudriere/ports > hpelitebook8570p/poudriere/ports/freebsd-ports-kde 1.98G 352G 1.98G = > /usr/local/poudriere/ports/freebsd-ports-kde > hpelitebook8570p/tmp 15.9M 352G 15.9M = > /tmp > hpelitebook8570p/usr 66.2G 352G 88K /= usr > hpelitebook8570p/usr/home 64.3G 352G 547M=20 > /usr/home > hpelitebook8570p/usr/home/grahamperrin 63.7G 352G 58.2G = > /usr/home/grahamperrin > hpelitebook8570p/usr/ports 1.34G 352G 1.34G = > /usr/ports > hpelitebook8570p/usr/src 638M 352G 638M=20 > /usr/src > hpelitebook8570p/var 1.25M 352G 88K /= var > hpelitebook8570p/var/VirtualBox 88K 352G 88K=20 > /var/VirtualBox > hpelitebook8570p/var/audit 88K 352G 88K=20 > /var/audit > hpelitebook8570p/var/crash 88K 352G 88K=20 > /var/crash > hpelitebook8570p/var/log 684K 352G 684K=20 > /var/log > hpelitebook8570p/var/mail 152K 352G 152K=20 > /var/mail > hpelitebook8570p/var/tmp 88K 352G 88K=20 > /var/tmp > # > _______________________________________________ > 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" Boot environments with a bootpool do not work. Support for GELI with UEFI is coming soon. This will allow you to move /boot into the GELI encrypted pool, and get rid of the bootpool, and properly use boot environments. --=20 Allan Jude --UKBmHN8Nm1PJbPw2i9oWPAVcOm3lhGnIw-- --P9BXATPpLcAVCNJN6in1hXtAhuuRex0jX 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.0.22 (MingW32) iQIcBAEBAgAGBQJZZO9WAAoJEBmVNT4SmAt+M9QQANOKJqsy/whsMUZaKnr/GoWy xldu//rdAYf/+Kc2J5wUU6EoEeQ33bcdLy4Q9NUA6gGhXgP+LhS6gKPzD0AC+ghN /ieqUx0Zj6bJ5THz7r7UroimOlZ/byHsljPxFYJ5r1bovFjimh0px4eHz+60qYSz lrkozygTB5bAr9YyzUo6NyloZvevf8uQZdLQyyUg4vyXgv1Sa9lznB5WaSMzxA6O KLt3bqt0X1kss7c5qek94Xp/RovL+ZEfGmElNVWuA3E+7K3N/zL9wc2XWrZmrWAG mZEs8I3xI+NRphYTH9XmT0yyLEzCnPfAgo4obZlODDzO5rT/HbZobizmFV/JwCNa AvaxEgmnPyDQgniZadbdtAD5/d2sAp+a9Wxo5iC4QQhx4sOMHw2UPWpSnuUASJ/1 owBE8tu0HuIembX6t7hEnhd9Nhm6ZFrYbA/qyxqGHTVE1zkWP4e1FclBIu/TTlZr ZMU6x2bhvrEQT73GL9fTLrs9PsuxHJmCuXRtcVRGRRq22UeBZQVui7uV4V5Aa9Et Z4wtTAK7uqKnWAd/aAW+l4tMr17KJKzfGsACuicVr7TQy7ayHZ9hsImalLgLt96f NKJi85rfUBmW/VPkUKQ7rhfy9HzTyUO3VB5I52xieK501PpqxtQVGK4wmXcVkV9D Lipeg+qt5Z+DKdoiYVHD =pGGL -----END PGP SIGNATURE----- --P9BXATPpLcAVCNJN6in1hXtAhuuRex0jX-- From owner-freebsd-current@freebsd.org Tue Jul 11 16:38:36 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 838EBDA4557 for ; Tue, 11 Jul 2017 16:38:36 +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 6A5AD7A692 for ; Tue, 11 Jul 2017 16:38:36 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 65B33DA4556; Tue, 11 Jul 2017 16:38:36 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 639EEDA4555 for ; Tue, 11 Jul 2017 16:38:36 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.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 DCAB87A691; Tue, 11 Jul 2017 16:38:35 +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 v6BGcVZT040842; Tue, 11 Jul 2017 16:38:31 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id v6BGcUfu040841; Tue, 11 Jul 2017 09:38:30 -0700 (PDT) (envelope-from david) Date: Tue, 11 Jul 2017 09:38:30 -0700 From: David Wolfskill To: Warner Losh Cc: FreeBSD Current Subject: Re: Panic on boot after upgrade from r320827 -> r320869 Message-ID: <20170711163830.GY1177@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Warner Losh , FreeBSD Current References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Ftwx2AbF8guY0WoT" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 16:38:36 -0000 --Ftwx2AbF8guY0WoT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 11, 2017 at 08:32:26AM -0600, Warner Losh wrote: > ... > > While O. Hartmann had written to indicate the he had identified r320844 > > as the culprit, and I had other reason to suspect it, I was a bit busy > > at work yesterday, and unable to determine this for myself empirically. > > > > I went ahead and updated my "head" sources to r320884 (without > > attempting to revert r320844), while running head @r320827. > > > > On reboot, I (again) had a panic on the laptop that looked similar > > to the one from yesterday (r320869). > > > > On the build machine, however, I encountered the "mountroot" issue that > > O. Hartmann had described. > ... > > Is there anything else I might be able to do to help resolve this? > > >=20 > Try building a kernel without sdhci in it. >=20 > It's looking like the scans for ata devices are returning errors on the > desktop machine you have, which shouldn't have been happening. >=20 > Also, can you try a 100% clean build of GENERIC to make sure there's not a > meta-mode bug? >=20 > Warner In thinking about the order of operations, it occurred to me that trying the last option first would make sense, so I did that (cleared /usr/obj/usr/src/sys/GENERIC, then re-built and -installed the kernel). And the build machine came up in multi-user mode: FreeBSD freebeast.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #404 r3= 20884M/320891:1200038: Tue Jul 11 09:12:03 PDT 2017 root@freebeast.catw= hisker.org:/common/S4/obj/usr/src/sys/GENERIC amd64 I'll call that "success" and stop while I'm ahead. :-) Thanks! Peace, david --=20 David H. Wolfskill david@catwhisker.org POTUS impeachment requires Congress buy-in. First, fix Congress, THEN impe= ach. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --Ftwx2AbF8guY0WoT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJZZP8GXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4XC2MIAJ+bP0njGxx+TBcgUuMEM4sj +7pCMGR6tDU+FktcwE8fJkkTMruMpoj67NYo0RVBkGg+QghUCYlx9lR4xsRQ+jmW wKY4+y3uOYWmvJrp+b8kTo2Ee4QDzgxmYMyiozLEgkDRVBROkktdfc6n9NOm8Ige ZlUJjd/FqWi37tc5DBzTlEk3PSIMTSv/0gpchKgCfXURnHW4E1Q0haNSUhn/p659 Yug+plpE5q5MfNKU6xQYerVXPsBZAyaA/tlfkTWTOWIapnns4/PjKXr1vnOzqq9V 5OrrPQnJBI7m8TtJbPUqByRvPHyoq1Wb22Fk/7X5/Bm/jEVKzm3bC/U+AoO37G4= =QjY3 -----END PGP SIGNATURE----- --Ftwx2AbF8guY0WoT-- From owner-freebsd-current@freebsd.org Tue Jul 11 16:44:20 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F600DA4990 for ; Tue, 11 Jul 2017 16:44:20 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A2987ACEF for ; Tue, 11 Jul 2017 16:44:20 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v6BGiDvN026531 for ; Tue, 11 Jul 2017 09:44:17 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201707111644.v6BGiDvN026531@gw.catspoiler.org> Date: Tue, 11 Jul 2017 09:44:13 -0700 (PDT) From: Don Lewis Subject: r320183 (rpc.lockd cleanup) breaks virtualbox-ose build To: freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 16:44:20 -0000 This is a really strange problem ... Last week I upgraded my 12.0-CURRENT package build box from r318774 to r320570. I also upgraded the poudriere jail to match. When I went to build packages, the virtualbox-ose build failed due to ar segfaulting. To debug I created a new 12.0-CURRENT poudriere jail with rev r318774 and the build passed. I then bisected, which took most of the last week, and found that this commit is what is causing the breakage: r320183 | delphij | 2017-06-20 23:34:06 -0700 (Tue, 20 Jun 2017) | 12 lines Reduce code duplication in rpc.lockd. Reuse create_service code instead of duplicating it in lookup_addresses for kernel NLM. As a (good) side effect this also fixed a few issues that were already fixed in the former but never applied to the latter. and it only touches usr.sbin/rpc.lockd/lockd.c. If I rebuild the r320570 jail with the r320183 change backed out, and then I can successfully build virtualbox-ose. I confirmed this on another machine. I have no idea why the rpc.lockd source would affect ar inside a poudriere jail where NFS isn't used. Like I said, really strange ... ex From owner-freebsd-current@freebsd.org Tue Jul 11 16:47:48 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A1AFDA4B8E for ; Tue, 11 Jul 2017 16:47:48 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4210F7AF61 for ; Tue, 11 Jul 2017 16:47:48 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: by mailman.ysv.freebsd.org (Postfix) id 3E7DDDA4B8D; Tue, 11 Jul 2017 16:47:48 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DA72DA4B8C for ; Tue, 11 Jul 2017 16:47:48 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (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 0F81A7AF60 for ; Tue, 11 Jul 2017 16:47:47 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from michaels-mbp.cambridge.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172]) (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 A6B4C3716E; Tue, 11 Jul 2017 12:47:39 -0400 (EDT) Subject: Re: Panic on boot after upgrade from r320827 -> r320869 To: Warner Losh , David Wolfskill , FreeBSD Current References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> From: Michael Butler Message-ID: Date: Tue, 11 Jul 2017 12:47:36 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 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.23 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, 11 Jul 2017 16:47:48 -0000 On 7/11/17 10:32 AM, Warner Losh wrote: > On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill > wrote: >> I believe that each of the machines has an MMC slot, but I also believe >> that in each case, it is empty. >> >> Is there anything else I might be able to do to help resolve this? >> > > Try building a kernel without sdhci in it. > > It's looking like the scans for ata devices are returning errors on the > desktop machine you have, which shouldn't have been happening. > > Also, can you try a 100% clean build of GENERIC to make sure there's not a > meta-mode bug? On a machine with SDHCI, a clean rebuild (after "r -rf /usr/obj") refuses to find /dev/ada0 :-( imb From owner-freebsd-current@freebsd.org Tue Jul 11 17:09:06 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5D3ADA6D05 for ; Tue, 11 Jul 2017 17:09:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7EAC87D866 for ; Tue, 11 Jul 2017 17:09:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7DEDBDA6D04; Tue, 11 Jul 2017 17:09:06 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BEA3DA6D03 for ; Tue, 11 Jul 2017 17:09:06 +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 401117D865 for ; Tue, 11 Jul 2017 17:09:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x230.google.com with SMTP id v202so69548227itb.0 for ; Tue, 11 Jul 2017 10:09:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hIHi70b5yKVL4TpzaHgTYRqFzS4QZyWlT5UPAxnwmKE=; b=Jh6mHC8WI5daE3ugPEjEQXm+OG/maoxYEZfVf7/7Omzrp//DS217o+4k+iER4sLV4W i6Ridp18pAzIE39AUJm24YdPvKfAeCFY6NQckEoHTCjvxUA3qf6e+EaUvyBZKgNOidiX fawdSrW4w56LEkA4Mq2VB2S19HSgt9KHncgBInjA3LGBsZL7uAH0i8pffSobFCaz+XJy IMGvb3enACvVFgsbdX8GWypt87oDy7bF/Y7PzvjzEEdaEqnpX8XgetrHGWdHjSbzSyNn 84+jYbWuN9qu5cRBtu8wQ2ImGvK2DntK1GArN+JJMhcfyzPLXSDphuNoYPf90Hfr+FCl hLVg== 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=hIHi70b5yKVL4TpzaHgTYRqFzS4QZyWlT5UPAxnwmKE=; b=Xjq5dcMhChMvjvsYtnjMrbHFYAkWK+iiSfNXvaw+mNOitEYmcCsLVtIG4avf4rJBbN sTMDzijXvev8ypwwLcyC2UTFwdJP+Ie1eVY4AYZfar9XumZIzVLt1652/TtHmcEzflHr kvDcDuOyrK/aomj9MYIS34O7aJx+kDD0zU7LOIGAGdURbxkP6aEU/R31iFKK7EghryCa i9ZNB5ZrOuk5fPu0vHtt1ldNWbW3ZE7eevNW4i/BlHTih6nnsaHmLLMDq6a34elRzlUX MNbqh/K65y1HUjmPpyQa6nmROuUFcfSLgmF9JYsJVRJw3vF2zFj7hlLNb6c0XfyLh06z z4zg== X-Gm-Message-State: AIVw110TOqUZrey0/8wr41OCtcqOFBUmj5N+Fu1ZORs5Mr7E61dRmGqd OBMuIccyZSaCNDPByyvW6ajH9JqMYcDp X-Received: by 10.107.180.5 with SMTP id d5mr1196699iof.56.1499792945533; Tue, 11 Jul 2017 10:09:05 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.212.167 with HTTP; Tue, 11 Jul 2017 10:09:05 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> From: Warner Losh Date: Tue, 11 Jul 2017 11:09:05 -0600 X-Google-Sender-Auth: YnrsxgOAUL9TBTTuW9C0tHc0KoM Message-ID: Subject: Re: Panic on boot after upgrade from r320827 -> r320869 To: Michael Butler Cc: David Wolfskill , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 17:09:06 -0000 On Tue, Jul 11, 2017 at 10:47 AM, Michael Butler wrote: > On 7/11/17 10:32 AM, Warner Losh wrote: > >> On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill >> wrote: >> >>> I believe that each of the machines has an MMC slot, but I also believe >>> that in each case, it is empty. >>> >>> Is there anything else I might be able to do to help resolve this? >>> >>> >> Try building a kernel without sdhci in it. >> >> It's looking like the scans for ata devices are returning errors on the >> desktop machine you have, which shouldn't have been happening. >> >> Also, can you try a 100% clean build of GENERIC to make sure there's not a >> meta-mode bug? >> > > On a machine with SDHCI, a clean rebuild (after "r -rf /usr/obj") refuses > to find /dev/ada0 :-( > Take sdhci out of the kernel and try again. If that works, it tells us one thing (need to troubleshoot sdhci stuff more). If not it tells us another (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY command? Does it try multiple times per AHCI port? What AHCI device do you have? You may need to scroll back with the screen-lock / pageup keys to see these messages. Plus we know we have at least one bug in meta-mode rebuilding since not everything is being rebuilt that should be across this change. The change itself didn't change CAM except for copying one set of data it didn't used to, into a structure whose size grew (which is why we're seeing crashes / failures for a 'cross-threaded' rebuild). There's nothing else that changed (especially after I removed the bogus debug printfs) that I can see in auditing the change. I was really hoping David's machine would exhibit the behavior since we're co-workers and have a shared infrastructure for debugging we can leverage. Warner From owner-freebsd-current@freebsd.org Tue Jul 11 17:13:26 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19EAEDA704A for ; Tue, 11 Jul 2017 17:13:26 +0000 (UTC) (envelope-from imb@protected-networks.net) 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 EECA67DD0A for ; Tue, 11 Jul 2017 17:13:25 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: by mailman.ysv.freebsd.org (Postfix) id E252ADA7049; Tue, 11 Jul 2017 17:13:25 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1EEADA7048 for ; Tue, 11 Jul 2017 17:13:25 +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 B2ABF7DD03 for ; Tue, 11 Jul 2017 17:13:25 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from michaels-mbp.cambridge.ibm.com (bi-03pt1.bluebird.ibm.com [129.42.208.172]) (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 C90E537F8E; Tue, 11 Jul 2017 13:13:22 -0400 (EDT) Subject: Re: Panic on boot after upgrade from r320827 -> r320869 To: Warner Losh Cc: FreeBSD Current References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> From: Michael Butler Message-ID: <954e8793-7e17-8ae4-8449-39c742e0d432@protected-networks.net> Date: Tue, 11 Jul 2017 13:13:21 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 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.23 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, 11 Jul 2017 17:13:26 -0000 On 7/11/17 1:09 PM, Warner Losh wrote: >> On a machine with SDHCI, a clean rebuild (after "r -rf /usr/obj") refuses >> to find /dev/ada0 :-( >> > > Take sdhci out of the kernel and try again. If that works, it tells us one > thing (need to troubleshoot sdhci stuff more). If not it tells us another > (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY > command? Does it try multiple times per AHCI port? What AHCI device do you > have? You may need to scroll back with the screen-lock / pageup keys to see > these messages. > > Plus we know we have at least one bug in meta-mode rebuilding since not > everything is being rebuilt that should be across this change. > > The change itself didn't change CAM except for copying one set of data it > didn't used to, into a structure whose size grew (which is why we're seeing > crashes / failures for a 'cross-threaded' rebuild). There's nothing else > that changed (especially after I removed the bogus debug printfs) that I > can see in auditing the change. > > I was really hoping David's machine would exhibit the behavior since we're > co-workers and have a shared infrastructure for debugging we can leverage. I'll try this tonight when I'm back at home. The laptop concerned uses the ICH-7M part in "legacy mode" so it doesn't do AHCI at all :-( imb From owner-freebsd-current@freebsd.org Tue Jul 11 17:13:28 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A545DA7060 for ; Tue, 11 Jul 2017 17:13:28 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 60C137DD28 for ; Tue, 11 Jul 2017 17:13:28 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6031DDA705E; Tue, 11 Jul 2017 17:13:28 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5FE2ADA705D for ; Tue, 11 Jul 2017 17:13:28 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 2A03B7DD26; Tue, 11 Jul 2017 17:13:28 +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 67CD413057; Tue, 11 Jul 2017 17:13:27 +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 84B4E2B24; Tue, 11 Jul 2017 17:13:26 +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 R7GLmJszlhft; Tue, 11 Jul 2017 17:13:24 +0000 (UTC) Subject: Re: Panic on boot after upgrade from r320827 -> r320869 DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com BAF2F2B1E To: Warner Losh , Michael Butler Cc: David Wolfskill , FreeBSD Current References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> From: Bryan Drewery Organization: FreeBSD Message-ID: Date: Tue, 11 Jul 2017 10:13:22 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="L0IjjBumrNKmgIpHHBWL1nSPf2VodAWf3" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 17:13:28 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --L0IjjBumrNKmgIpHHBWL1nSPf2VodAWf3 Content-Type: multipart/mixed; boundary="AQfkdKrGwCATLwshXEcpgPdfUDUcWrJrx"; protected-headers="v1" From: Bryan Drewery To: Warner Losh , Michael Butler Cc: David Wolfskill , FreeBSD Current Message-ID: Subject: Re: Panic on boot after upgrade from r320827 -> r320869 References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> In-Reply-To: --AQfkdKrGwCATLwshXEcpgPdfUDUcWrJrx Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 7/11/17 10:09 AM, Warner Losh wrote: > Plus we know we have at least one bug in meta-mode rebuilding since not= > everything is being rebuilt that should be across this change. Yes I'm looking into that. --=20 Regards, Bryan Drewery --AQfkdKrGwCATLwshXEcpgPdfUDUcWrJrx-- --L0IjjBumrNKmgIpHHBWL1nSPf2VodAWf3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJZZQczAAoJEDXXcbtuRpfPlXYH/3PrOuHBmVhipCzZ9z5Zj29p RXsnA8e9MGZ5qLmDTUvhCeLFCNJ0yzZI2vgUNEA0BXiy/LOFDBCJrrSc+6TRXng+ P2dKiIryHfzJl7vfLqKlbT4CFDiwXdU/MNX5m7A1C5Ha27aTOGG53KUqT5WohjnX a5KeP9IoSko3pHlqS0EZvBd7t80M99LrX+mm1PqNoMM46oHfAqvusyqe+GsnVNwr yogl8wRZHsfKu4phiwJjrfCzsN/dq3JylA/7Tw/quc4W2bgRa9EQo2mEAqcv77ak S+Pkf1VOeDhCQaGJocM6oqMnCuQGVBaRlouezuS6V1jSeXdY8T0JTqIOoIVNeV8= =Myom -----END PGP SIGNATURE----- --L0IjjBumrNKmgIpHHBWL1nSPf2VodAWf3-- From owner-freebsd-current@freebsd.org Tue Jul 11 17:39:05 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4919DA7E5F; Tue, 11 Jul 2017 17:39:05 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from forward12m.cmail.yandex.net (forward12m.cmail.yandex.net [IPv6:2a02:6b8:b030::99]) (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 A1DBE7EEA0; Tue, 11 Jul 2017 17:39:05 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from smtp1p.mail.yandex.net (smtp1p.mail.yandex.net [77.88.29.84]) by forward12m.cmail.yandex.net (Yandex) with ESMTP id 54C8121BC9; Tue, 11 Jul 2017 20:38:53 +0300 (MSK) Received: from smtp1p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1p.mail.yandex.net (Yandex) with ESMTP id 0959A1780965; Tue, 11 Jul 2017 20:38:51 +0300 (MSK) Received: by smtp1p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id p50qcDTnEt-comqbXuF; Tue, 11 Jul 2017 20:38:50 +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.com; s=mail; t=1499794730; bh=175rnZwAKAYSdJrABSYxJQylFAxB+hgoRgx5P061eMU=; h=From:Subject:To:Cc:Message-ID:Date; b=cdGCCKLPRnFH0I7lCXdWlge0WUHwR2lS1AlMAaNCI0TOZKgLxLmlG2Hs7rblPcm6w ftAbB7ak/4TPbjpjcVvPcT9TVabNKFoepxvRwpK2p0kW85daYEQ67My6ZJuKu609Bm iS2N8oQtTi+qBTjgJMKB6RjKa4PPIeT4b+eYkfpY= Authentication-Results: smtp1p.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-Suid-Status: 1 1022867361,1 0,1 0,1 0 From: Panagiotes Mousikides Subject: Run binary from test suite To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Cc: Kristof Provost Message-ID: <5a7ed4ea-de4c-4f6a-e528-9e3c70722d0c@yandex.com> Date: Tue, 11 Jul 2017 17:38:50 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 17:39:06 -0000 (Resending due to moderation.) Hello! I'm a Google Summer of Code student, writing some tests for the FreeBSD test suite, and putting them under src/tests. I need to run some binaries, specifically pfctl. How should I call pfctl from my test scripts? Should I call it directly and let the shell find the binary in the path? Or should I find where the build version got created (somewhere under /usr/obj) and call that? How do I find where the binary ended up getting created in that case? Best regards, Panagiotes From owner-freebsd-current@freebsd.org Tue Jul 11 17:13:58 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6915DA7176; Tue, 11 Jul 2017 17:13:58 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from forward11p.cmail.yandex.net (forward11p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::bb]) (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 A1E977DF5E; Tue, 11 Jul 2017 17:13:58 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [IPv6:2a02:6b8:0:801::ab]) by forward11p.cmail.yandex.net (Yandex) with ESMTP id ED222213C4; Tue, 11 Jul 2017 20:13:54 +0300 (MSK) Received: from smtp1j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1j.mail.yandex.net (Yandex) with ESMTP id E21A33C8109F; Tue, 11 Jul 2017 20:13:51 +0300 (MSK) Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 4ojvg8lGAh-DpB0P1Qj; Tue, 11 Jul 2017 20:13:51 +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.com; s=mail; t=1499793231; bh=oDg7eKXtRtHk199Bx/VgMGQVIk9JCwNMHclx0xvKypQ=; h=To:From:Subject:Cc:Message-ID:Date; b=aA6SixtvBhIfsCocjlXKhB4EIYaEU8kcBiB5tBlgXWFiXLcxk8Gff8G8XdwKf8uAb Uvw/gkzV5D8AxKAZg6IIRFl2E9nXE86xlLR8oH5RCYxXzlxqzp93+YoNcVyhu69aqy icHGZYclJC85bJMnjunQ8a0kj/OI5Jf0aHL7v2Ek= Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-Suid-Status: 1 1022867361,1 0,1 0,1 0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org From: Panagiotes Mousikides Subject: Run binary from test suite Cc: Kristof Provost Message-ID: Date: Tue, 11 Jul 2017 17:13:50 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Mailman-Approved-At: Tue, 11 Jul 2017 17:49:09 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 17:13:59 -0000 Hello! I'm a Google Summer of Code student, writing some tests for the FreeBSD test suite, and putting them under src/tests. I need to run some binaries, specifically pfctl. How should I call pfctl from my test scripts? Should I call it directly and let the shell find the binary in the path? Or should I find where the build version got created (somewhere under /usr/obj) and call that? How do I find where the binary ended up getting created in that case? Best regards, Panagiotes From owner-freebsd-current@freebsd.org Tue Jul 11 18:51:04 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A817FDA9EFA; Tue, 11 Jul 2017 18:51:04 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-yb0-x243.google.com (mail-yb0-x243.google.com [IPv6:2607:f8b0:4002:c09::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 6615B820E9; Tue, 11 Jul 2017 18:51:04 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-yb0-x243.google.com with SMTP id n205so47400yba.1; Tue, 11 Jul 2017 11:51:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=eJuAQlIcl8eru/MHSqFooVhEGf5g7sGWiCPr09mytBA=; b=qIUdfRglr5w8a7xBOxV12ppVSiVErJRfPI171WrUpkMD/YPKQXAG/FNbpzM8yNYmXx y4Bzz8CTgV4Fh7R8HEGhaVxxfj4EYUvrtGDvVb3nAnaO5O8c3JBGY9mEq2DCqtnbJJzj doSazkIZITjkBbjvxzuGXzo37MPPr03AtfzX9ecXQIauY1XF6KNCxDrQOTyiFu7B89/H hk3Dq8g7rMRnVaG7oghgVBd7cZg1FaaD9N1z9OOi5gHVff22FQuQY3l7T0hF/ljrR2hs 4kyuYy7CkWKxJbB2eE7vTtruM68pSdyikn363fVhx/XRKldpNiF60i5HJGtVo4AE5YtN MjfQ== 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=eJuAQlIcl8eru/MHSqFooVhEGf5g7sGWiCPr09mytBA=; b=Qe6bWAFfL+GBHlmFXD2a9Jk9lMReEpk0ibx7u60FNWOL4jrMwzKealxO98hlKaE/u5 EPG4JDYnJTY0huefbPuE8m/fja5yls8C8/LdjO6BbXT02PF/XfAXOdTaQ4krAHhGdUL7 aPmhIpMo7VMVWzO/IK+solEjJtZ5cxJKRBNtWRAxpLNyY9wO4QBOhgi914TPVgKUz0j9 /KKznoNiP/zCkxweLdaCWqDONPsDXhWAoolXgdJJ1jF2+psbMPkgqAr0UED8ph/BgrHA Yxn3OhRjKtSsmE52dVI47pghQ1nOtyzfVhE290xamRHapU+WKk8aYthWl+6DvZU7UMzG dK8w== X-Gm-Message-State: AIVw111E4N6f8ET90sdMTx4w8X5fFLGaJKriarbw4fKFmNsjI8gu7g++ clcIHZwEGCq1o/uFmyPHlKXjJzex0g== X-Received: by 10.37.219.208 with SMTP id g199mr37985ybf.195.1499799063562; Tue, 11 Jul 2017 11:51:03 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.13.243.135 with HTTP; Tue, 11 Jul 2017 11:51:03 -0700 (PDT) In-Reply-To: References: From: Alan Somers Date: Tue, 11 Jul 2017 12:51:03 -0600 X-Google-Sender-Auth: UleoGt4k4oZ4Y-Dq742qiiiol3o Message-ID: Subject: Re: Run binary from test suite To: Panagiotes Mousikides Cc: "freebsd-hackers@freebsd.org" , FreeBSD CURRENT , Kristof Provost Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 18:51:04 -0000 Are you using pfctl at build time or does your ATF test script need it? I'm assuming the latter. In that case, it's fine to call it directly. Your PATH will be correctly configured. Don't use /usr/obj, because that may no longer exist by the time somebody is running the ATF test. -Alan On Tue, Jul 11, 2017 at 11:13 AM, Panagiotes Mousikides wrote: > Hello! > > I'm a Google Summer of Code student, writing some tests for the FreeBSD test > suite, and putting them under src/tests. I need to run some binaries, > specifically pfctl. > > How should I call pfctl from my test scripts? Should I call it directly and > let the shell find the binary in the path? Or should I find where the build > version got created (somewhere under /usr/obj) and call that? How do I find > where the binary ended up getting created in that case? > > Best regards, > Panagiotes > > _______________________________________________ > 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 Tue Jul 11 20:05:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81E6FDAB416; Tue, 11 Jul 2017 20:05:44 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DAA46511E; Tue, 11 Jul 2017 20:05:44 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-qk0-x232.google.com with SMTP id p21so2444506qke.3; Tue, 11 Jul 2017 13:05:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ODgtcEI4h7Nqg3RhE7UzTxkmTdT5+lW+gS08gndSpWE=; b=TYt19qpyE5mT6EwpLaD2bBX07834uKrCEJbO1uVPOm6y3dc8hkbRUyA0d/wIhknkls uCg09+3XAa42PHcMhv2R1vDZ6zqDq0mM80ug6Fw5GA5ndLwYaoxYGXDGr/WvWF6ZiUVp wVnBWPOnPj/g1X8g+ovknsybR0569OS91EpGKzKBOL6L498rlldc4sB4bR22NZKX6kXp C3/YBEsS4sfOXVyC2bosj9DpNjqgNoClJYdbnU4grrEV2roQzpmQT1AEYS4aqPlWZoTO DK3UacCr7E11E+JQXI2iKZqJ4chdpTusuyb+xk3DhXMKVhqcigHvXy37SrJHashd3APY YY1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ODgtcEI4h7Nqg3RhE7UzTxkmTdT5+lW+gS08gndSpWE=; b=ss6AureIFn+SalXKQEIUc75C++N3X8s8sBKXIpMW+tvpv9n5JmsH4p6rgIsn3gSsd4 7ff5GSUy0NCM/gorkaxBsJxcbOttM750Vz9oTt3dGYiXm3pG/4zqDnvyxNDsnWCdIR9j /hELTexKjzSLYCzKLoIHDUnr1RsGUZLhwRIEvwXtMWdDnop1RBs6Kk658IiWgoDbe+n2 ncnnIDdLU7glyCipnUCoyWpmfmbRj8Bj4CPoUmI4NsKoyhDRkd7fya4db4qWGmzkoCuS ewM/PdniDsdVrFbt3V4XPf4zvZHXdJk+SDdN/NmAAptE/Xz9QCGvdH8BvHn6mqt3WPRm crrg== X-Gm-Message-State: AIVw1139c46ezN317aEKoizDv40bY9eOcL27y6o++NUAKUCNSSIJ/c/+ wdXe9d1M/wtvzBKEyE/JWiiKWw6TAQ== X-Received: by 10.55.21.223 with SMTP id 92mr2091978qkv.199.1499803543368; Tue, 11 Jul 2017 13:05:43 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.92.142 with HTTP; Tue, 11 Jul 2017 13:05:42 -0700 (PDT) In-Reply-To: <5a7ed4ea-de4c-4f6a-e528-9e3c70722d0c@yandex.com> References: <5a7ed4ea-de4c-4f6a-e528-9e3c70722d0c@yandex.com> From: Ngie Cooper Date: Tue, 11 Jul 2017 13:05:42 -0700 Message-ID: Subject: Re: Run binary from test suite To: Panagiotes Mousikides Cc: "freebsd-hackers@freebsd.org" , FreeBSD Current , Kristof Provost Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 20:05:44 -0000 On Tue, Jul 11, 2017 at 10:38 AM, Panagiotes Mousikides wrote: > (Resending due to moderation.) > > Hello! > > I'm a Google Summer of Code student, writing some tests for the FreeBSD test > suite, and putting them under src/tests. I need to run some binaries, > specifically pfctl. > > How should I call pfctl from my test scripts? Should I call it directly and > let the shell find the binary in the path? Or should I find where the build > version got created (somewhere under /usr/obj) and call that? How do I find > where the binary ended up getting created in that case? > > Best regards, > Panagiotes Hello Panagiotes, Please call pfctl from $PATH -- don't hardcode the path, ever. I'll be looking at making "make check" more developer friendly in the next 3-6 months, so running "make check" from usr.sbin/pf/... will automatically add a set path/environment which hooks in to *.test.mk. The goal of this is to simplify developer use for "make check". Also, if the tests (for whatever reason) aren't going to be installed alongside pfctl, e.g., tests/sys/pf/... please add 'atf_set "require.progs" "pfctl"' to the header to ensure that the test is skipped if/when pfctl isn't installed on the system. Cheers, -Ngie From owner-freebsd-current@freebsd.org Tue Jul 11 20:48:16 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 039ADDABD28 for ; Tue, 11 Jul 2017 20:48:16 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 69E7C675CE for ; Tue, 11 Jul 2017 20:48:15 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.227.219.210]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M7YF5-1dqOst0nP5-00xLC0; Tue, 11 Jul 2017 22:48:12 +0200 Date: Tue, 11 Jul 2017 22:48:04 +0200 From: "O. Hartmann" To: freebsd-current@freebsd.org Cc: "O. Hartmann" , Milan Obuch , Freddie Cash Subject: VLAN routing fails from VLAN -> non VLAN [was: Re: static routes on VLAN on CURRENT] Message-ID: <20170711224804.25628840@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170703062941.4eb9658d@freyja.zeit4.iv.bundesimmobilien.de> References: <20170702133957.1f337a2e@hermann> <20170702143934.2bbcc98a@zeta.dino.sk> <20170702201344.274eb23d@hermann> <20170702211217.0d22b349@zeta.dino.sk> <20170703062941.4eb9658d@freyja.zeit4.iv.bundesimmobilien.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/AhWem03ZjpQdyt=N=hambZS"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:DighPVxmOyrpGsUpVVMf/RfkIcR2xHHY6ssCs7eGZ5xjpd8C6wD Co8C4LufiRSlS6uu40OIh1tQQkof4aspEehSGXnKamJ9bCKaYmkMxwy8hk8VyGntHUDnama /9S5rQcSvGOc2XySzV5qQnh6aXt3LqE2PJp6H1xKmrwQ/jofnKQpkn79oeYbV/0QRZVXjJn acQDZeXyefvOkmEd3dTJQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:hYxQ3dkO9Vw=:OPuOlDLb4p9qutQFXb+4TM HAh1tOt8XM6p00iRYpk6rdPUVo2GYqg4Pd2SPgeu7p49R3m/dPFTGkC+vQ4FqEP0eqC69Rtbz njh3KXHu8SSP0wbGLSURgpsX135vFsCKceucvPoWch3fCCbnZjlwD7U4k/2OpCmGO9gJn1vOW 4C14XXRicJaTw6Ml3bU0OmPC1MYjrNRTTyJWfX95XcP39O0bvJc+5qv1yjpXIkD6VRCA5XHLj Fp5CcsoyOH8Caw8XDJ1TJKZwKuu3aq3gBd5YFy86jReQLbffO1KbbGWgPU7nqa/QbNkBAjjpc A70juqG+J/aK4nk24bDJ8TZr/qFwQUWh6Ap4KjRHmWJ6xKz0Gpp3B8/w/IOhVRJy5SL4zI0kf 169owiq3bdgoyREVCrmg13VcAZDjd9IfwLXk7F1SX/EcN34W7g6TBdBemiQNJwvayIVDsRKAT wX7EezNYErfbbumJ5BcqsT3H1zGQk+FxCOiQd86tc+naMgB6vWzc7F1Lzc7xNXAZ7J9M2hzt3 7qy8LeUt8zuq3kxgxgTTBZFDqpuCgVZ381XM0KGUwYg4MqYIacI3rebIKRtfF8+peZ4eApnoa +0hdd0v/yQE3TFwSBjK1ZrxbOR0+j/bLoyoKL1J98Ez1TEruQc8oya18N0DU27ftfTpHtJENB LaL87NOxcE6Mj3WDUU2UmUzvolKh8k9YN/SHT1py06tBcDK8NaUkThXrm9//AfWFqB2FVsNz+ fZat7sXhG9SMeOjAFJE/Z38/wRybCpyW05gtDYcm3NDdD1wUq92AiZ5lcSM= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Jul 2017 20:48:16 -0000 --Sig_/AhWem03ZjpQdyt=N=hambZS Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 3 Jul 2017 06:29:41 +0200 "O. Hartmann" wrote: Hello, I figured some severe problemes with the configuration of the cheap SoHo smart-managed switch Netgear GS110TP. This piece of crap is way to smart fo= r me. For short: If one leaves a port as "U" (untagged) withing a VLANG group in = the membership configuration and this port is also member of another VLAN as "U" (untagged) (Cisco calls those ports access ports), nothing works. There= is obviously no consistency check for such mistakes. So, after that, I was able to manage separated VLANs on the switch which get routed by the a freeBSD 12-CURRENT. The uplink port (igb1) on the FBSD box "trunks" all VLANs to the switch.=20 Now, the router shows this: Internet: Destination Gateway Flags Use Mtu Netif Exp= ire default xxx.xxx.xxx.xxx US 513 1492 tun0 xxx.xxx.xxx.xxx link#12 UHS 0 1492 tun0 xxx.xxx.xxx.xxx link#12 UHS 0 16384 lo0 127.0.0.1 link#5 UH 111 16384 lo0 192.168.2.0/24 link#7 U 0 1500 igb1.2 192.168.2.1 link#7 UHS 0 16384 lo0 192.168.10.0/24 link#8 U 0 1500 igb1.10 192.168.10.1 link#8 UHS 0 16384 lo0 192.168.66.0/24 link#10 U 0 1500 igb1.66 192.168.66.1 link#10 UHS 0 16384 lo0 192.168.100.0/24 link#11 U 0 1500 igb1.100 192.168.100.1 link#11 UHS 0 16384 lo0 192.168.0.0/24 link#9 U 0 1500 igb1.1000 192.168.0.1 link#9 UHS 0 16384 lo0 [ schnipp ]=20 tun0 is the ppp opened device towards my VDSL modem. ssh on the router box is listening on 192.168.0.1 - this for completeness. I also have FreeBSD hosts in networks 192.168.0.0/24 and 192.168.10.0/24 (network 192.168.10.0/24 is on a dual port NIC, the host is not gatewaying, checking pinging from 192.168.10.0/24 to 192.168.0.0/24 without the trunk p= ort from switch towards the router doesn't work, but works, when trunk port is connected - I consider this a s quick test that routing works). > >=20 > > [ sysctl stuff snipped - not relevant, I think ] > > =20 > > > > > From the routing device itself, it is possible to ssh into a VoIP > > > > > client attached to the switch to which igb1.2 trunks the net. > > > > > Pinging is also possible. > > > > >=20 > > > > > Attached to igb1 is the 192.168.0.1/24 network with a bunch of > > > > > hosts. From any host within this network it is possible to ping > > > > > the 192.168.2.0/24 network and its hosts within, but no SSH, not > > > > > web (80, 443).=20 > > > > > =20 > > > >=20 The problem still persists. I did some experiments by setting trying to ssh into several hosts from sev= eral spots. the router has 192.168.0.1:ssh 192.168.0.0/24 is on igb1.1000 ping: 192.168.0.111 -> 192.168.0.1 : ok ssh: 192.168.0.111 -> 192.168.0.1 : ok ping: 192.168.0.1 -> 192.168.0.111 : ok ssh: 192.168.0.111 -> 192.168.0.111 : ok ping: 192.168.0.111 -> google.com : ok 192.168.66.0/24 is on igb1.66 host 192.168.66.111 is a notebook with sshd enabled ping: 192.168.66.111 -> 192.168.0.1 : ok ssh: 192.168.66.111 -> 192.168.0.1 : NOT ok ssh: 192.168.0.1 -> 192.168.66.111 : NOT ok (do not understand this) ping: 192.168.66.111 -> 8.8.8.8 (no DNS): ok Ping from any VLAN to another VLAN host without the trunking cable connecte= d to the switch fails. With the cable plugged in, ping works. ping: 192.168.0.1 -> 192.168.2.50 (VoIP phone): ok ssh: 192.168.0.1 -> 192.168.2.50 (VoIP phone): ok ping: 192.168.0.111 -> 192.168.2.50 (VoIP phone): ok ssh 192.168.0.111 -> 192.168.2.50 (VoIP phone): NOT ok > > > > Weird - if icmp (ping) works and tcp (web, ssh) not, something is > > > > filtering traffic. But with net.inet.ip.forwarding=3D0, even pinging > > > > host should not work. Try tcpdump to see what's going on. =20 > > >=20 [ schnipp ] > >=20 > > Then I just recommend tcpdump - I would use 'tcpdump -nepi igb1.2 host > > 192.168.0.x and host 192.168.2.y' and 'tcpdump -nepi igb1 host > > 192.168.0.x and host 192.168.2.y' in two session and compare outputs > > when pinging from 192.168.0.x to 192.168.2.y and when trying to ssh > > from the former to the later. Also there is a question then what these > > two devices are, what OS are they running, their network > > configuration... then we can analyse the problem better.=20 Since the VoIP phone has a very restricted interface and shell capability s= et, I need to do this from another FreeBSD 12-CURRENT host and as I showed above, I put t= hat host into VLAN 66, bound to igb1.66 -> 192.168.66.1/24 on the router: Pinging from 192.168.0.111 <-> 192.168.66.111 gives on both machines nice "= ping-pong" results: echo request and echo reply. But ssh from one to the other is a mysterium magnum. ssh from 192.168.0.111= -> 192.168.66.111 gives something like 192.168.0.111 > 192.168.66.111: Flags [S] An never a response. The same in the opposite direction. Since I don't have= much computers to test (I need the notebook for setting up the switch) results m= ay be a bit sloppy. It seems that for the vlan 66, vlan 2 and even the vlan 10 (I did also test= ) there is never a return answer ... I have no further ideas :-( Oliver p.s. Also with ipfw (which is in-kernel) switched to allow everything, the = picture is the same. =20 >=20 > Thank you very much for the details of analysing. I regret, at the moment= I > have no access to the facility. But except the device bearing the IP > 192.168.2.y, which is a commercial VoIP endpoint, other parties are 12-CU= RRENT > of a very well known OS.=20 >=20 > I'll check as soon as I have acces. > >=20 > > Regards, > > Milan > > =20 >=20 > Thank you very much and kind regards, >=20 > Oliver > _______________________________________________ > 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" --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/AhWem03ZjpQdyt=N=hambZS Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWWU5hAAKCRDS528fyFhY lLRBAf4rpTOuU/5GM9wOUFgKxcN3UD7RuI1/rsXo2sRV3t9wN0tVzowd/HnlUrqV 0OO0ffmULKKfxwlknBxyHxfpb5lsAf9d9S5WNrbs1DursjWDrqrJZLyr4B7FOuZY zMMaul7mpCnQ6PTjQak96LqCJI5D5CW3bYLPm9SQzOami7Hb/3t0 =QZ/G -----END PGP SIGNATURE----- --Sig_/AhWem03ZjpQdyt=N=hambZS-- From owner-freebsd-current@freebsd.org Tue Jul 11 23:53:08 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2E85EDAE6B5 for ; Tue, 11 Jul 2017 23:53:08 +0000 (UTC) (envelope-from imb@protected-networks.net) 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 0FAE07077E for ; Tue, 11 Jul 2017 23:53:08 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: by mailman.ysv.freebsd.org (Postfix) id 0BF85DAE6B4; Tue, 11 Jul 2017 23:53:08 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B854DAE6B3 for ; Tue, 11 Jul 2017 23:53:08 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (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 C9DC97077D for ; Tue, 11 Jul 2017 23:53:07 +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:references:from :from:subject:subject; s=201508; t=1499817184; bh=QOZoW5HwStyNU7 hmsw75o2CyNfTtoak3oZDXDvrPUGA=; b=m78YS+e+t8jf51e15waMpOn+tFFiPY JCEqEqosXydWNqqQ+J4o2ae2G70Z3GcHIbuUJb+bPkXCEm+cJ0F9L8YSMIFNsC1U hboQz/nHkZklLeyjUzn73VDp4BijAo0c4U6IKRrKUjXqBQKgjDOQ/DqE+F+O57pB LB48hQ8Lvf+jo= 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 A071D3CDB9; Tue, 11 Jul 2017 19:53:04 -0400 (EDT) Subject: Re: Panic on boot after upgrade from r320827 -> r320869 From: Michael Butler To: Warner Losh Cc: FreeBSD Current References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> <954e8793-7e17-8ae4-8449-39c742e0d432@protected-networks.net> Message-ID: Date: Tue, 11 Jul 2017 19:53:04 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <954e8793-7e17-8ae4-8449-39c742e0d432@protected-networks.net> 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.23 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, 11 Jul 2017 23:53:08 -0000 On 07/11/17 13:13, I wrote: >> Take sdhci out of the kernel and try again. If that works, it tells us >> one >> thing (need to troubleshoot sdhci stuff more). If not it tells us another >> (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY >> command? Does it try multiple times per AHCI port? What AHCI device do >> you >> have? You may need to scroll back with the screen-lock / pageup keys >> to see >> these messages. [ .. snip .. ] > I'll try this tonight when I'm back at home. The laptop concerned uses > the ICH-7M part in "legacy mode" so it doesn't do AHCI at all :-( Without sdhci and mmc, it actually boots but everything KDE aborts with signal 6 :-( I'm not prepared to rebuild the ~1900 ports on this box to pursue this further, imb From owner-freebsd-current@freebsd.org Wed Jul 12 01:13:07 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B783DAFA1D for ; Wed, 12 Jul 2017 01:13:07 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DAD6C72A83; Wed, 12 Jul 2017 01:13:06 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v6C1CwDl038201; Tue, 11 Jul 2017 18:13:02 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201707120113.v6C1CwDl038201@gw.catspoiler.org> Date: Tue, 11 Jul 2017 18:12:58 -0700 (PDT) From: Don Lewis Subject: jemalloc_arena.c:821: Failed assertion: "nstime_compare(&decay->epoc h, &time) <= 0") To: jasone@FreeBSD.org cc: freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jul 2017 01:13:07 -0000 I'm trying to stabilize my new-ish Ryzen package build box. I've run into this error a couple of times: (: jemalloc_arena.c:821: Failed assertion: "nstime_compare(&decay->epoc h, &time) <= 0") most recently today when building llvm40. It seems to happen somewhat randomly. I don't remember seeing it before the jemalloc 5.0.0 import. What does it mean? Any ideas on how I might mitigate the problem? From owner-freebsd-current@freebsd.org Wed Jul 12 01:24:33 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16470DB0076; Wed, 12 Jul 2017 01:24:33 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (dmz-mailsec-scanner-4.mit.edu [18.9.25.15]) (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 A350373222; Wed, 12 Jul 2017 01:24:31 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190f-2fbff70000003f98-41-5965791ad7be Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 7B.D0.16280.A1975695; Tue, 11 Jul 2017 21:19:23 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v6C1JLaD017718; Tue, 11 Jul 2017 21:19:22 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v6C1JI19002367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Jul 2017 21:19:21 -0400 Date: Tue, 11 Jul 2017 20:19:18 -0500 From: Benjamin Kaduk To: Rick Macklem Cc: "freebsd-current@freebsd.org" , "rc@freebsd.org" Subject: Re: small patch for /etc/rc.d/nfsd, bugfix or POLA violation? Message-ID: <20170712011918.GB80947@kduck.kaduk.org> References: <201707092031.v69KVBSn045623@slippy.cwsent.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLIsWRmVeSWpSXmKPExsUixG6noitdmRpp8Owqu8WcNx+YLH6t/stk 8XDZNSYHZo8Zn+azePzevJcpgCmKyyYlNSezLLVI3y6BK2Nx6zbGgibmigMv9rI1MK5k6mLk 5JAQMJF4tGYVkM3FISSwmEnibscsNghnI6PEv4VHGCGcq0wSHT3fWUFaWARUJc4cnAFmswmo SDR0X2YGsUUE1CU2r+4Hs5kFsiWu3f0LZgsLuEnsuLqAEcTmBVr391E7K8TQX4wSLSeuMUEk BCVOznzCAtGsJXHj30ugOAeQLS2x/B8HSJhTIFaiY+M+dhBbVEBZ4u/heywTGAVmIemehaR7 FkL3AkbmVYyyKblVurmJmTnFqcm6xcmJeXmpRbomermZJXqpKaWbGEEhyynJv4NxToP3IUYB DkYlHt6GCymRQqyJZcWVuYcYJTmYlER5d+SnRgrxJeWnVGYkFmfEF5XmpBYfYpTgYFYS4Y19 AFTOm5JYWZValA+TkuZgURLnFddojBASSE8sSc1OTS1ILYLJynBwKEnw6lcADRUsSk1PrUjL zClBSDNxcIIM5wEa7h0NVMNbXJCYW5yZDpE/xajL0fRhyxcmIZa8/LxUKXFeZZBBAiBFGaV5 cHNAqUYie3/NK0ZxoLeEeQ+XA1XxANMU3KRXQEuYgJasyQb5oLgkESEl1cBYda1Fttn9tPZj 1dwjqmJ+Ux8cZKwIjA+8uklY4u1Zab/6tb0ROYE769KO9d1NvFzTcZP/esU1LTY9vpu3Dkmf F1P4nH/z6v1Jn9K4vkxzW1nfMaPf/r9huHO+w7cDEZJcjnmHn55xudgwSUSqueNDlJ1RtELU hXixlNPFcpaKl3TjoiwufFdiKc5INNRiLipOBADkBpt4EAMAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jul 2017 01:24:33 -0000 On Tue, Jul 11, 2017 at 11:48:55AM +0000, Rick Macklem wrote: > Cy Schubert wrote: > > > >How about a warning message + an UPDATING entry + no MFC? And, relnotes = > >yes to say we now support RFC7530 in 12.0? > Sounds fine to me. I'll wait to see if there are more comments. Yes, this seems like the sort of thing best done on a major version boundary and not MFC'd. -Ben From owner-freebsd-current@freebsd.org Wed Jul 12 17:01:49 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E96CD9D7F8; Wed, 12 Jul 2017 17:01:49 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from forward12p.cmail.yandex.net (forward12p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::ba]) (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 48FFB6E7EE; Wed, 12 Jul 2017 17:01:48 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from smtp1m.mail.yandex.net (smtp1m.mail.yandex.net [77.88.61.132]) by forward12p.cmail.yandex.net (Yandex) with ESMTP id E086122E3E; Wed, 12 Jul 2017 20:01:45 +0300 (MSK) Received: from smtp1m.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1m.mail.yandex.net (Yandex) with ESMTP id 2551663C0E22; Wed, 12 Jul 2017 20:01:43 +0300 (MSK) Received: by smtp1m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id nPLxJsHdzM-1JTiVlKc; Wed, 12 Jul 2017 20:01:19 +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.com; s=mail; t=1499878879; bh=6yePZuLwbuPkurQCMzubbLBYDcZzXKWlStZxag1sqNs=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=p82s7jlcUUUd3TwPu0jSdd/kvxhOr2rZKRxsls3GhDib2z7mmwddSFqkWIK19aFwN mWtZ6LS1tHQ0WH1df0jh9W4e/VBh8S5yE3h4DBGJ/baGwN9g0yQrlRAqSixMH0/rRb RM8x9jVDJfVCxHxjLWClUy6we2hMImuRkuq11Bhk= Authentication-Results: smtp1m.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-Suid-Status: 1 1022867361,1 0,1 0,1 0,1 0 Subject: Re: Run binary from test suite To: Ngie Cooper Cc: "freebsd-hackers@freebsd.org" , FreeBSD Current , Kristof Provost References: <5a7ed4ea-de4c-4f6a-e528-9e3c70722d0c@yandex.com> From: Panagiotes Mousikides Message-ID: <536264c1-9caa-48dd-7fb2-dfede17f5e3c@yandex.com> Date: Wed, 12 Jul 2017 17:01:19 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jul 2017 17:01:49 -0000 Den 2017-07-11 kl. 20:05, skrev Ngie Cooper: > On Tue, Jul 11, 2017 at 10:38 AM, Panagiotes Mousikides > wrote: >> (Resending due to moderation.) >> >> Hello! >> >> I'm a Google Summer of Code student, writing some tests for the FreeBSD test >> suite, and putting them under src/tests. I need to run some binaries, >> specifically pfctl. >> >> How should I call pfctl from my test scripts? Should I call it directly and >> let the shell find the binary in the path? Or should I find where the build >> version got created (somewhere under /usr/obj) and call that? How do I find >> where the binary ended up getting created in that case? >> >> Best regards, >> Panagiotes > Hello Panagiotes, > Please call pfctl from $PATH -- don't hardcode the path, ever. > I'll be looking at making "make check" more developer friendly in the > next 3-6 months, so running "make check" from usr.sbin/pf/... will > automatically add a set path/environment which hooks in to *.test.mk. > The goal of this is to simplify developer use for "make check". > Also, if the tests (for whatever reason) aren't going to be > installed alongside pfctl, e.g., tests/sys/pf/... please add 'atf_set > "require.progs" "pfctl"' to the header to ensure that the test is > skipped if/when pfctl isn't installed on the system. > Cheers, > -Ngie > _______________________________________________ > 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" Hi Ngie! Thanks a lot for your reply! I will change the tests to call pfctl from PATH. The tests in question are for the pfctl binary, so I'm going to move them from src/tests/sbin/pfctl to src/sbin/pfctl/tests. Also, how should I utilize 'make check'? What I currently do is 'make' and 'make install' from src/sbin/pfctl/tests, and then 'kyua test' from either the same directory or from /usr/tests/sbin/pfctl. Best regards, Panagiotes From owner-freebsd-current@freebsd.org Wed Jul 12 17:02:18 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 575C3D9D8D1; Wed, 12 Jul 2017 17:02:18 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from forward19p.cmail.yandex.net (forward19p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::aa]) (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 0FDAE6EA50; Wed, 12 Jul 2017 17:02:18 +0000 (UTC) (envelope-from paggas1@yandex.com) Received: from smtp1o.mail.yandex.net (smtp1o.mail.yandex.net [37.140.190.26]) by forward19p.cmail.yandex.net (Yandex) with ESMTP id 553C7216C2; Wed, 12 Jul 2017 20:02:15 +0300 (MSK) Received: from smtp1o.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp1o.mail.yandex.net (Yandex) with ESMTP id B7BC51300996; Wed, 12 Jul 2017 20:02:11 +0300 (MSK) Received: by smtp1o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id BY5aiKunQl-2A90tKHd; Wed, 12 Jul 2017 20:02:10 +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.com; s=mail; t=1499878930; bh=J4Detb1G1GpRZwjo/KNiwsfN944xqr1BtHh7nC/Wy8Y=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=u4RIjkq1BOXfqZ4K3qSuDQROJiLdQYcZbvh3UT+p1L5FZFm65sGSOc9hh59aoTDhL +i5Cx89coiLgpHpuFwhwEUx4tz09oFeMFfhjS23Ifz8HE2iEh5sP6z9+F1JaaYAhqT cE1vGFqJkzTD8o+8ahHcPbJ611ncgTqnllw1eOWw= Authentication-Results: smtp1o.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-Suid-Status: 1 1022867361,1 0,1 0,1 0,1 0 Subject: Re: Run binary from test suite To: Alan Somers Cc: "freebsd-hackers@freebsd.org" , FreeBSD CURRENT , Kristof Provost References: From: Panagiotes Mousikides Message-ID: <8d53af55-1e24-fc2b-fabe-f5e32b8b3255@yandex.com> Date: Wed, 12 Jul 2017 17:02:09 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 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.23 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, 12 Jul 2017 17:02:18 -0000 Den 2017-07-11 kl. 18:51, skrev Alan Somers: > Are you using pfctl at build time or does your ATF test script need > it? I'm assuming the latter. In that case, it's fine to call it > directly. Your PATH will be correctly configured. Don't use > /usr/obj, because that may no longer exist by the time somebody is > running the ATF test. > -Alan I see, thanks a lot for the input! I will change my tests to call pfctl from PATH. Best regards, Panagiotes > > On Tue, Jul 11, 2017 at 11:13 AM, Panagiotes Mousikides > wrote: >> Hello! >> >> I'm a Google Summer of Code student, writing some tests for the FreeBSD test >> suite, and putting them under src/tests. I need to run some binaries, >> specifically pfctl. >> >> How should I call pfctl from my test scripts? Should I call it directly and >> let the shell find the binary in the path? Or should I find where the build >> version got created (somewhere under /usr/obj) and call that? How do I find >> where the binary ended up getting created in that case? >> >> Best regards, >> Panagiotes >> >> _______________________________________________ >> 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 Wed Jul 12 18:09:42 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF712D9F87B for ; Wed, 12 Jul 2017 18:09:42 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BF01571234; Wed, 12 Jul 2017 18:09:42 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v6CI9WSk059429; Wed, 12 Jul 2017 11:09:36 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201707121809.v6CI9WSk059429@gw.catspoiler.org> Date: Wed, 12 Jul 2017 11:09:32 -0700 (PDT) From: Don Lewis Subject: Re: jemalloc_arena.c:821: Failed assertion: "nstime_compare(&decay->epoc h, &time) <= 0") To: jasone@canonware.com cc: jasone@FreeBSD.org, freebsd-current@FreeBSD.org In-Reply-To: <20170712090649.bb0aa3e8d4e745fce515ca48@canonware.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jul 2017 18:09:43 -0000 On 12 Jul, Jason Evans wrote: > On Tue, 11 Jul 2017 18:12:58 -0700 (PDT) > Don Lewis wrote: >> I'm trying to stabilize my new-ish Ryzen package build box. I've run >> into this error a couple of times: >> (: jemalloc_arena.c:821: Failed assertion: >> "nstime_compare(&decay->epoc h, &time) <= 0") most recently today >> when building llvm40. It seems to happen somewhat randomly. I don't >> remember seeing it before the jemalloc 5.0.0 import. >> >> What does it mean? Any ideas on how I might mitigate the problem? > > This assertion verifies that a monotonic time source is not going > backward in time. jemalloc has code for mitigating the effects of > non-monotonic time sources, but that code is only used for time source > APIs that do not promise monotonic time. Interesting ... In my case TSC is being used as the timecounter. I'm not seeing any problems with ntp, and I'm not seeing any "calcru: runtime went backwards" errors in the logs. I should be able to write some test code that specifically looks for this, but this error is pretty rare and there are bigger problems at the moment. From owner-freebsd-current@freebsd.org Wed Jul 12 19:03:17 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86D29DA0B8A; Wed, 12 Jul 2017 19:03:17 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 57EAF733D1; Wed, 12 Jul 2017 19:03:17 +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 9F805A778; Wed, 12 Jul 2017 19:03:16 +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 5EE7A98B9; Wed, 12 Jul 2017 19:03:15 +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 L8-6k8Mzl3Nz; Wed, 12 Jul 2017 19:03:10 +0000 (UTC) Subject: Re: Recent reports of needing to avoid META_MODE for head kernel builds for updates: a preliminary investigation DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 3D57A98B4 To: Mark Millard , FreeBSD Toolchain , FreeBSD Current References: <5D970E60-5F3A-4580-9E7F-5CFD96361546@dsl-only.net> From: Bryan Drewery Organization: FreeBSD Message-ID: Date: Wed, 12 Jul 2017 12:03:06 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <5D970E60-5F3A-4580-9E7F-5CFD96361546@dsl-only.net> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8ewvIq008DUvuc5pSPvBWAXhwd0652FoD" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jul 2017 19:03:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --8ewvIq008DUvuc5pSPvBWAXhwd0652FoD Content-Type: multipart/mixed; boundary="fXSRUwhLID2VM1iuMXO4ID2pHM1FEutTk"; protected-headers="v1" From: Bryan Drewery To: Mark Millard , FreeBSD Toolchain , FreeBSD Current Message-ID: Subject: Re: Recent reports of needing to avoid META_MODE for head kernel builds for updates: a preliminary investigation References: <5D970E60-5F3A-4580-9E7F-5CFD96361546@dsl-only.net> In-Reply-To: <5D970E60-5F3A-4580-9E7F-5CFD96361546@dsl-only.net> --fXSRUwhLID2VM1iuMXO4ID2pHM1FEutTk Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 6/26/17 8:11 PM, Mark Millard wrote: > For an example of the recent reports: >=20 > David Wolfskill david at catwhisker.org wrote on > Mon Jun 26 12:44:20 UTC 2017 : >=20 >> On Mon, Jun 26, 2017 at 03:29:59PM +0300, Konstantin Belousov wrote: >>> ... >>> >>> Hmmm..... >>> >>> As if computer tries to say you, do not use meta mode. >> >> For building the kernel, on head as of some commit after r320307 (but >> by r320324). > While there are other kernel issues going on I decided to try to > investigate the difference in meta mode incremental build results > vs. full rebuild. This was a bug with buildkernel with META_MODE using filemon (the default with META_MODE). It is fixed in r320919. I recommend doing another buildkernel after that and installing to ensure everything gets updated. --=20 Regards, Bryan Drewery --fXSRUwhLID2VM1iuMXO4ID2pHM1FEutTk-- --8ewvIq008DUvuc5pSPvBWAXhwd0652FoD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJZZnJrAAoJEDXXcbtuRpfPyVUH/3Z6fjp5rWI045jdTSsqVtyh T/o2EQX+xlzayE/QwwdfRRnFF6CpoW8is1yBb+BmrcaCYIz5uGlCLfMfpa8RyVF5 AUagy+8acgQrN33S2g0pGMs3EsVcxeHuM8+x3BdqRxCf3IFOXlkT8IDEtg2mHK71 7sNoMOYCQ4QUpQ5S/W1NTfbvgKi7aS8kzyl2POLbqkS6X1AmIs4hbVKXD8hJLPn2 zF0xnLmwOJepsKCmUNb9+QXZatqfPq1gVASZ5Qw5XskyY/ONx/U3dIP401bma/Rp MJEUqcN0U7Izr4hm1JyS7PHQw0OS2AwHLOeaIFe3qCMMk/pKW7uhwY0noQ3b5kE= =kD2q -----END PGP SIGNATURE----- --8ewvIq008DUvuc5pSPvBWAXhwd0652FoD-- From owner-freebsd-current@freebsd.org Wed Jul 12 19:03:41 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B33DDA0C2E for ; Wed, 12 Jul 2017 19:03:41 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 700D6734EF for ; Wed, 12 Jul 2017 19:03:41 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6CA48DA0C2D; Wed, 12 Jul 2017 19:03:41 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C536DA0C2C for ; Wed, 12 Jul 2017 19:03:41 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 357C9734EA; Wed, 12 Jul 2017 19:03:41 +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 668CBA81B; Wed, 12 Jul 2017 19:03:40 +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 A286898C8; Wed, 12 Jul 2017 19:03:39 +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 l0vEUZrFxvS2; Wed, 12 Jul 2017 19:03:35 +0000 (UTC) Subject: Re: Panic on boot after upgrade from r320827 -> r320869 DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com D3BE498C1 To: Warner Losh , Michael Butler Cc: David Wolfskill , FreeBSD Current References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> From: Bryan Drewery Organization: FreeBSD Message-ID: <887bdf09-a40e-8b7e-9821-1742c87ae27d@FreeBSD.org> Date: Wed, 12 Jul 2017 12:03:34 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="MD1g0QBJ7KEjwO3cUWEpeLrC4jh0gXhQ7" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jul 2017 19:03:41 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MD1g0QBJ7KEjwO3cUWEpeLrC4jh0gXhQ7 Content-Type: multipart/mixed; boundary="mwlgjbaaV1Rn1srDLd29pWKAttgTM4xiq"; protected-headers="v1" From: Bryan Drewery To: Warner Losh , Michael Butler Cc: David Wolfskill , FreeBSD Current Message-ID: <887bdf09-a40e-8b7e-9821-1742c87ae27d@FreeBSD.org> Subject: Re: Panic on boot after upgrade from r320827 -> r320869 References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> In-Reply-To: --mwlgjbaaV1Rn1srDLd29pWKAttgTM4xiq Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 7/11/17 10:13 AM, Bryan Drewery wrote: > On 7/11/17 10:09 AM, Warner Losh wrote: >> Plus we know we have at least one bug in meta-mode rebuilding since no= t >> everything is being rebuilt that should be across this change. >=20 > Yes I'm looking into that. >=20 This was a bug with buildkernel with META_MODE using filemon (the default with META_MODE). It is fixed in r320919. I recommend doing another buildkernel after that and installing to ensure everything gets updated. --=20 Regards, Bryan Drewery --mwlgjbaaV1Rn1srDLd29pWKAttgTM4xiq-- --MD1g0QBJ7KEjwO3cUWEpeLrC4jh0gXhQ7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJZZnKGAAoJEDXXcbtuRpfPN+0H/RjofjqGpDZisId9KkhPzH5a CUH+Zey/qHH4VFdaklYZrrq8dRAWdcCbmO9PRw9VOtSgewGL4Cshq4a1Bjrn2GeV gMC9j1Ecag2X5LELTDgOMacNl5ZNQHpxRb67BfDbF6ljKQ9rFBXBr5bdQQ3yAgm6 blAwY26Qywd5gCGZi7vO3YbzBDeNIa+b6JE3UJ4RouhPF6HtVBw74i09euKTE4QF GB+JjtX9MTN0HOH96HzkwHc+AB9dQKlm5lKGFrGl1jjRnftWbrOcIylYKIgQHEAG KkweiKUMxRwx3RT/kKm8HSDITJ5aokUTxEdgfTVD6AWrwh1Gng/ZtFXuoLyW1Qg= =H2FU -----END PGP SIGNATURE----- --MD1g0QBJ7KEjwO3cUWEpeLrC4jh0gXhQ7-- From owner-freebsd-current@freebsd.org Wed Jul 12 19:43:55 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6D91DA1BC2; Wed, 12 Jul 2017 19:43:55 +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 241F874BD7; Wed, 12 Jul 2017 19:43:54 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.71.3]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LbM2k-1dxWDw1jzu-00ktnw; Wed, 12 Jul 2017 21:43:46 +0200 Date: Wed, 12 Jul 2017 21:43:34 +0200 From: "O. Hartmann" To: FreeBSD CURRENT , FreeBSD Questions Subject: Inter-VLAN routing on CURRENT: any known issues? Message-ID: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/hakecsp8FO_KOq4QSAYnpJl"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:unxbJaZ8sAx0ZhWd4l1EvuV1X00rsh8BW6cvKtD/dd3F6NI0qD2 0I6R89BjuFQk1W1oyk3av6dPc2Q4D3a6FmoLcvaf+5zjkLZoHgvv+7tp9PA0WhF/vS/arfm sqjOGEwgte1WKqHJlpkAiDsjnJFU7HlrWEhVUbpUHXY2UEMQewYHSxGyt5ojNG+YJzvBjEe ud96Z3lbL8uZv4y2f+2EA== X-UI-Out-Filterresults: notjunk:1;V01:K0:pS61UUN7p2Q=:qa/4yIdC3DH9a1KAPOnHm4 R95LAW5wxE+4HbnP6QxEFwafpMgbzbLI0+rG1mdQEn5d9X3maOl7Zr9rEnih4JEl7a9462d0e e508jboTWpZ440ocLNMkIqoWnkr5SNT5Y5WTv+8oze4PjQ3bbqbWzQ6Z4aSUg1Nfp0w+ijaj8 5n2YAQpP3gC7VR2y7OVJwEPX6Lfg8cEUc9XlZ6J3+N5kdNjO+ntEYtWvLh7OevP0YyH94R1Hf uKLYjcRFmpWhrCUgU4a5y5TrPU1ehj691wrPdqxCxpfi3kRow+oUVEnn+Q2L2chorfLlCEP+v Dme6NzjeddkPDbazD8fgi7ikusBGniJOc71fez7xAejrfKiqd6PNOtPEH51BzW9qWKiaoiIEv 4PLnEOwfqfDjz5VCEn8bfrOTCKOo4nFrdbYuIT+0LNC+GFOXBwPZuNbuO2HKih0PsdaGf50qF n57qYO83lV16tecX0hD6D8iqtQMAWsZDAZ6MVD8dDXBXMD6MOoIv/aNgzB/NVCtJkTpKtaqd1 aXhEwI/hZqUoaOSpdRyWbCUOPpEuvVwCO/SjN1vCRObSDJ3cTJiilo3WPeMqqFpdqQQVaQycj ah34liJE6hVqnJWcRG50kccp7CkPsEVa2FR54HVE5HZajQdAlvF9T+ge3NS1irMyaDOwRAdFb E0T/L63pCrXy1EAA3r1LDRFB8VQ9YQ14m0GUsIsUtz2c14EnooBhYUAnEDbLMPCJ7DJTokygG BgkquYVBWOd6BD7CmG7oRVBhrqUaETGFI0kYhF2gIB10qq/xuPtCZBf1JVo= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jul 2017 19:43:55 -0000 --Sig_/hakecsp8FO_KOq4QSAYnpJl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Since a couple of days for now I fail to setup VLAN trunking on a FreeBSD 1= 2-CURRENT box (FreeBSD 12.0-CURRENT #9 r320913: Wed Jul 12 17:26:22 CEST 2017 amd64) whic= h is based on a PCEngines APU 2C4 board with three Intel i210 NICs. igb0 is connected to a Allnet VDSL modem via tun0/ppp. igb2 is unused. igb1 is considered "multihomed" and comprises several VLANs: [/etc/rc.conf] gateway_enable=3D"YES" ... ifconfig_igb1=3D"up" vlans_igb1=3D"1000 2 3 10 66 100" ifconfig_igb1_1000=3D"inet 192.168.0.1/24" create_args_igb1_1000=3D"vlanpcp 7" ifconfig_igb1_2=3D"inet 192.168.2.1/24" ifconfig_igb1_3=3D"inet 192.168.3.1/24" ifconfig_igb1_10=3D"inet 192.168.10.1/24" ifconfig_igb1_66=3D"inet 192.168.66.1/24" ifconfig_igb1_100=3D"inet 192.168.100.1/24" ... VLAN 1000 is considered my internal network, the others are for special pur= pose, e.g. VLAN 2 is for VoIP equiment. After booting (a customised) kernel the router shows the following settings: root@gate:~ # netstat -Warn Routing tables Internet: Destination Gateway Flags Use Mtu Netif Exp= ire default 111.111.111.111 US 570 1492 tun0 111.111.111.111 link#12 UHS 0 1492 tun0 22.33.44.55 link#12 UHS 0 16384 lo0 127.0.0.1 link#4 UH 115 16384 lo0 192.168.0.0/24 link#2 U 13930 1500 igb1.1000 192.168.0.1 link#2 UHS 0 16384 lo0 192.168.2.0/24 link#7 U 1 1500 igb1.2 192.168.2.1 link#7 UHS 0 16384 lo0 192.168.3.0/24 link#8 U 0 1500 igb1.3 192.168.3.1 link#8 UHS 0 16384 lo0 192.168.10.0/24 link#9 U 0 1500 igb1.10 192.168.10.1 link#9 UHS 0 16384 lo0 192.168.66.0/24 link#10 U 0 1500 igb1.66 192.168.66.1 link#10 UHS 0 16384 lo0 192.168.100.0/24 link#11 U 0 1500 igb1.100 192.168.100.1 link#11 UHS 0 16384 lo0 All interfaces (including vlan) show "UP" in their status.=20 sshd, named and services are bound on the router to 192.168.0.1, which is i= ts IP. The router's igb1-NIC is physically connected to a SoHo switch Netgear GS11= 0TP. Its config in short according to the manual (http://www.netgear.com/support/product/GS110TP.aspx#docs , chapter 3, pagu= s 84) is as follows. Port gs9 is considered the trunk/etherchannel port (via GBIC 1 Gig). Accord= ingly to my setup, the VLANs 1,2,3 (switch-native),10, 66, 100 and 1000 are defined. In= VLAN membership configuration for VLAN 1, only port g1 is marked "U", this is my maintenance port. For VLAN 1000 ports g1-g4 are "U" untagged, g9 is "T" tag= ged. For VLAN 2, port g7 is "U", g8 is "T" (the VoIP telephone has vlan tag 2) and the tr= unk is g9 "T". VLAN 100 occupies port g5 "U", port g9 is "T". The other VLANs are unused a= t the moment. According to handbook section "Port VLAN ID Configuration" (PVID), g1-g4 ar= e PVID 1000, Accept. Frame Type is "Admit All" and Ingress Filtering is "disabled". The = settings for the other so called "access ports" are accordingly.=20 g9, the trunk port, has PVID 1, Admit all, Ingress Filtering is disabled. O= ther configurations are mostly as the switch is set-up after factory reset. On ports g1 - g4 I have a dual-port NIC'ed server (one port vlan 1000, othe= r vlan 100) running and a notebook, which I can configure freely. Now the FUN PART: =46rom any host in any VLAN I'm able to ping hosts on the wild internet via t= heir IP, on VLAN 1000 there is a DNS running, so I'm also able to resolv names like goo= gle.com or FreeBSD.org. But I can NOT(!) access any host via http/www or ssh.=20 I also can not access a host's sshd in the neighbour VLAN routed via the ro= uter, say from a host/server on VLAN 1000 to a host/VoIP telephone on VLAN 2. I can p= ing the hosts from each VLAN to the other (so ICMP flows), but any IP service seems to ge= t sacked by a black hole. From hosts on VLAN 1000 I can access the router's sshd (192.168= .0.1). More disturbing: from the router itself, I'm able to access the sshd of eac= h host on each VLAN, i.e. VLAN 1000, VLAN 2 (VoIP), but when setting up a notebook (F= reeBSD 12-CURRENT of the same or similar revision) in VLAN 2 or VLAN 100 or VLAN 6= 6 with SSHD listening on all interfaces, I'm able to connect to that system. Also, from= the router itself, I can ping any host on any VLAN and the internet (routed via tun0/i= gb0/modem). =46rom any host on any VLAN, I can ping the router, I can ping the world, I c= an ping other hosts on other VLANs. Obviously, ICMP is routed. Any attempt to access a service from a host in any VLAN to a hosts's servic= e on another VLAN fails. IP is not routed and I do not see why. The kernel is compiled with in-kernel IPFW. No matter what I do, either ipf= w "OPEN" or using my ruleset which works in the special case I describe later, routing = through VLANs seems not to work for any IP packet! Using tcpdump on the router while trying to ssh into another host, I see th= e initial [S] marked attempt to connect, i.e. 192.168.0.128 > 192.168.2.50: [S]. Onece th= e packet has been sent from sender to the router, I never is passed to the recipient.=20 Before I start attempting making weird speculations, I must confess that us= ing tcpdump and other network tools is not my favourite and I'm quite new/novice on tha= t field.=20 I need advice. Also, I need to know whether the setup I showed is working o= r whether I make a serious and stupid mistake (maybe due to not having understood FreeB= SD's routing or routing at all).=20 If on the setup shown above the VLAN is dumped and when I use only igb1 as = the "vanilla" NIC, everything works smoothly - execpt the fact I do not have network sepa= rations. But it shows me that in principle the complete setup isn't complete bullshit. F= rom that persepctive, even just changing igb1 to igb1.1000 (a tagged VLAN), it shoul= d work. But it doesn't. I'm not sure whether IPFW is the culprit or not or anothe knob, for the rec= ord, these settings are for ipfw in the kernel: [...] options NETGRAPH # netgraph(4) system options NETGRAPH_IPFW options NETGRAPH_NETFLOW options NETGRAPH_ETHER options NETGRAPH_NAT options NETGRAPH_DEVICE options NETGRAPH_PPPOE options NETGRAPH_SOCKET options NETGRAPH_ASYNC options NETGRAPH_TEE # IPFW firewall options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=3D0 options IPFIREWALL_NAT #ipfw kernel nat support options LIBALIAS #ipfw kernel nat support options IPDIVERT # NAT options DUMMYNET # traffic shaper # #options IPFIREWALL_DEFAULT_TO_ACCEPT [...] and from sysctl: kern.features.ipfw_ctl3: 1 net.link.ether.ipfw: 0 net.link.bridge.ipfw: 0 net.link.bridge.ipfw_arp: 0 So, if someone is willing to give me some hints, I'd be glad to hear from y= ou. I'm starting getting insane over this problem :-( Kind regards and thanks for your patience, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/hakecsp8FO_KOq4QSAYnpJl Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWWZ75gAKCRDS528fyFhY lFDtAgCQfzw2Q1HpqjWeMDZDW52syCjmmcheUuOGUqKgikc+Dr1WYUMvhVM+FCkJ Thwef0zCavLdiTbUyf70hs8t3K24AfsHzAn3QMxr+XSgFsyATR1GEmPOjOF3tF/N sfMYty1efOBxW1FwjecyzvSoLu2yEyENt7ZnavjLTRYE8j5xn7tr =t2CV -----END PGP SIGNATURE----- --Sig_/hakecsp8FO_KOq4QSAYnpJl-- From owner-freebsd-current@freebsd.org Wed Jul 12 20:20:57 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B8EDDA2C8A for ; Wed, 12 Jul 2017 20:20:57 +0000 (UTC) (envelope-from peter@wemm.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 73DED76631 for ; Wed, 12 Jul 2017 20:20:57 +0000 (UTC) (envelope-from peter@wemm.org) Received: by mailman.ysv.freebsd.org (Postfix) id 72F95DA2C87; Wed, 12 Jul 2017 20:20:57 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 727F0DA2C86 for ; Wed, 12 Jul 2017 20:20:57 +0000 (UTC) (envelope-from peter@wemm.org) Received: from smtp2.wemm.org (smtp2.wemm.org [IPv6:2001:470:67:39d::78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp2.wemm.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5F27676630 for ; Wed, 12 Jul 2017 20:20:57 +0000 (UTC) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (canning.wemm.org [192.203.228.65]) by smtp2.wemm.org (Postfix) with ESMTP id B550E6AE for ; Wed, 12 Jul 2017 13:20:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=m20140428; t=1499890856; bh=FTiHsZG8g9Vk3rMKiomHgArf86ZZ4ehFLiWJ6tp/NuQ=; h=From:To:Subject:Date; b=KTveJgJvscFHloOvaqDeJhhscE5KrNTjgngmwWfDU0pfpTGRsreW7VGisoqvMq0tF Hbh8S5eHzal6SZaDZkGy2htQgvHE2aQFQ8bsxPzOOM0SqugKsuxJwADZaUZxy1N85e YW7enmztMCqP8PPkShdLWY9g2x9lBbOSUwIr7pRI= From: Peter Wemm To: Current Subject: Caveat emptor: Beware of ZFS on HEAD Date: Wed, 12 Jul 2017 13:20:55 -0700 Message-ID: <2830123.MIUbdsJfkU@overcee.wemm.org> User-Agent: KMail/4.14.10 (FreeBSD/12.0-CURRENT; KDE/4.14.10; amd64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2313450.qoWcZDlQWb"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jul 2017 20:20:57 -0000 --nextPart2313450.qoWcZDlQWb Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" We mostly run HEAD in the freebsd.org cluster. Sometime in the last fe= w weeks=20 an ugly zfs problem has surfaced. If a redundant volume is degraded, zf= s=20 panics on boot. If a drive fails while running, or is manually put off= line, zfs=20 panics the same way. I do not have a smoking gun, but I am suspicious of the June 28th commi= ts=20 (starting at r320156) and their follow-ups. eg: r320452. https://bugs.freebsd.org/220691 I believe single disk systems will *not* be affected by this - the pani= c only=20 happens when a raidz (and presumably mirror) degrades. Your laptop etc= should=20 be fine. I apologize for being vague - I do not know more. Folks running HEAD sh= ould=20 take appropritate precautions (eg: keeping a known-good kernel.old and = modules=20 around). This is always advisable when running HEAD anyway, particular= ly so=20 now. For us, a kernel.old from June 18th worked fine. =2D-=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI= 6FJV UTF-8: for when a ' or ... just won\342\200\231t do\342\200\246 --nextPart2313450.qoWcZDlQWb Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEBgrA0Vr/vfNVuPoUNdaXCeyAngQFAllmhKcACgkQNdaXCeyA ngQbVwgAwFUY7+xntVLNfUgK3SchTvxkDCMXO0YecLmdFHCtWSeuxpvV+EUJoOs7 hnZXy7IxRTh92F9g3dRh4M9ifsgE7ubgD/o/vcDR0uprsBQVEUECTaVL9sTRwm6A 9eyVKHnfiB3YmT7GdQCW45zyYotXLJ6vDb4m322V8tgonMv9k1lmIqQfYy6tpFyO YOwlVWBEc+9XcjQIys5t0ZkNinzv0wP+rv89fYBRsx1W4byY33oi6KikQ2ccT7VB eBM509hLoaFlSgcxIe+kZ6pssMAEqhQ+ADD7uggnTMylnxNwH0zflV0u42jOZiQX 1aCc10De/RvTfj4jFXCFRfxFV4qptw== =XwTW -----END PGP SIGNATURE----- --nextPart2313450.qoWcZDlQWb-- From owner-freebsd-current@freebsd.org Wed Jul 12 22:37:56 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0DCCDA69B0 for ; Wed, 12 Jul 2017 22:37:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-71.reflexion.net [208.70.210.71]) (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 8908E7A897 for ; Wed, 12 Jul 2017 22:37:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29683 invoked from network); 12 Jul 2017 22:31:15 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 12 Jul 2017 22:31:15 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.1) with SMTP; Wed, 12 Jul 2017 18:31:15 -0400 (EDT) Received: (qmail 18222 invoked from network); 12 Jul 2017 22:31:15 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 12 Jul 2017 22:31:15 -0000 Received: from [192.168.1.114] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 6861AEC8936; Wed, 12 Jul 2017 15:31:14 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: dump trying to access incorrect block numbers? From: Mark Millard In-Reply-To: Date: Wed, 12 Jul 2017 15:31:13 -0700 Cc: FreeBSD Current , linimon@FreeBSD.org Content-Transfer-Encoding: 7bit Message-Id: References: <73E92033-CB2F-404C-8B3F-736EF09AA9F7@dsl-only.net> To: peter@rulingia.com, Michael Butler , "Rodney W. Grimes" X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Jul 2017 22:37:57 -0000 I have extracted material from the list-exchanges related to this and submitted: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220693 against the kernel for the issue. I placed emphasis on the SSD-trim related "freeing free block" panics that "fsck -B" can lead to after it gets the g_vfs_done messages for unclean ufs file systems but first noted that: mksnap_ffs /.snap2 was enough to get the g_vfs_done messages. I figured that the nastiest and most important known consequences were "fsck -B" being broken for unclean ufs file systems and having later panics trying to trim based on how it is broken. I did also mention dump as producing the messages. I referenced. . . > See also the exchange of list submittals associated > with: > > https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066505.html > > and: > > https://lists.freebsd.org/pipermail/freebsd-current/2017-July/066508.html === Mark Millard markmi at dsl-only.net From owner-freebsd-current@freebsd.org Thu Jul 13 13:15:15 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CCA2DA25E0; Thu, 13 Jul 2017 13:15:15 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward4o.cmail.yandex.net (forward4o.cmail.yandex.net [IPv6:2a02:6b8:0:1a72::289]) (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 C1969776A4; Thu, 13 Jul 2017 13:15:14 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp2j.mail.yandex.net (smtp2j.mail.yandex.net [IPv6:2a02:6b8:0:801::ac]) by forward4o.cmail.yandex.net (Yandex) with ESMTP id C510220677; Thu, 13 Jul 2017 16:15:02 +0300 (MSK) Received: from smtp2j.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp2j.mail.yandex.net (Yandex) with ESMTP id DF3123EC0F75; Thu, 13 Jul 2017 16:15:00 +0300 (MSK) Received: by smtp2j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id Z9qNUibgxw-Ex0Sa5rQ; Thu, 13 Jul 2017 16:14:59 +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=1499951699; bh=lI4DhTat2PvGVy7CxSqDLMwksZ329a00wffknnl0l/U=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=soD35o8jNWNu/elsQYJljUo3jh9vTKLUP7SVx9Mfx4aVfQpb1PJAuqvOObstlD8vX rWokZmz3xiPu0IRcH+j70mwkXqE1AP+5Q61DnhtQKRkui0ttLbYAJdMXxzECQZIpFJ oyD5v5AdxCw4Ehv8PFeHrKW1bPgx4hIOXu6vdu5M= Authentication-Results: smtp2j.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0 Subject: Re: Inter-VLAN routing on CURRENT: any known issues? To: "O. Hartmann" , FreeBSD CURRENT , FreeBSD Questions References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: Date: Thu, 13 Jul 2017 16:12:06 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CueFjnWV1aGbTRKWeDcjoHWXWPmehqWKG" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Jul 2017 13:15:15 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --CueFjnWV1aGbTRKWeDcjoHWXWPmehqWKG Content-Type: multipart/mixed; boundary="Qo7f7gLTuFsLwUxFqH9iXR71pR9Qb4nOo"; protected-headers="v1" From: "Andrey V. Elsukov" To: "O. Hartmann" , FreeBSD CURRENT , FreeBSD Questions Message-ID: Subject: Re: Inter-VLAN routing on CURRENT: any known issues? References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> --Qo7f7gLTuFsLwUxFqH9iXR71pR9Qb4nOo Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 12.07.2017 22:43, O. Hartmann wrote: > Now the FUN PART: >=20 > From any host in any VLAN I'm able to ping hosts on the wild internet v= ia their IP, on > VLAN 1000 there is a DNS running, so I'm also able to resolv names like= google.com or > FreeBSD.org. But I can NOT(!) access any host via http/www or ssh.=20 You have not specified where is the NAT configured and its settings is matters. VLANs work on the layer2, they do not used for IP routing. Each received packet loses its layer2 header before it gets taken by IP stack. If an IP packet should be routed, the IP stack determines outgoing interface and new ethernet header with VLAN header from this interface is prepended= =2E What I would do in your place: 1. Check the correctness of the switch settings. - on the router use tcpdump on each vlan interface and also directly on igb1. Use -e argument to see ethernet header. Try ping router's IP address from each vlan, you should see tagged packet on igb1 and untagged on corresponding vlan interface. 2. Check the correctness of the routing settings for each used node. - to be able establish connection from one vlan to another, both nodes must have a route to each other. 3. Check the NAT settings. - to be able to connect to the Internet from your addresses, you must use NAT. If you don't have NAT, but it somehow works, this means that some device does the translation for you, but it's configuration does not meet to your requirements. And probably you need to translate prefixes configured for your vlans independently. --=20 WBR, Andrey V. Elsukov --Qo7f7gLTuFsLwUxFqH9iXR71pR9Qb4nOo-- --CueFjnWV1aGbTRKWeDcjoHWXWPmehqWKG 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/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAllncaYACgkQAcXqBBDI oXqW8Af9EWg6ZQlYUzJNA1LrHwfidVi2IOlZz+Qs3sS3yi9LYXTTzG3zRQUXMihl eLrhUAvrS3ro7PRLPyJ5gkueb30WXKCs3ZVyx2KSHLqQAqNHNLuFhwhDrQiMEoBg IKNMinDa2YUSdTpEbH0+2VPsdrigtK69wglqr7LOJsn04KCJFx5Gj6krwFgXQYXe PCMiGwycRSbMWk9YwzNETmoD1/0JRJO4PfUOvasGSOm4DdSqLX2eF894CZScTp+o whxTM35yfbuKGZQkpSRifDJ0kJofSfsVdG8pfMDY7TRKyD5SrG5PyOSDebozOE7o X+M8ooNa7DHg3obdXmgJYe/TmA4dGg== =MKWA -----END PGP SIGNATURE----- --CueFjnWV1aGbTRKWeDcjoHWXWPmehqWKG-- From owner-freebsd-current@freebsd.org Fri Jul 14 11:47:13 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5795D9EF09; Fri, 14 Jul 2017 11:47:13 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 598023303; Fri, 14 Jul 2017 11:47:12 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1dVyzf-001LP5-7I>; Fri, 14 Jul 2017 13:42:47 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1dVyze-003z22-Sx>; Fri, 14 Jul 2017 13:42:47 +0200 Date: Fri, 14 Jul 2017 13:42:41 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Cc: "Andrey V. Elsukov" , "O. Hartmann" , FreeBSD Questions Subject: Re: Inter-VLAN routing on CURRENT: any known issues? Message-ID: <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> Organization: FU Berlin X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: 87.138.105.249 X-Mailman-Approved-At: Fri, 14 Jul 2017 12:00:52 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Jul 2017 11:47:13 -0000 Am Thu, 13 Jul 2017 16:12:06 +0300 "Andrey V. Elsukov" schrieb: > On 12.07.2017 22:43, O. Hartmann wrote: > > Now the FUN PART: > >=20 > > From any host in any VLAN I'm able to ping hosts on the wild internet v= ia > > their IP, on VLAN 1000 there is a DNS running, so I'm also able to reso= lv > > names like google.com or FreeBSD.org. But I can NOT(!) access any host = via > > http/www or ssh. =20 >=20 > You have not specified where is the NAT configured and its settings is > matters. I use in-kernel NAT. IPFW is performing NAT. In firewall type "OPEN" from t= he vanilla rc.conf, IPFW has instance "nat 123" which provides then NAT. >=20 > VLANs work on the layer2, they do not used for IP routing. Each received > packet loses its layer2 header before it gets taken by IP stack. If an > IP packet should be routed, the IP stack determines outgoing interface > and new ethernet header with VLAN header from this interface is prepended. Since all VLANs are on the same NIC on that router, they should only differ= in the VLAN tag. >=20 > What I would do in your place: > 1. Check the correctness of the switch settings. > - on the router use tcpdump on each vlan interface and > also directly on igb1. Use -e argument to see ethernet header. > Try ping router's IP address from each vlan, you should see tagged > packet on igb1 and untagged on corresponding vlan interface. >=20 > 2. Check the correctness of the routing settings for each used node. > - to be able establish connection from one vlan to another, both nodes > must have a route to each other. >=20 > 3. Check the NAT settings. > - to be able to connect to the Internet from your addresses, you must > use NAT. If you don't have NAT, but it somehow works, this means > that some device does the translation for you, but it's > configuration does not meet to your requirements. And probably you > need to translate prefixes configured for your vlans independently. >=20 According to 1): I consider the settings of the switch now as correct. I have no access to t= he router right now. But I did short experiments yesterday evening and it is weird: loged in on thr router, I can ping every host on any VLAN, so ICMP travel from the router the right way to its destination and back. =46rom any host on any VLAN that is "trunked" through the router, I can ping = any other host on any other VLAN, preferrably not on the same VLAN. By cutting = off the trunk line to the router, pinging stops immediately. =46rom any host on any VLAN I can ping any host which is NATed on the outside world. =46rom the router itself, I can ssh into any host on any VLAN providing ssh service. That said, according to question 3), NAT is considered to be setup correctly. Now the strange things: Neither UDP, nor TCP services "flow" from hosts on = one VLAN to hosts on a different VLAN. Even ssh doens't work.=20 When loged in onto the router, I can't "traceroute" any host on any VLAN. According to question 2), the ability to ping from, say, a host on VLAN 100= 0 to another host on VLAN 2 passing through the router would indicate that both sides know their routes to each other. Or am I wrong? I got words from Sean bruno that there might be a problem with the Intel i2= 10 chipset in recent CURRENT - and the hardware on the PCEngine APU 2C4 is thr= ee i210. I'm aware of the problem since r320134 (the oldest CURRENT I started experimenting with the VLAN trunking). I hope it might be a problem with the driver, otherwise I have fully misunderstood FreeBSD's network abilities and techniques :-( I'll provide tcpdump data later. Kind regards, Oliver=20 --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). From owner-freebsd-current@freebsd.org Fri Jul 14 12:03:42 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE0DFD9FFAF; Fri, 14 Jul 2017 12:03:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward5h.cmail.yandex.net (forward5h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::15]) (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 90602632B7; Fri, 14 Jul 2017 12:03:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp4p.mail.yandex.net (smtp4p.mail.yandex.net [95.108.252.166]) by forward5h.cmail.yandex.net (Yandex) with ESMTP id 8BC96210F2; Fri, 14 Jul 2017 15:03:31 +0300 (MSK) Received: from smtp4p.mail.yandex.net (localhost.localdomain [127.0.0.1]) by smtp4p.mail.yandex.net (Yandex) with ESMTP id 0ED3A65011BD; Fri, 14 Jul 2017 15:03:27 +0300 (MSK) Received: by smtp4p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id u1y8D25su2-3Qa4MN5M; Fri, 14 Jul 2017 15:03:26 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1500033806; bh=/99GvL//BUH+lze/IsxFJOR1AqSWy9p+/OgV2jDNW7Q=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=SSpCQRFQlGnozB/ftWGhQCfUoMT6YbAtAzj1/Hz941ZXEMppxPv1VBcsuMLydMIhP 9YhPHdPDiWL2pTe+P361toPO8QFSHGHlt8+A98aqSDDiyc4sdIur5wc7JbC9nfXr3i UBHXe7GiXc7/eaw4ylZ0UJa09LvVmeG3g//XTG8w= Authentication-Results: smtp4p.mail.yandex.net; dkim=pass header.i=@yandex.ru X-Yandex-Suid-Status: 1 0,1 0,1 0,1 0 Subject: Re: Inter-VLAN routing on CURRENT: any known issues? To: "O. Hartmann" , FreeBSD CURRENT Cc: "O. Hartmann" , FreeBSD Questions References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Message-ID: Date: Fri, 14 Jul 2017 15:00:30 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="TXHdgUq6MEvt6OL3RlEmnGILovVvSBmw9" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Jul 2017 12:03:43 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --TXHdgUq6MEvt6OL3RlEmnGILovVvSBmw9 Content-Type: multipart/mixed; boundary="NH8mmNxt8NVIXXsa6qm9RF0ES8NfiqlBV"; protected-headers="v1" From: "Andrey V. Elsukov" To: "O. Hartmann" , FreeBSD CURRENT Cc: "O. Hartmann" , FreeBSD Questions Message-ID: Subject: Re: Inter-VLAN routing on CURRENT: any known issues? References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> --NH8mmNxt8NVIXXsa6qm9RF0ES8NfiqlBV Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 14.07.2017 14:42, O. Hartmann wrote: > I use in-kernel NAT. IPFW is performing NAT. In firewall type "OPEN" fr= om the > vanilla rc.conf, IPFW has instance "nat 123" which provides then NAT. I never used default config types for firewall, so, it would be nice to see what rules do you have. # ipfw show # ipfw nat show config >> VLANs work on the layer2 > According to 1): >=20 > I consider the settings of the switch now as correct. I have no access = to the > router right now. But I did short experiments yesterday evening and it = is > weird: loged in on thr router, I can ping every host on any VLAN, so IC= MP > travel from the router the right way to its destination and back. >=20 > From any host on any VLAN that is "trunked" through the router, I can p= ing any > other host on any other VLAN, preferrably not on the same VLAN. By cutt= ing off > the trunk line to the router, pinging stops immediately. >=20 > From any host on any VLAN I can ping any host which is NATed on the out= side > world. >=20 > From the router itself, I can ssh into any host on any VLAN providing s= sh > service. That said, according to question 3), NAT is considered to be s= etup > correctly. >=20 > Now the strange things: Neither UDP, nor TCP services "flow" from hosts= on one > VLAN to hosts on a different VLAN. Even ssh doens't work.=20 > When loged in onto the router, I can't "traceroute" any host on any VLA= N. This is most likely due to the problem with firewall rules. If you set net.inet.ip.firewall.enable=3D0, does it solve the problem wit= h TCP/UDP between hosts on a different VLANs? > According to question 2), the ability to ping from, say, a host on VLAN= 1000 to > another host on VLAN 2 passing through the router would indicate that b= oth > sides know their routes to each other. Or am I wrong? Yes. > I got words from Sean bruno that there might be a problem with the Inte= l i210 > chipset in recent CURRENT - and the hardware on the PCEngine APU 2C4 is= three > i210. I'm aware of the problem since r320134 (the oldest CURRENT I star= ted > experimenting with the VLAN trunking). It is very strange problems, why ICMP works, but TCP/UDP does not? :) You can try to disable any type of offloading for the card, there were some problems in the past with checksum offlading, that may lead to the problems with TCP, but this usually should be noticeable in the tcpdump output. --=20 WBR, Andrey V. Elsukov --NH8mmNxt8NVIXXsa6qm9RF0ES8NfiqlBV-- --TXHdgUq6MEvt6OL3RlEmnGILovVvSBmw9 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/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAllosl4ACgkQAcXqBBDI oXoaNggApk+Q/cCZ1kLczxIfdM2yJFK12Sx5C+uxBkRZ7v2LBKaFwgFwu/3EAHbx wC46VzAC6rqeVemP99NqWyfdLRCc2cjxJNqxGFiSAhI7FqkTqLjHPjuRg4wofj2Y sXXVBXPS8BrWci304nX0anuHXxxZgk65ajvXFTfrebU/jw/6MWSNZrS++rPGGlxR wP2JR6S7TVyJMiD+tnLQu/jZY8QpzCPpgg0HMQmB0n9W30AeZMaz6GHv000UxQ55 e2AX5RdxBoFdW3u3Kol8fOTC1Tez97SH30xa03KQzm4GeUw3koK0T31sPPdAZA8P TpGxiSE0JxdvRS9zK+4NcgJucbgBqg== =2EMb -----END PGP SIGNATURE----- --TXHdgUq6MEvt6OL3RlEmnGILovVvSBmw9-- From owner-freebsd-current@freebsd.org Fri Jul 14 16:32:58 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B28ADDA6CEF; Fri, 14 Jul 2017 16:32:58 +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 2E94C6BE48; Fri, 14 Jul 2017 16:32:57 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.180.149.38]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lux3h-1detKC2JNJ-0103GT; Fri, 14 Jul 2017 18:32:49 +0200 Date: Fri, 14 Jul 2017 18:32:48 +0200 From: "O. Hartmann" To: "Andrey V. Elsukov" Cc: FreeBSD CURRENT , "O. Hartmann" , FreeBSD Questions Subject: Re: Inter-VLAN routing on CURRENT: any known issues? Message-ID: <20170714182055.3cb1768a@thor.intern.walstatt.dynvpn.de> In-Reply-To: References: <20170712214334.4fc97335@thor.intern.walstatt.dynvpn.de> <20170713211004.13492aef@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/3=t_J+X+OLY8=raZazOl390"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:AaoerBJpBE5VPTrXV7GVepINPT3JlvWXtIVtVCV01d5sdF1dMTL Z0zZpvrrl2Y+OaDH8bz3xbG5DSd2i1p0rONmMqGXdbUwstanWIkODGNuzvMibhAy2eAU7NY 4jL8e+kji+VqnMgvn2bUfGFVxf9eIFZgxLilLV3rfkpane16n+Gr8yVSPRTmO6PX+zF8++S mLq2oLZjQ/ev06CdR/B+w== X-UI-Out-Filterresults: notjunk:1;V01:K0:8fiUIRnHfVU=:U/xeMCQqVWwAZa9toSEUjK jySiNO3jUbLXgZwUngPejK4ghdujvR6jqnxJ5y8U5cc4LOCvFh122yfPPK5ILrElMEy96WgAx Gyf/kMr31i2lirwPPNTYv1z/wz9c2aQSAccWdYD9TeJTvM3nrRoDAv8c5d03uVxZCowpGB1r5 ++FshfF+MC4tJbLKIOwgSTtBO87sHffF0UilF6IaP2PB7vuHnTzVCamN1o+3x7pvYCZK5WZzI h5rrH9+hANh0xHX8iN/wOBlmUscz2cILigzySf8SXykuN7Ua6F+Toek6FEynfb7bXhwG6dZcQ LPbqQxMopuRi/CseWeIkG7zKQ9iuayCkChJqGCIteVBxHKcG4qgtLkZWloAOPjZ3iV/Sbx+fx cVucDV8gaOYFGkjhka/jVJ/J52Usu5/U6ab9elVCdyOBWuRAyi+C6yRti5buVv2fXxkv/c0T5 KTnZ3+xEAgYaVACS8MDsDl5pkpGNY/Y/q29fN08sOO+wrbo0Pci/wClGJ6GnyO14pV7PwLw0i ZtUrp5U/xqFdGRjAkA6duMO2EsFz0aglmFLu+ddtEitDX4pcHfwIEnLIRJAjKSqncHAVyL5Ia T5IQpmZ/9GaEhnvCBXxv0vGxCNmxzxVemfk2uD16pf93G6nMyemIS3Hlcpbuc3VRKz9i4eld5 HT5k7K5Z3kP1PXWpOYFoNByPyzVZuMkP+Muw1WF8JN0SpfgaWZrBqDM6pZ0XBS6imKODQNzbb iWM6SEmL4trvhkSKJaoHWx6x4ko/bYbAw+s7e0j0zjLdpVZrmbz6gvuwkBCwW/1JPNctyoEbN Mx4QvJT3BtwxmGLyi9t71RvEOd9ZQ== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Jul 2017 16:32:58 -0000 --Sig_/3=t_J+X+OLY8=raZazOl390 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am Fri, 14 Jul 2017 15:00:30 +0300 "Andrey V. Elsukov" schrieb: > On 14.07.2017 14:42, O. Hartmann wrote: > > I use in-kernel NAT. IPFW is performing NAT. In firewall type "OPEN" fr= om the > > vanilla rc.conf, IPFW has instance "nat 123" which provides then NAT. = =20 >=20 > I never used default config types for firewall, so, it would be nice to > see what rules do you have. Me neither except on some hosts with very little complications in their set= ups or simple clients. >=20 > # ipfw show The OPEN firewall rules, which show the very same behaviour as I stated bef= ore: root@gate:~ # ipfw list 00050 nat 123 ip4 from any to any via tun0 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 65000 allow ip from any to any 65535 deny ip from any to any > # ipfw nat show config root@gate:~ # ipfw nat show config ipfw nat 123 config if tun0 log or ipfw nat 1 config if tun0 log same_ports reset redirect_port tcp 192.168.0.= 111:9734 9734 redirect_port tcp 192.168.0.111:5432 5432 redirect_port udp 192.168.2.1:242= 7 2427 redirect_port udp 192.168.2.1:4569 4569 redirect_port udp 192.168.2.1:5060 = 5060 redirect_port tcp 192.168.2.1:5060 5060 redirect_port tcp 192.168.0.111:443= 443 redirect_port tcp 192.168.0.111:80 80 redirect_port tcp 192.168.0.111:22 22 >=20 > >> VLANs work on the layer2 =20 > > According to 1): > >=20 > > I consider the settings of the switch now as correct. I have no access = to the > > router right now. But I did short experiments yesterday evening and it = is > > weird: loged in on thr router, I can ping every host on any VLAN, so IC= MP > > travel from the router the right way to its destination and back. > >=20 > > From any host on any VLAN that is "trunked" through the router, I can p= ing any > > other host on any other VLAN, preferrably not on the same VLAN. By cutt= ing off > > the trunk line to the router, pinging stops immediately. > >=20 > > From any host on any VLAN I can ping any host which is NATed on the out= side > > world. > >=20 > > From the router itself, I can ssh into any host on any VLAN providing s= sh > > service. That said, according to question 3), NAT is considered to be s= etup > > correctly. > >=20 > > Now the strange things: Neither UDP, nor TCP services "flow" from hosts= on one > > VLAN to hosts on a different VLAN. Even ssh doens't work.=20 > > When loged in onto the router, I can't "traceroute" any host on any VLA= N. =20 >=20 > This is most likely due to the problem with firewall rules. > If you set net.inet.ip.firewall.enable=3D0, does it solve the problem with > TCP/UDP between hosts on a different VLANs? net.inet.ip.firewall.enable does not exist, I suppose it is net.inet.ip.fw.= enable. Not, it doesn't change anything, last rule in my list is deny all, as you c= an see above (in-kernel). >=20 > > According to question 2), the ability to ping from, say, a host on VLAN= 1000 to > > another host on VLAN 2 passing through the router would indicate that b= oth > > sides know their routes to each other. Or am I wrong? =20 >=20 > Yes. >=20 > > I got words from Sean bruno that there might be a problem with the Inte= l i210 > > chipset in recent CURRENT - and the hardware on the PCEngine APU 2C4 is= three > > i210. I'm aware of the problem since r320134 (the oldest CURRENT I star= ted > > experimenting with the VLAN trunking). =20 >=20 > It is very strange problems, why ICMP works, but TCP/UDP does not? :) > You can try to disable any type of offloading for the card, there were > some problems in the past with checksum offlading, that may lead to the > problems with TCP, but this usually should be noticeable in the tcpdump > output. >=20 I tried that, but somehow I do not have any check: ifconfig_igb1=3D"up" #ifconfig_igb1=3D"inet6 ::1 prefixlen 64 mtu 6121" create_args_igb1=3D"-tso -lro -rxcsum -txcsum -rxcsum6 -txcsum6 -vlanhwtso = -vlanhwcsum -vlanhwfilter -vlanhwtag" and ifconfig igb1: igb1: flags=3D8843 metric 0 mtu 1500 options=3D6525bb Kind regards, Oliver --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/3=t_J+X+OLY8=raZazOl390 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWWjyMAAKCRDS528fyFhY lG8wAf4rs8/mrXg5Xrh1nXcf81faUVZwpFe/W4c8AlMevv7ESJ9DyJnEU93gIVNM 92pShy09yMT/n9QwGFa+uyli3GXuAfwLTVjWDGxKuRyH0988UCdVZ1Z+RnzJ2xOI axcHT+k51gMLxQHRQ8GJu+gl7Ve4WbadfxV4FDFBpobPsxwk4Cmj =3HSF -----END PGP SIGNATURE----- --Sig_/3=t_J+X+OLY8=raZazOl390-- From owner-freebsd-current@freebsd.org Sat Jul 15 19:32:49 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DA92B7A766 for ; Sat, 15 Jul 2017 19:32:49 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 1E6F182430 for ; Sat, 15 Jul 2017 19:32:49 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: by mailman.ysv.freebsd.org (Postfix) id 1AD2DB7A765; Sat, 15 Jul 2017 19:32:49 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18922B7A764 for ; Sat, 15 Jul 2017 19:32:49 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (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 C9B968242F for ; Sat, 15 Jul 2017 19:32:48 +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:references:from :from:subject:subject; s=201508; t=1500147159; bh=f8VWXoRTaDvEjP M/A3QF32Z2M0p/R/3lYjgF6kar20g=; b=DDXVlZx9L0zraQJvo9zXWXUkYono5t wXd7y7UNcUUwXCTii966b+MMKz6tHGfxhdKtIDwfUZpT9HNB8iXllMBGVN54aHMI xPnHlk/WLjr66Mnud07emQersivYf3PiSUkLuELBxUKDqIJckZI3IiXdHjDNEaPh UwEuQvUaACMNI= 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 84158F0A5; Sat, 15 Jul 2017 15:32:39 -0400 (EDT) Subject: Re: Panic on boot after upgrade from r320827 -> r320869 From: Michael Butler To: Warner Losh Cc: FreeBSD Current References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> <954e8793-7e17-8ae4-8449-39c742e0d432@protected-networks.net> Message-ID: <405f9924-5354-c6ba-0fc1-c4acf3eebcda@protected-networks.net> Date: Sat, 15 Jul 2017 15:32:38 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 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.23 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, 15 Jul 2017 19:32:49 -0000 On 07/11/17 19:53, Michael Butler wrote: > On 07/11/17 13:13, I wrote: >>> Take sdhci out of the kernel and try again. If that works, it tells >>> us one >>> thing (need to troubleshoot sdhci stuff more). If not it tells us >>> another >>> (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY >>> command? Does it try multiple times per AHCI port? What AHCI device >>> do you >>> have? You may need to scroll back with the screen-lock / pageup keys >>> to see >>> these messages. > > [ .. snip .. ] > >> I'll try this tonight when I'm back at home. The laptop concerned uses >> the ICH-7M part in "legacy mode" so it doesn't do AHCI at all :-( > > Without sdhci and mmc, it actually boots but everything KDE aborts with > signal 6 :-( > > I'm not prepared to rebuild the ~1900 ports on this box to pursue this > further, Something about SVN r320844 causes almost all KDE applications to fail on a signal 6. I've recompiled KDE and other components obviously dependent on kernel structures (e.g. everything dbus-related). I still get core-files with a back-trace that looks like: (gdb) bt #0 0x0000000804232f6a in thr_kill () from /lib/libc.so.7 #1 0x0000000804232f34 in raise () from /lib/libc.so.7 #2 0x0000000804232ea9 in abort () from /lib/libc.so.7 #3 0x00000008188597af in ?? () from /usr/local/lib/libdbus-1.so.3 #4 0x000000081884ef2c in _dbus_warn_check_failed () from /usr/local/lib/libdbus-1.so.3 #5 0x000000081883f539 in dbus_message_new_method_call () from /usr/local/lib/libdbus-1.so.3 #6 0x0000000801bddfe8 in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 #7 0x0000000801bd591e in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 #8 0x0000000801bd9af6 in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 #9 0x0000000801be656d in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 #10 0x0000000801be6807 in QDBusInterface::QDBusInterface(QString const&, QString const&, QString const&, QDBusConnection const&, QObject*) () from /usr/local/lib/qt4/libQtDBus.so.4 #11 0x000000080d12728e in ?? () from /usr/local/lib/libsolid.so.4 #12 0x000000080d11e68c in ?? () from /usr/local/lib/libsolid.so.4 #13 0x000000080d12a525 in ?? () from /usr/local/lib/libsolid.so.4 #14 0x000000080d0e7aac in Solid::Device::listFromType(Solid::DeviceInterface::Type const&, QString const&) () from /usr/local/lib/libsolid.so.4 #15 0x000000080e7e889a in ?? () from /usr/local/lib/libplasma.so.3 #16 0x000000080e7e6094 in Plasma::RunnerManager::RunnerManager(QObject*) () from /usr/local/lib/libplasma.so.3 #17 0x00000008172fab42 in ?? () from /usr/local/lib/libkdeinit4_krunner.so #18 0x00000008172fa9b4 in ?? () from /usr/local/lib/libkdeinit4_krunner.so #19 0x00000008172fd303 in kdemain () from /usr/local/lib/libkdeinit4_krunner.so #20 0x000000000040a015 in ?? () #21 0x000000000040aec0 in ?? () SVN r320843 works, r320844 doesn't :-( imb From owner-freebsd-current@freebsd.org Sat Jul 15 23:22:22 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2A3DB7DD7D for ; Sat, 15 Jul 2017 23:22:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7A6B03668 for ; Sat, 15 Jul 2017 23:22:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 79668B7DD7C; Sat, 15 Jul 2017 23:22:22 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 772A5B7DD7B for ; Sat, 15 Jul 2017 23:22:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::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 243693666 for ; Sat, 15 Jul 2017 23:22:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ua0-x234.google.com with SMTP id j53so68480655uaa.2 for ; Sat, 15 Jul 2017 16:22:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rO2qMEIr/wjc0sSljfi/STIBtgzRo7uQgV4L7RsZN9o=; b=LS6//io7eb+K3afcrt7+EQALTjM8mtFy9aGmY4s80FXVFqUnKsqKZVHpbo4CVTFvD9 1GYsWW754NAfJQ1/c8M/BnE6+wj6qMy3W1ND0I6bqNRgGRlePDrdLEmAgYPHM7RXoNrz a7k7Jbb++FQSbJbyVy7uqzsFxBbcFvboH2AmYtj7jARgIqHsrhO103CNykVzIlxOeupm NHE5mzsagmPhOTqAenmw4NIkllx8wxpwga9CthOWw85kob0obmNhtsnwT6ZKvzHu6DHp +WFMmhyITpghng3EYpxMUP1ktzH6BDzwqNIadFXWZCtIfFxW/fJNMlM6YQM0Ft4IWUT+ MbHQ== 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=rO2qMEIr/wjc0sSljfi/STIBtgzRo7uQgV4L7RsZN9o=; b=q/WNapcLmZ1CswXBVESkoDJOztLXp/Bl2ce23+AvdibsqZIM4fIYVzQdsKb7fqdGRd PNzQb8MvvKLiZ6Rf9/0w1SDB+uZJ5rH8ieNqXx9V5UKpHtKkbh54XRFp95YCjoGYVOkN JLgX6xM/V6QAgsXeq9A1Mext+LpyTz4u5s/7PGtt/GGvlM4GRhBzI8/nDOfKyoZqvbut IBgi1dIpFF/02bU/xmqM15O1y4Wgp7FhWVETkZfSV851xyHbZubR0TzMBljRbhkoy1Jj Tz6mC+l1Bu64zGKJ6ekF1EMBaCVE+HZ0JVeuMR2kCU1qNsLCRHo39+pvriLPeI8XKogX 3+3g== X-Gm-Message-State: AIVw111+wlou3mSeWWa64dKquCH1BedVwvNkQN7f2JsYTdSZnoztoth6 snkd/D5w+ua8EIdtvWsAmh0mEftzq5k2 X-Received: by 10.176.94.131 with SMTP id y3mr9146607uag.21.1500160940721; Sat, 15 Jul 2017 16:22:20 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.103.36.1 with HTTP; Sat, 15 Jul 2017 16:22:20 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <405f9924-5354-c6ba-0fc1-c4acf3eebcda@protected-networks.net> References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> <954e8793-7e17-8ae4-8449-39c742e0d432@protected-networks.net> <405f9924-5354-c6ba-0fc1-c4acf3eebcda@protected-networks.net> From: Warner Losh Date: Sat, 15 Jul 2017 17:22:20 -0600 X-Google-Sender-Auth: bls4JsXhSXCmbQJFB6CGDPtyEcg Message-ID: Subject: Re: Panic on boot after upgrade from r320827 -> r320869 To: Michael Butler Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Jul 2017 23:22:22 -0000 On Sat, Jul 15, 2017 at 1:32 PM, Michael Butler wrote: > On 07/11/17 19:53, Michael Butler wrote: > >> On 07/11/17 13:13, I wrote: >> >>> Take sdhci out of the kernel and try again. If that works, it tells us >>>> one >>>> thing (need to troubleshoot sdhci stuff more). If not it tells us >>>> another >>>> (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY >>>> command? Does it try multiple times per AHCI port? What AHCI device do >>>> you >>>> have? You may need to scroll back with the screen-lock / pageup keys to >>>> see >>>> these messages. >>>> >>> >> [ .. snip .. ] >> >> I'll try this tonight when I'm back at home. The laptop concerned uses >>> the ICH-7M part in "legacy mode" so it doesn't do AHCI at all :-( >>> >> >> Without sdhci and mmc, it actually boots but everything KDE aborts with >> signal 6 :-( >> >> I'm not prepared to rebuild the ~1900 ports on this box to pursue this >> further, >> > > Something about SVN r320844 causes almost all KDE applications to fail on > a signal 6. > I don't think that's possible, unless (a) your build hit the 'not everything in the kernel rebuilt' bug or (b) KDE is issuing raw CAM requests. Since I don't know KDE, don't run KDE or have any clue about KDE, I can't help you trace it down further. > I've recompiled KDE and other components obviously dependent on kernel > structures (e.g. everything dbus-related). I still get core-files with a > back-trace that looks like: > > (gdb) bt > #0 0x0000000804232f6a in thr_kill () from /lib/libc.so.7 > #1 0x0000000804232f34 in raise () from /lib/libc.so.7 > #2 0x0000000804232ea9 in abort () from /lib/libc.so.7 > #3 0x00000008188597af in ?? () from /usr/local/lib/libdbus-1.so.3 > #4 0x000000081884ef2c in _dbus_warn_check_failed () from > /usr/local/lib/libdbus-1.so.3 > #5 0x000000081883f539 in dbus_message_new_method_call () from > /usr/local/lib/libdbus-1.so.3 > #6 0x0000000801bddfe8 in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 > #7 0x0000000801bd591e in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 > #8 0x0000000801bd9af6 in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 > #9 0x0000000801be656d in ?? () from /usr/local/lib/qt4/libQtDBus.so.4 > #10 0x0000000801be6807 in QDBusInterface::QDBusInterface(QString const&, > QString const&, QString const&, QDBusConnection const&, QObject*) () > from /usr/local/lib/qt4/libQtDBus.so.4 > #11 0x000000080d12728e in ?? () from /usr/local/lib/libsolid.so.4 > #12 0x000000080d11e68c in ?? () from /usr/local/lib/libsolid.so.4 > #13 0x000000080d12a525 in ?? () from /usr/local/lib/libsolid.so.4 > #14 0x000000080d0e7aac in Solid::Device::listFromType(Solid::DeviceInterface::Type > const&, QString const&) () from /usr/local/lib/libsolid.so.4 > #15 0x000000080e7e889a in ?? () from /usr/local/lib/libplasma.so.3 > #16 0x000000080e7e6094 in Plasma::RunnerManager::RunnerManager(QObject*) > () from /usr/local/lib/libplasma.so.3 > #17 0x00000008172fab42 in ?? () from /usr/local/lib/libkdeinit4_krunner.so > #18 0x00000008172fa9b4 in ?? () from /usr/local/lib/libkdeinit4_krunner.so > > #19 0x00000008172fd303 in kdemain () from /usr/local/lib/libkdeinit4_krunner.so > > #20 0x000000000040a015 in ?? () > > #21 0x000000000040aec0 in ?? () > > > SVN r320843 works, r320844 doesn't :-( > I'd look to see if any of that software uses a CAM CCB for any reason. That's the only thing I can think of that might have been affected. Perhaps it's doing an identify? There was one CCB that changed size (and did so in an incompatible way between rev 320844 and 320878), I didn't think it was user visible. Does camcontrol identify or camcontrol inquiry work? Warner