From: Adam Nielsen <a.nielsen@shikadi.net>
To: LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: UML broken - runaway loop modprobe binfmt-464c
Date: Mon, 15 Feb 2010 16:47:49 +1000 [thread overview]
Message-ID: <4B78EE15.9020407@shikadi.net> (raw)
Hi all,
I've been forced to upgrade an old machine running a couple of UML VMs, but I
can't for the life of me figure out how to make them work on the new machine.
I've compiled the latest kernel from kernel.org with ARCH=um and when I run it
says this a few times and then stops:
request_module: runaway loop modprobe binfmt-464c
From Google it appears the cause of this is when you run a 64-bit system with
a 32-bit kernel, but I'm running a 64-bit kernel with a 32-bit system. I
vaguely recall something about IA32 emulation in the normal kernel build, but
I can't see anything like that in the UML kernel config.
Does anyone know what might fix this?
Many thanks,
Adam.
(please CC)
next reply other threads:[~2010-02-15 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 6:47 Adam Nielsen [this message]
2010-02-15 11:37 ` UML broken - runaway loop modprobe binfmt-464c Américo Wang
2010-02-15 16:11 ` Jeff Dike
2010-02-21 3:00 ` Adam Nielsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B78EE15.9020407@shikadi.net \
--to=a.nielsen@shikadi.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox