Hi Bosko, This is the output of sysctl vm.zone about 2 minutes before the crash occured. let me know if there is anything else I can provide you for this crashing problem. vm.zone: ITEM SIZE LIMIT USED FREE REQUESTS FFS2 dinode: 256, 0, 169095, 2670, 3126952 FFS1 dinode: 128, 0, 0, 0, 0 FFS inode: 144, 0, 169095, 2769, 3126952 SWAPMETA: 276, 121576, 0, 0, 0 unpcb: 140, 25620, 13, 99, 89564 ripcb: 228, 12342, 0, 51, 26 syncache: 136, 15370, 1, 144, 933999 tcptw: 48, 12367, 294, 1200, 698223 tcpcb: 356, 12331, 311, 712, 1406144 inpcb: 228, 12342, 605, 1520, 1406054 udpcb: 228, 12342, 2, 66, 2434251 socket: 256, 12330, 327, 693, 3929657 KNOTE: 64, 0, 1, 247, 1741346 PIPE: 176, 0, 28, 87, 414683 DIRHASH: 1024, 0, 1863, 209, 7982 NFSNODE: 304, 0, 0, 0, 0 NFSMOUNT: 224, 0, 0, 0, 0 L VFS Cache: 291, 0, 16515, 9654, 611843 S VFS Cache: 68, 0, 161636, 3859, 4443185 NAMEI: 1024, 0, 0, 180, 317484532 VNODEPOLL: 76, 0, 0, 0, 0 VNODE: 292, 0, 171622, 173, 171622 g_bio: 144, 0, 0, 1148, 21271397 VMSPACE: 256, 0, 157, 353, 532573 UPCALL: 44, 0, 0, 0, 0 KSE: 64, 0, 560, 60, 560 KSEGRP: 120, 0, 560, 29, 560 THREAD: 300, 0, 560, 25, 560 PROC: 484, 0, 207, 353, 532699 Files: 68, 0, 590, 1416, 38468316 65536: 65536, 0, 1, 1, 1 32768: 32768, 0, 1, 4, 47 16384: 16384, 0, 3, 17, 8638 8192: 8192, 0, 5, 9, 748 4096: 4096, 0, 511, 391, 543992 2048: 2048, 0, 31, 957, 3177 1024: 1024, 0, 309, 211, 22235682 512: 512, 0, 377, 367, 299800 256: 256, 0, 851, 2869, 5080136 128: 128, 0, 97455, 195, 38049176 64: 64, 0, 1521, 13793, 9862637 32: 32, 0, 1395, 3402, 9580393 16: 16, 0, 1251, 900, 11380832 DP fakepg: 72, 0, 0, 0, 0 PV ENTRY: 28, 2248540, 354739, 773941, 622568850 MAP ENTRY: 60, 0, 11434, 31136, 28180777 KMAP ENTRY: 60, 32670, 65, 463, 57555 MAP: 176, 0, 9, 37, 7 VM OBJECT: 148, 0, 170975, 9385, 13056273 UMA Buckets: 512, 0, 3669, 6, 0 UMA Hash: 128, 0, 0, 31, 0 UMA Slabs: 34, 0, 2234, 76, 0 UMA Zones: 276, 0, 52, 4, 0 same crash. panic: kmem_malloc(4096): kmem_map too small: 275251200 total allocated cpuid = 0; lapic.id = 00000000 boot() called on cpu#0 Thanks, Stephane > > > Please run 'sysctl vm.zone' periodically and capture the output. > Then wait for this to happen and feel free to send me the last captured > output before the crash. > > Is this a re-occuring crash for you? I thought we fixed this already. > Are you sure you have the absolute latest -current? (or are you supping > RELENG_5_1, which still has this problem?) > > -Bosko > > On Mon, Aug 11, 2003 at 03:45:14PM -0600, Stephane Raimbault wrote: > > 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" <segr_at_hotmail.com> > > To: "Bosko Milekic" <bmilekic_at_technokratis.com> > > Cc: <current_at_freebsd.org> > > 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" <bmilekic_at_technokratis.com> > > > 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 * 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" > > > > > -- > 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"Received on Thu Aug 14 2003 - 07:57:30 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:18 UTC