Date: Mon, 15 Jul 1996 18:43:25 -0700 (PDT) From: Mike Harshbarger <harsh882@uidaho.edu> To: freebsd-current@freebsd.org Cc: Veggy Vinny <richardc@CSUA.Berkeley.EDU> Subject: Re: sound driver problem Message-ID: <Pine.HPP.3.93.960715180939.20084A-100000@goshawk.csrv.uidaho.edu> In-Reply-To: <Pine.PTX.3.91.960714223317.25861H-100000@soda.CSUA.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 14 Jul 1996, Veggy Vinny wrote: > On Sun, 14 Jul 1996, Sujal Patel wrote: > > > On Sat, 13 Jul 1996, Veggy Vinny wrote: > > > > > gus0 at 0x220 irq 12 drq 1 on isa > > > > > > Jul 13 19:26:16 bigbang /kernel: GUS: DMA Transfer timed out > > > Jul 13 19:26:16 bigbang /kernel: isa_dmastart: channel 1 busy > > > > Is your DRQ correct and not conflicting with another device? > > Yes, it is..... Because nothing else in my system has that DRQ, > or DMA.... I've seen the same type of problem with my GUS-MAX when running s3mod. MODs *do* play, but I get tons of Jul 15 18:06:42 inertia /kernel: isa_dmastart: channel 1 busy Jul 15 18:06:45 inertia last message repeated 39 times which, right now, is just a minor annoyance to have fly by on the console. I see most of them occur when the sound samples are being written to the GUS' memory (512K on board). I've seen these errors for about a month now... from May 16th or so (the first occurance I have in my logs). 486/80 VLB, 8 megs, current as of Jun 26th. options "GUS_IRQ=11" #gus. device gus0 at isa? port 0x220 irq 11 drq 1 vector gusintr -- Mike 'axly' Harshbarger | OOPS! Adjustment fire, harsh882@uidaho.edu <*> | 1000 meters left!... axly@kuoi.asui.uidaho.edu | NO, NO, THE OTHER LEFT!!! http://www.cs.uidaho.edu/~harsh882/ | -- Forward Observer Axly
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.HPP.3.93.960715180939.20084A-100000>