From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@kernel-bugs.osdl.org>,
linux@solnet.ch
Subject: Re: [Bugme-new] [Bug 8677] New: booting with initrd fails: request_module: runaway loop modprobe binfmt-0000
Date: Tue, 26 Jun 2007 14:12:16 +0300 [thread overview]
Message-ID: <200706261412.16601.caglar@pardus.org.tr> (raw)
In-Reply-To: <20070626020256.4a03d6b2.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
26 Haz 2007 Sal tarihinde, Andrew Morton şunları yazmıştı:
> > I can't boot all 2.6.22_rc* kernels with an initrd. When booting I get
> > the following message about 6 times:
> >
> > request_module: runaway loop modprobe binfmt-0000
> >
> > If I disable the initrd, booting works without problems.
>
> I seem to recall having seen reports of this before. Does anyone recall
> the reason for it?
I've hit that before, first was the misc. compiliation issue which solved by
recompilation and other was related to "Load Custom Dsdt Table" [1] patch
which seems the case here (boots without initramfs/initrd) if that kernel has
that kind of out-of-tree patch.
[1] http://gaugusch.at/kernel.shtml
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-06-26 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8677-10286@http.bugzilla.kernel.org/>
2007-06-26 9:02 ` [Bugme-new] [Bug 8677] New: booting with initrd fails: request_module: runaway loop modprobe binfmt-0000 Andrew Morton
2007-06-26 11:12 ` S.Çağlar Onur [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=200706261412.16601.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@kernel-bugs.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@solnet.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.