From nobody Thu May 27 06:45:46 2021 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E8995C79F55 for ; Thu, 27 May 2021 06:45:59 +0000 (UTC) (envelope-from nbari@codigo.io) Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FrJHW62Vlz4SHd for ; Thu, 27 May 2021 06:45:59 +0000 (UTC) (envelope-from nbari@codigo.io) Received: by mail-lj1-x22e.google.com with SMTP id s25so4869640ljo.11 for ; Wed, 26 May 2021 23:45:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tequila.io; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=venYRLv71wubVSFSOyUesWbG1T6KEkapBSh4y/9d/9c=; b=QKxPvgMG+OmkUpFz7B+LL41wimmle9byjIqudpyhj3gswR3PZinapibq6Ogo8oS3Ty kNoqS2KFUjHmMNExcwkQy3cRMTrZu8cD6egIuA/Q5Y/gtbx+SlPrMkKu6vL4ZAl8ORs7 RcV5jmhCCQmuVVFOkN2hInjmcH8Al3ZGF4Mh+NWfK7hc0q6igrq7SUUXZicDQx+CApbJ iN6Hdu1Mt/ztMmo3qHrwGSIiv7a5i+knWtTTG8deIk54mJMToH8kZC39PWHwNGZNww2R j0FxnV4mgDa5k/98Q02vn0unXZoJOn5jTVqq39BSF8xYoUaiYrl49wfJ4b4A8W2OW26i NOZg== 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=venYRLv71wubVSFSOyUesWbG1T6KEkapBSh4y/9d/9c=; b=KSQM7iqRT5OPCy0nZxga6UL3Kw2iB9IRxKd+usdmWSyc/G988pLnnDlFhlRkbRiJ0w eqXU/hmdZ+VqTTSm4fF7ba40mpAxH9SSV1SL1Tmct/XjImc2bYduRJVS7mRf1yrSYIho vFV/BFKPM66pDTBGdkt9vWmCQUrLNVCN0jYXS5BpxsShcp6nJngrmrptRp9f/sI3OrGE 4WH63nhVP9NdHVSgNrEClxpMAJgoXCU3HWLO/JndPMFzeEl/wU2GkchR/F6sVjdPYSpn 6iBa6sKO/MAP7xUWkUOGz+wyD+xZDymJ/ftSKbrEua3Iq/7BBYAP8k0luMz7gKVl72V1 LUXQ== X-Gm-Message-State: AOAM532XryTrWpQ94JCz4bTjAF5pKVYH0enM11sV90cB9XurV5nDCOEc 5HPWOORuAYuikr4/uT8I5GFgdZNe3/ksHzOx+LdC57NtNx5Pk1XcSMk= X-Google-Smtp-Source: ABdhPJyI2qU+5ry7YaEZNGciDOTowlYU3yP6DrL8t3GWU0vU1vysb2xhc6m6sgoIFyrqGUI3zSS1nGAli6uKXrNq55w= X-Received: by 2002:a2e:a482:: with SMTP id h2mr1440503lji.246.1622097957485; Wed, 26 May 2021 23:45:57 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <0.2.0-final-1618742820.474-0x878fa2@qmda.emu.st> <20210420021318.GB18217@blisses.org> <0.2.0-final-1618896757.688-0xb6a34e@qmda.emu.st> <0.2.0-final-1618989350.827-0x8feb00@qmda.emu.st> <0.2.0-final-1622079919.897-0x87f63c@qmda.emu.st> In-Reply-To: <0.2.0-final-1622079919.897-0x87f63c@qmda.emu.st> From: Nicolas Embriz Date: Thu, 27 May 2021 08:45:46 +0200 Message-ID: Subject: Re: Various problems with 13.0 amd64 on vultr.com To: Mark Delany Cc: FreeBSD Hackers Content-Type: multipart/alternative; boundary="0000000000008c10a205c34a1c8a" X-Rspamd-Queue-Id: 4FrJHW62Vlz4SHd X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --0000000000008c10a205c34a1c8a Content-Type: text/plain; charset="UTF-8" Just in case you can reboot using: shutdown -o -n -r now Not ideal but works for now as a workaround. On Thu, May 27, 2021 at 3:47 AM Mark Delany wrote: > On 21Apr21, Mark Delany allegedly wrote: > > On 20Apr21, Freddie Cash allegedly wrote: > > > > > If you re-write your rules to use the in-kernel libalias support > instead of > > > divert sockets sending traffic to natd, does it stay up while passing > IPv4 > > > traffic? > > > > > > That would help narrow it down even further to natd issues. > > > > I've not used the in-kernel NAT support before so it'll take me a little > while, but I'll > > give it a shot and report back. > > Well, lucky me, I no longer need to do this as it looks like the problem > was fixed in > 13.0-RELEASE-p1 as part of an Errata fixed for "Kernel double free when > transmitting on a > divert socket". > > I tested with the new kernel and now running natd no longer causes a > kernel panic. > > My one remaining beef with 13.0 relates to vultr more than anything else > in that FBSD > doesn't reboot when requested. It gets into some late-stage of the > shutdown process and > just spins on CPU. I can live with this one, but will keep an eye on it. > > > Mark. > > --0000000000008c10a205c34a1c8a--