From owner-freebsd-questions@FreeBSD.ORG Fri Dec 2 07:40:02 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 783A8106566B for ; Fri, 2 Dec 2011 07:40:02 +0000 (UTC) (envelope-from doug@safeport.com) Received: from oceanpt.safeport.com (oceanpt.safeport.com [65.122.17.3]) by mx1.freebsd.org (Postfix) with ESMTP id 482F88FC12 for ; Fri, 2 Dec 2011 07:40:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by oceanpt.safeport.com (8.14.2/8.14.2) with ESMTP id pB276QZN065195 for ; Fri, 2 Dec 2011 02:06:27 -0500 (EST) (envelope-from doug@safeport.com) Date: Fri, 2 Dec 2011 02:06:26 -0500 (EST) From: doug@safeport.com To: freebsd-questions@freebsd.org In-Reply-To: <201112010829.pB18T88q096483@mail.r-bonomi.com> Message-ID: References: <201112010829.pB18T88q096483@mail.r-bonomi.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (oceanpt.safeport.com [127.0.0.1]); Fri, 02 Dec 2011 02:06:27 -0500 (EST) Subject: Re: make buildworld powers down system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2011 07:40:02 -0000 On Thu, 1 Dec 2011, Robert Bonomi wrote: >> 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 >> 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. > Thanks for your suggestions. I have ruled out hardware. I did change a BIOS setting to make the function keys be functions without the fn key (this is a Dell laptop). The only other thing I changed was to run a script to record the time and some of the hw.acpi sysctl values. As I now have the upgrade installed I will try the buildworld again. The screen does go into standby and I am not sure what is controling that, nothing in KDE or Xorg that I set, perhaps a sysctl setting but I did not see one in the acpi section.