[head tinderbox] failure on i386/pc98

TB --- 2012-04-14 05:20:01 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 05:20:01 - 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 ---

[head tinderbox] failure on i386/i386

TB --- 2012-04-14 05:20:01 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 05:20:01 - 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 ---

[head tinderbox] failure on amd64/amd64

TB --- 2012-04-14 05:20:01 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 05:20:01 - 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 ---

Re: howto debug a complete hard reset

Hi Alexander, On Fri, Apr 13, 2012 at 09:36:44PM +, Alexander Best wrote: i'm running HEAD on amd64 and experienced some really annoying resets during the last couple of months. when i do 'sysctl -a' or 'sysctl -a|grep bla', my whole system does a hard reset. no core dump gets

[head tinderbox] failure on ia64/ia64

TB --- 2012-04-14 07:48:11 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 07:48:11 - 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 ---

[head tinderbox] failure on sparc64/sparc64

TB --- 2012-04-14 09:37:47 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 09:37:47 - 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 ---

[head tinderbox] failure on powerpc/powerpc

TB --- 2012-04-14 08:29:21 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 08:29:21 - 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 ---

[head tinderbox] failure on powerpc64/powerpc

TB --- 2012-04-14 08:48:17 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 08:48:17 - 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 ---

Re: howto debug a complete hard reset

Jeremie Le Hen writes: This is probably a sysctl handler that is causing the reboot. You can run this one-liner to spot the culprit (use sh): for i in $(sysctl -Na); do sysctl $i ~/sysctl.out; sync; done Each sysctl will be called in turn and the output is appended to a

Re: DTrace on FreeBSD

On Tue, 10 Apr 2012 02:18:38 +0100 Sevan / Venture37 ventur...@gmail.com wrote: Hi, Ryan Stone got a chance to give a brief talk at the dtrace.conf last week where he covered the status of support on FreeBSD. http://smartos.org/2012/04/09/dtrace-conf-2012-dtrace-on-freebsd/ I was wondering

[head tinderbox] failure on i386/pc98

TB --- 2012-04-14 11:40:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 11:40: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 ---

[head tinderbox] failure on i386/i386

TB --- 2012-04-14 11:40:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 11:40: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 ---

[head tinderbox] failure on amd64/amd64

TB --- 2012-04-14 11:40:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 11:40: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 ---

Re: howto debug a complete hard reset

On Sat, Apr 14, 2012 at 08:59:42AM -0400, Robert Huff wrote: This is probably a sysctl handler that is causing the reboot. You can run this one-liner to spot the culprit (use sh): for i in $(sysctl -Na); do sysctl $i ~/sysctl.out; sync; done Each sysctl will be called

[head tinderbox] failure on ia64/ia64

TB --- 2012-04-14 13:56:27 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 13:56:27 - 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 ---

[head tinderbox] failure on powerpc/powerpc

TB --- 2012-04-14 14:30:58 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-14 14:30: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 ---

Re: howto debug a complete hard reset

On Sat Apr 14 12, Jeremie Le Hen wrote: On Sat, Apr 14, 2012 at 08:59:42AM -0400, Robert Huff wrote: This is probably a sysctl handler that is causing the reboot. You can run this one-liner to spot the culprit (use sh): for i in $(sysctl -Na); do sysctl $i ~/sysctl.out;

Re: kernel build failure

On Fri, 13 Apr 2012, O. Hartmann wrote: Am 04/13/12 00:21, schrieb AN: At Thu Apr 12 17:52:05 EDT 2012: [root@FBSD10 /usr/src]# svn up Updating '.': At revision 234196. Trying to build the kernel I get the following failure: time make -j8 buildkernel KERNCONF=MYKERNEL snip === zlib