> When I started to use devfs(d) a 'LOOKUP .* MODLOAD' in
> /etc/devfsd.conf could look up my system with modprobe eating CPU and
> I was unable to login or start kill... - I try to avoid this; maybe
> it was a modprobe problem or a module which didn't finished its
> init(), I don't know...
> Nobody else had this probleme here? Is this completly unknown?
We have experienced here at SGI. When turning module autoloading on, a
modprobe process will wedge and it won't allow us to umount the root
filesystem. It is a priority 1 bug for us right now as it will delay the
release of ProPack 1.4.
Jeremy Brown is assigned the bug right now, so he might have more
info on the status or what we have found so far. Any other leads would be
helpful.
I will probably slap a kernel with the kdb turned on and then try a
backtrace on the process to see where it is wedged. Will report more when
I get more info.
Thanks,
-tduffy
|