Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Dec 2011 02:29:08 -0600 (CST)
From:      Robert Bonomi <bonomi@mail.r-bonomi.com>
To:        doug@safeport.com
Cc:        freebsd-questions@freebsd.org
Subject:   Re: make buildworld powers down system
Message-ID:  <201112010829.pB18T88q096483@mail.r-bonomi.com>
In-Reply-To: <alpine.BSF.2.00.1112010156300.20797@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> From owner-freebsd-questions@freebsd.org  Thu Dec  1 01:16:21 2011
> Date: Thu, 1 Dec 2011 02:14:04 -0500 (EST)
> From: doug <doug@fledge.watson.org>
> To: freebsd-questions@freebsd.org
> Cc: 
> Subject: make buildworld powers down system
>
> Three times in a row. It seems to be repeatable. At the end what should my next 
> debugging step be?
>
> I ran the buildworld using script, the last lines in the make:
>
> cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. 
> -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncurses 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDEBUG 
> -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector  -c 
> /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_beep.c
> cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. 
> -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncurses 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDEBUG 
> -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector  -c 
> /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_bkgd.c
> cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. 
> -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncurses 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall -DNDEBUG 
> -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -fstack-protector  -c 
> /usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses/base/lib_box.c
> cc -O2 -pipe  -D_XOPEN_SOURCE_EXTENDED -DENABLE_WIDEC -I. 
> -I/usr/obj/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncursesw 
> -I/usr/src/lib/ncurses/ncursesw/../ncurses 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/include 
> -I/usr/src/lib/ncurses/ncursesw/../../../contrib/ncurses/ncurses -Wall 
> -DNDE^@^@^@^@^@^@^@
>
> this after about 30 minutes of running. There are no errors in the logs
>

First, look for *something* that would cause the machine to 
sleep/suspend/hibernate/shutdown after a period of "inactivity"

It _could_ be a BIOS setting, it could be 'power mangement' software
settings.

It is also -possible- that this is a *THERMAL* issue -- that the 30+
minutes of heavy CPU utilization is triggering an overtemperature 
shutdown.  Make sure all fans are working properly, and that CPU 
heat-sinks are dust-free.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201112010829.pB18T88q096483>