I updated to 5.1-CURRENT this weekend and my kernel panic'd this morning.
Here is what I have from the trace
panic: kmem_malloc(4096): kmem_map too small: 275251200 total allocated
cpuid = 0; lapic.id = 00000000
Debugger("panic")
Stopped at Debugger+0x55: xchgl %ebx,in_Debugger.0
db> trace
Debugger(c0538a46,0,c054e317,e91c4b6c,100) at Debugger+0x55
panic(c054e317,1000,10680000,e91c4b98,0) at panic+0x15f
kmem_malloc(c082f0b0,1000,2,e91c4bf0,c0490f22) at kmem_malloc+0x100
page_alloc(c083ad80,1000,e91c4be3,2,c053b88d) at page_alloc+0x27
slab_zalloc(c083ad80,102,c058f30c,60b,c0630c80) at slab_zalloc+0xc2
uma_zone_slab(c083ad80,102,167,c058f30c,c083ae44) at uma_zone_slab+0xe8
uma_zalloc_bucket(c083ad80,102,c054fb50,599,167) at uma_zalloc_bucket+0x185
uma_zalloc_arg(c083ad80,0,102,fe,d70cb400) at uma_zalloc_arg+0x369
malloc(80,c058f960,102,0,e91c4ce0) at malloc+0xd3
crget(bfbffa70,d70cb414,8,cb0017fc,1) at crget+0x25
setgroups(cafff130,e91c4d10,c0554758,3ee,2) at setgroups+0x58
syscall(2f,2f,bfbf002f,0,bfbffa70) at syscall+0x273
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (80, FreeBSD ELF32, setgroups), eip = 0x282d208f, esp =
0xbfbffa4c, ebp = 0xbfbffab8 ---
Let me know if there is other data you need from me.
Thanks again,
Stephane.
----- Original Message -----
From: "Stephane Raimbault" <[EMAIL PROTECTED]>
To: "Bosko Milekic" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 11:02 AM
Subject: Re: FreeBSD 5.1-R kernel panic
> Hi Bosko,
>
> Thank you for your suggestion. I am a little un-easy about upgrading my
> system from -RELEASE to -CURRENT. Did you mean, simply upgrading the
kernel
> to -CURRENT, or the entire system?
>
> I'll think of a way I can continue this testing with you so that we can
make
> sure this problem is resolved. It might take me a couple days for me to
> safeguard my data and come up with a backup plan for my system should
> upgrading to -current blows up my system :)
>
> If it's just a question of upgrading the kernel, then I can probably
> implement that sooner rather then later, so let me know if it's just the
> kernel, or the entire /usr/src system you would like me to upgrade.
>
> Thanks,
> Stephane.
>
> ----- Original Message -----
> From: "Bosko Milekic" <[EMAIL PROTECTED]>
> Newsgroups: mailing.freebsd.current
> Sent: Wednesday, July 30, 2003 9:35 AM
> Subject: Re: FreeBSD 5.1-R kernel panic
>
>
> >
> > On Wed, Jul 30, 2003 at 09:25:34AM -0600, Stephane Raimbault wrote:
> > > Hi Bosko,
> > >
> > > My kernel panic'd again this morning. I had removed all the USB
devices
> > > from my kernel and had set my /etc/rc.conf to usbd_enable="NO" and the
> > > kernel panic'd again.
> > >
> > > I have attached both my kernel config file and the trace of the panic.
> Let
> > > me know if I can provide any further information to help analyze this
> > > problem.
> > >
> > > Thanks,
> > > Stephane Raimbault.
> >
> > Hmmm. For what it's worth, I've seen both of these panics before.
> >
> > Have you tried to cvsup to the latest -current (with all of those UMA
> > fixes?)
> >
> > Also, try grabbing
> > http://people.freebsd.org/~bmilekic/uma_races.patch and applying
> > that to a fresh -current. I'm not sure that it's related, but at
> > this point it's worth a shot.
> >
> > It's worth noting that a small chunk of the above patch may fail as I
> > just committed a part of it. You should be able to safely ignore
> > that.
> >
> > Let me know how it works out.
> >
> > Regards,
> > --
> > Bosko Milekic * [EMAIL PROTECTED] * [EMAIL PROTECTED]
> > TECHNOkRATIS Consulting Services * http://www.technokratis.com/
> > _______________________________________________
> > [EMAIL PROTECTED] mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
>
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
