From owner-freebsd-bugs Tue Sep 28 23:40:13 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 69916158E3 for ; Tue, 28 Sep 1999 23:40:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id XAA02887; Tue, 28 Sep 1999 23:40:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 229CA14F06 for ; Tue, 28 Sep 1999 23:32:31 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: (from doconnor@localhost) by cain.gsoft.com.au (8.8.8/8.8.8) id QAA26462; Wed, 29 Sep 1999 16:02:30 +0930 (CST) (envelope-from doconnor) Message-Id: <199909290632.QAA26462@cain.gsoft.com.au> Date: Wed, 29 Sep 1999 16:02:30 +0930 (CST) From: "Daniel O'Connor" Reply-To: doconnor@gsoft.com.au To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: kern/14033: Data acq process gets stuck in vmopar Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Number: 14033 >Category: kern >Synopsis: Data acq process gets stuck in vmopar >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 28 23:40:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Daniel O'Connor >Release: FreeBSD 3.3-RELEASE i386 >Organization: Genesis Software >Environment: 3.2, 3.3-RC, 3.3-REL, and 3.3-STABLE. PII-350, 128meg of RAM. >Description: We have a PCI data acquisition card which effectivly maps a FIFO into memory and the kernel reads it during interrupt, and passes the data off to a userland process in read(). Occasionally (happens much more often when the system is loaded, ie buildworld, and doing networking) the process reading from the card gets stuck in vmopar. I looked in the archives and there was a suggestion that it was NFS related so I umount'd the NFS partitions but no joy. This problem does not occur in 2.2.8, and the driver code is almost identical, (except poll) so I suspect the OS, but I do not know where to start looking. >How-To-Repeat: Rather complicated :( >Fix: Go back to 2.2.8+CAM (blerg) >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message