Plans for BIND and DNSSEC readiness

2010-02-21 Thread Doug Barton
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 I've made a post to -arch regarding my plans for BIND in the base, along with some information about getting ready for DNSSEC, including the upcoming signing of the root zone. You can find the message at http://lists.freebsd.org/pipermail/freebsd-

LOR: if_wpi.c

2010-02-21 Thread Marcin Cieslak
r203753, amd64 lock order reversal: 1st 0xff80003ad018 wpi0_com_lock (wpi0_com_lock) @ /usr/src/sys/modules/wpi/../../dev/wpi/if_wpi.c:1292 2nd 0xff00034f4010 wpi0 (network driver) @ /usr/src/sys/modules/wpi/../../dev/wpi/if_wpi.c:2069 KDB: stack backtrace: db_trace_self_wrapper() at

lor freebsd zfs mount

2010-02-21 Thread Marcin Cieslak
r203753, amd64, while booting (mount filesystems):: lock order reversal: 1st 0xff00096c4098 zfs (zfs) @ /usr/src/sys/kern/vfs_mount.c:1058 2nd 0xff000973f9f8 devfs (devfs) @ /usr/src/sys/kern/vfs_subr.c:2091 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _wi

Re: [head tinderbox] failure on mips/mips

2010-02-21 Thread Randall Stewart
Rats.. Yep you are right.. and I was out all day yesterday .. opps.. R On Feb 20, 2010, at 9:49 PM, M. Warner Losh wrote: Maybe a forgotten svn add for mipsfbsd-nat.c? Warner In message: <201002210405.o1l45ggx008...@freebsd-current.sentex.ca> FreeBSD Tinderbox writes: : TB --- 2

[head tinderbox] failure on mips/mips

2010-02-21 Thread FreeBSD Tinderbox
TB --- 2010-02-21 13:58:04 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-02-21 13:58:04 - starting HEAD tinderbox run for mips/mips TB --- 2010-02-21 13:58:04 - cleaning the object tree TB --- 2010-02-21 13:58:08 - cvsupping the source tree TB --- 2010-02-21 13:58:08 - /usr/bin/c

Re: Non-responsive 8.0-RC1

2010-02-21 Thread Peter Jeremy
On 2009-Nov-29 08:22:26 +1100, Peter Jeremy wrote: >My main server is running 8.0/amd64 from between RC1 and RC2 and I've >recently had a couple of long-duration hangs on it during which time >processes doing I/O will stop responding. > >The first time, it stopped responding for about 25 minutes