Re: OOPS: 2.1.132 Soundblaster

Oleg Drokin (green@ccssu.ccssu.crimea.ua)
Sun, 27 Dec 1998 11:57:49 +0300

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Martin Mares: "Re: /proc/pci -- /proc/bus/pci discrepancy"
Previous message: Davidovac Zoran: "ASUS CD ROM 340 & 2.1.129+ dont work but work fine with 2.0.35+"
Maybe in reply to: Kevin Lentin: "OOPS: 2.1.132 Soundblaster"

>> I get the following oops when modprobe attempts to load the sound modules.
>> insmod: /lib/modules/2.1.132/misc/soundcore.o: init_module: Device or resource busy
AC> What does dmesg say after that fails. The crash is from what occurs after
AC> that. Its also occuring as far as I can tell because your sound blaster
AC> failed to configure.
There is only one place in sound_core.c::init_module, where we
can return -EBUSY:
if(register_chrdev(SOUND_MAJOR, "sound", &soundcore_fops)==-1)
{
printk(KERN_ERR "soundcore: sound device already in use.\n");
return -EBUSY;
}
But there is also KERN_ERR message printed and I do not know of any
linux distributin, that disables displaying of messages of such loglevel
on console. Seems strange for me.

Bye,
Oleg

-
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.tux.org/lkml/

Next message: Martin Mares: "Re: /proc/pci -- /proc/bus/pci discrepancy"
Previous message: Davidovac Zoran: "ASUS CD ROM 340 & 2.1.129+ dont work but work fine with 2.0.35+"
Maybe in reply to: Kevin Lentin: "OOPS: 2.1.132 Soundblaster"