uniq busted?

2013-09-11 Thread Don Lewis
I justed updated my 10.0-CURRENT box and ran into major problems with
port building.  I tracked the problem down to uniq not working.

# wc -l /etc/termcap
4666 /etc/termcap
# cat /etc/termcap | uniq
uniq: unable to limit ioctls for stdout: Capabilities insufficient

It complains about capabilities and nothing comes out ...

My kernel and userland are in sync, so the 20130905 note in src/UPDATING
shouldn't be a factor.  I'm not running a GENERIC kernel, but I include
GENERIC in my kernel config file:

# uname -a
FreeBSD scratch.catspoiler.org 10.0-CURRENT FreeBSD 10.0-CURRENT #32 r255089: 
Sat Aug 31 02:27:17 PDT 2013 
d...@scratch.catspoiler.org:/usr/obj/usr/src/sys/GENERICSMB  i386

# cat GENERICSMB
include GENERIC

nocpu   I486_CPU
nocpu   I586_CPU

options EXT2FS  # ext2 Filesystem

options BREAK_TO_DEBUGGER
options ALT_BREAK_TO_DEBUGGER
options DEBUG_VFS_LOCKS
#optionsDEBUG_LOCKS
#optionsKTR
#optionsKTR_VERBOSE
#optionsKTR_COMPILE=(KTR_EVH)
#optionsDEVICE_POLLING

#nooptions  WITNESS_SKIPSPIN
#nooptions  SMP


What am I doing wrong?

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: uniq busted?

2013-09-11 Thread Don Lewis
On 11 Sep, To: freebsd-current@freebsd.org wrote:
 I justed updated my 10.0-CURRENT box and ran into major problems with
 port building.  I tracked the problem down to uniq not working.
 
 # wc -l /etc/termcap
 4666 /etc/termcap
 # cat /etc/termcap | uniq
 uniq: unable to limit ioctls for stdout: Capabilities insufficient
 
 It complains about capabilities and nothing comes out ...
 
 My kernel and userland are in sync, so the 20130905 note in src/UPDATING
 shouldn't be a factor.  I'm not running a GENERIC kernel, but I include
 GENERIC in my kernel config file:
 
 # uname -a
 FreeBSD scratch.catspoiler.org 10.0-CURRENT FreeBSD 10.0-CURRENT #32 r255089: 
 Sat Aug 31 02:27:17 PDT 2013 
 d...@scratch.catspoiler.org:/usr/obj/usr/src/sys/GENERICSMB  i386
 
 # cat GENERICSMB
 include   GENERIC
 
 nocpu I486_CPU
 nocpu I586_CPU
 
 options   EXT2FS  # ext2 Filesystem
 
 options   BREAK_TO_DEBUGGER
 options   ALT_BREAK_TO_DEBUGGER
 options   DEBUG_VFS_LOCKS
 #options  DEBUG_LOCKS
 #options  KTR
 #options  KTR_VERBOSE
 #options  KTR_COMPILE=(KTR_EVH)
 #options  DEVICE_POLLING
 
 #nooptionsWITNESS_SKIPSPIN
 #nooptionsSMP
 
 
 What am I doing wrong?

It seems like it was some sort of kernel/userland mismatch after all.

I played around with uniq and found that
uniq /etc/termcap
was able to fstat() the input descriptor but read() would fail with
ENOTCAPABLE.  The cap_rights_init() call seemed to be doing the right
thing, so I tried adding a call to cap_rights_get() after
cap_rights_limit() to try to observe how the kernel was interpreting the
rights.  Strangely cap_rights_get() always failed with EFAULT.  I even
tried passing an invalid fd to cap_rights_get() and still got an EFAULT
return, even though sys___cap_rights_get() validates the fd before it
ever touches the buffer.  In order to debug that, I added a printf()
call to sys___cap_rights_get().  I then went to the kernel object
directory, ran make, which only recompiled sys_capability.c and relinked
the kernel, and then ran make reinstall.  After rebooting, both uniq
and cap_rights_get() started working as they should.

I did check the timestamps on the kernel and /usr/bin/uniq before
sending my original message and they were both recent.  I also build
both world and the kernel using a script that does both, so I know that
they were both rebuilt before being installed.  The only thing I can
think of is that maybe I forgot to reboot to bring up the new kernel.

Sigh ...

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Chicken and egg problem when building (third-party) kernel modules with bsd.kmod.mk -- how to solve?

2013-09-11 Thread Lev Serebryakov
Hello, Freebsd-current.

 It is good idea to set KERNBUILDDIR when build module. But to set it you
need to know ${.OBJDIR} from ${SYSDIR} and ${SYSDIR} is set in bsd.kmod.mk,
which should be included last (after defining KERNBUILDDIR).

 How this loop could be broken?

-- 
// Black Lion AKA Lev Serebryakov l...@freebsd.org

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on ia64/ia64

2013-09-11 Thread FreeBSD Tinderbox
TB --- 2013-09-11 12:48:28 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-11 12:48:28 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE 
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2013-09-11 12:48:28 - starting HEAD tinderbox run for ia64/ia64
TB --- 2013-09-11 12:48:28 - cleaning the object tree
TB --- 2013-09-11 12:48:28 - /usr/local/bin/svn stat /src
TB --- 2013-09-11 12:48:31 - At svn revision 255470
TB --- 2013-09-11 12:48:32 - building world
TB --- 2013-09-11 12:48:32 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 12:48:32 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 12:48:32 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 12:48:32 - SRCCONF=/dev/null
TB --- 2013-09-11 12:48:32 - TARGET=ia64
TB --- 2013-09-11 12:48:32 - TARGET_ARCH=ia64
TB --- 2013-09-11 12:48:32 - TZ=UTC
TB --- 2013-09-11 12:48:32 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 12:48:32 - cd /src
TB --- 2013-09-11 12:48:32 - /usr/bin/make -B buildworld
 Building an up-to-date make(1)
 World build started on Wed Sep 11 12:48:39 UTC 2013
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
 stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 World build completed on Wed Sep 11 14:26:53 UTC 2013
TB --- 2013-09-11 14:26:53 - generating LINT kernel config
TB --- 2013-09-11 14:26:53 - cd /src/sys/ia64/conf
TB --- 2013-09-11 14:26:53 - /usr/bin/make -B LINT
TB --- 2013-09-11 14:26:53 - cd /src/sys/ia64/conf
TB --- 2013-09-11 14:26:53 - /usr/sbin/config -m LINT
TB --- 2013-09-11 14:26:53 - building LINT kernel
TB --- 2013-09-11 14:26:53 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 14:26:53 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 14:26:53 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 14:26:53 - SRCCONF=/dev/null
TB --- 2013-09-11 14:26:53 - TARGET=ia64
TB --- 2013-09-11 14:26:53 - TARGET_ARCH=ia64
TB --- 2013-09-11 14:26:53 - TZ=UTC
TB --- 2013-09-11 14:26:53 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 14:26:53 - cd /src
TB --- 2013-09-11 14:26:53 - /usr/bin/make -B buildkernel KERNCONF=LINT
 Kernel build for LINT started on Wed Sep 11 14:26:53 UTC 2013
 stage 1: configuring the kernel
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3.1: making dependencies
 stage 3.2: building everything
[...]
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
-Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. -I/src/sys 
-I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=15000 --param inline-unit-growth=100 --param 
large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 
-mfixed-range=f32-f127 -fpic -ffreestanding -Werror  /src/sys/kern/uipc_shm.c
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
-Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. -I/src/sys 
-I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=15000 --param inline-unit-growth=100 --param 
large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 
-mfixed-range=f32-f127 -fpic -ffreestanding -Werror  
/src/sys/kern/uipc_sockbuf.c
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
-Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. -I/src/sys 
-I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 
-finline-limit=15000 --param inline-unit-growth=100 --param 
large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 
-mfixed-range=f32-f127 -fpic -ffreestanding -Werror  /src/sys/kern/uipc_socket.c
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
-Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. -I/src/sys 
-I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL 
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common 

SVN r255467 breaks kernel build on -current

2013-09-11 Thread Michael Butler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

GCC complains about two uninitialized variables:


*** sys/kern/uipc_syscalls.c~   Wed Sep 11 07:52:16 2013
- --- sys/kern/uipc_syscalls.cWed Sep 11 08:29:43 2013
***
*** 2189,2199 
struct socket *so;
struct mbuf *m;
struct sf_buf *sf;
!   struct vm_page *pg;
struct shmfd *shmfd;
struct sendfile_sync *sfs;
struct vattr va;
!   off_t off, xfsize, fsbytes, sbytes, rem, obj_size;
int error, bsize, nd, hdrlen, mnw;
bool inflight_called;

