On Sun, Nov 06, 2005 at 03:50:05PM +0100, Harald Dunkel wrote:
> Harald Dunkel wrote:
> >
> > For testing I have added it to Debian's
> > module-init-tools 3.2-pre9. Works for me.
> >
>
> No, it doesn't. After the 3rd reboot the
> problem was back.
Well, that's really wierd, It Should Work(tm) :)
Did you apply both patches (Rusty's + mine), or only the latter?
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.
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.
On Sun, Nov 06, 2005 at 03:50:05PM +0100, Harald Dunkel wrote:
> Harald Dunkel wrote:
> >
> > For testing I have added it to Debian's
> > module-init-tools 3.2-pre9. Works for me.
> >
>
> No, it doesn't. After the 3rd reboot the
> problem was back.
Well, that's really wierd, It Should Work(tm) :)
Did you apply both patches (Rusty's + mine), or only the latter?
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.
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.
--
pozsy