From: Brian Waite <waite@skycomputers.com>
To: Roland Dreier <roland@topspin.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: NFS root woes: No init found
Date: Wed, 4 Dec 2002 17:52:24 -0500 [thread overview]
Message-ID: <200212041752.24742.waite@skycomputers.com> (raw)
In-Reply-To: <523cpdbds5.fsf@topspin.com>
Oh I like the thought! I too have had good luch wit the eval board, but now
our custom is biting me. Lets have a looksie at the data.
Thanks for the idea.
Brian
> This is just a wild guess, but maybe there is a data corruption
> problem somewhere. (Maybe cache-coherency? I know the 74xx/gt64260
> is a cache-coherent platform but maybe the snooping isn't wired up or
> set up correctly??)
>
> You could try printing out the data the kernel thinks it read for init
> and compare it with what's actually on the disk. (It seems likely it
> will be different, since the kernel can't tell that it's an ELF file)
>
> Just as a data point, we have had good success running Linux with NFS
> root on both the Galileo Discovery eval board and our own custom board
> (both used the Galileo internal ethernet).
>
> Best,
> Roland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-04 22:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 21:35 NFS root woes: No init found Brian Waite
2002-12-04 21:48 ` Dan Malek
2002-12-04 22:11 ` Brian Waite
2002-12-04 22:20 ` Wolfgang Grandegger
2002-12-04 22:30 ` Brian Waite
2002-12-04 22:47 ` Jerry Van Baren
2002-12-04 23:03 ` Brian Waite
2002-12-04 22:49 ` Roland Dreier
2002-12-04 22:52 ` Brian Waite [this message]
2002-12-04 22:27 ` Roland Dreier
2002-12-04 22:36 ` Brian Waite
2002-12-05 8:50 ` Dan Vatca
2002-12-05 15:20 ` Brian Waite
2002-12-05 15:58 ` Allen Curtis
-- strict thread matches above, loose matches on Subject: below --
2002-12-07 1:36 Pagnotta, Chris
2002-12-07 11:02 ` 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=200212041752.24742.waite@skycomputers.com \
--to=waite@skycomputers.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=roland@topspin.com \
/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.