- --- 2189,2199 
struct socket *so;
struct mbuf *m;
struct sf_buf *sf;
!   struct vm_page *pg = NULL;
struct shmfd *shmfd;
struct sendfile_sync *sfs;
struct vattr va;
!   off_t off, xfsize, fsbytes, sbytes, rem, obj_size = 0;
int error, bsize, nd, hdrlen, mnw;
bool inflight_called;

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (FreeBSD)

iEYEARECAAYFAlIwgncACgkQQv9rrgRC1JJA5QCeNUkHfL7IwnQV4xdYlcbkUn/W
nGkAn0dxVf7EWEpTBQzki/TrLS9a5+w9
=2rpA
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: HEADS UP: OpenSSH with DNSSEC support in 10

2013-09-11 Thread Ian Lepore
On Wed, 2013-09-11 at 17:00 +0200, Dag-Erling Smørgrav wrote:
 OpenSSH in FreeBSD 10 is now built with DNSSEC support, unless you
 disable LDNS in src.conf.  If DNSSEC is enabled, the default setting for
 VerifyHostKeyDNS is yes.  This means that OpenSSH will silently trust
 DNSSEC-signed SSHFP records.  I consider this a lesser evil than ask
 (aka train the user to type 'yes' and hit enter) and no (aka train
 the user to type 'yes' and hit enter without even the benefit of a
 second opinion).
 
 DES

So what happens when there is no dns server to consult?  Will every ssh
connection have to wait for a long dns query timeout?

What if the machine is configured to use only /etc/hosts?

What if a DNS server is configured but doesn't respond?

For that matter, I just realized I'm a bit unclear on who is querying
DNS for this info, the ssh client or the sshd?

-- Ian


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: New iSCSI stack.

2013-09-11 Thread Outback Dingo
On Sun, Sep 8, 2013 at 9:32 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 6:29 AM, Edward Tomasz Napierała tr...@freebsd.org
  wrote:

 Wiadomość napisana przez Alfred Perlstein bri...@mu.org w dniu 6 wrz
 2013, o godz. 20:18:
  On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote:
  Hello.  At http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll 
  find
  a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
  To use the new initiator, start with man iscsictl.  For the target -
 man
  ctld.
 
  All feedback is welcome.  If nothing unexpected comes up, I'll commit
 it
  in a few days from now.  Note that it's still not optimized; at this
 point
  I'm focusing more on reliability and interoperability.
 
  This work is being sponsored by FreeBSD Foundation.
 
  ___
  freebsd-current@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-current
  To unsubscribe, send any mail to 
 freebsd-current-unsubscr...@freebsd.org
 
  Edward, this is really exciting!
 
  Is there an easy way to use the userland iscsi configuration files?

 Which iSCSI userland configuration files, the ctl.conf(5)?  If you need
 an ability to parse it and modify from a shell scripts, see confctl
 utility
 (sysutils/confctl, https://github.com/trasz/confctl/).

  We would love to quickly backport and ship this with FreeNAS as an
 option for our users, having the config files be the same OR having a very
 good converter would really make that much easier for us.

 Porting to 9 should be quite easy - there are Capsicum API differences;
 you might also want to compare CTL between 10 and 9 to see if there are
 any changes which need to be merged.  Taking a look at the code searching
 for possible security issues would be also very welcome :-)

 As for the config files - writing a converter should be quite easy.  Which
 configuration files you need to support, ctl.conf(5) and istgt
 configuration?


 I was i belive quite close to having it working on the last patch, however
 could never seem to get the ctl kernel module to function,
 And feel im a bit further away with this latest patch retracing my steps,
 from previous... quite easy to backport maybe for you, or other
 but yes, I also would like to integrate the work to stable/9 in the lab
 for some benchmarks



Still trying to tackle this.. any ideas?? I think if i can get past the
few errors im encountering i can get a patch against stable/9 for others to
test

clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
-fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
-mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option  -Wno-error-tautological-compare
-Wno-error-empty-body  -Wno-error-parentheses-equality -c
/usr/home/dingo/devel/sys/modules/ctl/../../cam/ctl/ctl_frontend_cam_sim.c
ctfconvert -L VERSION -g ctl_frontend_cam_sim.o
clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
-fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
-mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
 -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
-fdiagnostics-show-option  -Wno-error-tautological-compare
-Wno-error-empty-body  -Wno-error-parentheses-equality -c
/usr/home/dingo/devel/sys/modules/ctl/../../cam/ctl/ctl_frontend_internal.c
ctfconvert -L VERSION -g ctl_frontend_internal.o
clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc   -DHAVE_KERNEL_OPTION_HEADERS -include
/usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ -I@/contrib/altq
-fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
-mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
 -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
-std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
-Wredundant-decls -Wnested-externs 

HEADS UP: OpenSSH with DNSSEC support in 10

2013-09-11 Thread Dag-Erling Smørgrav
OpenSSH in FreeBSD 10 is now built with DNSSEC support, unless you
disable LDNS in src.conf.  If DNSSEC is enabled, the default setting for
VerifyHostKeyDNS is yes.  This means that OpenSSH will silently trust
DNSSEC-signed SSHFP records.  I consider this a lesser evil than ask
(aka train the user to type 'yes' and hit enter) and no (aka train
the user to type 'yes' and hit enter without even the benefit of a
second opinion).

DES
-- 
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

[head tinderbox] failure on mips/mips

2013-09-11 Thread FreeBSD Tinderbox
TB --- 2013-09-11 14:42:00 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-11 14:42:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE 
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2013-09-11 14:42:00 - starting HEAD tinderbox run for mips/mips
TB --- 2013-09-11 14:42:00 - cleaning the object tree
TB --- 2013-09-11 14:42:00 - /usr/local/bin/svn stat /src
TB --- 2013-09-11 14:42:20 - At svn revision 255470
TB --- 2013-09-11 14:42:21 - building world
TB --- 2013-09-11 14:42:21 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 14:42:21 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 14:42:21 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 14:42:21 - SRCCONF=/dev/null
TB --- 2013-09-11 14:42:21 - TARGET=mips
TB --- 2013-09-11 14:42:21 - TARGET_ARCH=mips
TB --- 2013-09-11 14:42:21 - TZ=UTC
TB --- 2013-09-11 14:42:21 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 14:42:21 - cd /src
TB --- 2013-09-11 14:42:21 - /usr/bin/make -B buildworld
 Building an up-to-date make(1)
 World build started on Wed Sep 11 14:42:28 UTC 2013
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
 stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 World build completed on Wed Sep 11 15:43:19 UTC 2013
TB --- 2013-09-11 15:43:19 - cd /src/sys/mips/conf
TB --- 2013-09-11 15:43:19 - /usr/sbin/config -m ADM5120
TB --- 2013-09-11 15:43:19 - skipping ADM5120 kernel
TB --- 2013-09-11 15:43:19 - cd /src/sys/mips/conf
TB --- 2013-09-11 15:43:19 - /usr/sbin/config -m ALCHEMY
TB --- 2013-09-11 15:43:19 - skipping ALCHEMY kernel
TB --- 2013-09-11 15:43:19 - cd /src/sys/mips/conf
TB --- 2013-09-11 15:43:19 - /usr/sbin/config -m AP121
TB --- 2013-09-11 15:43:19 - building AP121 kernel
TB --- 2013-09-11 15:43:19 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 15:43:19 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 15:43:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 15:43:19 - SRCCONF=/dev/null
TB --- 2013-09-11 15:43:19 - TARGET=mips
TB --- 2013-09-11 15:43:19 - TARGET_ARCH=mips
TB --- 2013-09-11 15:43:19 - TZ=UTC
TB --- 2013-09-11 15:43:19 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 15:43:19 - cd /src
TB --- 2013-09-11 15:43:19 - /usr/bin/make -B buildkernel KERNCONF=AP121
 Kernel build for AP121 started on Wed Sep 11 15:43:19 UTC 2013
 stage 1: configuring the kernel
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3.1: making dependencies
 stage 3.2: building everything
[...]
cc  -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1 
--param large-function-growth=10 --param max-inline-insns-single=1  
-fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x8005 -march=mips32 -msoft-float 
-ffreestanding -Werror  /src/sys/kern/uipc_shm.c
cc  -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1 
--param large-function-growth=10 --param max-inline-insns-single=1  
-fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x8005 -march=mips32 -msoft-float 
-ffreestanding -Werror  /src/sys/kern/uipc_sockbuf.c
cc  -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1 
--param large-function-growth=10 --param max-inline-insns-single=1  
-fno-pic -mno-abicalls -G0 -DKERNLOADADDR=0x8005 -march=mips32 -msoft-float 
-ffreestanding -Werror  /src/sys/kern/uipc_socket.c
cc  -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  

Re: HEADS UP: OpenSSH with DNSSEC support in 10

