From owner-freebsd-current@freebsd.org Wed Feb 5 09:12:07 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D1FD5244AA8 for ; Wed, 5 Feb 2020 09:12:07 +0000 (UTC) (envelope-from se@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48CG6H55xVz4HH6; Wed, 5 Feb 2020 09:12:07 +0000 (UTC) (envelope-from se@freebsd.org) Received: from Stefans-MBP-449.fritz.box (p200300CD5F20A8004CC14CEA08057604.dip0.t-ipconnect.de [IPv6:2003:cd:5f20:a800:4cc1:4cea:805:7604]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 6071F10E91; Wed, 5 Feb 2020 09:12:07 +0000 (UTC) (envelope-from se@freebsd.org) To: freebsd-current@freebsd.org From: =?UTF-8?Q?Stefan_E=c3=9fer?= Subject: Panic in gptzfsboot? Message-ID: <1a6a221a-42de-b74c-ef1f-f6939506dff8@freebsd.org> Date: Wed, 5 Feb 2020 10:12:04 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 05 Feb 2020 09:12:07 -0000 I have just re-built world and kernel and get a boot failure: panic: free: guard2 fail @ 0x412f6c50 + 513 from unknown:0 --> Press a key in the console to reboot <-- I'll try to boot from a memory stick, now, but wanted to let others know, that there seems to be a problem with the latest UMA code which may cause a boot failure at this early stage. STefan