From nobody Wed Jun 26 09:02:39 2024 X-Original-To: freebsd-arm@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 4W8G521vvWz5PPS2 for ; Wed, 26 Jun 2024 09:05:42 +0000 (UTC) (envelope-from bounce.f2x469l03m9hel0=l212nzycftgz=o529k8zjxzyg85@em790814.fubar.geek.nz) Received: from e3i74.smtp2go.com (e3i74.smtp2go.com [158.120.84.74]) (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 4W8G513SBLz4Hwh for ; Wed, 26 Jun 2024 09:05:39 +0000 (UTC) (envelope-from bounce.f2x469l03m9hel0=l212nzycftgz=o529k8zjxzyg85@em790814.fubar.geek.nz) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smtpservice.net; i=@smtpservice.net; q=dns/txt; s=a1-4; t=1719392731; h=feedback-id : x-smtpcorp-track : date : message-id : to : subject : from : reply-to : sender : list-unsubscribe : list-unsubscribe-post; bh=TRWVR0uQAjuJhVAdCwmY4o7pHVjIWOTkbvELpO/HV9U=; b=sCT0CKp7W1Mn49fYYor3kX+tWiQmtSbuljkCyT6eOm+b/mVUwMX31plg1R3rSCJ6c8S+s eH1Hrutv9g5kzSpn392sbis/LsE1TZ/AIHF+FsFELSp6EJEHz5okbeBRV2LHL3iQvigrZk9 K3k0f26oYcyxAgdDDYMwf/fqIM8lI1pyxNycnZtvuuWJyh7JOCgbGGSvhx8FhQfYoWg5zfS VNFb3fWHDX4Vgm7zVmx7UTDvewHzpFZtEYOeSnbnRlrgos93L3FgCoyP9PYcZLwFa+PddN4 ad63If2GWDPfzxnRAuLwsoBy/SF3t55tnIyR/x6FzOilyaoJ7VHgPSaMdS1A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fubar.geek.nz; i=@fubar.geek.nz; q=dns/txt; s=s790814; t=1719392731; h=from : subject : to : message-id : date; bh=TRWVR0uQAjuJhVAdCwmY4o7pHVjIWOTkbvELpO/HV9U=; b=UDN0mpSHPywXyib0mNkdb0FRx2bGEtksAWSOUtCJFZY8Iuk4T375mISlAhTssi1deragA yi7GozRBAL5O1HIEEVr6Y17B5oyW3pQV9+CFFDJUFRulegGab7vwryYIHWVQ4q0v14CJWQB 1INwZ3dzrbV5JhP3wci4pcnl02IeBKHlrOov70r4kMUWPIYNYUIM31CqI+gO+hucXF4T+d5 xVksNlpGDzGj9xG+FCW+QWjXSRRwBM5ayNnhQQXrK47++XshdBm13UIDJKqm+4J+9UhHFaJ BR3CwSLr2uqhE2rf51XkHlahMEDfKR0W0w+tVOxgu4rVNH7S0ejIoeDyfdmg== Received: from [10.99.243.232] (helo=morbo.fubar.geek.nz) by smtpcorp.com with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.97.1-S2G) (envelope-from ) id 1sMOYG-4o5NDgrkpwc-mwTg; Wed, 26 Jun 2024 09:02:52 +0000 Received: from smtpclient.apple (92.40.184.0.threembb.co.uk [92.40.184.0]) by morbo.fubar.geek.nz (Postfix) with ESMTPSA id A2CFB41642; Wed, 26 Jun 2024 09:02:50 +0000 (UTC) Content-Type: text/plain; charset=utf-8 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.100.2.1.4\)) Subject: Re: FreeBSD OS installation stuck after selecting Boot installer From: Andrew Turner In-Reply-To: Date: Wed, 26 Jun 2024 10:02:39 +0100 Cc: "Anantharam, Arjun" , Warner Losh , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <9FA9D2D4-E36E-415E-A55F-F711F5E5FAE2@fubar.geek.nz> References: <9BE6FB50-27DC-453E-B915-131D45C901CD.ref@yahoo.com> <9BE6FB50-27DC-453E-B915-131D45C901CD@yahoo.com> To: Mark Millard X-Mailer: Apple Mail (2.3774.100.2.1.4) X-Report-Abuse: Please forward a copy of this message, including all headers, to Feedback-ID: 790814m:790814amQcrys:790814s4L-EoCuCE X-smtpcorp-track: 48Rn4DbDSCLg.PCxJHhoSzYmx.1CDgTQFlQvi X-Spamd-Bar: ---- 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:23352, ipnet:158.120.84.0/22, country:US] X-Rspamd-Queue-Id: 4W8G513SBLz4Hwh > On 26 Jun 2024, at 02:18, Mark Millard wrote: >=20 >=20 > On Jun 25, 2024, at 17:44, Anantharam, Arjun = wrote: >=20 >> I was able to make some more progress with the boot loader cmd: >>=20 >> set hw.uart.console=3D"mm:0x2058400000,rs:2"=20 >> However, with the .iso image i ran into this issue: >>=20 >> Your emails don=E2=80=99t seem to be making it to the list as it=E2=80=99s= likely the images are too large. >=20 > That .png showed that you are tryin got boot 13_2_RELEASE_AARCH64_CD, > which has its 13.2 EoL on: June 30, 2024 >=20 > You may want to try 13.3 or some other Release that has significantly > more time before its EoL (no support). (But you already tried a main > [15] build below.) >=20 >> And with the .img (memstick image) file, kernel panics were seen: >=20 > This is not a boot of the same release, in fact it is a > boot of main [15] from early June, instead of a release. >=20 >> OK boot >> Loading kernel... >> /boot/kernel/kernel text=3D0x318 text=3D0x97e6d8 text=3D0x2b4130 = data=3D0x166e60 data=3D0x >> 0+0x370000 0x8+0x1652e8+0x8+0x196120 >> Loading configured modules... >> can't find '/etc/hostid' >> can't find '/boot/entropy' >> No valid device tree blob found! >> WARNING! Trying to fire up the kernel, but no device tree blob found! >> ---<>--- >> GDB: no debug ports present >> KDB: debugger backends: ddb >> KDB: current backend: ddb >> Type Physical Virtual #Pages Attr >> ConventionalMemory 0040e0000000 000000000000 002a0000 WC WT WB=20 >> Reserved 004400000000 000000000000 00000700 WC WT WB=20 >> RuntimeServicesData 004400700000 004400700000 00000100 WC WT WB = RUNTIME ... >> Reserved 004400700000 004400700000 00000010 WB RUNTIME Why do the ACPI tables list the same address space twice? >> MAP 4400700000 mode 2 pages 256 >> MAP 44b6940000 mode 2 pages 32 >> MAP 44b6b60000 mode 2 pages 128 >> MAP 44b6c20000 mode 2 pages 80 >> MAP 44b6c70000 mode 2 pages 80 >> MAP 44b6cf0000 mode 2 pages 80 >> MAP 44b6d40000 mode 2 pages 80 >> MAP 44b6d90000 mode 2 pages 80 >> MAP 44b6de0000 mode 2 pages 80 >> MAP 44b6e40000 mode 2 pages 80 >> MAP 44b6e90000 mode 2 pages 80 >> MAP 44b6ee0000 mode 2 pages 80 >> MAP 44b6f30000 mode 2 pages 80 >> MAP 44bbf50000 mode 2 pages 64 >> MAP 44bbfa0000 mode 2 pages 80 >> MAP 4400700000 mode 2 pages 16 >> panic: efi_1t1_l3: Already mapped: va 0x4400700000 *pt 0x4400700f0b This is complaining that the kernel is trying to map memory it already = mapped. As a workaround you can disable the EFI runtime you can try = setting =E2=80=9Cefi.rt.disabled=3D1=E2=80=9D in loader to disable the = use of these services. Andrew