From owner-freebsd-arm@freebsd.org Tue Feb 23 01:00:59 2021 Return-Path: Delivered-To: freebsd-arm@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 D59F7555A7D for ; Tue, 23 Feb 2021 01:00:59 +0000 (UTC) (envelope-from freebsd-arm@darkain.com) Received: from MTA-07-4.privateemail.com (mta-07-4.privateemail.com [68.65.122.27]) (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 4Dl12M0vqYz3MV7; Tue, 23 Feb 2021 01:00:58 +0000 (UTC) (envelope-from freebsd-arm@darkain.com) Received: from MTA-07.privateemail.com (localhost [127.0.0.1]) by MTA-07.privateemail.com (Postfix) with ESMTP id 63798600AA; Mon, 22 Feb 2021 20:00:56 -0500 (EST) Received: from mail-lf1-f45.google.com (unknown [10.20.151.241]) by MTA-07.privateemail.com (Postfix) with ESMTPA id C46326009F; Tue, 23 Feb 2021 01:00:55 +0000 (UTC) Received: by mail-lf1-f45.google.com with SMTP id p21so8645763lfu.11; Mon, 22 Feb 2021 17:00:56 -0800 (PST) X-Gm-Message-State: AOAM532Vk/tuafCgpMVcdOs0vE28hAYSC4fhZuKff+P3syox0Q7HWvCG +XbjtEbjMBkQPVogA15WjZRFJPhT3HFFe/Y41Mk= X-Google-Smtp-Source: ABdhPJz3ifIBlaEUCnj6adligMI3buLqhTqu54mFvhUe2qAav61X5x/15a+S9lVcWABnhB/q3Cbw3ALvgdlQs7fldwM= X-Received: by 2002:a19:c18b:: with SMTP id r133mr14590116lff.159.1614042054817; Mon, 22 Feb 2021 17:00:54 -0800 (PST) MIME-Version: 1.0 References: <5189D185-4A1F-43A0-A61D-E3D24CC74B3D@freebsd.org> <08F81EB7-251B-4CCC-911E-4094A83FE356@freebsd.org> In-Reply-To: <08F81EB7-251B-4CCC-911E-4094A83FE356@freebsd.org> From: Vincent Milum Jr Date: Mon, 22 Feb 2021 17:00:43 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Running current in Parallels 16.3.2 To: Michael Tuexen Cc: freebsd-arm@freebsd.org X-Virus-Scanned: ClamAV using ClamSMTP X-Rspamd-Queue-Id: 4Dl12M0vqYz3MV7 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd-arm@darkain.com designates 68.65.122.27 as permitted sender) smtp.mailfrom=freebsd-arm@darkain.com X-Spamd-Result: default: False [-1.89 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:68.65.122.0/27]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[darkain.com]; RBL_DBL_DONT_QUERY_IPS(0.00)[68.65.122.27:from]; RWL_MAILSPIKE_GOOD(0.00)[68.65.122.27:from]; NEURAL_SPAM_SHORT(0.41)[0.410]; SPAMHAUS_ZRD(0.00)[68.65.122.27:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[68.65.122.27:from]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:22612, ipnet:68.65.122.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[freebsd-arm] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Feb 2021 01:00:59 -0000 In my testing of FreeBSD under ESXi ARM Fling, I never tested SMP under single-user mode. However, from what I recall, the stalling was in CPU initialization, not in storage mounting. On Mon, Feb 22, 2021 at 1:42 PM wrote: > > > > On 18. Feb 2021, at 00:28, Vincent Milum Jr > wrote: > > > > We had similar issues getting FreeBSD SMP working under ESXi ARM Fling. > In > > that instance, there were bugs in both the hypervisor as well as in > FreeBSD. > > > > With the FreeBSD kernel fixes, I tested those on Parallels last night, > but > > still no go with SMP. There is possibly more work to do in the kernel, > but > > may also be some bugs in the hypervisor as well. > > > > For ESXi ARM Fling, the issues all revolved around the GIC (Generic > > Interrupt Controller) and the way inter-CPUs communication happened. If > > memory serves me correctly, one CPU core was waiting on another CPU core > to > > finish initialization and report back in a "ready" state so to speak. > Where > > Parallels with FreeBSD is hanging, and how it is hanging, looks virtually > > identical from my very limited testing last night. > If you boot into single user mode, the system comes up and uses multiple > CPUs. > Then using ^D to start multi user mode shows that mount seems to hang. You > can > use ^T, but it never finishes. Is that what you observed on ESXi? > > Best regards > Michael > > > > On Wed, Feb 17, 2021 at 3:05 PM Michael Tuexen > wrote: > > > >> Dear all, > >> > >> I tried running current on an ARM-based Mac using the technical preview > of > >> Parallels. > >> With using only a single CPU, everything seems to run fine. One can git > >> clone the > >> source tree, do a buildworld / buildkernel and install it and run it. > >> Pretty stable, > >> not problems. > >> > >> When using more than one CPU, the kernel doesn't completely boot. It > gets > >> stuck after > >> reporting that the file system is clean. The system also does not > respond > >> to keyboard > >> input anymore. > >> > >> Any idea what is going wrong or how to figure out if this is a problem > >> related to > >> FreeBSD or to Parallels? > >> > >> Best regards > >> Michael > >> _______________________________________________ > >> freebsd-arm@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm > >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >> > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > >