Date: Tue, 25 Feb 2025 07:08:02 -0800 From: Mark Millard <marklmi@yahoo.com> To: Jason Bacon <bacon4000@gmail.com> Cc: freebsd-arm@freebsd.org Subject: Re: FreeBSD db> prompt vs. heat under Parallels on macOS Message-ID: <82652A1E-ADC6-4518-BC5C-A5679C153C07@yahoo.com> In-Reply-To: <5863d6b5-d264-4b5e-b8e8-51a459fbebc2@gmail.com> References: <283514E4-76F7-4966-B8CD-604EB1240C6D@yahoo.com> <5863d6b5-d264-4b5e-b8e8-51a459fbebc2@gmail.com>
index | next in thread | previous in thread | raw e-mail
On Feb 25, 2025, at 06:33, Jason Bacon <bacon4000@gmail.com> wrote: > On 2/25/25 08:20, Mark Millard wrote: >> I found this morning that FreeBSD had crashed somewhat after >> I went to sleep last night. The MacBook Pro M4 Max had spent >> around 6 hrs with all 16 cores maxed out and the fan going >> full blast. >> === >> Mark Millard >> marklmi at yahoo.com > > I recently installed on my M1 under VirtualBox 7.1.6 and saw similar CPU usage. A 4-core VM idles at 300% CPU. Normal idle operation of FreeBSD is not showing such CPU usage in my Parallels context. The issue was specific to having ended up at the db> prompt. "kenv | grep -F smbios" output may be of interest for https://reviews.freebsd.org/D49084 for VirtualBox as a context. What does "sysctl kern.hz" show? (Not that it should matter.) > Installing FreeBSD was also a little sketchy: > > 1. virtio drivers did not work, had to use Intel Other than virtio_gpu not having anything to display with virtio seems to be working in my context. I used /boot/device.hints to avoid the virtio_gpu so that efifb stayed in use. That seems to be working fine for my simple use of the console. > 2. No virtual hard drive by default, just CD and floppy I actually booted the media that I boot the Windows Dev Kit 2023 with (and sometimes the RPi5 with). It and all its partitions show up as: # ls -C1 /dev/ada0* /dev/ada0 /dev/ada0p1 /dev/ada0p2 /dev/ada0p3 /dev/ada0p4 /dev/ada0p5 /dev/ada0p6 /dev/ada0p7 /dev/ada0p8 /dev/ada0p9 Actual context: USB 3.2 Gen 2 (10 Gpbs). > I got it working by trial and error, but Arm support is clearly still a work in progress. Seems like it may be somewhat more specific to VirtualBox 7.1.6 as a context in some respects. > FreeBSD didn't crash, but there were some odd network issues (unable to reach another host on the local network). I also saw this under Qemu, though the host macOS had no such problem. > So far my little bit of network use seems to have generally gone just fine, at least if it gets a dhcp binding explicitly. Was your Qemu use via using UTM? If not, "kenv | grep -F smbios" output may be of interest for https://reviews.freebsd.org/D49084 . === Mark Millard marklmi at yahoo.comhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82652A1E-ADC6-4518-BC5C-A5679C153C07>