|
request_module: runaway loop modprobe binfmt-464c
Hello,
I built bzImage from 2.6.30.1, and ran it on a Pentium-M CPU. The file system is NFS. After few seconds I saw the following messages:
VFS: Mounted root (nfs filesystem) readonly on device 0:16
async_waiting @ 1
async_continuing @ 1 after 0 usec
Freeing unused kernel memory: 348k freed
Write protecting the kernel text: 4204k
Write protecting the kernel read-only data: 2084k
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
khelper used greatest stack depth: 5672 bytes left
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
khelper used greatest stack depth: 4240 bytes left
khelper used greatest stack depth: 5400 bytes left
khelper used greatest stack depth: 5356 bytes left
khelper used greatest stack depth: 5296 bytes left
khelper used greatest stack depth: 5292 bytes left
khelper used greatest stack depth: 5220 bytes left
khelper used greatest stack depth: 5216 bytes left
khelper used greatest stack depth: 5152 bytes left
According to google the cause is a 32bits machine running a file system on a 64bits machine. Is it true ?
The file system is located on a server running RHEL 64 bits. The target is Pentium-M. But all the file system was created using an i686 toolchain. Not the one supplied with RHEL.
It seems that the target saw the file system. I have no kernel panic.
But I got the above messages.
The file system is busybox. I have nothing under /etc.
Upon boot completion I want linux to run a simple script.
This script will be in /etc/rc.d/rc.sysinit
The bzImage is located on a USB disk not on the main disk (hda). This is where grub was installed.
I didn't do make modules_install yet. There is no module=xxx in grub's menu.lst. Can this cause the problem ?
Thanks.
|