2013-09-11 Thread Ian Lepore
On Wed, 2013-09-11 at 17:42 +0200, Dag-Erling Smørgrav wrote:
 Ian Lepore i...@freebsd.org writes:
  So what happens when there is no dns server to consult?  Will every
  ssh connection have to wait for a long dns query timeout?  What if the
  machine is configured to use only /etc/hosts?
 
 If there is no DNS server, no query will be sent.
 
  What if a DNS server is configured but doesn't respond?
 
 The DNS request will time out.
 
 In the vast majority of cases, you will either have no DNS at all (so no
 query will be sent), or you will have a functioning DNS server.  In a
 slightly less vast majority of cases, you will not be able to resolve
 the server's IP address without DNS anyway.
 
  For that matter, I just realized I'm a bit unclear on who is querying
  DNS for this info, the ssh client or the sshd?
 
 The client - and you can override this in your ~/.ssh/config or on the
 command line (-oVerifyHostKeyDNS=no).
 
 DES
 -- 

Thanks.  If this is client-side I'm much less scared by it.  At $work we
have embedded systems with less than full network functionality, often
including either /etc/hosts usage or worse, sometimes a dns is
configured but unreachable, and we ssh into them a lot for development.

-- Ian


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on mips64/mips

2013-09-11 Thread FreeBSD Tinderbox
TB --- 2013-09-11 15:15:23 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-11 15:15:23 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE 
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2013-09-11 15:15:23 - starting HEAD tinderbox run for mips64/mips
TB --- 2013-09-11 15:15:23 - cleaning the object tree
TB --- 2013-09-11 15:15:23 - /usr/local/bin/svn stat /src
TB --- 2013-09-11 15:15:27 - At svn revision 255470
TB --- 2013-09-11 15:15:28 - building world
TB --- 2013-09-11 15:15:28 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 15:15:28 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 15:15:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 15:15:28 - SRCCONF=/dev/null
TB --- 2013-09-11 15:15:28 - TARGET=mips
TB --- 2013-09-11 15:15:28 - TARGET_ARCH=mips64
TB --- 2013-09-11 15:15:28 - TZ=UTC
TB --- 2013-09-11 15:15:28 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 15:15:28 - cd /src
TB --- 2013-09-11 15:15:28 - /usr/bin/make -B buildworld
 Building an up-to-date make(1)
 World build started on Wed Sep 11 15:15:35 UTC 2013
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
 stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 World build completed on Wed Sep 11 16:17:32 UTC 2013
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m ADM5120
TB --- 2013-09-11 16:17:32 - skipping ADM5120 kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m ALCHEMY
TB --- 2013-09-11 16:17:32 - skipping ALCHEMY kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AP121
TB --- 2013-09-11 16:17:32 - skipping AP121 kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AP91
TB --- 2013-09-11 16:17:32 - skipping AP91 kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AP93
TB --- 2013-09-11 16:17:32 - skipping AP93 kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AP94
TB --- 2013-09-11 16:17:32 - skipping AP94 kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AP96
TB --- 2013-09-11 16:17:32 - skipping AP96 kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AR71XX_BASE
TB --- 2013-09-11 16:17:32 - skipping AR71XX_BASE kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AR724X_BASE
TB --- 2013-09-11 16:17:32 - skipping AR724X_BASE kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AR91XX_BASE
TB --- 2013-09-11 16:17:32 - skipping AR91XX_BASE kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AR933X_BASE
TB --- 2013-09-11 16:17:32 - skipping AR933X_BASE kernel
TB --- 2013-09-11 16:17:32 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:32 - /usr/sbin/config -m AR934X_BASE
TB --- 2013-09-11 16:17:33 - skipping AR934X_BASE kernel
TB --- 2013-09-11 16:17:33 - cd /src/sys/mips/conf
TB --- 2013-09-11 16:17:33 - /usr/sbin/config -m BERI_DE4_MDROOT
TB --- 2013-09-11 16:17:33 - building BERI_DE4_MDROOT kernel
TB --- 2013-09-11 16:17:33 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 16:17:33 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 16:17:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 16:17:33 - SRCCONF=/dev/null
TB --- 2013-09-11 16:17:33 - TARGET=mips
TB --- 2013-09-11 16:17:33 - TARGET_ARCH=mips64
TB --- 2013-09-11 16:17:33 - TZ=UTC
TB --- 2013-09-11 16:17:33 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 16:17:33 - cd /src
TB --- 2013-09-11 16:17:33 - /usr/bin/make -B buildkernel 
KERNCONF=BERI_DE4_MDROOT
 Kernel build for BERI_DE4_MDROOT started on Wed Sep 11 16:17:33 UTC 2013
 stage 1: configuring the kernel
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3.1: making dependencies
 stage 3.2: building everything
[...]
cc  -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1 
--param large-function-growth=10 --param max-inline-insns-single=1  

Re: HW fed /dev/random

2013-09-11 Thread Mark R V Murray

On 10 Sep 2013, at 19:13, Harald Schmalzbauer h.schmalzba...@omnilan.de wrote:

 Hello,
 
 some time ago, before random(4) was rewritten for FreeBSD 5 by Mark
 Murray, we had rng, the i815 hardware random number generator.
 At this time, there were rumors about the quality of the randomness.
 
 Now we have rdrand (BullMountain hardware random generator in IvyBridge)
 and Dual_EC_DRBG (NSA's NIST contribution) makes me wonder if quality is
 again something to worry about - although kib's commit message states:
 „From the Intel whitepapers and articles about Bull Mountain, it seems
 that we do not need to perform post-processing of RDRAND results, like
 AES-encryption of the data with random IV and keys, which was done for
 Padlock. Intel claims that sanitization is performed in hardware.“
 
 When we use the software random device, one has great control over
 /dev/random with sysctk kern.random.
 Are there considerations to extend the HW-rng-implementation by optional
 post processing?

Yes. This was discussed in Cambridge recently, and will no doubt be brought
up again in Malta. There are indeed plans to post-process the output of
rdrand.

M
-- 
Mark R V Murray



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: New iSCSI stack.

2013-09-11 Thread Outback Dingo
On Wed, Sep 11, 2013 at 11:06 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 9:32 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 6:29 AM, Edward Tomasz Napierała 
 tr...@freebsd.org wrote:

 Wiadomość napisana przez Alfred Perlstein bri...@mu.org w dniu 6 wrz
 2013, o godz. 20:18:
  On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote:
  Hello.  At http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll 
  find
  a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
  To use the new initiator, start with man iscsictl.  For the target
 - man
  ctld.
 
  All feedback is welcome.  If nothing unexpected comes up, I'll commit
 it
  in a few days from now.  Note that it's still not optimized; at this
 point
  I'm focusing more on reliability and interoperability.
 
  This work is being sponsored by FreeBSD Foundation.
 
  ___
  freebsd-current@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-current
  To unsubscribe, send any mail to 
 freebsd-current-unsubscr...@freebsd.org
 
  Edward, this is really exciting!
 
  Is there an easy way to use the userland iscsi configuration files?

 Which iSCSI userland configuration files, the ctl.conf(5)?  If you need
 an ability to parse it and modify from a shell scripts, see confctl
 utility
 (sysutils/confctl, https://github.com/trasz/confctl/).

  We would love to quickly backport and ship this with FreeNAS as an
 option for our users, having the config files be the same OR having a very
 good converter would really make that much easier for us.

 Porting to 9 should be quite easy - there are Capsicum API differences;
 you might also want to compare CTL between 10 and 9 to see if there are
 any changes which need to be merged.  Taking a look at the code searching
 for possible security issues would be also very welcome :-)

 As for the config files - writing a converter should be quite easy.
  Which
 configuration files you need to support, ctl.conf(5) and istgt
 configuration?


 I was i belive quite close to having it working on the last patch,
 however could never seem to get the ctl kernel module to function,
 And feel im a bit further away with this latest patch retracing my steps,
 from previous... quite easy to backport maybe for you, or other
 but yes, I also would like to integrate the work to stable/9 in the lab
 for some benchmarks



 Still trying to tackle this.. any ideas?? I think if i can get past
 the few errors im encountering i can get a patch against stable/9 for
 others to test
 Negate the last posted error, Ive worked past it. I think if i can get
 past this capsicum issue, ill have a kernel

 === iscsi (all)
 clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
 -nostdinc  -I/usr/home/dingo/devel/sys/modules/iscsi/../../ofed/include
 -DHAVE_KERNEL_OPTION_HEADERS -include
 /usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ 
 -I@/contrib/altq
 -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
 -I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
 -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
  -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
 -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
 -Wredundant-decls -Wnested-externs -Wstrict-prototypes
  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
 -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
 -fdiagnostics-show-option  -Wno-error-tautological-compare
 -Wno-error-empty-body  -Wno-error-parentheses-equality -c
 /usr/home/dingo/devel/sys/modules/iscsi/../../dev/iscsi//icl.c
 /usr/home/dingo/devel/sys/modules/iscsi/../../dev/iscsi//icl.c:1098:26:
 error: use of undeclared identifier 'CAP_SOCK_CLIENT'
 cap_rights(rights, CAP_SOCK_CLIENT), fp);
 ^
 1 error generated.
 *** [icl.o] Error code 1

 Stop in /usr/home/dingo/devel/sys/modules/iscsi.


  ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to 
 freebsd-current-unsubscr...@freebsd.org




