Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Jun 1997 19:27:03 -0400 (EDT)
From:      Brian Tao <taob@nbc.netcom.ca>
To:        FREEBSD-HACKERS <freebsd-hackers@freebsd.org>
Subject:   "ad1848: Problems when clearing interrupt"
Message-ID:  <Pine.GSO.3.95.970621191929.20160L-100000@tor-adm1.nbc.netcom.ca>

next in thread | raw e-mail | index | archive | help
    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"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.95.970621191929.20160L-100000>