Re: GELI attach issue from r326073 -> r334996

2018-06-17 Thread Julian Elischer
On 14/6/18 4:46 am, Michael Jung wrote: On 2018-06-13 15:27, Ian Lepore wrote: On Wed, 2018-06-13 at 14:29 -0400, Michael Jung wrote: Hi! I just tried updating current from r326073 -> r334996 and when I try 'geli attach' I get the following error: # geli attach -p -k mykey.key /dev/gpt/da14 g

Re: ESXi NFSv4.1 client id is nasty

2018-06-17 Thread Benjamin Kaduk
On Sun, Jun 17, 2018 at 12:35:12PM +, Rick Macklem wrote: > Hi, > > Andreas Nagy has been doing a lot of testing of the NFSv4.1 client in ESXi > 6.5u1 > (VMware) against the FreeBSD server. I have given him a bunch of hackish > patches > to try and some of them do help. However not all issue

head -r335307 breaks various builds on ci.freebsd.org (powerpc64, mips64, sparc64)

2018-06-17 Thread Mark Millard
https://ci.freebsd.org/job/FreeBSD-head-powerpc64-build/6086/consoleText (and later) shows: --- all_subdir_tests --- cc1: warnings being treated as errors /usr/src/tests/sys/audit/inter-process.c: In function 'atfu_shmat_success_body': /usr/src/tests/sys/audit/inter-process.c:463: warning: cast f

Re: NFSv4.1 server deficiencies fixed for ESXi client

2018-06-17 Thread Rick Macklem
Rodney W. Grimes wrote: [stuff snipped] >Have you any contact with VMWare so that they might fix the issues >in their code, rather than having to put hacks in FreeBSD for these >issues? Nope. I tried an email to nf...@ietf.org about one issue (that isn't yet resolved related to it complaining that

Re: NFSv4.1 server deficiencies fixed for ESXi client

2018-06-17 Thread Rodney W. Grimes
> Hi, > > Since I posted w.r.t. issues that seem to violate the RFC, I figured I should > also > post ones that identified deficiencies in the FreeBSD server. These have > either > been patched in head/current or will be soon and will be MFC'd. > > - BindConnectiontoSession wasn't implemented.

NFSv4.1 server deficiencies fixed for ESXi client

2018-06-17 Thread Rick Macklem
Hi, Since I posted w.r.t. issues that seem to violate the RFC, I figured I should also post ones that identified deficiencies in the FreeBSD server. These have either been patched in head/current or will be soon and will be MFC'd. - BindConnectiontoSession wasn't implemented. It is never used by

ESXi NFSv4.1 client id is nasty

2018-06-17 Thread Rick Macklem
Hi, Andreas Nagy has been doing a lot of testing of the NFSv4.1 client in ESXi 6.5u1 (VMware) against the FreeBSD server. I have given him a bunch of hackish patches to try and some of them do help. However not all issues are resolved. The problem is that these hacks pretty obviously violate the N

Re: freebsd bhyve instance does not show kernel messages after boot screen

2018-06-17 Thread tech-lists
On 15/06/2018 15:02, Rodney W. Grimes wrote: With the VM shutdown look in /dev/vmm for the same name as the VM, if you see it there, make sure you do not have a running instnace of it, then do: bhyvectl --destroy --name=fbsd11-vm You may have remanants of a prior/crashed VM hanging around causin

Panic on RPI boot with revision 335282

2018-06-17 Thread Tom Vijlbrief
I get an: panic: Assertion zone->uz_flags & UMA_ZONE_PCPU failed at /media/swan/src.svn/sys/vm/uma_core.c:2239 A one month old kernel runs fine, uma_core.c was edited at that location 9 days ago ___ freebsd-current@freebsd.org mailing list https://lists

r335282: first stage boot failure on PCengines APU 2C4

2018-06-17 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Running CURRENT as routing and firewalling appliance on a PCengines APU 2C4 with the latest (official) SEABios available for this product, NanoBSD (FreeBSD CURRENT FreeBSD 12.0-CURRENT #60 r335278: Sun Jun 17 07:57:20 CEST 2018 amd64)is unable to b