Re: FreeBSD 5.1-R kernel panic

panic: kmem_malloc(4096): kmem_map too small: 275251200 total allocated
cpuid = 2; lapic.id = 01000000
boot() called on cpu#2

syncing disks, buffers remaining... 7149 7148 7148 7148 7143 7151 7143 7143
7143
 7143 7143 7143 7143 7143
7143 7143 7143
7143 7143 7143 7143 7143 7143 7143 7143 7143


kernel paniced again... this time with the re-compiled 5.1-R kernel with the
1.126 kern_malloc.c file.

I was looking at uping the kern.vm.kmem.size as suggested to do as well, but
I cannot find that value in sysctl -a, so I'm not sure where to set that
specifically.  I have found the value for nmbclusters and it is set to the
following:

kern.ipc.nmbclusters: 25600

I guess short of setting the kern.vm.kmem.size I need to get someone here
the stack trace leading to the crash... is there a URL that someone can
point me to for me to set the box up for this?  I'll dig around in the
developers handbook, I seem to remember seeing something about it in there.

Thanks,
Stephane.


----- Original Message ----- 
From: ""Stephane Raimbault"" <segr_at_hotmail.com>
Newsgroups: mailing.freebsd.current
Sent: Tuesday, July 22, 2003 0:33
Subject: Re: FreeBSD 5.1-R kernel panic


> Hi Thanks for your response,
>
> I do not have PAE enabled... I've been hesitant of turning it on, I'm not
> sure if it's too stable, I noticed that the asr driver is in the nodriver
> list in the PAE kernel config file and I use the asr driver for my Adaptec
> 2015S raid card.  If you think its safe to enable PAE with my current
setup,
> please let me know, I do have 2 more gig's of ram in this particular box
> that I'd like to enable if it doesn't compromise system stability.
>
> I will re-compile the kernel with the kern_malloc.c as you suggested,
> however I see that 1.126 fixes a PAE issue, so I'm not sure if that's
going
> to help me out much.
>
> Where can I get information on how to get my kernel to provide a stack
> trace?  I have done little of this type of troubleshooting, but would like
> to provide as much info before I'm forced to revert to 4.8-R in hopes to
> return stability to our system.  If the new kernel with the updated
> kern_malloc.c doesn't help, I'll look at increasing the values you
> suggested.
>
> Thanks for the info, and I'll keep you posted with what I find.
>
> Thanks again,
> Stephane Raimbault
>
> ----- Original Message ----- 
> From: "Bosko Milekic" <bmilekic_at_technokratis.com>
> Newsgroups: mailing.freebsd.current
> Sent: Monday, July 21, 2003 16:36
> Subject: Re: FreeBSD 5.1-R kernel panic
>
>
> >
> > On Mon, Jul 21, 2003 at 03:01:24PM -0600, Stephane Raimbault wrote:
> > > I'm running FreeBSD 5.1-RELEASE with the SMP kernel and ran across the
> > > following kernel panic.
> > >
> > > panic: kmem_malloc(4096): kmem_map too small: 275251200 total
allocated
> > >
> > > I'm trying to figure out what could be causing this, what kind of
> > > information that I could provide to this group (or other group?) to
see
> if
> > > this is a bug in FreeBSD that needs to be looked into?
> > >
> > > The box is basically a busy apache server... the kernel panic seemed
to
> > > occur during the periodic daily was running.  It seems to complete the
> > > 440.status-mailq part of periodic daily , but doesn't do
> > > 450.status-security.
> > >
> > > This isn't the first time the box has crashed at aprox. 3:01 am (when
> daily
> > > runs)... however this is the first time I've seend the kernel panic
> message
> > > quoted above in the /var/run/dmesg.boot file.
> > >
> > > I have attached the entire /var/run/dmesg.boot file to this message.
> > >
> > > What can I do to assist in identifiying and resolving this problem?
> > >
> > > Thanks,
> > > Stephane Raimbault.
> >
> >   Just a few things:
> >
> >   1) Do you have PAE enabled?
> >
> >   2) Can you upgrade to src/sys/kern/kern_malloc.c version 1.126 or
> >   upgrade to HEAD?
> >
> >   If you have PAE enabled and (2) does not fix your problem, then please
> >   post a stack trace that resulted in the panic.  You also have a lot of
> >   RAM so if (2) above does not fix your problem, try setting the
> >   kern.vm.kmem.size bootable to approximately 350,000,000 or so (even
> >   400,000,000 is OK as long as NMBCLUSTERS is not too-too high).
> >
> > -- 
> > Bosko Milekic  *  bmilekic_at_technokratis.com  *  bmilekic_at_FreeBSD.org
> > TECHNOkRATIS Consulting Services  *  http://www.technokratis.com/
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to
"freebsd-current-unsubscribe_at_freebsd.org"
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"