Messages in this thread | | | Date | Wed, 26 Mar 1997 13:48:01 -0800 (PST) | From | Trevor Johnson <> | Subject | Re: modald - NEW module autoloader |
| |
After applying the patch to the kernel, compiling and installing modutils-970317m, killing kerneld (which is started by my init scripts), doing "depmod -a" and running modald as root, I observed the following:
* mount /dev/fd0 /fd0 outputs "Continued" (I'm using mount 2.6b) and the floppy module is not loaded
* an strace of modald's process while doing this shows:
SYS_167(0, 0x9, 0xbffff940, 0x100, 0xbffff93c) = 0 fork() = 18834 wait4(-1, NULL, 0, NULL) = 18834 --- SIGCHLD (Child exited) --- kill(18833, SIGCONT) = 0 SYS_167(0, 0x9, 0xbffff940, 0x100, 0xbffff93c) = 0 fork() = 18835 wait4(-1, NULL, 0, NULL) = 18835 --- SIGCHLD (Child exited) --- kill(18833, SIGCONT) = 0 SYS_167(0, 0x9, 0xbffff940, 0x100, 0xbffff93c
* when I run an audio program, the sound module is not loaded--in fact, no modules seem to be loaded at all
* syslogd records these new errors:
Mar 26 13:25:28 topside modprobe: can't locate module block-major-2 Mar 26 13:25:44 topside last message repeated 3 times Mar 26 13:27:10 topside modprobe: can't locate module char-major-14 Mar 26 13:34:23 topside modprobe: can't locate module block-major-2 Mar 26 13:34:23 topside modprobe: can't locate module block-major-2 Mar 26 13:39:32 topside modprobe: can't locate module char-major-14 Mar 26 13:39:36 topside modprobe: can't locate module char-major-14
* if I start modald more than once, the later invocations start heating up the CPU with:
SYS_167(0, 0x9, 0xbffff940, 0x100, 0xbffff93c) = -1 EBUSY (Device or resource busy)
* the man page included is for bdflush. ___ Trevor Johnson <trevor@jpj.net>
| |