From owner-freebsd-current Wed Sep 3 21:05:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA02372 for current-outgoing; Wed, 3 Sep 1997 21:05:49 -0700 (PDT) Received: from pluto.plutotech.com (ken@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA02362 for ; Wed, 3 Sep 1997 21:05:46 -0700 (PDT) Received: (from ken@localhost) by pluto.plutotech.com (8.8.5/8.8.5) id WAA07230; Wed, 3 Sep 1997 22:05:31 -0600 (MDT) From: Kenneth Merry Message-Id: <199709040405.WAA07230@pluto.plutotech.com> Subject: Re: 3.0/SMP panic In-Reply-To: <199709030758.AAA07447@schizo.cdsnet.net> from Jaye Mathisen at "Sep 3, 97 00:58:29 am" To: mrcpu@schizo.cdsnet.net (Jaye Mathisen) Date: Wed, 3 Sep 1997 22:05:31 -0600 (MDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen wrote... > > Hmm... 3.0-current (supped 9/2/97), DPT RAID. fpx0, not a whole lot else. > > I was using M$ Inetload 2.0 to simulate a bunch of mail users. IT was > running fine for a few minutes, then died horribly with: > > Fatal trap 12: page fault while in kernel mode > cpuid = 1 > lapic.id = 33554432 > > current process = Idle > mp_lock = 01000003 > > interrupt mask = net tty bio <- SMP: XXX > > Stopped at _pmap_enter+0xa7: > > > and some other stuff. > > The traceback is not too long, but I don't have any good way to type it > all in. > > It goes like: [ traceback ] By any chance do you have more than 64MB in your machine and options MAXMEM=... in your kernel config file? I did, and I had panics very much like that (in pmap_enter) immediately on boot. When I took the MAXMEM line out (I've got 128MB), things worked just fine... I'm still not sure why, though. Ken -- Kenneth Merry ken@plutotech.com