Re: r355097 make buildkernel: ports module graphics/gpu-firmware-kmod (all): could not find bsd.sysdir.mk

So when I committed the sysdir stuff I forgot to add it to the install list. I've fixed it now. Either upgrade, or just copy src/share/mk/ bsd.sysdir.mk to /usr/share/mk Warner On Mon, Nov 25, 2019, 9:40 PM Graham Perrin wrote: > The tail of my most recent run of > > make -j2 buildkernel

r355097 make buildkernel: ports module graphics/gpu-firmware-kmod (all): could not find bsd.sysdir.mk

The tail of my most recent run of make -j2 buildkernel KERNCONF=GENERIC-NODEBUG ===> Ports module graphics/gpu-firmware-kmod (all) cd ${PORTSDIR:-/usr/ports}/graphics/gpu-firmware-kmod; env  -u CC -u CXX  -u CPP  -u MAKESYSPATH  -u MK_AUTO_OBJ  -u MAKEOBJDIR MAKEFLAGS="-j 2 -J 15,16 -j 2 -J

Testing needed:)

Hi! Can someone with arm media file path type of storage device and someone with apple UEFI 1.10 test https://reviews.freebsd.org/D22553 please:) Other tests are also very welcome:) thanks, toomas ___ freebsd-current@freebsd.org mailing list

ng_snd_item: I thought(?) we fixed this :( r354843

I thought someone, somewhere fixed this, but it's hit again. core *IS* available, and I can give access as well. Unread portion of the kernel message buffer: panic: ng_snd_item: 42 != 1414 cpuid = 0 time = 1574707403 KDB: stack backtrace: db_trace_self_wrapper() at

Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

Ruslan Garipov wrote on 2019/11/25 19:26: [...] I didn't tried this with current but I am using it with stable (11.3 at this time). Building on Xeon E3-1240v3 and installing on many different machines. Some of them are 10+ years old AMD Opteron, some Xeon E5649, some 10 years old Intel

Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

On 11/25/2019 10:30 PM, Miroslav Lachman wrote: > Ruslan Garipov wrote on 2019/11/25 15:06: >> Hello. >> >> I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast >> virtual machine for other ones (all the virtual machines are hosted on >> VMware EXSi hypervisors, which have

Re: Fwd: [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: 0x41: Clock Unsynchronized)

On November 25, 2019 1:05:34 AM PST, "Vinícius Zavam" wrote: >as this one also hits HEAD, I am forwarding this email to current@. > >-- Forwarded message - >Von: Vinícius Zavam >Date: Do., 21. Nov. 2019 um 12:22 Uhr >Subject: [NTP] "Unexpected origin timestamp

Re: buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

Ruslan Garipov wrote on 2019/11/25 15:06: Hello. I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast virtual machine for other ones (all the virtual machines are hosted on VMware EXSi hypervisors, which have different physical CPUs). After `make -j16 buildworld` has finished

merge of NFSv4.2 support into head/current

Hi, I have completed development and a testing cycle for the NFSv4.2 (RFC-7862) code in base/projects/nfsv42 on subversion. NFSv4.2 is a minor revision to NFSv4.1 and adds support for the following optional features: - lseek(SEEK_DATA/SEEK_HOLE) - posix_fallocate() -

buildworld on CPU-A, installworld on CPU-B ends up with SIGILL

Hello. I want to build kernel and world (of FreeBSD 13.0-CURRENT) on a fast virtual machine for other ones (all the virtual machines are hosted on VMware EXSi hypervisors, which have different physical CPUs). After `make -j16 buildworld` has finished successfully on the build machine, I get

Fwd: [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: 0x41: Clock Unsynchronized)

as this one also hits HEAD, I am forwarding this email to current@. -- Forwarded message - Von: Vinícius Zavam Date: Do., 21. Nov. 2019 um 12:22 Uhr Subject: [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 00. from server" (kernel