Hi all :)) I'm CC'ing this message to LKML because I don't know if this is some weird (and known) interaction between modules.
I'm using vanilla 2.6.19.5. I was having a problem using this rule: ACTION=="add", ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe $env{MODALIAS}" and I finally found the module that was hanging the system: something with alias "serio:alotofnumbersanddigits". I've replaced the rule above by this one: ACTION=="add", ENV{MODALIAS}=="?*", ENV{MODALIAS}!="serio*", RUN+="/sbin/modprobe $env{MODALIAS}" But the question is: why?. And: who is causing the request?. As far as I know, the only serio things I have are my keyboard and my PS/2 mouse connector (which *doesn't* have a mouse connected), and of course my keyboard support is not a module (although psaux is). Anyone has any idea about what the problem may be? The aliases for the modules when the event is handled by udev are those: serio:ty06pr00id00ex00 serio:ty01pr00id00ex00 If I filter out THOSE TWO aliases and only those, the system doesn't hang. Otherwise, the system appears dead, not even sysrq works (I can't check ping because right now there aren't other machines in the network, so probably the machine is not *that* dead, and only the keyboard has dead :??). Thanks a lot in advance. If anyone needs more information or tests, just ask. Kay, I followed your advice, booted without udev and make some tests until I found the culprit. Hard, but fruitful ;)) Thanks :) 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! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/