From owner-freebsd-questions@FreeBSD.ORG Sun Jan 30 17:47:17 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50EAB16A4CE for ; Sun, 30 Jan 2005 17:47:17 +0000 (GMT) Received: from outside.taborandtashell.net (sub18-33.member.dsl-only.net [63.105.18.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FDE043D1D for ; Sun, 30 Jan 2005 17:47:16 +0000 (GMT) (envelope-from tkelly-freebsd-questions@taborandtashell.net) Received: (qmail 96681 invoked from network); 30 Jan 2005 09:47:14 -0800 Received: from unknown (HELO ?192.168.0.9?) (tkelly@192.168.0.9) by 192.168.0.2 with AES256-SHA encrypted SMTP; 30 Jan 2005 09:47:14 -0800 Message-ID: <41FD1DBF.7080700@taborandtashell.net> Date: Sun, 30 Jan 2005 09:47:43 -0800 From: Tabor Kelly User-Agent: Mozilla Thunderbird 1.0 (X11/20041230) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ben Haysom References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: reboot DURING a portupgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: tkelly-freebsd-questions@taborandtashell.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2005 17:47:17 -0000 Ben Haysom wrote: > Hi > > I am running FBSD 5.3-CURRENT on a Duron 700Mhz 384Mb RAM. > > When I do (as root) > > #portupgrade -a > > it comes back with: > > Stale dependency: acroread-5.10_1 --> linux_base-8-8.0_6 -- manually > run 'pkgdb -F' to fix, or specify -O to force. > > So I do > > #portupgrade -a -O > > and *everytime* it reboots itself before the portupgrade is complete. > Not a clean reboot though - it doesn't dismount filesystems before it goes. > > I can't work out what it's doing. > There is nothing relevant in /var/log/messages. > > Can anyone help? > > Ben. Like Karol Kwiatkowski suggested, I would say you have about a 99% chance this is a hardware failure. In addition to what Karol suggested, it could also be a faulty power supply. Also, I would say look into the hardware in this order: 1. RAM 2. Power Supply 3. CPU Note: The above is just my personal opinion. -- Tabor Kelly tkelly-freebsd-questions@taborandtashell.net http://tabor.taborandtashell.net