From: Kay Sievers <kay.sievers@vrfy.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.28.[45] boot failure: request_module: runaway loop modprobe binfmt-464c
Date: Tue, 17 Feb 2009 11:01:51 +0100 [thread overview]
Message-ID: <ac3eb2510902170201t696df348ka167c12ad5819494@mail.gmail.com> (raw)
In-Reply-To: <499A7EE2.50108@imap.cc>
On Tue, Feb 17, 2009 at 10:09, Tilman Schmidt <tilman@imap.cc> wrote:
> My workhorse machine (Pentium D 940, Intel DG965QF board,
> mirrored SATA disks), which runs fine with kernel:
> ts@xenon:~> uname -a
> Linux xenon 2.6.28.3-testing #1 SMP PREEMPT Mon Feb 2 23:32:07 CET 2009 i686 i686 i386 GNU/Linux
> fails to come up with an identically configured 2.6.28.4 or 2.6.28.5
> kernel. The boot process hangs at about the time the root
> file system is mounted, the last messages being (scribbled
> down manually on a piece of paper, please make allowances):
>
> /dev/RAID/root: recovering journal ... clean
> fsck successful. Mounting root device r/w
> Mounting root /dev/RAID/root
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on dm-0, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
> request_module: runaway loop modprobe binfmt-464c
Are you sure, that you don't have a 32/64 bit mismatch between the
kernel and userspace? Like you miss 32-bit emulation in a 64-bit
kernel, or your modprobe is 64-bit and you are trying to run it on a
32-bit kernel?
Kay
next prev parent reply other threads:[~2009-02-17 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 9:09 Tilman Schmidt
2009-02-17 10:01 ` Kay Sievers [this message]
2009-02-17 10:45 ` Tilman Schmidt
2009-02-18 8:37 ` 2.6.28.[45] boot failure: request_module: runaway loop modprobe binfmt-464c [SOLVED] Tilman Schmidt
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=ac3eb2510902170201t696df348ka167c12ad5819494@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/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
all inboxes | Powered by JetHome®