From owner-freebsd-scsi Mon Jan 4 06:19:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18740 for freebsd-scsi-outgoing; Mon, 4 Jan 1999 06:19:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18734 for ; Mon, 4 Jan 1999 06:19:05 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id HAA51665; Mon, 4 Jan 1999 07:10:52 -0700 (MST) Date: Mon, 4 Jan 1999 07:10:52 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199901041410.HAA51665@narnia.plutotech.com> To: Randy Bush cc: scsi@FreeBSD.ORG Subject: Re: read DMA channel unavailable X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > Jan 2 10:57:34 rip /kernel: sorry, read DMA channel unavailable I would guess that this is coming from the sound code. It certainly isn't coming from your PCI SCSI controller since it doesn't use an (E)ISA DMA channel. > Jan 2 18:07:12 rip /kernel: sorry, read DMA channel unavailable -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message