From owner-freebsd-current@FreeBSD.ORG  Tue Aug 26 07:30:06 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 583DB16A4BF
	for <current@freebsd.org>; Tue, 26 Aug 2003 07:30:06 -0700 (PDT)
Received: from mail26d.sbc-webhosting.com (mail26d.sbc-webhosting.com
	[216.173.237.167])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2D76443FDD
	for <current@freebsd.org>; Tue, 26 Aug 2003 07:30:01 -0700 (PDT)
	(envelope-from alc@imimic.com)
Received: from www.imimic.com (64.143.12.21)2-0588178187;
	Tue, 26 Aug 2003 10:29:48 -0400 (EDT)
Sender: alc@FreeBSD.ORG
Message-ID: <3F4B6EDC.B40E0332@imimic.com>
Date: Tue, 26 Aug 2003 09:29:48 -0500
From: "Alan L. Cox" <alc@imimic.com>
Organization: iMimic Networking, Inc.
X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.2 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Tinguely <tinguely@casselton.net>
References: <200308261229.h7QCTdwN062563@casselton.net>
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit
X-Loop-Detect: 1
cc: alc@freebsd.org
cc: current@freebsd.org
cc: bmilekic@freebsd.org
cc: l.ertl@univie.ac.at
Subject: Re: Another pmap related panic
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Aug 2003 14:30:06 -0000

Mark Tinguely wrote:
> 
> It could be a memory problem. Could you also please apply an assert
> to pmap_enter_quick() + INVARIANTS. This is a quick test that checks
> all the other paths that call pmap_enter_quick() are locked out so
> that two processors cannot be using the PADDR1/PMAP1 at the same time.
> 

Neither of Lukas's panics suggests that PADDR1/PMAP1 is being used.  The
faulting virtual addresses are

fault virtual address   = 0xbfca1974

and

fault virtual address   = 0xbfcadf10

which are within the PTmap, not PADDR1.  In other words,
pmap_pte_quick() concluded that the given pmap was currently active and
therefore the pte was accessible through the mapping that each address
space has to its own page table.

Regards,
Alan