-CURRENT kernel panic

[Vincent Poy]

On Fri, 5 Mar 2004, Andrew Gallatin wrote:

> Vincent Poy writes:
>  > > real memory  = 2147360768 (2047 MB)
>  > > avail memory = 2095669248 (1998 MB)
>  > >
>  > > > Just add vm.kmem_size=VALUE to /boot/loader.conf.  That way you don't
>  > > > need to rebuild a kernel.   I run with vm.kmem_size=429391872
>  >
>  > Just tried what you mentioned and the kernel panics at the same spot above
>  > on vm_kern.c.  I'm glad I cloned my drives on a nightly basis so I booted
>
> What is the panic message?

	No idea what it was but it panics as soon as it gets to the memory
portion at the bootup.  I guess it's the same panic one gets if one sets
maxusers=512 in the kernel and tries this.

> BTW, that's why hardcoding is not good, and why the defaults should
> work..

	Yeah but the problem is the defaults don't work.  It used to work
fine on my September 23, 2003 -CURRENT but when I went with February 28,
2004 and later -CURRENT, they all had this problem.


Cheers,
Vince - vince at WURLDLINK.NET - Vice President             ________   __ ____
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
WurldLink Corporation                                  / / / /  | /  | __] ]
San Francisco - Honolulu - Hong Kong                  / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____]
Almighty1 at IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin