From owner-freebsd-stable  Wed Feb 17  3:38:45 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from eagle.plab.ku.dk (eagle.plab.ku.dk [130.225.105.63])
	by hub.freebsd.org (Postfix) with ESMTP id 298B510E6D
	for <freebsd-stable@freebsd.org>; Wed, 17 Feb 1999 03:38:41 -0800 (PST)
	(envelope-from voland@eagle.plab.ku.dk)
Received: (from voland@localhost)
	by eagle.plab.ku.dk (8.9.2/8.9.1) id MAA08327;
	Wed, 17 Feb 1999 12:38:41 +0100 (CET)
	(envelope-from voland)
Mime-version: 1.0
Content-type: text/plain; charset="koi8-r"
Content-transfer-encoding: 8bit
To: freebsd-stable@freebsd.org
Subject: Does pcm driver works correctly?
From: Vadim Belman <voland@plab.ku.dk>
Date: 17 Feb 1999 12:38:41 +0100
Message-ID: <85n22dgszi.fsf@eagle.plab.ku.dk>
Lines: 42
X-Mailer: Gnus v5.5/Emacs 20.3
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	Hi!

	Recently I've switched from VoxWare drivers to pcm on my 3.1-STABLE
	box. The soundcard is AWE64 PnP configured with the following
	script:

pnp 1 0 os enable port0 0x220 port1 0x330 port2 0x388 drq0 1 drq1 5 irq0 5
pnp 1 1 os enable port0 0x200 drq0 4 drq1 4
pnp 1 2 os enable port0 0x620 port1 0xA20 port2 0xE20 drq0 4 drq1 4

	The kernel config contains this line for pcm driver:

device pcm0 at isa? port 0x220 tty irq 5 drq 1 flags 0x15

	So far, so good. The card is detected:

Feb 17 01:26:24 eagle /kernel: pcm1 (SB16pnp <SB16 PnP> sn 0x1994d93d) at 0x220-0x22f irq 5
Feb 17 01:26:24 eagle /kernel: drq 1 flags 0x15 on isa

	and I can even use it. But the same time I have lots of messages of
	this kind:

Feb 17 11:23:52 eagle /kernel: sorry, read DMA channel unavailable
Feb 17 11:23:52 eagle last message repeated 2 times
Feb 17 11:27:10 eagle /kernel: sorry, read DMA channel unavailable
Feb 17 11:35:27 eagle last message repeated 8 times
Feb 17 11:44:16 eagle last message repeated 6 times
Feb 17 11:56:55 eagle last message repeated 12 times
Feb 17 12:06:16 eagle last message repeated 9 times

	Neither DMA1 nor DMA5 are used somewhere else.

	I suppose this is a bug. But since I'm not sure I would rather ask
	first: are there any pit-holes? May be something has been done
	wrong?

P.S. The same time, playing a bit with sound I found a way to panic the
system using pcm audio... It was too easy... 8(

-- 
    /Voland			Vadim Belman
				E-mail: voland@plab.ku.dk


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message