[Bug 225182] devel/powerpc64-xtoolchain-gcc: SLOF Data Storage Exception on boot with kernel built with devel/powerpc64-xtoolchain-gcc

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225182

--- Comment #23 from Kenneth Salerno <kennethsalerno at yahoo.com> ---
I want to add two somewhat related notes here.

1. At some point devel/binutils started using a BUTARGET?=     
${PKGNAMEPREFIX}unknown-${OPSYS:tl}${OSREL} which equates to
CROSS_BINUTILS_PREFIX= /usr/local/bin/powerpc64-unknown-freebsd11.1- in my
environment, where previously I was used to seeing CROSS_BINUTILS_PREFIX=
powerpc64-freebsd- (devel/amd64-binutils forces this previous behavior I was
used to with BUTARGET=       x86_64-${OPSYS:tl})

The net of this is I had a CROSS_BINUTILS_PREFIX pointing to nowhere. Fixed
that in my make.conf. Still have RELEASE-11.1 kernel blowing up with gcc5&6
either way, but want to ensure I'm using binutils 2.30.

2. This one is a complete mystery to me: if I set KERNCONF, even if I copy
GENERIC64 exactly, I get the Data Storage Exception in SLOF. If I copy my
kernel config to overwrite GENERIC64 (and not set KERNCONF) the kernel will
boot normally, if built with the system compiler (again, still getting Data
Storage Exception with gcc5&6 no matter what configuration I use).

To reproduce error with system compiler:
cp /usr/src/sys/powerpc/conf/GENERIC64 /usr/src/sys/powerpc/conf/SALERNO
make buildkernel __MAKE_CONF=/dev/null __SRC_CONF=/dev/null KERNCONF=SALERNO
ARCH=powerpc TARGET_ARCH=powerpc64
(this kernel will cause a Data Storage Exception)

Then take the custom kernel config and overwrite GENERIC64:
cp /root/kernels/SALERNO /usr/src/sys/powerpc/conf/GENERIC64
make buildkernel __MAKE_CONF=/dev/null __SRC_CONF=/dev/null ARCH=powerpc
TARGET_ARCH=powerpc64
(this kernel will boot normally)

3. Previously in RELEASE-11.0 and older, I could build and boot a kernel
excluding CTF. Now with 11.1, I get a Data Storage Exception if I do this,
forcing me to build including CTF.

-- 
You are receiving this mail because:
You are on the CC list for the bug.