Date: Thu, 11 Oct 2018 15:00:20 -0400 From: Dennis Clarke <dclarke@blastwave.org> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-ppc@freebsd.org Subject: Re: FreeBSD 12.0-ALPHA4 fails to boot on POWER9/KVM Message-ID: <573eb381-35f0-5523-3d6a-77a01174bdc8@blastwave.org> In-Reply-To: <E23ABDA5-40EA-428C-BF3F-4199096DF7A8@yahoo.com> References: <5d84652d-8b54-19f9-1396-e7c9acbe6c03@neo-zeon.de> <CAHSQbTAgow0yESJo-oV83Oq9ePzwoOL_viUxNirYmeOXy_2zmg@mail.gmail.com> <a9aed989-9ea0-4e34-0619-7d54ddc28ea6@neo-zeon.de> <5f44c6d6-7eec-6732-6fef-123e7e0d3292@freebsd.org> <E610CDE0-7BEE-4E79-BB15-9FB023690BA5@macmic.franken.de> <ff249f1e-9c2d-013a-1a37-cc79a261fbac@freebsd.org> <cd6efedd-627c-1758-1b01-cd1547180e8b@neo-zeon.de> <2b4455f4-37f6-5645-dcba-2cc41c845ae8@neo-zeon.de> <0a970b75-160a-e40e-b360-1b73a753f701@freebsd.org> <c6fb42ef-fba3-9a79-1356-759900cb24d0@blastwave.org> <E23ABDA5-40EA-428C-BF3F-4199096DF7A8@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/11/2018 02:50 PM, Mark Millard wrote: > On 2018-Oct-11, at 11:19 AM, Dennis Clarke <dclarke at blastwave.org> wrote: > >> On 10/10/2018 11:59 PM, Nathan Whitehorn wrote: >>> The first part of this (all the errors about "NOT FOUND") I just fixed >>> and the fixes will be included in BETA1 and subsequent builds. The >>> remaining issue is that virtio SCSI is not part of the standard kernel >>> on PPC (there are some endian and DMA bugs), so you will need to use an >>> alternative storage backend. The default storage backend (VSCSI) is >>> fine, as are more PC-ish things like AHCI emulation. >>> This command line will work and is otherwise equivalent to the below: >>> qemu-system-ppc64 -enable-kvm -m 2048 -nographic -vga none -cdrom >>> FreeBSD-12.0-ALPHA9-powerpc-powerpc64-20181009-r339271-disc1.iso >>> /var/lib/libvirt/images/freebsd-ppc.qcow2 -mem-prealloc -mem-path >>> /dev/hugepages -smp 2 >>> -Nathan >> >> >> Has anyone tried this on a PowerMac G5 yet ? > > "this"? I'm unsure if the following is addressing what you are > referring to or not. But it might be. > > Until the problems with -r334498 's adjustment to VM_MAX_KERNEL_ADDRESS > are dealt with, PowerMac G5's have boot problems (and possibly other > problems), at least those with multiple sockets (for what I can test). > (I've no access to other forms of PowerMac G5's.) > > See: > > https://lists.freebsd.org/pipermail/freebsd-ppc/2018-October/009669.html > > and later in that thread. (Earlier in the thread is likely a waste of time > to read, given what is now known.) > > My G5 contexts are operational by reverting -r334498 . The contexts are > otherwise based on -r339076 currently. > > > Note: > > My boot test on a 8 GiByte, dual-socket, one "CPU" per socket, > PowerMac G5 met the conditions of Andreas Tobler's requested test > conditions and the machine boot fine (VM_MAX_KERNEL_ADDRESS near > the RAM size, on the low side). > > The G5 so-called "Quad Core"s, 4 cores total in each system but > split evenly across 2 sockets in each), one with 12 GiByte and > one with 16 GiByte of RAM, booted fine as well. But > VM_MAX_KERNEL_ADDRESS was somewhat under 8GiByte and so not near > those sizes. > OKay ... that is a lot of good information and I'll sum up as "no". Was merely curious if I should give it a try. Dennis
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?573eb381-35f0-5523-3d6a-77a01174bdc8>