Re: Newly upgraded -CURRENT box does not boot

2018-08-20 Thread Kyle Evans
On Mon, Aug 20, 2018 at 4:27 PM, Brett Gmoser wrote: > Hi there, > > I was told to e-mail these addresses with this. > > I did an `svn update` on /usr/src last night, build world and kernel as > usual. This morning I installed the kernel, booted into single user, > installed world and did

Re: building LLVM threads gets killed

2018-08-20 Thread Rodney W. Grimes
> On Mon, Aug 20, 2018 at 11:04 PM Mark Millard wrote: > > > Rodney W. Grimes freebsd-rwg at pdx.rh.CN85.dnsmgr.net wrote on > > Mon Aug 20 14:26:55 UTC 2018 : > > > > > > On 20 Aug 2018, at 05:01, blubee blubeeme > > wrote: > > > > > > > > > > I am running current compiling LLVM60 and when it

Re: building LLVM threads gets killed

2018-08-20 Thread blubee blubeeme
On Mon, Aug 20, 2018 at 11:04 PM Mark Millard wrote: > Rodney W. Grimes freebsd-rwg at pdx.rh.CN85.dnsmgr.net wrote on > Mon Aug 20 14:26:55 UTC 2018 : > > > > On 20 Aug 2018, at 05:01, blubee blubeeme > wrote: > > > > > > > > I am running current compiling LLVM60 and when it comes to linking >

soundcard.h expose device block size

2018-08-20 Thread blubee blubeeme
I'm looking at FreeBSD's soundcard.h and it doesn't seem to expose the hardware block size, this seems like a limitation stemming from FreeBSD's soundcard.h being an extension of OSS. Since we've already implemented a lot of additional features on top of the OSS API, is it possible to also expose

Re: Newly upgraded -CURRENT box does not boot

2018-08-20 Thread Warner Losh
On Mon, Aug 20, 2018 at 5:24 PM, Brett wrote: > On 8/20/2018 7:09 PM, Warner Losh wrote: > >> On Mon, Aug 20, 2018 at 4:50 PM, Brett >> wrote: >> >> Hi Kevin, >>> >>> Thanks for your help. >>> >>> Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make >>>

Re: Newly upgraded -CURRENT box does not boot

2018-08-20 Thread Brett
On 8/20/2018 7:09 PM, Warner Losh wrote: On Mon, Aug 20, 2018 at 4:50 PM, Brett wrote: Hi Kevin, Thanks for your help. Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make LOADER_DEFAULT_INTERP=4th installkernel"? Nope. Kernel has nothing to do with it. That won't work.

Re: Newly upgraded -CURRENT box does not boot

2018-08-20 Thread Warner Losh
On Mon, Aug 20, 2018 at 4:50 PM, Brett wrote: > Hi Kevin, > > Thanks for your help. > > Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make > LOADER_DEFAULT_INTERP=4th installkernel"? > Nope. Kernel has nothing to do with it. That won't work. I had also previously tried "

Re: Newly upgraded -CURRENT box does not boot

2018-08-20 Thread Brett
Hi Kevin, Thanks for your help. Should I be doing "make LOADER_DEFAULT_INTERP=4th buildkernel && make LOADER_DEFAULT_INTERP=4th installkernel"? I had also previously tried " make clean all install WITHOUT_LUA_LOADER=yes" in /usr/src/stand which did not help. Thanks! -Brett On 8/20/2018

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

2018-08-20 Thread Michael Gmelin
> On 20. Aug 2018, at 17:09, Konstantin Belousov wrote: > >> On Mon, Aug 20, 2018 at 12:45:12AM +0200, Michael Gmelin wrote: >> >> See here for a screenshot (also including the output of "show pte >> 0xf8000100"): >> >>

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

2018-08-20 Thread Dhananjay Balan
On Mon, Aug 20, 2018 at 05:48:04AM -0700, Cy Schubert wrote: > Make sure the archs are the same. Make sure the src and obj pathnames > on both servers are exactly the same. Make sure /usr/src (or wherever > you put it) is the same, it too needs to be rsynced. > > The tiniest differences will

Re: buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

2018-08-20 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Mon, 20 Aug 2018 21:24:21 +0200 "O. Hartmann" schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Building NanoBSD world on CURRENT r338113 fails due to: > > [...] > cd /pool/sources/CURRENT/src/rescue/rescue/../../sbin/gbde &&

Newly upgraded -CURRENT box does not boot

2018-08-20 Thread Brett Gmoser
Hi there, I was told to e-mail these addresses with this. I did an `svn update` on /usr/src last night, build world and kernel as usual. This morning I installed the kernel, booted into single user, installed world and did mergemaster -Ui as usual. The new kernel had booted fine. Upon

Re: CFT: TRIM Consolodation on UFS/FFS filesystems

