Date: Thu, 11 Mar 1999 11:43:32 -0600 (CST) From: Greg Rowe <greg@uswest.net> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: freebsd-hackers@FreeBSD.ORG, David Greenman <dg@root.com> Subject: Re: SMP Woes Message-ID: <XFMail.990311114332.greg@uswest.net> In-Reply-To: <199903110732.XAA61853@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bingo !!! The system is a 1 gig of memory, 4 cpu's. Maxusers down to 64 solved the Fatal Trap problem. I'll try moving the number up in stages and see where it breaks. I had been using 256 and a couple times 512 in testing. Thanks. Greg On 11-Mar-99 Matthew Dillon wrote: > Well, zalloci() can call _zget(), which can call bzero(). Maybe the > underscore in the _zget() is preventing DDB from listing it. > > The call offset in zalloci() in the trace below is zalloci+0x29. If > you disassemble zalloci, you will note that this is the call-return > point for _zget: > > 0xf020b59f <zalloci+23>: pushl %ebx > 0xf020b5a0 <zalloci+24>: call 0xf020b5f8 <_zget> > 0xf020b5a5 <zalloci+29>: movl %eax,%ebx > > The generic_bzero() call arguments are either bogus, or the stack > length argument has been modified by generic_bzero(). > > The fault virtual address is 0, but vm_page_alloc() seems to properly > test for m == NULL so this should not be possible. > > It would be useful to print out the contents of *m from the _zget > frame, and also the *z structure. > > -- > > If this machine has a large amount of memory, it may have overrun its > KVA allocation. This can also happen if you have a large 'maxusers' > in the kernel config. If so, try reducing maxusers to 128 or less. > > -Matt > Matthew Dillon > <dillon@backplane.com> > Greg Rowe <greg@uswest.net> US WEST - Internet Service Operations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.990311114332.greg>