Glad this issue is brought up ... I have been experiencing what I
think might be the same problem for several months now, but I have not
reported it yet because I always thought it was a misconfiguration problem
so far ...
To be more specific, here is my hardware configuration:
FIC PA-2012/AMD K6 233MHz
Buslogic/Mylex BT-958
TurtleBeach Malibu 64
Kernel 2.0.35, Debian 2.0 installation
I am using the CS4232 sound driver with the TurtleBeach.
Generally I get a hard lock whenever I try to use the rvplayer.
Playing wav files or MP3s seems stable if I use the sound driver that
comes with the kernel, but if I try to use the latest OSS/Free, all sound
applications become highly unreliable and lock the PC very quickly.
I have tried kernels 2.0.33/34/35, as well as 2.1.105 (not newer
versions though), and the same thing happens. Compiling the driver as a
module or not does not seem to make a difference.
I had noticed some sort of relationship with disk access as well,
but I did not pursue it very much.
There are no traces at all in my logfiles as far as I can tell,
and examining the log of "strace rvplayer" does not show abnormal activity
before the lock.
Any idea what else I could try? I guess I can always add debug
statements in the sound driver :-)
Thanks and Regards,
-Christian
> From: <linker@z.ml.org>
> Date: Sun, 16 Aug 1998 11:41:44 -0400 (EDT)
> Subject: Re: Solid v2.1.115 kernel lockup
>
> Thats alright, it's still better then my situation:
>
> SMP + Buslogic 956c + Kernels>2.1.101 + Any SB16 (or awe 32) = Hard lock
>
> I can't find the problem, and I've tried backing out patches but there
> were some real extensive changes to the sound system so I can't just do a
> single patch at a time..
>
> Part of the problem is the buslogic.. If I hook up an IDE and run form it
> or boot single user and cp a player and a file to a ramdisk and play it
> the computer doesn't lock until I cause a disk access..
>
> I'm fairly sure it's a deadlock bettwen the two drivers but I can't see
> it.. The sb drivers are a mess of cli's..
>
> Why doesn't Linus have this problem? Does he not have a sound blaster 16+
> or does this only affect certian buslogic cards or only 586 smp systems?
>
> - -
> Gregory Maxwell
>
> On Sun, 16 Aug 1998, Kirk Petersen wrote:
>
> > > I've been testing the sound drivers in v2.1.115 of the kernel, and I'm sad
> > > to say that playing two different WAVs one after the other resulted in a
> > > solid system lockup. Nothing, not even SYSRQ worked, needed to use the big
> > > red switch. :o(
> >
> > I've had the same problem for a while now. Both the rvplayer and the
> > esound daemon lock things up hard. I haven't tried to isolate the
> > problem (it isn't easy when the machine just freezes) but I will if
> > this is a mystery (not just something I have configured incorrectly).
> >
> > I've got a SoundBlaster 16 and the driver is built as a module.
> >
> > (I think, but am not sure, that it also happens in the latest
> > 2.0 kernels. I'll probably test this tomorrow)
> >
> > --
> > Kirk Petersen
> > www.speakeasy.org/~kirk/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html