___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on sparc64/sparc64

2013-09-11 Thread FreeBSD Tinderbox
TB --- 2013-09-11 16:18:53 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-11 16:18:53 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE 
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2013-09-11 16:18:53 - starting HEAD tinderbox run for sparc64/sparc64
TB --- 2013-09-11 16:18:53 - cleaning the object tree
TB --- 2013-09-11 16:18:53 - /usr/local/bin/svn stat /src
TB --- 2013-09-11 16:18:57 - At svn revision 255470
TB --- 2013-09-11 16:18:58 - building world
TB --- 2013-09-11 16:18:58 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 16:18:58 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 16:18:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 16:18:58 - SRCCONF=/dev/null
TB --- 2013-09-11 16:18:58 - TARGET=sparc64
TB --- 2013-09-11 16:18:58 - TARGET_ARCH=sparc64
TB --- 2013-09-11 16:18:58 - TZ=UTC
TB --- 2013-09-11 16:18:58 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 16:18:58 - cd /src
TB --- 2013-09-11 16:18:58 - /usr/bin/make -B buildworld
 Building an up-to-date make(1)
 World build started on Wed Sep 11 16:19:05 UTC 2013
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
 stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 World build completed on Wed Sep 11 17:23:00 UTC 2013
TB --- 2013-09-11 17:23:00 - generating LINT kernel config
TB --- 2013-09-11 17:23:00 - cd /src/sys/sparc64/conf
TB --- 2013-09-11 17:23:00 - /usr/bin/make -B LINT
TB --- 2013-09-11 17:23:00 - cd /src/sys/sparc64/conf
TB --- 2013-09-11 17:23:00 - /usr/sbin/config -m LINT
TB --- 2013-09-11 17:23:00 - building LINT kernel
TB --- 2013-09-11 17:23:00 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 17:23:00 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 17:23:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 17:23:00 - SRCCONF=/dev/null
TB --- 2013-09-11 17:23:00 - TARGET=sparc64
TB --- 2013-09-11 17:23:00 - TARGET_ARCH=sparc64
TB --- 2013-09-11 17:23:00 - TZ=UTC
TB --- 2013-09-11 17:23:00 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 17:23:00 - cd /src
TB --- 2013-09-11 17:23:00 - /usr/bin/make -B buildkernel KERNCONF=LINT
 Kernel build for LINT started on Wed Sep 11 17:23:00 UTC 2013
 stage 1: configuring the kernel
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3.1: making dependencies
 stage 3.2: building everything
[...]
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
-Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. -I/src/sys 
-I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 
--param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float 
-ffreestanding -fstack-protector -Werror  /src/sys/kern/uipc_shm.c
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
-Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. -I/src/sys 
-I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 
--param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float 
-ffreestanding -fstack-protector -Werror  /src/sys/kern/uipc_sockbuf.c
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
-Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. -I/src/sys 
-I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 
--param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float 
-ffreestanding -fstack-protector -Werror  /src/sys/kern/uipc_socket.c
cc  -c -O2 -pipe -fno-strict-aliasing  -std=c99  -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith 
-Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fformat-extensions  
-Wmissing-include-dirs -fdiagnostics-show-option   -nostdinc  -I. -I/src/sys 
-I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 
--param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float 
-ffreestanding 

Re: HEADS UP: OpenSSH with DNSSEC support in 10

2013-09-11 Thread Mark Felder
On Wed, Sep 11, 2013, at 11:16, Ian Lepore wrote:
 
 Thanks.  If this is client-side I'm much less scared by it.  At $work we
 have embedded systems with less than full network functionality, often
 including either /etc/hosts usage or worse, sometimes a dns is
 configured but unreachable, and we ssh into them a lot for development.
 

Do you work around that problem by setting UseDNS no? We have that
pretty much standard on all our servers at work because if you ssh and
both client and server have ipv6 the connection takes forever for it to
give up trying to find a PTR for your client's ipv6 address. And don't
try to use GENERATE in BIND to make PTRs for all your ipv6 addresses...
you'll run out of memory trying to start the daemon :-)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Chicken and egg problem when building (third-party) kernel modules with bsd.kmod.mk -- how to solve?

2013-09-11 Thread John-Mark Gurney
Lev Serebryakov wrote this message on Wed, Sep 11, 2013 at 17:37 +0400:
  It is good idea to set KERNBUILDDIR when build module. But to set it you
 need to know ${.OBJDIR} from ${SYSDIR} and ${SYSDIR} is set in bsd.kmod.mk,
 which should be included last (after defining KERNBUILDDIR).
 
  How this loop could be broken?

You don't set it as part of the module Makefile... It is expected that
KERNBUILDDIR is set before invoking the module Makefile, such as when
the module is built as part of the kernel...

If you need to build it stand alone, you still need the opt_*.h files
from the kernel you are going to run it with, and that directory is
what you need to set KERNBUILDDIR...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 All that I will do, has been done, All that I have, has not.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: svn commit: r255219 - in head: contrib/tcpdump lib/libc lib/libc/capability lib/libc/include lib/libc/sys lib/libprocstat sbin/dhclient sbin/hastd sys/amd64/linux32 sys/bsm sys/cddl/compat/opensol

2013-09-11 Thread Idwer Vollering
I think r255219 broke compilation on amd64 with WITHOUT_CLANG=yes.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: New iSCSI stack.

2013-09-11 Thread Outback Dingo
On Wed, Sep 11, 2013 at 1:09 PM, Outback Dingo outbackdi...@gmail.comwrote:




 On Wed, Sep 11, 2013 at 11:06 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 9:32 AM, Outback Dingo outbackdi...@gmail.comwrote:




 On Sun, Sep 8, 2013 at 6:29 AM, Edward Tomasz Napierała 
 tr...@freebsd.org wrote:

 Wiadomość napisana przez Alfred Perlstein bri...@mu.org w dniu 6 wrz
 2013, o godz. 20:18:
  On 9/5/13 3:27 AM, Edward Tomasz Napierała wrote:
  Hello.  At http://people.freebsd.org/~trasz/cfiscsi-20130904.diffyou'll 
  find
  a patch which adds the new iSCSI initiator and target, against
 10-CURRENT.
  To use the new initiator, start with man iscsictl.  For the target
 - man
  ctld.
 
  All feedback is welcome.  If nothing unexpected comes up, I'll
 commit it
  in a few days from now.  Note that it's still not optimized; at this
 point
  I'm focusing more on reliability and interoperability.
 
  This work is being sponsored by FreeBSD Foundation.
 
  ___
  freebsd-current@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-current
  To unsubscribe, send any mail to 
 freebsd-current-unsubscr...@freebsd.org
 
  Edward, this is really exciting!
 
  Is there an easy way to use the userland iscsi configuration files?

 Which iSCSI userland configuration files, the ctl.conf(5)?  If you need
 an ability to parse it and modify from a shell scripts, see confctl
 utility
 (sysutils/confctl, https://github.com/trasz/confctl/).

  We would love to quickly backport and ship this with FreeNAS as an
 option for our users, having the config files be the same OR having a very
 good converter would really make that much easier for us.

 Porting to 9 should be quite easy - there are Capsicum API differences;
 you might also want to compare CTL between 10 and 9 to see if there are
 any changes which need to be merged.  Taking a look at the code
 searching
 for possible security issues would be also very welcome :-)

 As for the config files - writing a converter should be quite easy.
  Which
 configuration files you need to support, ctl.conf(5) and istgt
 configuration?


 I was i belive quite close to having it working on the last patch,
 however could never seem to get the ctl kernel module to function,
 And feel im a bit further away with this latest patch retracing my
 steps, from previous... quite easy to backport maybe for you, or other
 but yes, I also would like to integrate the work to stable/9 in the lab
 for some benchmarks



 Still trying to tackle this.. any ideas?? I think if i can get past
 the few errors im encountering i can get a patch against stable/9 for
 others to test
 Negate the last posted error, Ive worked past it. I think if i can
 get past this capsicum issue, ill have a kernel

 === iscsi (all)
 clang -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
 -nostdinc  -I/usr/home/dingo/devel/sys/modules/iscsi/../../ofed/include
 -DHAVE_KERNEL_OPTION_HEADERS -include
 /usr/obj/usr/home/dingo/devel/sys/GENERIC/opt_global.h -I. -I@ 
 -I@/contrib/altq
 -fno-common -g -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
 -I/usr/obj/usr/home/dingo/devel/sys/GENERIC  -mno-aes -mno-avx
 -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float
  -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector
 -std=iso9899:1999 -Qunused-arguments -fstack-protector -Wall
 -Wredundant-decls -Wnested-externs -Wstrict-prototypes
  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
 -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs
 -fdiagnostics-show-option  -Wno-error-tautological-compare
 -Wno-error-empty-body  -Wno-error-parentheses-equality -c
 /usr/home/dingo/devel/sys/modules/iscsi/../../dev/iscsi//icl.c
 /usr/home/dingo/devel/sys/modules/iscsi/../../dev/iscsi//icl.c:1098:26:
 error: use of undeclared identifier 'CAP_SOCK_CLIENT'
 cap_rights(rights, CAP_SOCK_CLIENT), fp);
 ^
 1 error generated.
 *** [icl.o] Error code 1

 Stop in /usr/home/dingo/devel/sys/modules/iscsi.


