Re: "Could not allocate I/O space" and "intsmb0 attach returned 6" in a under-Hyper-V context on Ryzen Threadripper: Is this expected?

2018-04-09 Thread Andriy Gapon
On 09/04/2018 22:37, John Baldwin wrote: > On Sunday, April 01, 2018 02:23:36 PM Mark Millard wrote: >> For: >> >> # uname -apKU >> FreeBSD FBSDHUGE 12.0-CURRENT FreeBSD 12.0-CURRENT r331831M amd64 amd64 >> 1200060 1200060 >> >> I get: >> >> . . . >> pci0: at device 7.3 (no driver attached) >>

Re: Odd ZFS boot module issue on r332158

2018-04-09 Thread Allan Jude
On 2018-04-09 19:11, Andrew Gallatin wrote: > I updated my main amd64 workstation to r332158 from something much > earlier (mid Jan). > > Upon reboot, all seemed well.  However, I later realized that the vmm.ko > module was not loaded at boot, because bhyve PCI passthru did not > work.  My loader.

Odd ZFS boot module issue on r332158

2018-04-09 Thread Andrew Gallatin
I updated my main amd64 workstation to r332158 from something much earlier (mid Jan). Upon reboot, all seemed well. However, I later realized that the vmm.ko module was not loaded at boot, because bhyve PCI passthru did not work. My loader.conf looks like (I'm passing a USB interface through):

Re: g_handleattr: md0 bio_length 24 len 31 -> EFAULT

2018-04-09 Thread Julian Elischer
On 8/4/18 10:48 pm, Kyle Evans wrote: On Sun, Apr 8, 2018 at 5:53 AM, Peter Holm wrote: On Sun, Apr 08, 2018 at 02:36:08AM -0700, Michael Dexter wrote: On 3/24/18 2:35 AM, O. Hartmann wrote: Writing out memory (md) backed images of UFS2 filesystems (NanoBSD images, created via the classical

Duplicate free in of file caps data

2018-04-09 Thread John Baldwin
I updated my laptop to HEAD as of Friday and got the following panic after a bhyve process using capabilities exited: panic: Duplicate free of 0xf8039515eba0 from zone 0xf8000200e540(16) slab 0xf8039515ef90(186) ... (kgdb) where #0 __curthread () at ./machine/pcpu.h:230 #1 doadump (

Re: "Could not allocate I/O space" and "intsmb0 attach returned 6" in a under-Hyper-V context on Ryzen Threadripper: Is this expected?

2018-04-09 Thread John Baldwin
On Sunday, April 01, 2018 02:23:36 PM Mark Millard wrote: > For: > > # uname -apKU > FreeBSD FBSDHUGE 12.0-CURRENT FreeBSD 12.0-CURRENT r331831M amd64 amd64 > 1200060 1200060 > > I get: > > . . . > pci0: at device 7.3 (no driver attached) > . . . > intsmb0: at device 7.3 on pci0 > intsmb0:

Re: Can't load linux64.ko module

2018-04-09 Thread John Baldwin
On Wednesday, April 04, 2018 02:34:53 PM Steve Kargl wrote: > On Wed, Apr 04, 2018 at 02:13:15PM -0700, Steve Kargl wrote: > > > > OK, so where is elf64_linux_vdso_fixup suppose to come from? > > > > The answer is compat/linux/linux_vdso.c where we find > > #if defined(__i386__) || (defined(__a

Re: Module compiles looking in /usr/src when alternate src tree is in use [actually the arm_neon.h and stdint.h issue]

2018-04-09 Thread bob prohaska
On Mon, Apr 09, 2018 at 06:04:24AM -0700, Mark Millard wrote: > On 2018-Apr-8, at 10:08 PM, bob prohaska wrote: > >> . . . > > On my RPi3 > > root@www:/usr/src # ls -l /usr/lib/clang/6.0.0/include/stdint.h > > -rw-r--r-- 1 root wheel 23387 Feb 16 07:37 > > /usr/lib/clang/6.0.0/include/stdint.

Re: Module compiles looking in /usr/src when alternate src tree is in use [actually the arm_neon.h and stdint.h issue]

2018-04-09 Thread Mark Millard
On 2018-Apr-8, at 10:08 PM, bob prohaska wrote: >> . . . > On my RPi3 > root@www:/usr/src # ls -l /usr/lib/clang/6.0.0/include/stdint.h > -rw-r--r-- 1 root wheel 23387 Feb 16 07:37 > /usr/lib/clang/6.0.0/include/stdint.h > > Every other file in that directory is dated January 22nd. > > >>

Re: i386 4/4 change

2018-04-09 Thread Konstantin Belousov
On Mon, Apr 09, 2018 at 08:22:13AM -0400, Yoshihiro Ota wrote: > What is the current status of this? > > Based on SVN history, it doesn't look https://reviews.freebsd.org/D14633 has > been merged/commited yet. I fixed bugs reported by Bruce. Right now the patch is waiting for some other testing

Re: i386 4/4 change

2018-04-09 Thread Yoshihiro Ota
What is the current status of this? Based on SVN history, it doesn't look https://reviews.freebsd.org/D14633 has been merged/commited yet. I can try after I recover from disk crahes. I expect I need few more days to restore. Will this retire PAE option? Thanks, Hiro On Sun, 1 Apr 2018 17:05:0

Re: buildworld fails: fatal error: 'netpfil/pf/pf.h' file not found

2018-04-09 Thread Vladimir Zakharov
On Mon, Apr 09, 2018, Kristof Provost wrote: > On 9 Apr 2018, at 10:50, Vladimir Zakharov wrote: > > For several days buildworld fails for me with the following error. > Cleaning > and > rebuilding didn't help. > > ===> tests/sys/netpfil/pf/ioctl (all) > --- validation --- >

Re: buildworld fails: fatal error: 'netpfil/pf/pf.h' file not found

2018-04-09 Thread Kristof Provost
On 9 Apr 2018, at 10:50, Vladimir Zakharov wrote: For several days buildworld fails for me with the following error. Cleaning and rebuilding didn't help. ===> tests/sys/netpfil/pf/ioctl (all) --- validation --- (cd /usr/src/tests/sys/netpfil/pf/ioctl && DEPENDFILE=.depend.validation NO_SUBDI

buildworld fails: fatal error: 'netpfil/pf/pf.h' file not found

2018-04-09 Thread Vladimir Zakharov
Hello! For several days buildworld fails for me with the following error. Cleaning and rebuilding didn't help. ===> tests/sys/netpfil/pf/ioctl (all) --- validation --- (cd /usr/src/tests/sys/netpfil/pf/ioctl && DEPENDFILE=.depend.validation NO_SUBDIR=1 make -f /usr/src/tests/sys/netpfil/pf/ioc