From owner-freebsd-current Thu Feb 8 04:30:53 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA19167 for current-outgoing; Thu, 8 Feb 1996 04:30:53 -0800 (PST) Received: from deadline.snafu.de (deadline.snafu.de [194.64.158.28]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA19161 for ; Thu, 8 Feb 1996 04:30:47 -0800 (PST) Received: by deadline.snafu.de id m0tkVVW-0009Z1C; Thu, 8 Feb 96 13:31 MET (/\oo/\ Smail3.1.29.1 #29.1) Message-Id: Date: Thu, 8 Feb 96 13:31 MET X-Newsreader: knews 0.9.3 References: From: root@deadline.snafu.de (Andreas S. Wetzel) Subject: Re: Tired of "isa_dmadone_nobounce" messages X-Original-Newsgroups: deadline.lists.freebsd-current In-Reply-To: To: Jim Lowe Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk Hi! --- In article , Jim Lowe writes: >The problem is that someone changed the isa.c dma_start code >and the sound code a week or so ago and didn't complete the >required changes. They added the code to set dma_dusy[], but didn't >add the code to clear dma_busy[] in dmabuf.c. Thus, the messages. Yesterday I had another look at isa.c and I think isa_dmastart as well as isa_dmadone and isa_dmadone_nobounce look ok. The problem definately seems to be in the sounddriver, although I couldn't find anything obscure in there. Perhaps somebody with more experience of the sound- drivers could have a look at this again. BTW: The problem is not that the busy flag gets set and not reset but rather that some part of the sounddriver attempts to clear the flag twice in which case the flag isn't set in the second attempt. Thus the message: "channel xx not busy" This could happen if isa_dmadone_nobounce was called twice for example. Regards, Mickey -- (__) (@@) Andreas S. Wetzel E-mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://deadline.snafu.de/ / | || 13347 Berlin Voice: <+4930> 456 81 68 * ||----|| Germany Fax/Data: <+4930> 455 19 57 ~~ ~~