and i guess, icl needs to be upgraded ?

KLD ctl.ko: depends on icl - not available or version mismatch




  ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to 
 freebsd-current-unsubscr...@freebsd.org





___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on powerpc64/powerpc

2013-09-11 Thread FreeBSD Tinderbox
TB --- 2013-09-11 15:45:12 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-11 15:45:12 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE 
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2013-09-11 15:45:12 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2013-09-11 15:45:12 - cleaning the object tree
TB --- 2013-09-11 15:45:12 - /usr/local/bin/svn stat /src
TB --- 2013-09-11 15:45:16 - At svn revision 255470
TB --- 2013-09-11 15:45:17 - building world
TB --- 2013-09-11 15:45:17 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 15:45:17 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 15:45:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 15:45:17 - SRCCONF=/dev/null
TB --- 2013-09-11 15:45:17 - TARGET=powerpc
TB --- 2013-09-11 15:45:17 - TARGET_ARCH=powerpc64
TB --- 2013-09-11 15:45:17 - TZ=UTC
TB --- 2013-09-11 15:45:17 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 15:45:17 - cd /src
TB --- 2013-09-11 15:45:17 - /usr/bin/make -B buildworld
 Building an up-to-date make(1)
 World build started on Wed Sep 11 15:45:24 UTC 2013
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
 stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 stage 5.1: building 32 bit shim libraries
 World build completed on Wed Sep 11 18:48:52 UTC 2013
TB --- 2013-09-11 18:48:52 - generating LINT kernel config
TB --- 2013-09-11 18:48:52 - cd /src/sys/powerpc/conf
TB --- 2013-09-11 18:48:52 - /usr/bin/make -B LINT
TB --- 2013-09-11 18:48:52 - cd /src/sys/powerpc/conf
TB --- 2013-09-11 18:48:52 - /usr/sbin/config -m LINT
TB --- 2013-09-11 18:48:52 - skipping LINT kernel
TB --- 2013-09-11 18:48:52 - cd /src/sys/powerpc/conf
TB --- 2013-09-11 18:48:52 - /usr/sbin/config -m GENERIC
TB --- 2013-09-11 18:48:52 - skipping GENERIC kernel
TB --- 2013-09-11 18:48:52 - cd /src/sys/powerpc/conf
TB --- 2013-09-11 18:48:52 - /usr/sbin/config -m GENERIC64
TB --- 2013-09-11 18:48:52 - building GENERIC64 kernel
TB --- 2013-09-11 18:48:52 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 18:48:52 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 18:48:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 18:48:52 - SRCCONF=/dev/null
TB --- 2013-09-11 18:48:52 - TARGET=powerpc
TB --- 2013-09-11 18:48:52 - TARGET_ARCH=powerpc64
TB --- 2013-09-11 18:48:52 - TZ=UTC
TB --- 2013-09-11 18:48:52 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 18:48:52 - cd /src
TB --- 2013-09-11 18:48:52 - /usr/bin/make -B buildkernel KERNCONF=GENERIC64
 Kernel build for GENERIC64 started on Wed Sep 11 18:48:52 UTC 2013
 stage 1: configuring the kernel
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3.1: making dependencies
 stage 3.2: building everything
[...]
ctfconvert -L VERSION -g uipc_sockbuf.o
cc  -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 
--param large-function-growth=1000  -msoft-float -Wa,-many 
-fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding 
-fstack-protector -Werror  /src/sys/kern/uipc_socket.c
ctfconvert -L VERSION -g uipc_socket.o
cc  -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 
--param large-function-growth=1000  -msoft-float -Wa,-many 
-fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding 
-fstack-protector -Werror  /src/sys/kern/uipc_syscalls.c
cc1: warnings being treated as errors
/src/sys/kern/uipc_syscalls.c: In function 'vn_sendfile':
/src/sys/kern/uipc_syscalls.c:2196: warning: 'obj_size' may be used 
uninitialized in this function
/src/sys/kern/uipc_syscalls.c:2192: warning: 'pg' may be used uninitialized in 
this function
*** Error code 1

Stop.
bmake[1]: stopped in /obj/powerpc.powerpc64/src/sys/GENERIC64
*** Error code 1

Stop.
bmake: stopped in /src
*** Error code 1

Stop in /src.
TB --- 2013-09-11 18:53:07 - WARNING: /usr/bin/make returned exit code  1 
TB --- 2013-09-11 18:53:07 - ERROR: 

Re: r255449: kernel compilation fails due to : cc: error: no input files

2013-09-11 Thread David O'Brien
On Tue, Sep 10, 2013 at 08:14:30PM +0200, O. Hartmann wrote:
 On Tue, 10 Sep 2013 09:24:45 -0700 John-Mark Gurney j...@funkthat.com wrote:
  But, can you tell use how you built your kernel and on what system?
  COMPILER_TYPE should always be defined...  Are you trying to build
  a HEAD kernel on 9stable w/o using buildkernel or something strange
  like that?
 
 With r255453 everything works as expected again. Thank you very much.

It would still be helpful to know how you were building your kernel.

If you were trying to build it on non-CURRENT, maybe we should add a
check to ensure that COMPILER_TYPE is defined and if not warn folks
their environment is not-supported.

-- 
-- David  (obr...@freebsd.org)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc

2013-09-11 Thread David O'Brien
On Fri, Sep 06, 2013 at 09:19:32PM +0100, David Chisnall wrote:
 As of r255321, we are no longer building gcc or libstdc++ as part of
 the default install on platforms where clang is cc.

I guess I missed where this was discussed.

I don't feel we should not ship 10.0 without /usr/bin/g[c+][c+].

It is still very useful for folks to test changes in order to help ensure
one doesn't break the build on platforms still using GCC.

In the past, we've deprecated for a full release and then remove on the
next.  This is pretty late in the 10.0 game (now in code freeze) to be
making such impactful changes.

We have no idea how many 3rd party Makefiles (or other build systems)
specify gcc explicitly.


 2) Put WITH_GCC=yes and WITH_GNUCXX=yes in your src.conf when you build world.
 GCC will stay in the base system tree for at least the lifetime of the
 10.x release, and possibly longer if it is still being actively used.
 It will remain used by tinderboxes and make universe for some
 architectures, so if you commit code without testing with gcc people
 will know very soon...

Requiring folks to keep remembering to add this knob to any new
installation will make it harder for developers to test...

Compare to the buildworld time impact of Clang, the GCC build is nothing,
so why not just have a WITHOUT_GCC knob for those that want nothing more
to do with GCC?

-- 
-- David  (obr...@freebsd.org)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: r255449: kernel compilation fails due to : cc: error: no input files

2013-09-11 Thread O. Hartmann
On Wed, 11 Sep 2013 13:06:44 -0700
David O'Brien obr...@freebsd.org wrote:

 On Tue, Sep 10, 2013 at 08:14:30PM +0200, O. Hartmann wrote:
  On Tue, 10 Sep 2013 09:24:45 -0700 John-Mark Gurney
  j...@funkthat.com wrote:
   But, can you tell use how you built your kernel and on what
   system? COMPILER_TYPE should always be defined...  Are you trying
   to build a HEAD kernel on 9stable w/o using buildkernel or
   something strange like that?
  
  With r255453 everything works as expected again. Thank you very
  much.
 
 It would still be helpful to know how you were building your kernel.

Well, you're right. Usually, I try to explain everything I use in an
unconevtional manner except compiler options.

My systems are purified, I use no crosscompiling.

