From owner-freebsd-current  Sun May 26 20:55:59 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA02608
          for current-outgoing; Sun, 26 May 1996 20:55:59 -0700 (PDT)
Received: from VX23.CC.MONASH.EDU.AU (vx23.cc.monash.edu.au [130.194.1.23])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA02581;
          Sun, 26 May 1996 20:55:40 -0700 (PDT)
Received: from moa.cc.monash.edu.au (george@moa.cc.monash.edu.au)
 by vaxc.cc.monash.edu.au (PMDF V5.0-6 #16291)
 id <01I57B3MAK6Q9IBJE7@vaxc.cc.monash.edu.au>; Mon, 27 May 1996 13:54:18 +1000
Received: (george@localhost) by moa.cc.monash.edu.au (8.6.10/8.6.4)
 id NAA00578; Mon, 27 May 1996 13:54:13 +1000
Date: Mon, 27 May 1996 13:54:13 +1000
From: George Scott <George.Scott@cc.monash.edu.au>
Subject: Re:  biodone w/current kernel & diskless operation
To: dyson@FreeBSD.ORG, pst@Shockwave.COM
Cc: current@FreeBSD.ORG, pst@precipice.shockwave.com
Message-id: <199605270354.NAA00578@moa.cc.monash.edu.au>
Content-transfer-encoding: 7BIT
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I was playing around with a completely diskless system today running wiht
> a -current kernel as of 8am this morning (Sunday).
> 
> I'm seeing very reproducable "biodone: buffer already done" messages.
> When this happens, the current process usually hangs, the rest of the
> system seems to operate just fine.
> 
> I just switched to an alternate terminal and did a ps axlwww in case this
> helps.  The process that's interesting is the vi (which is what I was
> doing when the system wigged).  The vi session itself seemed to keep
> working just fine, and I was even able to write out my file, but when
> I went to exit the process, everything hung for that terminal.  It
> seems there's something going on in the vm system that causes the biodone
> message and screws up the process spindown.

In case it is any help....

My system is set up the same way.  I get the same error, also usually when
quitting vi.  This has been happening (on and off) since I started playing
with -current (over a year ago).

I thought I had sent mail about it, but can't find it in my archives.

George.