[lkml]   [2002]   [Apr]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.5.7 and runaway modprobe loop?
On Wed, 10 Apr 2002 11:00:49 -0700 (PDT), 
"Randy.Dunlap" <> wrote:
>| On Tue, 9 Apr 2002 09:17:08 -0700 (PDT),
>| "Randy.Dunlap" <> 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
>| >
>| >If I build/boot it with 4 GB support, it boots fine.
>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

Interesting. The binfmt-0000 implies that search_binary_handler() is
reading garbage for the executable. It tries to load a handler for
binfmt-0000 which tries to execute modprobe which hits the same bug.
At a guess, the executable binary is not being mapped correctly with
64GB support.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

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