From owner-freebsd-current Tue Sep 25 8:16:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D6DDC37B416 for ; Tue, 25 Sep 2001 08:16:13 -0700 (PDT) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA00772; Tue, 25 Sep 2001 17:16:12 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org Subject: Weird thing... From: Dag-Erling Smorgrav Date: 25 Sep 2001 17:16:12 +0200 Message-ID: Lines: 10 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ...really weird, but apart from the "vnode interlock not locked" panic (debug.witness_watch="0" seems to work around it), and the ACPI timer stuff (debug.acpi.disable="timer" took care of *that*), the latest -CURRENT actually seems to work. Even my floppy drive works now, which it hasn't since mid-June. I may even be able to get some work done on pseudofs and procfs :) DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message