lkml.org 
[lkml]   [2002]   [Apr]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.5.7 and runaway modprobe loop?
On Wed, 10 Apr 2002, Keith Owens wrote:

| On Tue, 9 Apr 2002 09:17:08 -0700 (PDT),
| "Randy.Dunlap" <rddunlap@osdl.org> wrote:
| >If I build/boot 2.5.7 with 64 GB support (with or without
| >high_pte), I get:
| >
| >Freeing unused kernel memory: 448k freed
| >INIT: version 2.78 booting
| >kmod: runaway modprobe loop assumed and stopped
| >kmod: runaway modprobe loop assumed and stopped
| >kmod: runaway modprobe loop assumed and stopped
| >kmod: runaway modprobe loop assumed and stopped
| >kmod: runaway modprobe loop assumed and stopped
| >
| >If I build/boot it with 4 GB support, it boots fine.
| >
| >Fixes, suggestion?
|
| If /var/log/ksymoops exists and is mounted rw when that message is
| issued, look at 20020409.log to see what modprobe is asking for.
| Otherwise add a printk to kernel/kmod::request_module() to print
| module_name. In either case, work out why it is going recursive.

Thanks for replying, Keith.

I added module_name to the runaway message (OK ?) and its
answer is binfmt-0000.

I also moved from 2.5.7 to 2.5.8-pre2 and don't have this
problem.

--
~Randy

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:25    [W:0.038 / U:3.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site