All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Schramel <Schramel.Linux@go.bartec.de>
To: Wolfgang Denk <wd@denx.de>
Cc: "PPC_LINUX" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Init hangs
Date: Fri, 6 Aug 2004 08:26:21 +0200	[thread overview]
Message-ID: <200408060826.21301.Schramel.Linux@go.bartec.de> (raw)
In-Reply-To: <20040805174857.A42F4C109F@atlas.denx.de>


Dear Wolfgang,

> The fragmentation is OK, but this is not what you're looking for.

Ok.

> You should see a couple of LOOKUP calls, probably in the sequence  of
> /dev, console, sbin, init, lib, ld.so.1, and so on. Find out what the
> last succesful lookup call was, and what happens after this.

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?


Best regards
Marco


--
---------
Marco Schramel
R&D
Bartec GmbH
Schulstr. 30
94239 Gotteszell, Germany
www.bartec.de
Marco.Schramel@go.bartec.de
Phone:  +49 (0)9929/301332
Fax:    +49 (0)9929/301112

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-08-06  6:26 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 [this message]
2004-08-06  8:11         ` Wolfgang Denk
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=200408060826.21301.Schramel.Linux@go.bartec.de \
    --to=schramel.linux@go.bartec.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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.