public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.28.[45] boot failure: request_module: runaway loop modprobe binfmt-464c [SOLVED]
Date: Wed, 18 Feb 2009 09:37:41 +0100	[thread overview]
Message-ID: <499BC8D5.9030005@imap.cc> (raw)
In-Reply-To: <ac3eb2510902170201t696df348ka167c12ad5819494@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

On Tue, 17 Feb 2009 11:01:51 +0100, Kay Sievers wrote:

>> 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?

Aaaugh, never mind my previous reply, you were right on spot!
"make install" had picked up the wrong root partition when it
created the GRUB menu entry for the new kernel, so it actually
tried to boot an experimental 64 bit installation on a different
disk with my newly built 32 bit kernels. That'll teach me not to
choose too similar partition names.

Now to find out how "make install" creates its GRUB menu entries
and why it suddenly started to go wrong ...

Thanks,
Tilman

-- 
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

      parent reply	other threads:[~2009-02-18  8:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17  9:09 2.6.28.[45] boot failure: request_module: runaway loop modprobe binfmt-464c Tilman Schmidt
2009-02-17 10:01 ` Kay Sievers
2009-02-17 10:45   ` Tilman Schmidt
2009-02-18  8:37   ` Tilman Schmidt [this message]

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=499BC8D5.9030005@imap.cc \
    --to=tilman@imap.cc \
    --cc=kay.sievers@vrfy.org \
    --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