From owner-freebsd-questions@FreeBSD.ORG Sun May 18 13:47:12 2003 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 8D21D37B401 for ; Sun, 18 May 2003 13:47:12 -0700 (PDT) Received: from zoon.lafn.org (zoon.lafn.org [206.117.18.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 139BB43F93 for ; Sun, 18 May 2003 13:47:12 -0700 (PDT) (envelope-from bc979@lafn.org) Received: from lafn.org (host-66-81-178-180.rev.o1.com [66.81.178.180]) by zoon.lafn.org (8.12.3/8.11.3) with ESMTP id h4IKlARn054681 for ; Sun, 18 May 2003 13:47:10 -0700 (PDT) (envelope-from bc979@lafn.org) Date: Sun, 18 May 2003 13:47:09 -0700 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: Doug Hardie To: freebsd-questions@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.552) Subject: Re: Kernel panic -supervisor read, page not present X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 May 2003 20:47:12 -0000 On Sunday, May 18, 2003, at 09:34 US/Pacific, Doug Hardie wrote: > I have a system that is almost a year old. It started rebooting last > week several times each day with the message "supervisor read, page > not present". A search of the archives indicates this is most likely > a hardware failure, but there is no indication of what might have > failed. The only messages preceeding the panic have been a gzip that > failed, several crons and atruns that failed. Most of the panics show > nothing unusual preceeding them in console.log or messages. The > machine is an archive server. Its role in life is to do an rsync > every 5 minutes for off-site archival storage. Nothing else is > running on it. Any ideas how to determine the failure as its still > under warrantee for a few more weeks. The situation is deteriating. Now rsync is core dumping. ls works, but ls -l does not. It also core dumps. The problem occurs when reading /etc/spwd.db. Something must be corrupt in it. I can't find any info on that file.