From owner-freebsd-current  Sun May 20 13:46:11 2001
Delivered-To: freebsd-current@freebsd.org
Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8])
	by hub.freebsd.org (Postfix) with ESMTP id 422F137B424
	for <current@freebsd.org>; Sun, 20 May 2001 13:46:09 -0700 (PDT)
	(envelope-from bright@superconductor.rush.net)
Received: (from bright@localhost)
	by superconductor.rush.net (8.11.2/8.11.2) id f4KKk7J19722
	for current@freebsd.org; Sun, 20 May 2001 16:46:07 -0400 (EDT)
Date: Sun, 20 May 2001 16:46:04 -0400
From: Alfred Perlstein <bright@rush.net>
To: current@freebsd.org
Subject: HEADS UP: I broke swapping
Message-ID: <20010520164603.B17514@superconductor.rush.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0us
X-all-your-base: are belong to us.
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

I broke swapping with the vm mutex.

Hopefully I should have this fixed up within a couple of days tops.

No, I'm not heading off to Aruba or someplace after this intrusive
change, I am working on it.  Your kernel may panic, but I hope you
all keep a level head about this and don't follow suit. :)

Patches, suggestions and crashdumps would be helpful.

Bruce has been giving me some helpful tracebacks that I'm planning
to use to stabilize the system.

thanks,
-- 
-Alfred Perlstein [alfred@freebsd.org]
Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message