Re: kernel build failure

2018-08-19 Thread John Baldwin
On 8/14/18 1:35 AM, Matthew Macy wrote: > On Mon, Aug 13, 2018 at 5:33 PM Rick Macklem wrote: > >> Rodney W. Grimes wrote: On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > Sorry guys, last time I touched ZFS I tried to push to make it an >> option to > statically link and

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-19 Thread Matthew Seaman
On 19/08/2018 01:55, Shane Ambler wrote: >> I run 12-CURRENT on few machines, some more powerful that other (all >> of them x86_64, march varies). > You can use freebsd-update by setting up your own update server > https://www.freebsd.org/doc/en/articles/freebsd-update-server freebsd-upgrade(8)

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-19 Thread Miroslav Lachman
Dhananjay Balan wrote on 2018/08/19 00:34: Hi, I run 12-CURRENT on few machines, some more powerful that other (all of them x86_64, march varies). Is there is a way to avoid building CURRENT on all machines? Rather than building everywhere, can I just build it on the big server that I have and

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-19 Thread blubee blubeeme
On Sun, Aug 19, 2018 at 6:30 PM O. Hartmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Am Sun, 19 Aug 2018 00:34:20 +0200 > Dhananjay Balan schrieb: > > > Hi, > > > > I run 12-CURRENT on few machines, some more powerful that other (all > > of them x86_64, march varies). > >

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

2018-08-19 Thread Michael Gmelin
On Fri, 17 Aug 2018 10:02:08 +0100 John Baldwin wrote: > On 8/17/18 9:54 AM, Michael Gmelin wrote: > > > > > >> On 17. Aug 2018, at 08:17, John Baldwin wrote: > >> > >>> On 8/16/18 1:58 PM, Michael Gmelin wrote: > >>> > >>> > On 15. Aug 2018, at 15:55, Konstantin Belousov >

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Kyle Evans
On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: > On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: > >> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: >> > On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: >> > >> > > With today's change to LUA as the loader, I

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

2018-08-19 Thread Michael Gmelin
On Sun, 19 Aug 2018 19:16:42 +0300 Konstantin Belousov wrote: > On Sun, Aug 19, 2018 at 04:59:51PM +0200, Michael Gmelin wrote: > > > > > > On Fri, 17 Aug 2018 10:02:08 +0100 > > John Baldwin wrote: > > > > > On 8/17/18 9:54 AM, Michael Gmelin wrote: > > > > > > > > > > > >> On

panic excl->shared for an AF_LOCAL socket

2018-08-19 Thread Rick Macklem
Hi, PR#230752 shows a witness panic() for "excl->shared" on a vnode lock. In this case, the kernel RPC code is trying to do a soconnect() on an AF_LOCAL socket. The code is unp_connectat() looks like is does a straightforward namei()/lookup(), so I am surprised to see this. Does anyone know if

What's this gregset_t gregs thing

2018-08-19 Thread blubee blubeeme
Linux has gregset_t gregs; https://github.com/lattera/glibc/blob/master/sysdeps/unix/sysv/linux/x86/sys/ucontext.h Defined above, I also see it in the RISC-V glibc stuff as well. FreeBSD doesn't seem to have this field defined, I see FreeBSD uses /usr/include/x86/ucontext.h but there's no

Re: panic excl->shared for an AF_LOCAL socket

2018-08-19 Thread Matthew Macy
On Sun, Aug 19, 2018 at 4:32 PM Rick Macklem wrote: > Hi, > > PR#230752 shows a witness panic() for "excl->shared" on a vnode lock. > In this case, the kernel RPC code is trying to do a soconnect() on an > AF_LOCAL > socket. The code is unp_connectat() looks like is does a straightforward >

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread John Baldwin
On 8/19/18 5:28 PM, Kyle Evans wrote: > On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: >> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: >> >>> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > With

LUA loader: non UEFI boxes have weird ssh output

2018-08-19 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just updated some boxes to 12-CURRENT r338057 and I face a very strange behaviour: on non-UEFI booting boxes (older Fujitsu and Dell servers from 2008/2009, PCengine APU 2C4), logging in via ssh reveals broken output: even top does show nothing,

Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy)

2018-08-19 Thread Konstantin Belousov
On Sun, Aug 19, 2018 at 04:59:51PM +0200, Michael Gmelin wrote: > > > On Fri, 17 Aug 2018 10:02:08 +0100 > John Baldwin wrote: > > > On 8/17/18 9:54 AM, Michael Gmelin wrote: > > > > > > > > >> On 17. Aug 2018, at 08:17, John Baldwin wrote: > > >> > > >>> On 8/16/18 1:58 PM, Michael

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Warner Losh
On Sun, Aug 19, 2018 at 11:04 AM, Larry Rosenman wrote: > so it still looks forth'ish, but it's using lua. > It will always look forthish becuase it's unused in loader_lua. Warner ___ freebsd-current@freebsd.org mailing list

Re: LUA loader: non UEFI boxes have weird ssh output

2018-08-19 Thread Kyle Evans
On Sun, Aug 19, 2018 at 12:33 PM, O. Hartmann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Just updated some boxes to 12-CURRENT r338057 and I face a very strange > behaviour: > > on non-UEFI booting boxes (older Fujitsu and Dell servers from 2008/2009, > PCengine APU > 2C4),

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-19 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Sun, 19 Aug 2018 00:34:20 +0200 Dhananjay Balan schrieb: > Hi, > > I run 12-CURRENT on few machines, some more powerful that other (all > of them x86_64, march varies). > > Is there is a way to avoid building CURRENT on all machines? Rather

