From owner-freebsd-arch@freebsd.org Thu Dec 17 04:46:09 2020 Return-Path: Delivered-To: freebsd-arch@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 ACBC84AA78B for ; Thu, 17 Dec 2020 04:46:09 +0000 (UTC) (envelope-from yuripv@yuripv.dev) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 4CxKFX3ZmBz4sNw for ; Thu, 17 Dec 2020 04:46:08 +0000 (UTC) (envelope-from yuripv@yuripv.dev) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E5DB45C00F5; Wed, 16 Dec 2020 23:38:24 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 16 Dec 2020 23:38:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.dev; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm1; bh=U q9N2tBmmlKyBWA90N5/lz9UEsZsfbjE588GLs5dGQM=; b=bs4420mC7AlVE8irW WToue45jwnN0gZXK65RFdffAd4he3zztqCErsmB7ZRFMcSuouD5hMJvaqNb3iCHA sI1BS71oZfmep5w6Wqr4sNkKR9OtU4hRYu9c63tSTCT708GdJls2lg4IExrCSHqH UwkxXo3UVWWbD0JOno8E6yzP/RgLdDGjUEPuIdCE9lKFbVoESJR4zMJ8eG+xdu6j PNITA8B614nGquSsWQIEtXtmyHCCOFoy5GfsHvdjMvQ8O01/iQzRJNvTWZirj3JL c20Z48wdinWIwz0sccgMJGx6e84Tiq6EbAV8x8otABo2D1vs09kCzbOHRC3VrZT3 dJrYg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Uq9N2tBmmlKyBWA90N5/lz9UEsZsfbjE588GLs5dG QM=; b=EswhfLhLkmaov3qUl0YBdHqZODbUxjnUhDWf+dnYhVpkBYs2JbVAfhzdc zCusWe3So7v/j7lLRZxsWb5bkEJljBkOZq2e4KwCCUX59qV24TJUqVK2Fthu8A4z kcbhEMaJO562LMetKicA/JTfO8SsOSpLNbw5G6vbtXNXgRur2t8B/htpeoF6/pXW E4ACq3jbtTnvVCROI4GUEnvVKtF8qSR14GG5LycI67DstwK7ZfEqu05L/DStwCqp DISknPuojUkTgmga0pwz6WbwCEh2AELXYRzeyj5D9quUOx5banzLi4iuxNuUnvH6 RrDQq2ulVeLSHi3mvQ0FsVH9/ELhg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudelfedgjeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtje ertddtfeejnecuhfhrohhmpegjuhhrihcurfgrnhhkohhvuceohihurhhiphhvseihuhhr ihhpvhdruggvvheqnecuggftrfgrthhtvghrnhepieekteeftdeftdekhfffueeljeefff fgffffuefhhefgheejvdegfeehieevudfgnecuffhomhgrihhnpehfrhgvvggsshgurdho rhhgnecukfhppeeluddrvdegtddruddvgedrudehjeenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpeihuhhrihhpvheshihurhhiphhvrdguvghv X-ME-Proxy: Received: from mercury.lan (unknown [91.240.124.157]) by mail.messagingengine.com (Postfix) with ESMTPA id 0C10E24005B; Wed, 16 Dec 2020 23:38:23 -0500 (EST) Subject: Re: Because the loader.efi modified the size of EFI_STAGING_SIZE, vmware could not start the system above FreeBSD 12.2 To: Warner Losh , YUAN RUI Cc: "freebsd-arch@freebsd.org" References: <3833edf0-4717-1254-a005-e4be8820b010@me.com> <72c45ce8-f89e-3f66-acce-54177109ea8a@me.com> From: Yuri Pankov Message-ID: <4020f013-7cb7-14bf-c518-44605ce7167e@yuripv.dev> Date: Thu, 17 Dec 2020 07:38:22 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 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-Rspamd-Queue-Id: 4CxKFX3ZmBz4sNw X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yuripv.dev header.s=fm1 header.b=bs4420mC; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=EswhfLhL; dmarc=none; spf=pass (mx1.freebsd.org: domain of yuripv@yuripv.dev designates 66.111.4.29 as permitted sender) smtp.mailfrom=yuripv@yuripv.dev X-Spamd-Result: default: False [3.92 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(0.00)[+ip4:66.111.4.29:c]; RWL_MAILSPIKE_GOOD(0.00)[66.111.4.29:from]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[yuripv.dev:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-0.98)[-0.977]; FREEMAIL_TO(0.00)[bsdimp.com,me.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[66.111.4.29:from]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.29:from]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_XBL(5.00)[91.240.124.157:received]; R_DKIM_ALLOW(0.00)[yuripv.dev:s=fm1,messagingengine.com:s=fm1]; FREEFALL_USER(0.00)[yuripv]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[yuripv.dev]; BAD_REP_POLICIES(0.10)[]; SPAMHAUS_ZRD(0.00)[66.111.4.29:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[1.000]; GREYLIST(0.00)[pass,body]; MAILMAN_DEST(0.00)[freebsd-arch] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2020 04:46:09 -0000 Warner Losh wrote: > On Tue, Dec 15, 2020 at 9:34 AM YUAN RUI via freebsd-arch < > freebsd-arch@freebsd.org> wrote: > >> yes, all >> >> It cannot be the problem of too small memory. I allocated 32g of memory >> for vmware and this problem still occurs. After debugging, I found that >> if the memory allocation is greater than 64M, it will trigger a crash. >> > > OK. That's good to know. I'll have to think about the best way forward. > There was, at the time this was done (by others), the thought it was 'free' > and had no consequences. I can confirm reducing EFI_STAGING_SIZE back to 64 and building "cdrom" image successfully boots on ESXi 7, it does not with latest snapshot. More so, looks like https://svnweb.freebsd.org/base?view=revision&revision=355132 should take care, in a dynamic way, of the original problem increasing EFI_STAGING_SIZE was supposed to fix? >> On 12/16/2020 12:09 AM, Warner Losh wrote: >>> Is this at all? Or only on memory sizes that are small? >>> >>> Warner >>> >>> On Tue, Dec 15, 2020 at 3:45 AM YUAN RUI via freebsd-arch < >>> freebsd-arch@freebsd.org> wrote: >>> >>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866 Thanks a lot!