Date: Fri, 04 Jun 2010 02:37:14 -0700 From: Dave Hayes <dave@jetcafe.org> To: John Baldwin <jhb@freebsd.org> Cc: Garrett Cooper <yanefbsd@gmail.com>, freebsd-stable@freebsd.org, Clifton Royston <cliftonr@lava.net>, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: Locking a file backed mdconfig into memory Message-ID: <201006040937.o549bEFt054288@hugeraid.jetcafe.org> In-Reply-To: <201006031029.00588.jhb@freebsd.org> References: <201005272348.o4RNmgWh014243@hugeraid.jetcafe.org> <201006011020.01318.jhb@freebsd.org> <201006022237.o52MbxZM066281@hugeraid.jetcafe.org> <201006031029.00588.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin <jhb@freebsd.org> writes: > On Wednesday 02 June 2010 6:37:59 pm Dave Hayes wrote: >> John Baldwin <jhb@freebsd.org> writes: >> > Ok, if you are using a stock mfsroot from a release build, that should >> > work fine. If you have built a custom mfsroot that is larger, then >> > you may need to increase NKPT on i386. In very recent 7 and later you >> > can do this by setting it to a new value in your kernel config. In >> > older versions you can do this by manually adding a #define to set a >> > new value of NKPT in opt_global.h or hacking on the source directly. >> >> Is this also true for amd64 (which is my particular target)? > > It might be. What is the panic you are seeing? I can't see the panic as it repeatedly scrolls across the console screen faster than I can read it. In this case the mfsroot is around 275MB. I have noticed that sometimes I can build an mfsroot that does not crash of this size. -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< People usually oppose things because they are ignorant of them.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201006040937.o549bEFt054288>