SB16 sound problems (2.1.99pre3) -- standing corrected

Trever Adams (arabian@onramp.net)
Thu, 30 Apr 1998 10:48:08 +0000

It seems I must admit I was wrong. I thought it was the sound drivers.
It may be, but it sure doesn't seem it. I tried watching
/proc/interrupts for the first time as I did these tests. 91 then 99
(first then second run). First run was perfect, as you can guess from
the second it failed miserably. Only two kernels in the 9x seires have
even played the first time. This pre 99 and I cant remember the other.

Is there a way to track when an interrupt is sent to the CPU and then to
the kernel? (While on that subject, is there something like strace, but
that will follow it through the kernel instead of just to the kernel?)
It seems it is getting lost, or the sound driver is losing it (I don't
know which actually increments the proc entry). I did see something
strange. ALT-SysRq-T and M seem to sometimes allow you to make the
sound look as if you just boot, so it is the first time, and it works.
This isn't 100% though.

Trever Adams
arabian@onramp.net

P.S. In sb_audio.c, I believe it is, for the SB16 the DMA_buf_start_xxxx
call seems to be commented out in the play block function. Is this
correct? Is DMA for SB16 off?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu