RC2 seems to need kern.smp.disabled=1

Dennis Clarke dclarke at blastwave.org
Mon Nov 26 21:08:31 UTC 2018


On 11/26/18 2:41 PM, Mark Millard wrote:
> 
> 
> On 2018-Nov-26, at 11:13, Dennis Clarke <dclarke at blastwave.org> wrote:
> 
> 
>> Hello ppc64 types:
>>
>> Merely an observation that RC1 was running more or less fine without the
>> need to castrate the smp feature whereas RC2 won't even boot.
> 
> If you were able to smp boot a PowerMac G5 based on a version that
> was based on:
> 
> #define VM_MAX_KERNEL_ADDRESS           0xe0000007ffffffffUL
> 
> from sys/powerpc/include/vmparam.h that is interesting.
> 
> This is the value I (and others?) have been reverting to:
> 
> #define VM_MAX_KERNEL_ADDRESS           0xe0000001c7ffffffUL
> 
> in order to allow smp use on such G5's. Quoting an old reply
> from 2018-Oct-11 (-r??????'s are from 13-CURRENT):
> 

I don't see that file in my install but then again I did not drag in the 
sources or much of anything to get off the ground.  What I do have is :

/usr/include/machine/vmparam.h

which says :

#define VM_MAX_KERNEL_ADDRESS           0xe0000007ffffffffUL

Looking into 
https://download.freebsd.org/ftp/releases/powerpc/powerpc64/12.0-RC2/src.txz 
I see :


root at eris:~ # grep "VM_MAX_KERNEL_ADDRESS" 
/usr/src/sys/powerpc/include/vmparam.h
#define VM_MAX_KERNEL_ADDRESS           0xe0000007ffffffffUL
#define VM_MAX_SAFE_KERNEL_ADDRESS      VM_MAX_KERNEL_ADDRESS
#define VM_MAX_KERNEL_ADDRESS   (VM_MIN_KERNEL_ADDRESS + 
3*SEGMENT_LENGTH - 1)
#define VM_MAX_KERNEL_ADDRESS   0xffffefff
#define VM_MAX_SAFE_KERNEL_ADDRESS      VM_MAX_KERNEL_ADDRESS

I certainly didn't change anything :



root at eris:~ # openssl dgst -sha256 -r /usr/include/machine/vmparam.h
023d840eb725d4310904cd3fd6560e23761c0e1141f38e354d73af2f126602ee 
*/usr/include/machine/vmparam.h
root at eris:~ # openssl dgst -sha256 -r /usr/src/sys/powerpc/include/vmparam.h
023d840eb725d4310904cd3fd6560e23761c0e1141f38e354d73af2f126602ee 
*/usr/src/sys/powerpc/include/vmparam.h


In any case maybe I am wrong in some way and should try a boot
without setting kern.smp.disabled and see what happens.

Nope.

Machine will not boot.

So the exact same hardware will boot and run fine with RC1 but not with
RC2. That is certain.  Unless kern.smp.disabled=1 is set.

Dennis


More information about the freebsd-ppc mailing list