From: Martin Costabel <costabel@wanadoo.fr>
To: linuxppc-dev@lists.linuxppc.org
Subject: 2.4.0-test4 doesn't boot
Date: Fri, 14 Jul 2000 16:50:03 +0200 [thread overview]
Message-ID: <396F289B.7D5705EF@wanadoo.fr> (raw)
Hi,
booting rsync/bitkeeper kernel 2.4.0-test4 gets me into an infinite
loop: At the end of the kernel boot proces, right after "freeing unused
kernel memory", I get a couple of
kmod: runaway modprobe loop assumed and stopped
and then a never ending loop of
kmod: failed to exec /sbin/modprobe -s -k binfmt-4c46, errno=8
Has anyone else seen this or knows what it means?
I have spent many hours changing all kinds of config options, modutils
version, kernel arguments, but I am giving up now. 2.4.0-test3 from 2
weeks ago worked OK.
The number 4c46 exists as PCI_DEVICE_ID_ATI_RAGE128_LF in
include/linux/pci_ids.h, but whether I enable aty128 support or not
makes no difference (I don't have an ATI card).
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-07-14 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-14 14:50 Martin Costabel [this message]
2000-07-15 21:03 ` 2.4.0-test4 doesn't boot (solved) Martin Costabel
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=396F289B.7D5705EF@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).