The problem has gone. Obviously, it was a fallout from a commit and I
hit the missing piece when I was trying to recompile the kernel.

 
 If you were trying to build it on non-CURRENT, maybe we should add a
 check to ensure that COMPILER_TYPE is defined and if not warn folks
 their environment is not-supported.
 


As said, vanilla CURRENT, simply performing make kernel or make
buildkernel on the machine the system is also running later - same
architecture et cetera.

Regards,
Oliver



signature.asc
Description: PGP signature


Re: Panic in ZFS: solaris assert: dn-dn_datablkshift != 0

2013-09-11 Thread Matthew Ahrens
FYI, I missed that this fix has already gone into illumos:

commit 5253393b09789ec67bec153b866d7285a1cf1645
Author: Matthew Ahrens mahr...@delphix.com
Date:   Fri Aug 30 02:19:35 2013

4082 zfs receive gets EFBIG from dmu_tx_hold_free()
Reviewed by: Eric Schrock eric.schr...@delphix.com
Reviewed by: Christopher Siden christopher.si...@delphix.com
Reviewed by: George Wilson george.wil...@delphix.com
Approved by: Richard Lowe richl...@richlowe.net

--matt


On Wed, Sep 11, 2013 at 7:43 AM, Jeremie Le Hen j...@freebsd.org wrote:

 On Mon, Sep 09, 2013 at 09:32:26AM +0200, Jeremie Le Hen wrote:
  
   Indeed, probably a bad key combo in vi :).
  
   I'm reverting r253821 and r254753 (the second one was supposingly
 fixing
   the first one) and recompiling my kernel.
  
   I will let you know.
 
  So far so good, I've been able to synchronize my datasets beyond the
  point where it crashed last time.
 
  Matthew, do you have any idea of a fix I could try on top of FreeBSD's
  r253821 and r254753?

 There has been some debugging on the ZFS mailing-list and I have tested
 a working fix.

 See:

 http://www.listbox.com/member/archive/182191/2013/09/sort/time_rev/page/1/entry/1:38/20130909182626:D79EC5B8-199E-11E3-8BF5-CB08091A731B/

 --
 Jeremie Le Hen

 Scientists say the world is made up of Protons, Neutrons and Electrons.
 They forgot to mention Morons.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: GCC withdraw

2013-09-11 Thread David O'Brien
On Thu, Aug 29, 2013 at 06:02:06PM +0100, David Chisnall wrote:
 rather busy organising the DevSummit.  The notes for the sessions will
 be posted to various mailing lists soon (and summarised for a special
 status report), but since the ports and toolchain build sessions are
 already largely up you can check these on the wiki.  You'll notice that
 in both sessions the topic of removing gcc / libstdc++ was raised and
 there was no objection (not sure if it's in the notes, but there was a
 lot of support during the ports session from people who didn't want the
 pain of maintaining compatibility with gcc-in-base, and especially with
 g++/libstdc++ in base).

And committers need to learn that Devsummit discussions (and optional
wiki's) are just like IRC ones -- we're all not there.  But we're on the
mailing lists.  That's how we communicate far-and-wide.

John and others bring up really good points.  Until GCC is no longer
used to build FreeBSD on any platform it should remain in all platforms.

If part of your reasoning is to free up gcc and g++ commands for
ports -- fine, but change the names /usr/bin/gcc and /usr/bin/g++ on
all platforms for something else.
/usr/bin/fbsd-gcc  /usr/bin/fbsd-g++ or what not.

-- 
-- David  (obr...@freebsd.org)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: HEADS UP: OpenSSH with DNSSEC support in 10

2013-09-11 Thread Dag-Erling Smørgrav
Ian Lepore i...@freebsd.org writes:
 So what happens when there is no dns server to consult?  Will every
 ssh connection have to wait for a long dns query timeout?  What if the
 machine is configured to use only /etc/hosts?

If there is no DNS server, no query will be sent.

 What if a DNS server is configured but doesn't respond?

The DNS request will time out.

In the vast majority of cases, you will either have no DNS at all (so no
query will be sent), or you will have a functioning DNS server.  In a
slightly less vast majority of cases, you will not be able to resolve
the server's IP address without DNS anyway.

 For that matter, I just realized I'm a bit unclear on who is querying
 DNS for this info, the ssh client or the sshd?

The client - and you can override this in your ~/.ssh/config or on the
command line (-oVerifyHostKeyDNS=no).

DES
-- 
Dag-Erling Smørgrav - d...@des.no
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: New iSCSI stack.

2013-09-11 Thread Edward Tomasz Napierała
I'm working on last few minor nits to get this into the tree.  Give me few days,
I'll prepare a patch against 9-STABLE.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Chicken and egg problem when building (third-party) kernel modules with bsd.kmod.mk -- how to solve?

2013-09-11 Thread Lev Serebryakov
Hello, John-Mark.
You wrote 11 сентября 2013 г., 20:53:46:

  It is good idea to set KERNBUILDDIR when build module. But to set it you
 need to know ${.OBJDIR} from ${SYSDIR} and ${SYSDIR} is set in bsd.kmod.mk,
 which should be included last (after defining KERNBUILDDIR).
 
  How this loop could be broken?

JMG If you need to build it stand alone, you still need the opt_*.h files
 I'm speaking about making port with kernel module, but this port is using
bsd.*.mk infrastructure by itself.

JMG from the kernel you are going to run it with, and that directory is
JMG what you need to set KERNBUILDDIR...
 KERNBUILDDIR could be set automagically with:

KERNBUILDROOT!= make -C ${SYSDIR} -V .OBJDIR
KERNNAME!=  uname -i
.if exists(${KERNBUILDROOT}/${KERNNAME}/opt_global.h)  !defined(KERNBUILDDIR)
KERNBUILDDIR:=${KERNBUILDROOT}/${KERNNAME}
.endif

  But here is problem, which I'm speaking about: it should go BEFORE
 bsd.kmod.mk but it needs to use ${SYSDIR}.

-- 
// Black Lion AKA Lev Serebryakov l...@freebsd.org

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Chicken and egg problem when building (third-party) kernel modules with bsd.kmod.mk -- how to solve?

2013-09-11 Thread John-Mark Gurney
Lev Serebryakov wrote this message on Thu, Sep 12, 2013 at 01:17 +0400:
 Hello, John-Mark.
 You wrote 11  2013 ??., 20:53:46:
 
   It is good idea to set KERNBUILDDIR when build module. But to set it you
  need to know ${.OBJDIR} from ${SYSDIR} and ${SYSDIR} is set in bsd.kmod.mk,
  which should be included last (after defining KERNBUILDDIR).
  
   How this loop could be broken?
 
 JMG If you need to build it stand alone, you still need the opt_*.h files
  I'm speaking about making port with kernel module, but this port is using
 bsd.*.mk infrastructure by itself.
 
 JMG from the kernel you are going to run it with, and that directory is
 JMG what you need to set KERNBUILDDIR...
  KERNBUILDDIR could be set automagically with:
 
 KERNBUILDROOT!= make -C ${SYSDIR} -V .OBJDIR
 KERNNAME!=  uname -i
 .if exists(${KERNBUILDROOT}/${KERNNAME}/opt_global.h)  
 !defined(KERNBUILDDIR)
 KERNBUILDDIR:=${KERNBUILDROOT}/${KERNNAME}
 .endif
 
   But here is problem, which I'm speaking about: it should go BEFORE
  bsd.kmod.mk but it needs to use ${SYSDIR}.

After a brief discussion w/ imp, we have the idea of pulling this
information from the current running kernel.  It isn't hard to put
this information into an elf section and then extract it at module
build time...

For people releasing kernel modules for others, we'll need a better
way to handle this...

Plus, we might be able to identify a few macros that are KBI changing,
and finally get close to being able to prevent loading kernels that
would cause a crash due to KBI differences...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 All that I will do, has been done, All that I have, has not.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


[head tinderbox] failure on powerpc/powerpc

2013-09-11 Thread FreeBSD Tinderbox
TB --- 2013-09-11 15:20:35 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-09-11 15:20:35 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE 
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC  amd64
TB --- 2013-09-11 15:20:35 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2013-09-11 15:20:35 - cleaning the object tree
TB --- 2013-09-11 15:20:35 - /usr/local/bin/svn stat /src
TB --- 2013-09-11 15:20:38 - At svn revision 255470
TB --- 2013-09-11 15:20:39 - building world
TB --- 2013-09-11 15:20:39 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 15:20:39 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 15:20:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 15:20:39 - SRCCONF=/dev/null
TB --- 2013-09-11 15:20:39 - TARGET=powerpc
TB --- 2013-09-11 15:20:39 - TARGET_ARCH=powerpc
TB --- 2013-09-11 15:20:39 - TZ=UTC
TB --- 2013-09-11 15:20:39 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 15:20:39 - cd /src
TB --- 2013-09-11 15:20:39 - /usr/bin/make -B buildworld
 Building an up-to-date make(1)
 World build started on Wed Sep 11 15:20:46 UTC 2013
 Rebuilding the temporary build tree
 stage 1.1: legacy release compatibility shims
 stage 1.2: bootstrap tools
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3: cross tools
 stage 4.1: building includes
 stage 4.2: building libraries
 stage 4.3: make dependencies
 stage 4.4: building everything
 World build completed on Wed Sep 11 17:55:00 UTC 2013
TB --- 2013-09-11 17:55:00 - generating LINT kernel config
TB --- 2013-09-11 17:55:00 - cd /src/sys/powerpc/conf
TB --- 2013-09-11 17:55:00 - /usr/bin/make -B LINT
TB --- 2013-09-11 17:55:00 - cd /src/sys/powerpc/conf
TB --- 2013-09-11 17:55:00 - /usr/sbin/config -m LINT
TB --- 2013-09-11 17:55:00 - building LINT kernel
TB --- 2013-09-11 17:55:00 - CROSS_BUILD_TESTING=YES
TB --- 2013-09-11 17:55:00 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-09-11 17:55:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-09-11 17:55:00 - SRCCONF=/dev/null
TB --- 2013-09-11 17:55:00 - TARGET=powerpc
TB --- 2013-09-11 17:55:00 - TARGET_ARCH=powerpc
TB --- 2013-09-11 17:55:00 - TZ=UTC
TB --- 2013-09-11 17:55:00 - __MAKE_CONF=/dev/null
TB --- 2013-09-11 17:55:00 - cd /src
TB --- 2013-09-11 17:55:00 - /usr/bin/make -B buildkernel KERNCONF=LINT
 Kernel build for LINT started on Wed Sep 11 17:55:00 UTC 2013
 stage 1: configuring the kernel
 stage 2.1: cleaning up the object tree
 stage 2.2: rebuilding the object tree
 stage 2.3: build tools
 stage 3.1: making dependencies
 stage 3.2: building everything
[...]
cc  -c -O -pipe  -std=c99  -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 
--param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many 
-fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding 
-fstack-protector -Werror  /src/sys/kern/uipc_shm.c
cc  -c -O -pipe  -std=c99  -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 
--param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many 
-fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding 
-fstack-protector -Werror  /src/sys/kern/uipc_sockbuf.c
cc  -c -O -pipe  -std=c99  -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 
--param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many 
-fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding 
-fstack-protector -Werror  /src/sys/kern/uipc_socket.c
cc  -c -O -pipe  -std=c99  -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions  -Wmissing-include-dirs 
-fdiagnostics-show-option   -nostdinc  -I. -I/src/sys -I/src/sys/contrib/altq 
-I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common 

mountroot while booting r255342 memstick

2013-09-11 Thread Uzumaki Naruto
Hi,
I downloaded FreeBSD-10.0-CURRENT-amd64-20130907-r255342-memstick.img and dd 
into KINGSTON DT 101 G2 1.00 USB pendrive

boot it from Intel I5 laptop but hang
screen output as below.

Root mount waiting for: usbus0
ugen0.3: SunplusIT INC. at usbus0
Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]...
mountroot: waiting for device /dev/ufs/FreeBSD_Install ...
Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19.

