Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Satoshi Matsushita <matusita@k-micro.com>
To: buildroot@busybox.net
Subject: [Buildroot] modprobe doesn't work with MIPS codesourcery
Date: Wed, 05 Oct 2011 10:16:17 +0900	[thread overview]
Message-ID: <4E8BAFE1.1030503@k-micro.com> (raw)

Hello,

I'd like to use buildroot-2011.05 with Linux2.6.28
on the MIPS CPU system.

As for the toolchain, I planed to use "CodeSourcery
MIPS 2011.03". So I changed options as follows from
default settings:
Target Architecture (mipsel)
Target Architecture Variant (mips 32r2)
Toolchain type (External toolchain)
Toolchain (CodeSourcery MIPS 2011.03)
Filesystem images (jffs2 root filesystem)

As the result, the build process itself has been
finished successfully. But when the Linux boot with
this image, the following messages was displayed and
boot process was failed.

------------------------------------------------------
VFS: Mounted root (jffs2 filesystem) readonly.
Freeing prom memory: 956k freed
Freeing unused kernel memory: 136k freed
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
------------------------------------------------------

If I could have any suggestions to solve this problem,
it would very helpful for me.

BTW, when I used crosstool-ng as toolchain, Linux booted
without problem.

Best Regards,
Satoshi Matsushita

                 reply	other threads:[~2011-10-05  1:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4E8BAFE1.1030503@k-micro.com \
    --to=matusita@k-micro.com \
    --cc=buildroot@busybox.net \
    /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