From owner-freebsd-hackers Sat Jun 21 16:27:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25689 for hackers-outgoing; Sat, 21 Jun 1997 16:27:39 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25684 for ; Sat, 21 Jun 1997 16:27:36 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id TAA23264 for ; Sat, 21 Jun 1997 19:27:04 -0400 (EDT) Date: Sat, 21 Jun 1997 19:27:03 -0400 (EDT) From: Brian Tao To: FREEBSD-HACKERS Subject: "ad1848: Problems when clearing interrupt" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At some point today, while listening to a bunch of MP3 using the mpg123 0.59i player, the sound system on my 2.2-BETA machine at home stopped working (Gravis Ultrasound MAX 512k, not the newer PnP models). The dmesg buffer was filled with: isa_dmastart: channel 1 busy ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff isa_dmastart: channel 1 busy ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff isa_dmastart: channel 1 busy ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff ad1848: Problems when clearing interrupt, status=ff [etc...] Anything sound-related no longer worked (mpg123, xanim, s3mod, catting files to /dev/audio, etc.). In an effort to clear up the problem, I shut down to single user mode. All non-essential processes were apparently killed off, but I could not umount /usr/local (where mpg123 lives), even though fstat didn't show any process holding open a file descriptor on that filesystem. Re-entering multiuser mode didn't solve the sound problem either. I haven't upgraded this machine since last December (in fact it hasn't even been rebooted since early March), so I suppose I should do that anyway, but is this a known problem. If so, has it been fixed in the (presumably) newer sound drivers in 3.0-current? -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't"