Re: Panic on boot after upgrade from r320827 -> r320869

On Mon, Jul 10, 2017 at 04:51:09AM -0700, David Wolfskill wrote: > Pnic occurred prior to mounting file systems While O. Hartmann had written to indicate the he had identified r320844 as the culprit, and I had other reason to suspect it, I was a bit busy at work yesterday, and unable to

Re: small patch for /etc/rc.d/nfsd, bugfix or POLA violation?

Cy Schubert wrote: >Rick Macklem wrote: >> Hi, >> >> The attached one line patch to /etc/rc.d/nfsd modifies the script so that i= >> t >> does not force the nfsuserd to be run when nfsv4_server_enable is set. >> (nfsuserd can still be enabled via nfsuserd_enable=3D"YES" is /etc/rc.conf.= >> ) >>

strip: elf_strptr failed: Invalid argument

Hello, I'm trying to build packages on an rpi3, on a freshly build image (with crochet), and when it's trying to build pkg from ports, I'm getting the following error message: libtool: link: cc -D_BSD_SOURCE -I../libpkg -I../libpkg -I../compat -I../external/libucl/klib -I../external/uthash

Re: beadm activate, cp: /tmp/BE-.../boot/zfs/zpool.cache: No such file or directory

On 2017-07-11 10:18, Graham Perrin wrote: > UEFI, booted from GELI-encrypted ZFS. > > Whenever I attempt to activate a boot environment, activation fails. > Instead, the environment is mounted. > > I tried both beadm and (below) beadm-devel. > > Thoughts? Is this, maybe, a known issue when

Re: Panic on boot after upgrade from r320827 -> r320869

On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill wrote: > On Mon, Jul 10, 2017 at 04:51:09AM -0700, David Wolfskill wrote: > > Pnic occurred prior to mounting file systems > > While O. Hartmann had written to indicate the he had identified r320844 > as the culprit, and

beadm activate, cp: /tmp/BE-.../boot/zfs/zpool.cache: No such file or directory

UEFI, booted from GELI-encrypted ZFS. Whenever I attempt to activate a boot environment, activation fails. Instead, the environment is mounted. I tried both beadm and (below) beadm-devel. Thoughts? Is this, maybe, a known issue when booting r320599 from encrypted ZFS? Also: at boot time, the

Re: Panic on boot after upgrade from r320827 -> r320869

On 7/11/17 1:09 PM, Warner Losh wrote: On a machine with SDHCI, a clean rebuild (after "r -rf /usr/obj") refuses to find /dev/ada0 :-( Take sdhci out of the kernel and try again. If that works, it tells us one thing (need to troubleshoot sdhci stuff more). If not it tells us another (need

Re: Panic on boot after upgrade from r320827 -> r320869

On 7/11/17 10:09 AM, Warner Losh wrote: > Plus we know we have at least one bug in meta-mode rebuilding since not > everything is being rebuilt that should be across this change. Yes I'm looking into that. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature

Re: Panic on boot after upgrade from r320827 -> r320869

On Tue, Jul 11, 2017 at 10:47 AM, Michael Butler wrote: > On 7/11/17 10:32 AM, Warner Losh wrote: > >> On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill >> wrote: >> >>> I believe that each of the machines has an MMC slot, but I also believe

r320183 (rpc.lockd cleanup) breaks virtualbox-ose build

This is a really strange problem ... Last week I upgraded my 12.0-CURRENT package build box from r318774 to r320570. I also upgraded the poudriere jail to match. When I went to build packages, the virtualbox-ose build failed due to ar segfaulting. To debug I created a new 12.0-CURRENT

Re: Panic on boot after upgrade from r320827 -> r320869

On Tue, Jul 11, 2017 at 08:32:26AM -0600, Warner Losh wrote: > ... > > While O. Hartmann had written to indicate the he had identified r320844 > > as the culprit, and I had other reason to suspect it, I was a bit busy > > at work yesterday, and unable to determine this for myself empirically. > >

Re: Panic on boot after upgrade from r320827 -> r320869

On 7/11/17 10:32 AM, Warner Losh wrote: On Tue, Jul 11, 2017 at 6:13 AM, David Wolfskill wrote: I believe that each of the machines has an MMC slot, but I also believe that in each case, it is empty. Is there anything else I might be able to do to help resolve this?

Run binary from test suite

(Resending due to moderation.) Hello! I'm a Google Summer of Code student, writing some tests for the FreeBSD test suite, and putting them under src/tests. I need to run some binaries, specifically pfctl. How should I call pfctl from my test scripts? Should I call it directly and let the

Re: Run binary from test suite

On Tue, Jul 11, 2017 at 10:38 AM, Panagiotes Mousikides wrote: > (Resending due to moderation.) > > Hello! > > I'm a Google Summer of Code student, writing some tests for the FreeBSD test > suite, and putting them under src/tests. I need to run some binaries, > specifically

Re: Run binary from test suite

Are you using pfctl at build time or does your ATF test script need it? I'm assuming the latter. In that case, it's fine to call it directly. Your PATH will be correctly configured. Don't use /usr/obj, because that may no longer exist by the time somebody is running the ATF test. -Alan On

Run binary from test suite

Hello! I'm a Google Summer of Code student, writing some tests for the FreeBSD test suite, and putting them under src/tests. I need to run some binaries, specifically pfctl. How should I call pfctl from my test scripts? Should I call it directly and let the shell find the binary in the

VLAN routing fails from VLAN -> non VLAN [was: Re: static routes on VLAN on CURRENT]

On Mon, 3 Jul 2017 06:29:41 +0200 "O. Hartmann" wrote: Hello, I figured some severe problemes with the configuration of the cheap SoHo smart-managed switch Netgear GS110TP. This piece of crap is way to smart for me. For short: If one leaves a port as "U" (untagged)

jemalloc_arena.c:821: Failed assertion: "nstime_compare(>epoc h, ) <= 0")

I'm trying to stabilize my new-ish Ryzen package build box. I've run into this error a couple of times: (: jemalloc_arena.c:821: Failed assertion: "nstime_compare(>epoc h, ) <= 0") most recently today when building llvm40. It seems to happen somewhat randomly. I don't remember seeing it

Re: small patch for /etc/rc.d/nfsd, bugfix or POLA violation?

On Tue, Jul 11, 2017 at 11:48:55AM +, Rick Macklem wrote: > Cy Schubert wrote: > > > >How about a warning message + an UPDATING entry + no MFC? And, relnotes = > >yes to say we now support RFC7530 in 12.0? > Sounds fine to me. I'll wait to see if there are more comments. Yes, this seems like

Re: Panic on boot after upgrade from r320827 -> r320869

On 07/11/17 13:13, I wrote: Take sdhci out of the kernel and try again. If that works, it tells us one thing (need to troubleshoot sdhci stuff more). If not it tells us another (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY command? Does it try multiple times per AHCI