Messages in this thread | | | From | Keith Owens <> | Subject | Re: 2.5.7 and runaway modprobe loop? | Date | Thu, 11 Apr 2002 09:27:51 +1000 |
| |
On Wed, 10 Apr 2002 11:00:49 -0700 (PDT), "Randy.Dunlap" <rddunlap@osdl.org> 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 >| > >| >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 >problem.
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 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/
| |