2018-08-20 Thread Kirk McKusick
From: Kirk McKusick To: FreeBSD Current , FreeBSD Filesystems Subject: CFT: TRIM Consolodation on UFS/FFS filesystems Date: Mon, 20 Aug 2018 12:40:56 -0700 Oops, forgot that attachments get stripped. Below are the diffs for gathering statistics. Sorry to those of you on Gmail for whom

CFT: TRIM Consolodation on UFS/FFS filesystems

2018-08-20 Thread Kirk McKusick
I have recently added TRIM consolodation support for the UFS/FFS filesystem. This feature consolodates large numbers of TRIM commands into a much smaller number of commands covering larger blocks of disk space. Best described by the commit message: Author: mckusick Date: Sun Aug 19 16:56:42

Re: Loader post r338064 deletes GOP screen when asking geli passphrase

2018-08-20 Thread Kyle Evans
On Mon, Aug 20, 2018 at 1:01 PM, Harry Schmalzbauer wrote: > Hello, > > as far as I understand, r338064 should bring back default loader > environment. > > I'm UEFI booting r338093/amd64 (LynxPoint/Haswell). > > Since today, the GOP-console output of the first loader lines get deleted > when the

buildworld failure: Do not include ${SRCTOP}/sys when building bootstrap tools

2018-08-20 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Building NanoBSD world on CURRENT r338113 fails due to: [...] cd /pool/sources/CURRENT/src/rescue/rescue/../../sbin/gbde && MK_TESTS=no UPDATE_DEPENDFILE=no _RECURSING_CRUNCH=1

Loader post r338064 deletes GOP screen when asking geli passphrase

2018-08-20 Thread Harry Schmalzbauer
Hello, as far as I understand, r338064 should bring back default loader environment. I'm UEFI booting r338093/amd64 (LynxPoint/Haswell). Since today, the GOP-console output of the first loader lines get deleted when the geli passphrase prompt shows up. Nothing uncommon here, and never

Re: building LLVM threads gets killed

2018-08-20 Thread bob prohaska
On Mon, Aug 20, 2018 at 07:33:32PM +0200, Dimitry Andric wrote: > On 20 Aug 2018, at 16:26, Rodney W. Grimes > wrote: > > > >> It is running out of RAM while running multiple parallel link jobs. If > >> you are building using WITH_DEBUG, turn that off, it consumes large > >> amounts of memory.

Re: LUA boot loader coming very soon

2018-08-20 Thread Manfred Antar
> On Aug 20, 2018, at 10:47 AM, Kyle Evans wrote: > > On Mon, Aug 20, 2018 at 12:44 PM, Manfred Antar > wrote: >> >> >>> On Aug 20, 2018, at 9:20 AM, Warner Losh wrote: >>> >>> >>> >>> On Mon, Aug 20, 2018 at 9:55 AM, Kyle Evans wrote: >>> On Mon, Aug 20, 2018 at 10:39 AM, Manfred

Re: LUA boot loader coming very soon

2018-08-20 Thread Kyle Evans
On Mon, Aug 20, 2018 at 12:44 PM, Manfred Antar wrote: > > >> On Aug 20, 2018, at 9:20 AM, Warner Losh wrote: >> >> >> >> On Mon, Aug 20, 2018 at 9:55 AM, Kyle Evans wrote: >> On Mon, Aug 20, 2018 at 10:39 AM, Manfred Antar >> wrote: >> > Hi >> > How do i get the menu back after switching to

Re: LUA boot loader coming very soon

2018-08-20 Thread Manfred Antar
> On Aug 20, 2018, at 9:20 AM, Warner Losh wrote: > > > > On Mon, Aug 20, 2018 at 9:55 AM, Kyle Evans wrote: > On Mon, Aug 20, 2018 at 10:39 AM, Manfred Antar > wrote: > > Hi > > How do i get the menu back after switching to LUA loader? > > I’m using a comconsole. Before the switch to LUA

Re: building LLVM threads gets killed

2018-08-20 Thread Dimitry Andric
On 20 Aug 2018, at 16:26, Rodney W. Grimes wrote: > >> On 20 Aug 2018, at 05:01, blubee blubeeme wrote: >>> >>> 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

Re: LUA boot loader coming very soon

2018-08-20 Thread Warner Losh
On Mon, Aug 20, 2018 at 9:55 AM, Kyle Evans wrote: > On Mon, Aug 20, 2018 at 10:39 AM, Manfred Antar > wrote: > > Hi > > How do i get the menu back after switching to LUA loader? > > I’m using a comconsole. Before the switch to LUA I had a menu and a > little devil with pitchfork:) > > Now just

Re: LUA boot loader coming very soon

2018-08-20 Thread Kyle Evans
On Mon, Aug 20, 2018 at 10:39 AM, Manfred Antar wrote: > Hi > How do i get the menu back after switching to LUA loader? > I’m using a comconsole. Before the switch to LUA I had a menu and a little > devil with pitchfork:) > Now just get the countdown from 10 , then boot. > Here is my

