From: Wolfgang Denk <wd@denx.de>
To: Marco Schramel <Schramel.Linux@go.bartec.de>
Cc: "PPC_LINUX" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Init hangs
Date: Fri, 06 Aug 2004 10:11:46 +0200 [thread overview]
Message-ID: <20040806081151.B77FCC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 06 Aug 2004 08:26:21 +0200." <200408060826.21301.Schramel.Linux@go.bartec.de>
In message <200408060826.21301.Schramel.Linux@go.bartec.de> you wrote:
>
> Searching the outputfile of ethereal tells me that the last working nfs LOOKUP call is the libc-2.3.1 call. After this and a lot of Read Call, Read Reply transfers the Target doesn't answer the host.
> (ARP "who has targetip-address?"). Before this, the ld.so.preload LOOKUP call fails.
> (History: dev, console, sbin, init, lib, ld.so.1, ld-2.3.1.so, etc, ld.so.preload (fails), ld.so.cache, libc.so.6, libc-2.3.1, than it crashes). Is the ld.so.preload necessary?
No, it's not necesary. It's normal that this lookup fails.
Looks as if your init is crashing.
Try running a (statically linked) shell instead (by passing some
init=/bin/sh" option on the boot command line).
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
It is easier to write an incorrect program than understand a correct
one.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-06 8:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 9:54 Init hangs Marco Schramel
2004-08-05 10:33 ` Wolfgang Denk
2004-08-05 15:28 ` Marco Schramel
2004-08-05 17:48 ` Wolfgang Denk
2004-08-06 6:26 ` Marco Schramel
2004-08-06 8:11 ` Wolfgang Denk [this message]
2004-08-06 11:22 ` Ralph Siemsen
2004-08-06 12:38 ` Dan Malek
2004-08-06 13:14 ` Robert P. J. Day
2004-08-06 13:49 ` Dan Malek
2004-08-06 12:46 ` Wolfgang Denk
2004-08-06 13:12 ` Ralph Siemsen
2004-08-06 13:44 ` Dan Malek
2004-08-06 14:36 ` Wolfgang Denk
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=20040806081151.B77FCC109F@atlas.denx.de \
--to=wd@denx.de \
--cc=Schramel.Linux@go.bartec.de \
--cc=linuxppc-embedded@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).