From owner-freebsd-alpha@FreeBSD.ORG Wed Apr 14 14:05:22 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 668EE16A4CE; Wed, 14 Apr 2004 14:05:22 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B42943D1F; Wed, 14 Apr 2004 14:05:22 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id i3EL5LFC011916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Apr 2004 17:05:21 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i3EL5Jhg061206; Wed, 14 Apr 2004 17:05:19 -0400 (EDT) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16509.42895.49213.222503@grasshopper.cs.duke.edu> Date: Wed, 14 Apr 2004 17:05:19 -0400 (EDT) To: kris@obsecurity.org In-Reply-To: <200404132236.20792.jhb@FreeBSD.org> References: <20040411093343.GA89809@xor.obsecurity.org> <200404132236.20792.jhb@FreeBSD.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: alc@FreeBSD.org cc: alpha@FreeBSD.org Subject: Re: Another alpha panic X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2004 21:05:22 -0000 John Baldwin writes: > On Sunday 11 April 2004 05:33 am, Kris Kennaway wrote: > > Not that I've had any luck getting someone to take a look at the last > > half-dozen alpha panics I've reported, but: > > > > panic: pmap_emulate_reference(0xfffffc0019436a00, 0xfffffe0014495e68, 0, > > 1): pa 0xb0a0000 not managed at line 2585 in file > > /a/asami/portbuild/alpha/src-client/sys/alpha/alpha/pmap.c Stack backtrace: > > db_print_backtrace() at db_print_backtrace+0x18 > > backtrace() at backtrace+0x2c > > __panic() at __panic+0x150 > > pmap_emulate_reference() at pmap_emulate_reference+0x15c > > trap() at trap+0x39c > > XentMM() at XentMM+0x2c > > --- memory management fault (from ipl 7) --- > > pmap_activate() at pmap_activate+0xb4 > > Lcs1() at Lcs1+0x1c > > --- root of call graph --- > > This is a VM-related panic. Perhaps alc@ might have an idea. There might be > a reference fault on a K0SEG address or some other silly bug. I just googled and saw that at least 2 of these have come with the same stack (context-switch(), pmap_activate()). What does pmap_activate+0xb4 map to in your kernel? What sort of machine? Is this UP or SMP? Drew