That is weird.
Why did syspatch believe this is a system it can operate on?
+aja +robert
>On Wed, May 22, 2019 at 12:31:48AM -0700, Mike Larkin wrote:
>> On Wed, May 22, 2019 at 08:46:06AM +0200, Matthieu Herrb wrote:
>> > Hi,
>> >
>> > The latest syspatch failed for me on one machine running syspatch:
>> >
>> > $ doas syspatch
>> > Get/Verify syspatch64-016_vmmints... 100% |*************| 170 KB
>> > 00:00
>> > Installing patch 016_vmmints
>> > Get/Verify syspatch64-017_rip6cks... 100% |*************| 193 KB
>> > 00:00
>> > Installing patch 017_rip6cksum
>> > Relinking to create unique kernel... failed!
>> >
>> > And /usr/share/relink/kernel/GENERIC.MP/relink.log contains:
>> >
>> > (SHA256) /bsd: OK
>> > LD="ld" sh makegap.sh 0xcccccccc
>> > ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o
>> > ${OBJS}
>> > vmm.o: In function `vmm_fpurestore':
>> > /usr/src/sys/arch/amd64/amd64/vmm.c:3887: undefined reference to
>> > `xsetbv_user'
>> > /usr/src/sys/arch/amd64/amd64/vmm.c:3887: undefined reference to
>> > `xsetbv_user'
>> > /usr/src/sys/arch/amd64/amd64/vmm.c:3887: undefined reference to
>> > `xsetbv_user'
>> > *** Error 1 in /usr/share/relink/kernel/GENERIC.MP (Makefile:988 'newbsd':
>> > @echo ld -T ld.script -X --warn-common -nopie -o newbsd '${SYSTEM...)
>> >
>>
>> Odd. That function is present in 6.4, not sure why it isn't being found.
>>
>> Can you objdump your KARL locore.o and see if xsetbv_user is there?
>
>Hi,
>
>xsetbv_user isn't in locore.o on this machine.
>
>I've checked another 6.4 machine and it's definatly here. Apparently I
>managed to get a pre-6.4 snapshot on the affected machine as the
>locore.o file there is dated from oct 6, 2018, while on the other
>(good one) it's from oct 11.
>
>Sorry for the noise.
>--
>Matthieu Herrb
>
>