LUA loader: bhyve now doesn't?

2018-08-19 Thread Larry Rosenman
With today's change to LUA as the loader, I seem to have an issue with bhyhve: Consoles: userboot FreeBSD/amd64 User boot, Revision 1.1 (Thu Nov 16 15:04:02 CST 2017 r...@borg.lerctr.org) Startup error in /boot/lua/loader.lua: LUA ERROR: cannot open /boot/lua/loader.lua: no such file or

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Warner Losh
On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: > On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > > On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > > > > > With today's change to LUA as the loader, I seem to have an issue with > > > bhyhve: > > > > > > Consoles:

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Warner Losh
On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > With today's change to LUA as the loader, I seem to have an issue with > bhyhve: > > Consoles: userboot > > FreeBSD/amd64 User boot, Revision 1.1 > (Thu Nov 16 15:04:02 CST 2017 r...@borg.lerctr.org) > Startup error in

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Larry Rosenman
On Sun, Aug 19, 2018 at 09:42:05AM -0600, Warner Losh wrote: > On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: > > > On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > > > On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > > > > > > > With today's change to LUA as the

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Larry Rosenman
On Sun, Aug 19, 2018 at 11:28:10AM -0500, Kyle Evans wrote: > > filesystem? > > > > (CC'ing jhb@ and tychon@, who might have better insight) > > If we can swing it, I think the best model here should have always > been that userboot uses the host's scripts but the guest's > loader.conf. The

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Kyle Evans
On Sun, Aug 19, 2018 at 11:35 AM, Larry Rosenman wrote: > On Sun, Aug 19, 2018 at 11:28:10AM -0500, Kyle Evans wrote: >> > filesystem? >> > >> >> (CC'ing jhb@ and tychon@, who might have better insight) >> >> If we can swing it, I think the best model here should have always >> been that userboot

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Warner Losh
On Sun, Aug 19, 2018 at 11:03 AM, Kyle Evans wrote: > On Sun, Aug 19, 2018 at 11:58 AM, John Baldwin wrote: > > On 8/19/18 5:28 PM, Kyle Evans wrote: > >> On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: > >>> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman > wrote: > >>> > On Sun,

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Joe Maloney
I ran into this as well months ago. To workaround it I extracted userboot.so for the VM's, and launched bhyve with the alternate userboot.so. You can use a flag as described in the manpage to start userboot.so from an alternate location. https://www.freebsd.org/cgi/man.cgi?query=bhyveload=8

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Larry Rosenman
On Sun, Aug 19, 2018 at 11:54:51AM -0400, Joe Maloney wrote: > I ran into this as well months ago. To workaround it I extracted > userboot.so for the VM's, and launched bhyve with the alternate > userboot.so. You can use a flag as described in the manpage to start > userboot.so from an alternate

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Warner Losh
On Sun, Aug 19, 2018 at 10:05 AM, Larry Rosenman wrote: > On Sun, Aug 19, 2018 at 11:54:51AM -0400, Joe Maloney wrote: > > I ran into this as well months ago. To workaround it I extracted > > userboot.so for the VM's, and launched bhyve with the alternate > > userboot.so. You can use a flag as

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Warner Losh
On Sun, Aug 19, 2018 at 11:10 AM, Warner Losh wrote: > > I think including both loaders in userboot is probably a no-start >> based on the current interface. >> > > Yea, it would be a challenge... Sadly, we have POLA violations either way > we jump here. > Just to summarize the IRC

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Larry Rosenman
On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > On Sun, Aug 19, 2018 at 9:22 AM, Larry Rosenman wrote: > > > With today's change to LUA as the loader, I seem to have an issue with > > bhyhve: > > > > Consoles: userboot > > > > FreeBSD/amd64 User boot, Revision 1.1 > > (Thu Nov 16

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Larry Rosenman
On Sun, Aug 19, 2018 at 05:58:43PM +0100, John Baldwin wrote: > On 8/19/18 5:28 PM, Kyle Evans wrote: > > On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: > >> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: > >> > >>> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: >

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Kyle Evans
On Sun, Aug 19, 2018 at 11:58 AM, John Baldwin wrote: > On 8/19/18 5:28 PM, Kyle Evans wrote: >> On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: >>> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman wrote: >>> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > On Sun,

Re: LUA loader: bhyve now doesn't?

2018-08-19 Thread Warner Losh
On Sun, Aug 19, 2018 at 10:58 AM, John Baldwin wrote: > On 8/19/18 5:28 PM, Kyle Evans wrote: > > On Sun, Aug 19, 2018 at 10:42 AM, Warner Losh wrote: > >> On Sun, Aug 19, 2018 at 9:35 AM, Larry Rosenman > wrote: > >> > >>> On Sun, Aug 19, 2018 at 09:33:18AM -0600, Warner Losh wrote: > On

building LLVM threads gets killed

2018-08-19 Thread blubee blubeeme
I am running current compiling LLVM60 and when it comes to linking basically all the processes on my computer gets killed; Chrome, Firefox and some of the LLVM threads as well I am using ninja which is a little better but gmake or make are a lot worse. uname -a: FreeBSD blubee 12.0-CURRENT

Re: Sharing compiled builds between multiple 12-CURRENT boxes.

2018-08-19 Thread Shane Ambler
On 19/8/18 5:31 pm, Matthew Seaman wrote: > On 19/08/2018 01:55, Shane Ambler wrote: >>> I run 12-CURRENT on few machines, some more powerful that other (all >>> of them x86_64, march varies). > >> You can use freebsd-update by setting up your own update server >>