Johannes Rosenberger <gen...@jorsn.eu> writes: > I found something interesting: >> request_module: runaway loop modprobe binfmt-464c >> Short answer: If you are getting this error right after linux kernel >> initialization, you are likely booting a 32-bit kernel with a 64-bit OS. >> >> Long answer: If you boot a 32-bit kernel with a 64-bit OS, when the >> kernel tries to start /sbin/init (a 64-bit binary), it won't recognize >> the binary format, and it'll try to load the binfmt-464c kernel >> module, which is ELF support. (ELF support is generally compiled into >> the kernel, not built as a module, by the way.) >> >> The reason for the loop error is that the kernel is trying to invoke >> modprobe to load the module, and modprobe is itself an ELF binary, >> resulting in a recursion loop...
Just a bit ago I had one of those slap myself in the head moments. Just realized that the host I took the .config to do oldconfig from is a 32 bit host. Now, I did set the switch when menuconfig rolled around for a 64 bit kernel but still the whole thing is based on an a .config from a 32 bit host running a 32 bit kernel. So no telling what all might get jimmied up in that mess. I'd already trashed all disks from the test vm and am starting from scratch again but this time I won't get tricky with the .config file. Had I not done so (trashed the disks from my first go around), I probably could have just reconfigged the kernel from scratch and been ok...
