From owner-freebsd-current  Sun Oct  8 19:36:22 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id TAA19059
          for current-outgoing; Sun, 8 Oct 1995 19:36:22 -0700
Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA19053
          for <freebsd-current@freebsd.org>; Sun, 8 Oct 1995 19:36:15 -0700
Received: (from news@localhost) by haywire.DIALix.COM (sendmail) id KAA00534 for freebsd-current@freebsd.org; Mon, 9 Oct 1995 10:35:57 +0800 (WST)
Received: from GATEWAY by haywire.DIALix.COM with netnews
	for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com)
To: freebsd-current@freebsd.org
Date: 9 Oct 1995 10:35:53 +0800
From: peter@haywire.dialix.com (Peter Wemm)
Message-ID: <45a1q9$gi$1@haywire.DIALix.COM>
Organization: DIALix Services, Perth, Australia.
References: <199510082335.QAA06276@newport.ece.uci.edu>
Subject: Re: vm_page_free panic with KTRACE
Sender: owner-current@freebsd.org
Precedence: bulk

swallace@ece.uci.edu (Steven Wallace) writes:

>I just noticed that doing a ktrace will cause a vm_page_free panic:
>vm_page_free:  offset(46092288), bmapped(0), busy(1), PG_BUSY - freeing busy pg.

>Just do a ktrace and then during or shortly after while swapping
>it will panic.  Don't do ktrace, system up for long time.
>Same ktrace/free bug in today -current and sept 25 -current kernel of mine.

>Steven

>P.S.  I *need* ktrace to debug the stupid ibcs2 emulator (:

Ahh.. So I wasn't imagining it!  I've had this turn up occasionally
for quite some time now.

The last time was a couple of days ago when I was trying to ktrace the
-current "port" of screen which doesn't work.  (it only works if
setuid is turned off)

-Peter