[PlanetCCRMA] Kernel barf during modprobe/alsaconf/SBLive

Peter Lawler planetccrma@six-by-nine.com.au
Wed Nov 26 16:20:02 2003

While I was sitting on the thinking throne today, it occured to me that
there was some kind of 'snddevices' command that used to exist back in
they days when I first tinkered with alsa.

So, next step is to unload oss, snddevices (or similar, the actual
command escapes me @ the moment), then try the snddevices then
alsaconfig. Worth a shot. I only mention this as the docs don't mention
snddevices. I there a reason for this?

Needless to say, same result. Trying next to compile own kernel and alsa.


Fernando Pablo Lopez-Lezcano wrote:
>>Alsaconf picks up the card ok, thn goes to configure it and the kernel
>>throws this error.
>>The snd-emu10k1 and snd-timer drivers are left in 'initializing' state,
>>and as I'm fairly new to linux and rmmod fails (in use), I don't know
>>how to 'workaround' this without reboot.
> That is a "kernel panic", something really wrong happened during the
> module load and the kernel prints some debugging info and basically
> quits. The module cannot be removed without a reboot. 
> A bit more information about the crash can be found (only usable for
> alsa gurus, I guess) if you pipe that information through the ksymoops
> program, the output should include some symbol information (ie: not just
> numbers). 
>>This is a fresh system, only one sound card, one network card. Whether
>>low latency is enabled in the kernel or not seems to have no effect
>>Any assistance *GREATLY* appreciated.
> What version of alsa and of the kernel?
> Did you try with the redhat capabilities enabled kernel as well?
> -- Fernando