FreeBSD_HEAD_amd64_gcc - Build #1345 - Fixed

2016-07-06 Thread jenkins-admin
FreeBSD_HEAD_amd64_gcc - Build #1345 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1345/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1345/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_amd64_gcc/1345/console

Re: Setting sysctl vfs.zfs.arc_max failed: 22

2016-07-06 Thread Steven Hartland
On 06/07/2016 02:25, Allan Jude wrote: On 2016-07-05 20:27, Steven Hartland wrote: Ahh right, let me check that. On 06/07/2016 00:51, Nathan Bosley wrote: I actually have this same problem. I'll send more details when I get home later. I think the problem started for me after r302265. Before

Re: Issues to maybe prioritize before pkg-base

2016-07-06 Thread Mark Felder
On Tue, Jul 5, 2016, at 13:01, Jeffrey Bouquet wrote: > Main disk would not boot cleanly. > could not fsck_ffs, cannot find inode > files went missing from /etc (make.conf, pf.conf, firewall*, > file went missing from rc.d > files went missing from /etc/X11 > shell history file remained locked.

Re: Setting sysctl vfs.zfs.arc_max failed: 22

2016-07-06 Thread Steven Hartland
The ARC settings and kmem aren't initialised when tunables are loaded so the tests fail. I've fixed this locally by blindly setting if ARC is not configured. Request to commit the fix is with re@ In the mean time the patch is attached. Thanks for the report and sorry about the breakage. On

Re: Setting sysctl vfs.zfs.arc_max failed: 22

2016-07-06 Thread Eric van Gyzen
On 07/06/16 03:35 PM, Steven Hartland wrote: > The ARC settings and kmem aren't initialised when tunables are loaded > so the tests fail. > > I've fixed this locally by blindly setting if ARC is not configured. > Request to commit the fix is with re@ > > In the mean time the patch is attached. > >

refcnt 0 on LLE at boot....

2016-07-06 Thread Larry Rosenman
First boot, and I got the following panic. 2nd boot ran just fine. borg.lerctr.org dumped core - see /var/crash/vmcore.0 Wed Jul 6 18:13:34 CDT 2016 FreeBSD borg.lerctr.org 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #5 r302379: Wed Jul 6 16:59:11 CDT 2016 r...@borg.lerctr.org:/usr/obj/usr/src/sys

Re: refcnt 0 on LLE at boot....

2016-07-06 Thread Larry Rosenman
Got a similar crash a few minutes later. On 2016-07-06 18:17, Larry Rosenman wrote: First boot, and I got the following panic. 2nd boot ran just fine. borg.lerctr.org dumped core - see /var/crash/vmcore.0 Wed Jul 6 18:13:34 CDT 2016 FreeBSD borg.lerctr.org 11.0-ALPHA6 FreeBSD 11.0-ALPHA6

Re: Setting sysctl vfs.zfs.arc_max failed: 22

2016-07-06 Thread Nathan Bosley
Awesome. I'll probably try this tonight or tomorrow. Thanks very much! On Wed, Jul 6, 2016 at 4:35 PM, Steven Hartland wrote: > The ARC settings and kmem aren't initialised when tunables are loaded so > the tests fail. > > I've fixed this locally by blindly setting if ARC is not configured. > R

Re: Setting sysctl vfs.zfs.arc_max failed: 22

2016-07-06 Thread Steven Hartland
On 06/07/2016 21:39, Eric van Gyzen wrote: On 07/06/16 03:35 PM, Steven Hartland wrote: The ARC settings and kmem aren't initialised when tunables are loaded so the tests fail. I've fixed this locally by blindly setting if ARC is not configured. Request to commit the fix is with re@ In the mea

difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-06 Thread Matthew Macy
As a first step towards managing linux user space in a chrooted /compat/linux, initially for i915 testing with intel gpu tools, later on to get widevine and steam to work I'm trying to get apt to work. I've fixed a number of issues to date in pseudofs/linprocfs but now I'm running in to a bug ca

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-06 Thread Don Lewis
On 6 Jul, Matthew Macy wrote: > As a first step towards managing linux user space in a chrooted > /compat/linux, initially for i915 testing with intel gpu tools, later > on to get widevine and steam to work I'm trying to get apt to work. > I've fixed a number of issues to date in pseudofs/linprocf

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-06 Thread K. Macy
On Wednesday, July 6, 2016, Don Lewis wrote: > On 6 Jul, Matthew Macy wrote: > > As a first step towards managing linux user space in a chrooted > > /compat/linux, initially for i915 testing with intel gpu tools, later > > on to get widevine and steam to work I'm trying to get apt to work. > > I

dtrace and kernel modules

2016-07-06 Thread Julian Elischer
I'm specifically interested in the case of kernel modules that instantiate new syscalls. How much support do we have for that? In the one example in our sources of a kld with a syscall (kgssapi.ko) dtrace seems to find regular function entrypoints but not the syscall. root@porridge:/usr/sr

Last call for 2016Q2 quarterly status reports

2016-07-06 Thread Benjamin Kaduk
Reminder: we're still looking for more submissions for the 2015Q2 status report! Please let us know if you wish to write an entry, even if it will not be finished by today. Thanks, Ben (for the monthly@ team) On Tue, 21 Jun 2016, Benjamin Kaduk wrote: > Dear FreeBSD Community, > > The deadline

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-06 Thread Andrey Chernov
On 07.07.2016 7:52, K. Macy wrote: > On Wednesday, July 6, 2016, Don Lewis wrote: > >> On 6 Jul, Matthew Macy wrote: >>> As a first step towards managing linux user space in a chrooted >>> /compat/linux, initially for i915 testing with intel gpu tools, later >>> on to get widevine and steam to w

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-06 Thread Matthew Macy
On Wed, 06 Jul 2016 23:28:40 -0700 Andrey Chernov wrote > On 07.07.2016 7:52, K. Macy wrote: > > On Wednesday, July 6, 2016, Don Lewis wrote: > > > >> On 6 Jul, Matthew Macy wrote: > >>> As a first step towards managing linux user space in a chrooted > >>> /compat/lin

Re: difference in SIGCHLD behavior between Linux and FreeBSD breaks apt

2016-07-06 Thread Andrey Chernov
On 07.07.2016 9:40, Matthew Macy wrote: > > > > On Wed, 06 Jul 2016 23:28:40 -0700 Andrey Chernov > wrote > > On 07.07.2016 7:52, K. Macy wrote: > > > On Wednesday, July 6, 2016, Don Lewis wrote: > > > > > >> On 6 Jul, Matthew Macy wrote: > > >>> As a first step towards