Date: Sat, 10 Oct 2015 17:37:29 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203682] Slow boot under VMware Fusion w/ UEFI firmware and SMP -- until APs are launched Message-ID: <bug-203682-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203682 Bug ID: 203682 Summary: Slow boot under VMware Fusion w/ UEFI firmware and SMP -- until APs are launched Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: marcel@FreeBSD.org Host: - Mac OS 10.10 - Mac OS 10.11 Hypervisor: - VMware Fusion 7 Pro - VMware Fusion 8 Pro VM configuration: - UEFI firmware - UEFI console (std 1024x768) - Multiple CPUs (minimal 2) - RAM (don't care AFAICT) Description: As soon as FreeBSD takes the APs out of INIT and has them spinning in a tight loop and until until the APs are launched, the UEFI frame buffer is *very* slow. It takes 1 or 2 seconds to scroll 1 line of characters (in graphics mode). After the APs are launched, frame buffer access reverts to normal. >From the code (init_secondary_tail() in sys/x86/x86/mp_x86.c) it looks like the APs, while waiting to be unleashed, are not completely configured yet. In particular (and this comes from a gut feeling) the PAT MR is configured until the end (see pmap_init_pat() in sys/amd64/amd64/pmap.c). I wonder if the APs, while not being configured completely, cause the H/W (VMware Fusion in this case) to behave erratically. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203682-8>