similar to: [releng_9 tinderbox] failure on arm/arm

TB --- 2012-12-11 03:57:29 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-12-11 03:57:29 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtancsa at freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-12-11 03:57:29 - starting RELENG_9 tinderbox run for i386/i386 TB --- 2012-12-11 03:57:29 - cleaning the

TB --- 2013-11-19 23:00:41 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-11-19 23:00:41 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-19 23:00:41 - starting RELENG_10 tinderbox run for sparc64/sparc64 TB --- 2013-11-19 23:00:41 - cleaning the

TB --- 2012-04-08 08:26:29 - tinderbox 2.9 running on freebsd-stable.sentex.ca TB --- 2012-04-08 08:26:29 - FreeBSD freebsd-stable.sentex.ca 8.2-STABLE FreeBSD 8.2-STABLE #4: Wed Sep 28 13:48:49 UTC 2011 mdtancsa@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2012-04-08 08:26:29 - starting RELENG_9 tinderbox run for sparc64/sparc64 TB --- 2012-04-08 08:26:29 - cleaning the

TB --- 2013-11-13 13:00:41 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-11-13 13:00:41 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-13 13:00:41 - starting RELENG_10 tinderbox run for i386/i386 TB --- 2013-11-13 13:00:41 - cleaning the

TB --- 2013-11-25 17:30:12 - tinderbox 2.20 running on freebsd-legacy2.sentex.ca TB --- 2013-11-25 17:30:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-11-25 17:30:12 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2013-11-25 17:30:12 -

TB --- 2013-10-31 19:50:43 - tinderbox 2.20 running on worker01.tb.des.no TB --- 2013-10-31 19:50:43 - FreeBSD worker01.tb.des.no 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-10-31 19:50:43 - starting RELENG_10 tinderbox run for i386/pc98 TB --- 2013-10-31 19:50:43 - cleaning the

TB --- 2012-12-04 23:10:18 - tinderbox 2.9 running on freebsd-legacy2.sentex.ca TB --- 2012-12-04 23:10:18 - FreeBSD freebsd-legacy2.sentex.ca 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-12-04 23:10:18 - starting RELENG_8 tinderbox run for sparc64/sparc64 TB --- 2012-12-04 23:10:18 - cleaning

Operating system virtualization is the most effective way to utilize your system resources, jails let you setup isolated mini-systems. Jails are explains well in handbook however, from practical standpoint of view, the presented material is incomplete. The post below setup few scrips that follow handbook's 'Application of Jails' article and enhance with few missing features

Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh.

Running FreeBSD 8.3 -- and updating sources on a daily base and building everything -- I found a new APIC/ACPI problem introduced in the past week. I have a Toshiba Satellite U205 with an Intel Core Duo (not a Core 2). It used to work fine with both cores but then sometime in on the road to BSD 8.0 the machine began hanging. So I added to /boot/loader.conf hint.apic.0.disabled="1"

Hello, Arne. I try to build storage server for my home (I have a LOT of media files) with FreeBSD 7, 5xHDD (WD 500Gb) and geom_raid5 ("simple" version from perforce, beacuse http://home.tiscali.de/cmdr_faako/geom_raid5.tbz is not patched for FreeBSD7). Array & FS were created with default arguments: # graid5 label storage ad6 ad8 ad10 ad12 ad14 # newfs -O2 -U /dev/raid5/storage

(Please keep me CC'd as I'm not subscribed to the list) I'd like to request that folks running RELENG_8 (and RELENG_9, though I do not use it) please check the behaviour of their terminal after each of following commands are run (check terminal after each command): top -a (press "q" after 1 screen refresh) top -b If you find that your input characters in your shell

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-EN-12:02.ipv6refcount Errata Notice The FreeBSD Project Topic: Reference count errors in IPv6 code Category: core Modules: sys_netinet sys_netinet6

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-12:04.sysret Security Advisory The FreeBSD Project Topic: Privilege escalation when returning from kernel Category: core Module: sys_amd64

Hi! I'm trying to cross-compile 4.8-STABLE world to install it over NFS later. I have ./make.conf: # start of file CPUTYPE=i486 KERNCONF?=CONS MODULES_WITH_WORLD=true DESTDIR=/mnt/cons # end of file I run: dir=`pwd` make __MAKE_CONF=$dir/make.conf buildworld 2>&1 | tee $dir/bw.log It fails: ===> gnu/usr.bin/groff/contrib ===> gnu/usr.bin/groff/contrib/mm sh

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-11:09.pam_ssh Security Advisory The FreeBSD Project Topic: pam_ssh improperly grants access when user account has unencrypted SSH private keys

Back before the 7.0 Release I used to install cross builds by NFS-mounting /usr/src and /usr/obj of the build machine on the target machine and running: # cd /usr/src # env MAKEOBJDIRPREFIX=/usr/obj/<stuff> make installkernel KERNCONF=<kernconf> ... This doesn't work any more because all the installation tools are built for the architecture of the build system. The alternative

Seems something grew beyond what will fit on the kernel floppy. From today's cvsup: linking BOOTMFS text data bss dec hex filename 2659952 210228 208148 3078328 2ef8b8 BOOTMFS -------------------------------------------------------------- >>> Kernel build for BOOTMFS completed on Wed Aug 20 19:03:49 GMT 2003

I tried rebuilding yesterday. It failed [I don't recall the output]. I then completely deleted the /usr/src and /usr/obj, and cvsuped again last night [Approx 7PM on 2003-06-23]. I set the machine up with a buildworld and went to bed. This am I looked at the nohup.out file that was generated and it had failed. I took out the NOMAN=false in /etc/make.conf - as it appeared the failure

Hi, Has anyone seen this before? I'm trying to build 7-STABLE on 6.3. I've removed everything from /usr/obj* but buildworld still fails. Maybe it's got something to do with recent dtrace MFC? -------------------------------------------------------------- >>> stage 1.2: bootstrap tools -------------------------------------------------------------- cd /usr/src;