request_module: runaway loop modprobe binfmt-464c Kernel panic - not syncing: No init found Pid: 1, comm: swapper/0 Not tainted
This is usually caused by a mismatch in architecture and happens frequently in development environments.
Here is a example of what caused this issue:
Your binaries are based on one architecture
Your kernel was compiled with another architecture.
Why does this happe........
2.6.35.2 stuck on the following:
msgmni has been set to 1466
request_module: run away loop modprobe char-major-5-1
I don't know the fix for it, but it is an old bug that has reappeared.........