From owner-freebsd-current@FreeBSD.ORG Sun Mar 7 06:59:17 2004 Return-Path: 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 9ABCF16A4CE for ; Sun, 7 Mar 2004 06:59:17 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47E4843D3F for ; Sun, 7 Mar 2004 06:59:15 -0800 (PST) (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 i27ExAF6011996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Mar 2004 09:59:10 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id i27Ex54Q089353; Sun, 7 Mar 2004 09:59:05 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16459.14520.982776.823223@grasshopper.cs.duke.edu> Date: Sun, 7 Mar 2004 09:59:04 -0500 (EST) To: Sam Leffler In-Reply-To: References: <16453.61095.940884.597029@grasshopper.cs.duke.edu> <16456.43337.389382.661597@grasshopper.cs.duke.edu> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: freebsd-current@freebsd.org Subject: Re: reproducable "panic: pmap_enter: attempted pmap_enter on 4MB page" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Mar 2004 14:59:17 -0000 Sam Leffler writes: > On Mar 5, 2004, at 8:22 AM, Andrew Gallatin wrote: > > I've been getting this panic off+on for >9 months but haven't been able > to characterize it and/or narrow down the cause. I mostly see it on an > NFS server. For me it seemed to always happen when a particular kva was used. (0xc86ce000). It did not matter if I used my real driver, or a contrived 20-line test case that just malloc'ed a bunch of memory at module load. As soon as pmap_enter() was called on that kva, kaboom! But this behaviour stopped when: a) I changed from a non-WITNESS, non-INVARIANTS kernel to a WITNESS and INVARIANTS kernel. a) I upgraded kernel sources from Weds -> Fri It almost smells like something size related. Eg, something is overflowing and corrupting the page tables when the kernel has a particular size or alignment. I'm just curious -- when this happens to you, is it the same KVA that I saw? There is a printf just before the panic which spits out the kva.. Drew