mountroot ?

List of GEOM managed disk devices:
diskid/DISK-TEA553QBGV3WZ4Gs1 diskid/DISK-TEA553QBGV3WZ4G ada0s1 cd0 ada0

mountroot ufs:/dev/da0s1a
Trying to mount root from ufs:/dev/da0s1a []...
mountroot: waiting for device /dev/da0s1a ...
Mounting from ufs:/dev/da0s1a failed with error 19

// i take out the usb pendrive and put it back

mountroot ufs:/dev/da0s1a
Trying to mount root from ufs:/dev/da0s1a []...
mountroot: waiting for device /dev/da0s1a ...
ugen0.2: Kingston at usbus0 (disconnected)
umass0: at uhub0, port 1, addr 1 (disconnected)
ugen0.2: Kingston at usbus0
umass0: Kingston DT 101 G2, class 0/0, rev 2.00/1.00, addr 3 on usbus0
umass0: SCSI over Bulk-Only; quirks = 0x0100
umass0:3:0:-1: Attached to scbus3
da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
da0: Kingston DT 101 G2 1.00 Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 3690MB (7557704 512 byte sectors: 255H 63S/T 470C)
da0: quirks=0x2NO_6_BYTE
(da0:umass-sim0:0:0:0): got CAM status 0x50
(da0:umass-sim0:0:0:0): fatal error, failed to attach to device
(da0:umass-sim0:0:0:0): lost device - 0 outstanding, 5 refs
(da0:umass-sim0:0:0:0): removing device entry
Mounting from ufs:/dev/da0s1a failed with error 19.

Any idea to troubleshoot this issue?
Thank you.
  
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: mountroot while booting r255342 memstick

2013-09-11 Thread Glen Barber
On Thu, Sep 12, 2013 at 12:32:12AM +, Uzumaki Naruto wrote:
 Hi,
 I downloaded FreeBSD-10.0-CURRENT-amd64-20130907-r255342-memstick.img and dd 
 into KINGSTON DT 101 G2 1.00 USB pendrive
 
 boot it from Intel I5 laptop but hang
 screen output as below.
 
 Root mount waiting for: usbus0
 ugen0.3: SunplusIT INC. at usbus0
 Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]...
 mountroot: waiting for device /dev/ufs/FreeBSD_Install ...
 Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19.
 
 mountroot ?
 
 List of GEOM managed disk devices:
 diskid/DISK-TEA553QBGV3WZ4Gs1 diskid/DISK-TEA553QBGV3WZ4G ada0s1 cd0 ada0
 
 mountroot ufs:/dev/da0s1a
 Trying to mount root from ufs:/dev/da0s1a []...
 mountroot: waiting for device /dev/da0s1a ...
 Mounting from ufs:/dev/da0s1a failed with error 19
 
 // i take out the usb pendrive and put it back
 
 mountroot ufs:/dev/da0s1a
 Trying to mount root from ufs:/dev/da0s1a []...
 mountroot: waiting for device /dev/da0s1a ...
 ugen0.2: Kingston at usbus0 (disconnected)
 umass0: at uhub0, port 1, addr 1 (disconnected)
 ugen0.2: Kingston at usbus0
 umass0: Kingston DT 101 G2, class 0/0, rev 2.00/1.00, addr 3 on usbus0
 umass0: SCSI over Bulk-Only; quirks = 0x0100
 umass0:3:0:-1: Attached to scbus3
 da0 at umass-sim0 bus 0 scbus3 target 0 lun 0
 da0: Kingston DT 101 G2 1.00 Removable Direct Access SCSI-0 device
 da0: 40.000MB/s transfers
 da0: 3690MB (7557704 512 byte sectors: 255H 63S/T 470C)
 da0: quirks=0x2NO_6_BYTE
 (da0:umass-sim0:0:0:0): got CAM status 0x50
 (da0:umass-sim0:0:0:0): fatal error, failed to attach to device
 (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 5 refs
 (da0:umass-sim0:0:0:0): removing device entry
 Mounting from ufs:/dev/da0s1a failed with error 19.
 
 Any idea to troubleshoot this issue?
 Thank you.
 

Is this USB 2.0 or USB 3.0 port?

Glen



pgpMlxHB_YYGc.pgp
Description: PGP signature


mountroot while booting r255342 memstick‏

2013-09-11 Thread Uzumaki Naruto



 Is this USB 2.0 or USB 3.0 port?


 


 Glen


 





Hi Glen,


This laptop got 3 USB ports,


1 - 3.0 (blue colored),


2 - 2.0 (black colored)





tried on both, 2.0 and 3.0, same result.
  
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


RE: mountroot while booting r255342 memstick

2013-09-11 Thread Uzumaki Naruto
 Date: Wed, 11 Sep 2013 20:56:10 -0400
 From: g...@freebsd.org
 Subject: Re: mountroot while booting r255342 memstick
 
 On Thu, Sep 12, 2013 at 12:44:31AM +, Uzumaki Naruto wrote:
   Is this USB 2.0 or USB 3.0 port?
   
   Glen
   
  
  Hi Glen,
  This laptop got 3 USB ports,
  1 - 3.0 (blue colored),
  2 - 2.0 (black colored)
  
  tried on both, 2.0 and 3.0, same result.
  
 
 Hmm.  Can you check if your BIOS has a Legacy USB option, and make
 sure it is enabled?  We are aware of some BIOSes that do not support
 GPT-boot (meaning, they require the MBR).  We are working on fixing
 this, so we will either have a single memstick image with both MBR and
 GPT boot ability, or maybe two separate memstick images (which will be
 far more confusing...).
 
 It is possible you have one of these BIOSes, unfortunately, but please
 try my suggestion about enabling Legacy USB, if it is not already
 enabled.
 
 Glen
 

Sorry for corrupted this mailing list thread view, kinda new with this,

The laptop bios is Phoniex SecureCore Tiano, I don't see Legacy USB option,
Bios Main page,

Quite Boot : [Disabled]
Network Boot : [Disabled]
F12 Boot Menu: [Enabled]
D2D Recovery: [Disabled]
Wake on Lan: [Disabled]
SATA Mode: [AHCI Mode] or [IDE Mode]

If the issue is GPT and MBR, I am quite sure this laptop BIOS doesn't support 
GPT disk type, because OEM Acer only gave GPT supported BIOS for model that 
pre-loaded with Windows 8.


  
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


RE: mountroot while booting r255342 memstick

2013-09-11 Thread Uzumaki Naruto
 If the issue is GPT and MBR, I am quite sure this laptop BIOS doesn't support 
 GPT disk type, because OEM Acer only gave GPT supported BIOS for model that 
 pre-loaded with Windows 8.

Maybe it helps to clarify, this laptop got no UEFI firmware, I could convert my 
hard disk to GPT type using diskpart command, but the functionality to boot 
from GPT partition is unavailable through BIOS.
  
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: mountroot while booting r255342 memstick

2013-09-11 Thread Nathan Whitehorn

On 09/11/13 20:42, Uzumaki Naruto wrote:

If the issue is GPT and MBR, I am quite sure this laptop BIOS doesn't support 
GPT disk type, because OEM Acer only gave GPT supported BIOS for model that 
pre-loaded with Windows 8.

Maybe it helps to clarify, this laptop got no UEFI firmware, I could convert my 
hard disk to GPT type using diskpart command, but the functionality to boot 
from GPT partition is unavailable through BIOS.



Booting from GPT does not require BIOS support. BIOSes don't (or aren't 
supposed to -- some broken ones do) parse the partition table at all.

