Messages in this thread | | | Date | Mon, 8 Jan 2007 08:49:22 +1030 | From | "Tom Lanyon" <> | Subject | Re: runaway loop modprobe binfmt-0000 |
| |
On 1/6/07, Andrew Morton <akpm@osdl.org> wrote: > On Sat, 6 Jan 2007 09:43:14 +1030 > "Tom Lanyon" <tomlanyon@gmail.com> wrote: > > > How can I discover > > what is trying to load binfmt-0000 and why is it looping? > > Start with this, I guess.. > > --- a/kernel/kmod.c~a > +++ a/kernel/kmod.c > @@ -98,10 +98,12 @@ int request_module(const char *fmt, ...) > atomic_inc(&kmod_concurrent); > if (atomic_read(&kmod_concurrent) > max_modprobes) { > /* We may be blaming an innocent here, but unlikely */ > - if (kmod_loop_msg++ < 5) > + if (kmod_loop_msg++ < 5) { > printk(KERN_ERR > "request_module: runaway loop modprobe %s\n", > module_name); > + dump_stack(); > + } > atomic_dec(&kmod_concurrent); > return -ENOMEM; > } > _ > >
Thanks for the reply, Andrew.
How interesting... added that to kmod.c, rebuilt without change to config, reboot.... machine booted perfectly!
I'm going to leave it for now, but I'll leave the dump_stack() call in there in case further issues arise.
Regards
-- Tom Lanyon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |