(In reply to Cristian Rodr�guez from comment #8) > > This is what the kernel people had told us > > Of course they told you that, to avoid having to fix the real problem which is > in their side :-) Sorry, but this is b*sh*t ;) In fact there is more than one problem realated to killing one or more running modprobs. > > due to the fact that a killed > > worker job loading a module is not the solution on large workstations or > > mainframes where it could be that scanning and initializing hardware takes > > more time than the hard coded timeout. And ... which is the real problem > > ... killing this can cause huge trouble. Compare with bsc#889297 > > "You are not authorized to access bug #889297" *sigh*.. Now you should be able to read it, therefore read it.