Re: LUA boot loader coming very soon

2018-08-20 Thread Manfred Antar
Hi How do i get the menu back after switching to LUA loader? I’m using a comconsole. Before the switch to LUA I had a menu and a little devil with pitchfork:) Now just get the countdown from 10 , then boot. Here is my loader.conf.local: console="comconsole" beastie_disable="NO" hw.vga.textmode=1

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

2018-08-20 Thread Konstantin Belousov
On Mon, Aug 20, 2018 at 12:45:12AM +0200, Michael Gmelin wrote: > > See here for a screenshot (also including the output of "show pte > 0xf8000100"): > > https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658#file-ddb1-png It is too early for ddb routines to register. Ok can you

Re: building LLVM threads gets killed

2018-08-20 Thread Mark Millard
Rodney W. Grimes freebsd-rwg at pdx.rh.CN85.dnsmgr.net wrote on Mon Aug 20 14:26:55 UTC 2018 : > > On 20 Aug 2018, at 05:01, blubee blubeeme wrote: > > > > > > I am running current compiling LLVM60 and when it comes to linking > > > basically all the processes on my computer gets killed;

Re: What's this gregset_t gregs thing

2018-08-20 Thread blubee blubeeme
On Mon, Aug 20, 2018 at 9:49 PM Shawn Webb wrote: > On Mon, Aug 20, 2018 at 08:33:04AM +0800, blubee blubeeme wrote: > > Linux has gregset_t gregs; > > > https://github.com/lattera/glibc/blob/master/sysdeps/unix/sysv/linux/x86/sys/ucontext.h > > Please note that that repo is hopelessly old and

Re: building LLVM threads gets killed

2018-08-20 Thread blubee blubeeme
On Mon, Aug 20, 2018 at 10:26 PM Rodney W. Grimes < freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > > On 20 Aug 2018, at 05:01, blubee blubeeme wrote: > > > > > > I am running current compiling LLVM60 and when it comes to linking > > > basically all the processes on my computer gets killed; Chrome,

Re: building LLVM threads gets killed

2018-08-20 Thread Rodney W. Grimes
> On 20 Aug 2018, at 05:01, blubee blubeeme wrote: > > > > 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 > ... > > llvm/build % ninja -j8 > > [2408/2473]

Loading carp module crash i386 (12-ALPHA2), seems VNET related

2018-08-20 Thread Olivier Cochard-Labbé
Just loading carp kernel module is enough to panic it: [root@router]~# uname -a FreeBSD router.bsdrp.net 12.0-ALPHA2 FreeBSD 12.0-ALPHA2 r338100M i386 [root@router]~# kldload carp Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x14de0f4c fault

Re: What's this gregset_t gregs thing

2018-08-20 Thread Shawn Webb
On Mon, Aug 20, 2018 at 08:33:04AM +0800, blubee blubeeme wrote: > Linux has gregset_t gregs; > https://github.com/lattera/glibc/blob/master/sysdeps/unix/sysv/linux/x86/sys/ucontext.h Please note that that repo is hopelessly old and out-of-date. I created it as a mirror of the official glibc repo

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

2018-08-20 Thread Cy Schubert
In message <20180820062511.yaa2rimgmwpv3hxx@kazhap>, Dhananjay Balan writes: > On Sat, Aug 18, 2018 at 04:36:15PM -0700, Cy Schubert wrote: > > You can use NFS or rsync. Make sure the src and obj path names are > > exactly the same on all thes servers. I used to use NFS until a year or > > two

Re: What's this gregset_t gregs thing

2018-08-20 Thread Jan Beich
blubee blubeeme writes: > 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 >

Re: building LLVM threads gets killed

2018-08-20 Thread Dimitry Andric
On 20 Aug 2018, at 05:01, blubee blubeeme wrote: > > 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 ... > llvm/build % ninja -j8 > [2408/2473] Building CXX object

Re: building LLVM threads gets killed

2018-08-20 Thread Mark Millard
blubee blubeeme gurenchan at gmail.com wrote on Mon Aug 20 03:02:01 UTC 2018 : > 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 > . . . > last pid: 20965; load

Re: building LLVM threads gets killed

2018-08-20 Thread Mark Millard
[In part a resend from the right Email account. In part adding a note about another Mark Johnston patch for reporting information.] On 2018-Aug-19, at 11:25 PM, Mark Millard wrote: > blubee blubeeme gurenchan at gmail.com wrote on > Mon Aug 20 03:02:01 UTC 2018 : > >> I am running current

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

2018-08-20 Thread Dhananjay Balan
On Sat, Aug 18, 2018 at 04:36:15PM -0700, Cy Schubert wrote: > You can use NFS or rsync. Make sure the src and obj path names are > exactly the same on all thes servers. I used to use NFS until a year or > two ago when I started using different patches on different machines. > On occasion I've