Pozsar Balazs wrote: > > Well, that's really wierd, It Should Work(tm) :) > Did you apply both patches (Rusty's + mine), or only the latter? >
I hadn't seen Rusty's patch on Debian's bts, until you mentioned it. I have applied both patches now, and rebooted twice: By now it worked. But that's what I thought before. > Could you send me debug output please? The first time I met the problem, > I used a modprobe wrapper which dumped /proc/modules and modprobe > stdout/stderr to a temp file. > If the problem comes back then I will do. > I would like to also mention, that my patch leaves a very little time > window open, but that's only a problem if module unloading is also > happening: after parsing /proc/modules, but before actually loading the > module, it is possible that an rmmod unloads (starts to unload) a > dependant module. But this does not affect booting. > > Are there several modprobe's running in parallel? Or does modprobe return SUCCESS while the kernel is still busy "making the module usable somehow"? Regards Harri
modprobe.patch.gz
Description: Unix tar archive
signature.asc
Description: OpenPGP digital signature
