From owner-freebsd-hackers Sun Nov 15 09:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15453 for freebsd-hackers-outgoing; Sun, 15 Nov 1998 09:32:33 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15448 for ; Sun, 15 Nov 1998 09:32:32 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id JAA03798; Sun, 15 Nov 1998 09:33:12 -0800 (PST) Message-Id: <199811151733.JAA03798@root.com> To: Dennis cc: hackers@FreeBSD.ORG Subject: Re: pmap_remove_pages problem In-reply-to: Your message of "Sun, 15 Nov 1998 12:15:54 EST." <3.0.32.19981115121552.006cc944@etinc.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 15 Nov 1998 09:33:11 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Every few days I have a 2.2.7-RELEASE machine that panics in the >pmap_remove_pages routing. Its usually in the middle of night when >nothing is going on. > >When is this function called, and what might be the cause of the >problem? Note that the same problem occurred in 2.2.6, so its not >a bad kernel build. A stack traceback might be useful. pmap_remove_pages is called when a process execs or exits in order to remove any and all pages in the process address space. Panics in it often indicate damage to the physical to virtual (pv) lists that happened sometime earlier, and is usually not related to the events going on at the time. Usually the problem is caused by improper management of virtual memory while in an interrupt context, but could have other causes. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message