[head tinderbox] failure on powerpc/powerpc

TB --- 2013-12-17 02:57:09 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-17 02:57:09 - 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

[head tinderbox] failure on sparc64/sparc64

TB --- 2013-12-17 04:25:48 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-17 04:25:48 - 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

[head tinderbox] failure on i386/pc98

TB --- 2013-12-17 01:07:50 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-17 01:07:50 - 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

[head tinderbox] failure on amd64/amd64

TB --- 2013-12-16 22:00:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 22:00:19 - 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

Re: [head tinderbox] failure on i386/i386

My bad, lemme go figure out what the hell causes this to break on these platforms. -a On 16 December 2013 17:34, FreeBSD Tinderbox wrote: > TB --- 2013-12-16 22:00:19 - tinderbox 2.20 running on > freebsd-current.sentex.ca > TB --- 2013-12-16 22:00:19 - FreeBSD freebsd-current.sentex.ca 8.3-PR

[head tinderbox] failure on ia64/ia64

TB --- 2013-12-17 01:12:57 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-17 01:12:57 - 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

[head tinderbox] failure on mips/mips

TB --- 2013-12-17 01:34:35 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-17 01:34: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

[head tinderbox] failure on i386/i386

TB --- 2013-12-16 22:00:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 22:00:19 - 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

[head tinderbox] failure on arm/arm

TB --- 2013-12-16 22:00:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 22:00:19 - 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

[head tinderbox] failure on armv6/arm

TB --- 2013-12-16 22:00:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 22:00:19 - 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

Re: r259286 panic

On Mon, Dec 16, 2013 at 6:41 PM, Aleksandr Rybalko wrote: > > Hi guys! > > I've investigate problem a bit. And can say that callout initialized with > callout_int(), w/o mpsafe flag: > callout_init(&vw->vw_proc_dead_timer, 0); > [sys/dev/vt/vt_core.c:1714] > And callout_init did not set CALLOUT_RE

Re: r259286 panic

Hi guys! I've investigate problem a bit. And can say that callout initialized with callout_int(), w/o mpsafe flag: callout_init(&vw->vw_proc_dead_timer, 0); [sys/dev/vt/vt_core.c:1714] And callout_init did not set CALLOUT_RETURNUNLOCKED flag, and assign it's lock object to Giant, but where Giant l

Re: RFC: less chatty system builds

On 16 Dec 2013, at 19:46, Luigi Rizzo wrote: > The following is a proof-of-concept patch to make system builds > less chatty. > > It also has the nice side effect of showing more clearly > which rules are used during the build and possibly help > debugging the share/mk files and the individual Ma

[head tinderbox] failure on powerpc/powerpc

TB --- 2013-12-16 18:33:18 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 18:33:18 - 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

[head tinderbox] failure on sparc64/sparc64

TB --- 2013-12-16 19:08:08 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 19:08:08 - 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

Re: RFC: less chatty system builds

On Mon, Dec 16, 2013 at 1:46 PM, Luigi Rizzo wrote: > The following is a proof-of-concept patch to make system builds > less chatty. > > It also has the nice side effect of showing more clearly > which rules are used during the build and possibly help > debugging the share/mk files and the indivi

RFC: less chatty system builds

The following is a proof-of-concept patch to make system builds less chatty. It also has the nice side effect of showing more clearly which rules are used during the build and possibly help debugging the share/mk files and the individual Makefiles. The logic is the following: the environment/make

[head tinderbox] failure on ia64/ia64

TB --- 2013-12-16 16:49:40 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 16:49:40 - 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

buildworld error (tcpdump and Capsicum)

/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/addrtoname.c:36:10: fatal error: 'libcapsicum.h' file not found #include I have, notably, WITHOUT_CAPSICUM=1 in /etc/src.conf. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd

[head tinderbox] failure on amd64/amd64

TB --- 2013-12-16 11:10:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 11:10:19 - 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

[head tinderbox] failure on i386/i386

TB --- 2013-12-16 11:10:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 11:10:19 - 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

RFC can we use __builtin_prefetch() directly in our kernel sources ?

Is it ok in kernel code to use __builtin_prefetch() and assume that all supported compilers will do the right thing for all architectures ? I am asking is because I need to use prefetch() in a small number of places in my netmap code, and nothing in our kernel sources uses __builtin_prefetch() dir

FreeBSD 10.0-RC2 Now Available

The second RC build of the 10.0-RELEASE release cycle is now available on the FTP servers for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures. The image checksums follow at the end of this email. ISO images and, for architectures that support it, the memory stick images are av

Re: 10-BETA{3,4} - Consistent Kernel Panics (pf_ioctl.c:1289)

0n Wed, Dec 04, 2013 at 07:16:52PM +1100, Gleb Smirnoff wrote: >On Tue, Dec 03, 2013 at 11:21:09PM -0800, Craig Rodrigues wrote: >C> > KERNCONF: >C> > >C> > options VIMAGE >C> > >C> > makeoptions DEBUG=-g >C> > >C> > device pf >C> >

[head tinderbox] failure on arm/arm

TB --- 2013-12-16 11:10:19 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 11:10:19 - 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

Re: r259286 panic

On 15.12.2013 22:22, Eitan Adler wrote: On Sun, Dec 15, 2013 at 3:23 AM, Eitan Adler wrote: FreeBSD gravity.local 11.0-CURRENT FreeBSD 11.0-CURRENT #7 r259286: Fri Dec 13 00:33:37 EST 2013 eitan@gravity.local:/usr/obj/usr/src/sys/EADLER amd64 Complete textdump here: http://people.freebsd.org/

Re: spec violation of xHCI?

From: Hans Petter Selasky Date: Mon, 16 Dec 2013 11:53:31 +0100 > Hi Kohji, > > A regression issue has been reported when using the CHAIN-BIT patch. Can you > verify this additional patch on you hardware and report back? > > http://svnweb.freebsd.org/changeset/base/259462 > > Thank you! > > --

[HEADS UP] xorg version switch in CURRENT

[ This message is cross-posted between x11@, current@ and ports@ for maximum coverage. Please please PLEASE respect reply-to: ] The xorg stack has been switched to use what has been dubbed new xorg in CURRENT. This means new xserver, new MESA (dri/libGL) stack and in some cases new versions. If

Re: spec violation of xHCI?

Hi Kohji, A regression issue has been reported when using the CHAIN-BIT patch. Can you verify this additional patch on you hardware and report back? http://svnweb.freebsd.org/changeset/base/259462 Thank you! --HPS ___ freebsd-current@freebsd.org ma

[head tinderbox] failure on powerpc/powerpc

TB --- 2013-12-16 07:26:58 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 07:26:58 - 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

[head tinderbox] failure on sparc64/sparc64

TB --- 2013-12-16 08:03:49 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-16 08:03:49 - 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