From owner-freebsd-questions@FreeBSD.ORG Sat Nov 11 21:18:19 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 35D9F16A526 for ; Sat, 11 Nov 2006 21:18:19 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE9B043D5C for ; Sat, 11 Nov 2006 21:18:18 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from [10.0.1.2] (pool-71-109-167-24.lsanca.dsl-w.verizon.net [71.109.167.24]) (authenticated bits=0) by zoot.lafn.org (8.13.6/8.13.4) with ESMTP id kABLIDsL074755 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Sat, 11 Nov 2006 13:18:15 -0800 (PST) (envelope-from bc979@lafn.org) Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <7D505A6C-DEEB-4EF1-AF15-96DB89E909CD@lafn.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-questions From: Doug Hardie Date: Sat, 11 Nov 2006 13:18:16 -0800 X-Mailer: Apple Mail (2.752.3) X-Virus-Scanned: ClamAV 0.88/2187/Sat Nov 11 08:49:23 2006 on zoot.lafn.org X-Virus-Status: Clean Subject: Another Hardware Issue 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: Sat, 11 Nov 2006 21:18:19 -0000 I have another machine which will not boot the first time after a power on. It gives the following messages: Mounting root from ufs:/dev/ad0s1a panic: vm_fault: fault on nofault entry, addr: c6303000 syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up on 1 buffers Uptime: 16s However, if after that you hit any key on the console or the reset button on the front panel it will boot and run just fine. This is running FreeBSD 4.6.2-RELEASE-p13. It has run fine for years until this started. There is no point to updating it as it has no users. It has no running services. It only sends a couple of status emails daily and does frequent rcp's to my production servers. Are we about to lose the motherboard?