From nobody Fri Nov 22 18:31:52 2024 X-Original-To: freebsd-current@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 4Xw3bP6xSyz5fBwT for ; Fri, 22 Nov 2024 18:31:45 +0000 (UTC) (envelope-from rdunkle@smallcatbrain.com) Received: from outbound5f.eu.mailhop.org (outbound5f.eu.mailhop.org [3.127.8.113]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xw3bP4sBDz4K4H for ; Fri, 22 Nov 2024 18:31:45 +0000 (UTC) (envelope-from rdunkle@smallcatbrain.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:content-type:in-reply-to:from:references:cc:to: subject:mime-version:date:message-id:from; bh=Wgfvk2Q2qg7oj41DOMXdg3GjbRV0Tpj5G+fK1ZBYNUg=; b=Br3Wh9uXhq70M9s7KqN5KZ/vLSEPkJp/3ABONFF/3ewUAU3UVDgzrJLAIcg6sCzZBfLu+NdbcHg6/ OTfVjiNZvyjuNY47Prk4jrlkxpHAcKRV8RIb4L+nk4HL+ECWCATu4jxHQ/R6e0MzR6osKbHrnsjcUw LELdXKw5+7m1b7RJPUQkIxYlC+INY1jnWRGxBPv8qLQ6UaC8j27aZiLhD562Ws3KDzEkrpK1PjjAJG 7YoHVkxlxmnrZL+xXf5mQo2vPEkhA47bk4f5AY0vzDvbJ7szupQ5GEr8OSKpQqZbFZM5zPvTXTsSdC oFZc/r+HZoTKYmzmrApSh8GxBI2Y/9g== X-Originating-IP: 185.209.57.35 X-MHO-RoutePath: cmR1bmtsZQ== X-MHO-User: 0499c409-a900-11ef-a1b9-7b4c7e2b9385 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Mail-Handler: DuoCircle Outbound SMTP Received: from [192.168.2.159] (smp5.smallcatbrain.com [185.209.57.35]) by outbound2.eu.mailhop.org (Halon) with ESMTPSA id 0499c409-a900-11ef-a1b9-7b4c7e2b9385; Fri, 22 Nov 2024 18:31:41 +0000 (UTC) Message-ID: Date: Fri, 22 Nov 2024 20:31:52 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: arm64-aarch64 no longer boots on UTM MacOS To: Alexander Leidinger Cc: freebsd-current@freebsd.org References: <9d9cb81e-244b-496b-88c5-0475ce447ec7@smallcatbrain.com> <528dba14fb340c281e10086757553c08@Leidinger.net> Content-Language: en-US From: Rich Dunkle In-Reply-To: <528dba14fb340c281e10086757553c08@Leidinger.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.124.0.0/14, country:US] X-Rspamd-Queue-Id: 4Xw3bP4sBDz4K4H X-Spamd-Bar: ---- On 22.11.2024 17:05, Alexander Leidinger wrote: > Am 2024-11-22 13:36, schrieb Rich Dunkle: >> FreeBSD-15.0-CURRENT used to boot on UTM. >> Now it hangs right after the EFI information, and never boots. >> >> Tested last week and this week iso images. >> >> FreeBSD-15.0-CURRENT-arm64-aarch64-20241121-e8263ace39c8-273771-bootonly.iso >> >> >> The iso is OK, and boots on arm64- Orange Pi 5 Plus. > > Does it boot when you revert this change? > https://cgit.freebsd.org/src/commit/?id=c87b3f0006be9ac5813f1ff636f18c9b4a41b08e > > If yes, please comment on >     https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282493 > > Bye, > Alexander. > I did a revert on that change, then rebuilt world and kernel. I see the same hang on UTM.