-Nathan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: HEADS UP: OpenSSH with DNSSEC support in 10

2013-09-11 Thread Benjamin Kaduk

On Wed, 11 Sep 2013, Ian Lepore wrote:


On Wed, 2013-09-11 at 17:00 +0200, Dag-Erling Smørgrav wrote:

OpenSSH in FreeBSD 10 is now built with DNSSEC support, unless you
disable LDNS in src.conf.  If DNSSEC is enabled, the default setting for
VerifyHostKeyDNS is yes.  This means that OpenSSH will silently trust
DNSSEC-signed SSHFP records.  I consider this a lesser evil than ask
(aka train the user to type 'yes' and hit enter) and no (aka train
the user to type 'yes' and hit enter without even the benefit of a
second opinion).

DES


So what happens when there is no dns server to consult?  Will every ssh
connection have to wait for a long dns query timeout?


There is a long precent for ssh waiting on DNS timeouts, with the GSSAPI* 
options.  At least in some cases, ssh could end up waiting for 3 retries 
against each KDC for each of some six GSSAPI mechanisms, at (IIRC) a 
3-second timeout each.  This was so bad that corrective action was taken, 
but there are still some delays if DNS is not functioning properly.


-Ben Kaduk___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Intermittent hangs in vmem_periodic()

2013-09-11 Thread hiren panchasara
I am seeing really weird system freeze for 2-3 seconds every minute or so.

% uname -a
FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2
r255423M: Mon Sep  9 12:29:22 PDT 2013 root@flymocko
ur-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC  amd64

Simple comands like man top hangs and this is what I see in ctrl+T
 % man top
 load: 1.59  cmd: zcat 76574 [*kmem arena] 2.16r 0.00u 1.82s 16% 2000k
 load: 1.70  cmd: zcat 76574 [*kmem arena] 7.19r 0.00u 1.82s 7% 2000k
 load: 1.89  cmd: zcat 76574 [*kmem arena] 12.58r 0.00u 1.82s 3% 2000k
 load: 1.90  cmd: zcat 76574 [*kmem arena] 14.58r 0.00u 1.82s 2% 2000k

I see similar things while trying to exit a terminal window.

I see following in pmcstat:

PMC: [INSTR_RETIRED_ANY] Samples: 117647 (100.0%) , 6885 unresolved

%SAMP CALLTREE
 75.9 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked
vmem_periodic(75.9%)

I am not running anything funny and I do not see anything weird in top
too.

Any help is appreciated.

cheers,
Hiren
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Intermittent hangs in vmem_periodic()

2013-09-11 Thread hiren panchasara
On Wed, Sep 11, 2013 at 9:51 PM, hiren panchasara 
hiren.panchas...@gmail.com wrote:

 I am seeing really weird system freeze for 2-3 seconds every minute or so.

 % uname -a
 FreeBSD flymockour-l7.corp.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2
 r255423M: Mon Sep  9 12:29:22 PDT 2013 root@flymocko
 ur-l7.corp.yahoo.com:/usr/obj/usr/home/hirenp/head/sys/GENERIC  amd64

 Simple comands like man top hangs and this is what I see in ctrl+T
  % man top
  load: 1.59  cmd: zcat 76574 [*kmem arena] 2.16r 0.00u 1.82s 16% 2000k
  load: 1.70  cmd: zcat 76574 [*kmem arena] 7.19r 0.00u 1.82s 7% 2000k
  load: 1.89  cmd: zcat 76574 [*kmem arena] 12.58r 0.00u 1.82s 3% 2000k
  load: 1.90  cmd: zcat 76574 [*kmem arena] 14.58r 0.00u 1.82s 2% 2000k

 I see similar things while trying to exit a terminal window.

 I see following in pmcstat:

 PMC: [INSTR_RETIRED_ANY] Samples: 117647 (100.0%) , 6885 unresolved

 %SAMP CALLTREE
  75.9 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked
 vmem_periodic(75.9%)


At any point in time whether system is misbehaving or not, I see this on
top of the graph. Which seems wrong.

Providing a few samples over the time:

PMC: [INSTR_RETIRED_ANY] Samples: 97253 (100.0%) , 6080 unresolved

%SAMP CALLTREE
 78.1 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked
vmem_periodic(78.1%)
  1.0 bsea...@libc.so.7(1.0%)
  0.7 0xe7b661@libnvidia-glcore.s clock_gett...@libc.so.7 0x128c6e
0x128a80(0.6%)
  0.2 amd64_syscall@kernel sys_select kern_select
  0.2 lapic_handle_timer@kernel timercb handleevents hardclock_cnt
pmc_hook_hand...@hwpmc.ko pmc_process_samples
  0.0 amd64_syscall@kernel sys_poll
  0.0 f...@libc.so.7
  0.0 0x212f...@libxul.so 0x2130835 0x212f907 0x212f1e7 0x212d2fa 0x22b6777
0x22b6478

PMC: [INSTR_RETIRED_ANY] Samples: 35320 (100.0%) , 3663 unresolved

%SAMP CALLTREE
 32.4 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked
vmem_periodic(32.4%)
  1.6 f...@libc.so.7 0x9ad75 0x9a597(1.4%)
  1.3 intr_event_execute_handlers@kernel hdac_intr_handler hdaa_stream_intr
chn_intr chn_intr_locked sndbuf_feed
  feed_mixer_feed z_resampler_feed z_feed_linear_S16LE(1.0%)
  1.3 hdac_intr_handler@kernel hdaa_stream_intr chn_intr chn_intr_locked
sndbuf_feed feed_mixer_feed z_resampler_feed
  z_feed_linear_S16LE(1.0%)
  1.2 amd64_syscall@kernel sys___sysctl userland_sysctl sysctl_root
cpufreq_curr_sysctl cf_set_method est_set DELAY(0.6%)
  get_tsc(0.5%)
  1.1 bsea...@libc.so.7(1.1%)

PMC: [INSTR_RETIRED_ANY] Samples: 118799 (100.0%) , 7859 unresolved

%SAMP CALLTREE
 70.5 fork_exit@kernel taskqueue_thread_loop taskqueue_run_locked
vmem_periodic(70.5%)
  1.1 bsea...@libc.so.7(1.1%)
  0.2 lapic_handle_timer@kernel timercb handleevents hardclock_cnt
pmc_hook_hand...@hwpmc.ko pmc_process_samples
  0.1 f...@libc.so.7
  0.1 0xe7b661@libnvidia-glcore.s clock_gett...@libc.so.7
  0.1 amd64_syscall@kernel sys_select kern_select
  0.1 __real...@libc.so.7
  0.1 amd64_syscall@kernel sys_poll

cheers,
Hiren


 I am not running anything funny and I do not see anything weird in top
 too.

 Any help is appreciated.

 cheers,
 Hiren

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org