From owner-freebsd-multimedia Tue May 14 11:46:24 1996 Return-Path: owner-multimedia Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA02164 for multimedia-outgoing; Tue, 14 May 1996 11:46:24 -0700 (PDT) Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA02157 for ; Tue, 14 May 1996 11:46:17 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de) by mail.rwth-aachen.de (PMDF V5.0-4 #13110) id <01I4PG9J0R4G000S40@mail.rwth-aachen.de> for multimedia@freebsd.org; Tue, 14 May 1996 19:07:35 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id TAA09694 for multimedia@freebsd.org; Tue, 14 May 1996 19:14:50 +0200 Date: Tue, 14 May 1996 19:14:50 +0200 From: "Christoph P. Kukulies" Subject: vat under 2.2-current To: multimedia@freebsd.org Message-id: <199605141714.TAA09694@gilberto.physik.rwth-aachen.de> Content-transfer-encoding: 7BIT Sender: owner-multimedia@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I removed the isa_dmastart: channel busy from isa.c and as a consequence of this (not absolutely sure) I could run a vat session without system freeze. But what I get is: failed PCM 64 sendmsg: No buffer space available sendmsg: No buffer space available sendmsg: No buffer space available sendmsg: No buffer space available sendmsg: No buffer space available sendmsg: No buffer space available The failed PCM messages appear a lot when moving the speaker slider and I doubt whether it is really a useful message. More concerns me the sendmsg: No buffer space available message. Which portion of the sounddriver is cassuing this? Obviously it comes from one of uipc_socket.c: error = ENOBUFS; uipc_socket2.c: return (ENOBUFS); uipc_syscalls.c: error = ENOBUFS; uipc_syscalls.c: return (ENOBUFS); uipc_syscalls.c: return (ENOBUFS); uipc_syscalls.c: return (ENOBUFS); uipc_syscalls.c: return (ENOBUFS); uipc_usrreq.c: error = ENOBUFS; uipc_usrreq.c: return (ENOBUFS); Could it be that it came the fact that I was using a slow (64Kbit/s) ISDN connection ? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de