Re: Loading modules on demand with /sbin/hotplug

[DervishD <udev@dervishd.net>]

    Hi Kay :)

 * Kay Sievers <kay.sievers@vrfy.org> dixit:
> > I've done this and now the systems hangs up at bootup. I can't find
> > any information in any log, so I don't know the cause (probably
> > modprobe caused some driver to load, which caused an udev event,
> > which caused modprobe to run again, causing an
> > infinite loop).
> 
> Start: udevd -n and run: udevtrigger and watch where it fails. Good
> luck! :)

    -n? My udevd (v105) doesn't have that option. Do you mean '-t'? I've
thought about using -t and -v to see which can be the problem.

> > #ACTION="add", ENV{MODALIAS}="?*", RUN="/sbin/modprobe
> > $env{MODALIAS}" #ACTION="remove", ENV{MODALIAS}="?*",
> > RUN="/sbin/modprobe -r $env{MODALIAS}"
> 
> Unloading modules may be possible - I don't know, and have no plans to
> try this, because I don't think it makes a lot of sense.

    I must confess that it doesn't make much sense in 2.6. Back in 2.4 I
needed to unload usb-storage when I wasn't using it, otherwise my
ide-scsi got weird scsi numbers and cdrecord... well, you know. Now, I
don't feel the need of unloading modules on demand.

    I've deleted that line and the system works OK now. Well, it hung
with my USB card reader but I've been unable to reproduce this. No
matter what I do, everything works seamlessly now.

> > The two commented lines are the ones that caused the problem. Any
> > idea about the possible causes? If I move the modprobe command to my
> > "hal" script (IT IS NOT freedesktop HAL, but my own script), the
> > problem is the same: the system hangs as soon as the booting process
> > finishes, and I don't have any evidence of modprobe being hung or
> > whatever.
> >
> > I think I'm missing something VERY simple here, but I can't see
> > what: have you any idea about which the problem may be? Should I
> > delete the second commented line and don't unload modules on demand?
> > May any of the commented lines be causing an infinite loop?
> 
> Maybe it's just a module that gets loaded and crashes the box, or a
> failing module-init, that is causing a loop (like some platform
> modules are known to do sometimes, because of misuse of MODALIAS).

    It's not really a crash: the system just stops. No sysrq, no
nothing, the system is dead. I'll try to isolate the problem if I can,
and will use the on-demand loading by now. I'm not going to use my "hal"
right now because I don't need it, even to create mount points.

    Thanks a lot for all your help, Kay :)))

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736 | http://www.dervishd.net
It's my PC and I'll cry if I want to... RAmen!

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel