From owner-freebsd-questions@FreeBSD.ORG Sat Jan 29 13:37:45 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 14FF716A4CE for ; Sat, 29 Jan 2005 13:37:45 +0000 (GMT) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id B279343D3F for ; Sat, 29 Jan 2005 13:37:44 +0000 (GMT) (envelope-from m.hauber@mchsi.com) Received: from wizard.valleygate.net (12-219-204-24.client.mchsi.com[12.219.204.24]) by sccmmhc91.asp.att.net (sccmmhc91) with ESMTP id <20050129133743m9100fu57ie>; Sat, 29 Jan 2005 13:37:44 +0000 From: Mike Hauber To: freebsd-questions@freebsd.org Date: Sat, 29 Jan 2005 08:41:53 -0500 User-Agent: KMail/1.7.2 References: <200501291315.54293.ian@codepad.net> In-Reply-To: <200501291315.54293.ian@codepad.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501290841.54557.m.hauber@mchsi.com> Subject: Re: panic on boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: m.hauber@mchsi.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jan 2005 13:37:45 -0000 On Saturday 29 January 2005 08:15 am, Xian wrote: > I woke up this morning to find that my computer had rebooted > and panicked as soon as the kernel had started to run. it said: > > The rights of the University... > panic: vm_page_insert: alredy inserted > uptime: 0s > > in bright white on the screen. All I could do was switch it off > and on and it just did it again. Help: how do I fix it? It was > running 4.9R. This is my home web server that I use quite a lot > from college. It is extremely old - its a P90. > > Thank God for getting me to play around with taking backups 2 > days ago. I've seen this on various lists before, and I _think_ the general consensus was to first check the RAM by taking all the modules out but one and then adding them back until the panic returns. Hope that helps Mike