From owner-freebsd-current Mon Feb 15 15:00:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19362 for freebsd-current-outgoing; Mon, 15 Feb 1999 15:00:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19356 for ; Mon, 15 Feb 1999 15:00:25 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id SAA15708; Mon, 15 Feb 1999 18:00:16 -0500 (EST) (envelope-from luoqi) Date: Mon, 15 Feb 1999 18:00:16 -0500 (EST) From: Luoqi Chen Message-Id: <199902152300.SAA15708@lor.watermarkgroup.com> To: current@FreeBSD.ORG, khetan@iafrica.com Subject: Re: Problems in VM structure ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi. > > I saw that my 4-CURRENT box from 8 February dropped to ddb > after my last make world. I rebuilt world today, and the > same problem is occuring. These problems started occuring > after Matt Dillon's changes to the VM system. > > What is worrying/troubling is that in single user mode, > the machine is stable, and manages to build world without > a problem. When booted into multi-user mode, it's stable > and usable for anywhere from 1 to 3 hours, and then > panics. There are no active users on at the time, and the > machine is not heavily loaded (0.0-0.2) > > I suspected a hardware error, so swopped all the RAM from a > production machine, and it still produces the same fault. > > The error is > panic: vm_fault: fault on nofault entry, addr : f2572000 This indicates an unmapped struct buf, should be a software bug. > Debugger ("panic") > Stopped at Debuger+0x37: movl $0,in_Debugger > > When I hit c, I get this : > Could you type in "bt" next time this happens, and post the result? -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message