Date: Mon, 16 Feb 1998 02:48:33 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: sthaug@nethelp.no Cc: tlambert@primenet.com, roberto@keltia.freenix.fr, hackers@FreeBSD.ORG Subject: Re: VM messed: vm_page_free panic problem Message-ID: <199802160248.TAA20273@usr05.primenet.com> In-Reply-To: <6069.887584835@verdi.nethelp.no> from "sthaug@nethelp.no" at Feb 16, 98 00:20:35 am
next in thread | previous in thread | raw e-mail | index | archive | help
> boot.flp from 3.0-980206-SNAP (from releng22.freebsd.org) panics at the > end of the boot process, with: > > changing root device to fd0c > rootfs is 1440 KByte compiled in MFS > vm_page_free: pindex(12), busy(0), PG_BUSY(0), hold(0) > panic: vm_page_free: freeing free page > > boot.flp from 3.0-980204-SNAP works okay. > > It's very much reproducible - the panic occurs every time :-). The numbers > in the parentheses are the same every time. I've tried it on a PPro-200 > with 64 mByte memory, and an AMD 5x86-133 with 24 MByte memory. OK. Disable the PSE. The problem seems (to me) to be that there is a requirement for more than 4M for the kernel, but with PSE enables, there is only a single 4M page. The MFS pushes the page boundry out, and then you fail when you try to page in from the unmapped region of the MFS. I would be surprised if these disks would boot on a 5M system without PSE capability. I think we are talking 6M now. The easiest test would be to build a distribution after defining DISABLE_PSE, and see if those boot. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802160248.TAA20273>