From owner-freebsd-hackers Thu Mar 11 9:44:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from psv.oss.uswest.net (psv.oss.uswest.net [204.147.85.6]) by hub.freebsd.org (Postfix) with ESMTP id 6AB1E14C2E for ; Thu, 11 Mar 1999 09:44:27 -0800 (PST) (envelope-from greg@psv.oss.uswest.net) Received: (from greg@localhost) by psv.oss.uswest.net (8.9.2/8.9.2) id LAA58931; Thu, 11 Mar 1999 11:43:32 -0600 (CST) (envelope-from greg) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199903110732.XAA61853@apollo.backplane.com> Date: Thu, 11 Mar 1999 11:43:32 -0600 (CST) Reply-To: greg@uswest.net Organization: US WEST !NTERACT From: Greg Rowe To: Matthew Dillon Subject: Re: SMP Woes Cc: freebsd-hackers@FreeBSD.ORG, David Greenman Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 : pushl %ebx > 0xf020b5a0 : call 0xf020b5f8 <_zget> > 0xf020b5a5 : 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 > > Greg Rowe US WEST - Internet Service Operations To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message