From owner-freebsd-questions@FreeBSD.ORG Sat Jan 29 23:22:06 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 7217C16A4F6 for ; Sat, 29 Jan 2005 23:22:06 +0000 (GMT) Received: from ptb-relay03.plus.net (ptb-relay03.plus.net [212.159.14.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2851243D41 for ; Sat, 29 Jan 2005 23:22:06 +0000 (GMT) (envelope-from ian@codepad.net) Received: from [80.229.159.44] (helo=[192.168.0.4]) by ptb-relay03.plus.net with esmtp (Exim) id 1Cv2Ct-000249-Jd for freebsd-questions@freebsd.org; Sat, 29 Jan 2005 23:40:47 +0000 From: Xian To: freebsd-questions@freebsd.org User-Agent: KMail/1.7 References: <200501291315.54293.ian@codepad.net> <200501290841.54557.m.hauber@mchsi.com> In-Reply-To: <200501290841.54557.m.hauber@mchsi.com> MIME-Version: 1.0 Content-Disposition: inline Date: Sat, 29 Jan 2005 23:22:04 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501292322.04200.ian@codepad.net> Subject: Re: panic on boot 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: Sat, 29 Jan 2005 23:22:07 -0000 On Saturday 29 January 2005 13:41, Mike Hauber wrote: > 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 Thanks Mike, I found the bad stick of ram, unfortunately this computer has a strange obsession about sticks of ram being in pairs!? So I can't use the other good stick of 32MB (There were 2 other good stick of 32MB). Gone from 128MB to 64 - Ouch! I have found another 2 sticks of 16MB in my spars box so that makes 96MB not too bad I suppose. -- /Xian "I have not failed. I've just found 10,000 ways that won't work" Thomas Edison