From: Daniel Wu <Daniel.Wu@alcatel.com.au>
To: Dan Malek <dan@netx4.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Using zImage.initrd
Date: Tue, 13 Jun 2000 09:09:40 +1000 [thread overview]
Message-ID: <00Jun13.090942est.115229@border.alcanet.com.au> (raw)
In-Reply-To: 394110AB.1B25BBF4@embeddededge.com
Dan Malek wrote:
>
> > > What is the rest of this backtrace?
> > >
> >
> > C00FF71B buf
> > C00B8474 extract_entropy
> > C00B8648 get random_bytes
> > C00FA2B4 init_elf_binfmt
> > C00F7774 start_kernel
> > C000221C start_here
>
> Oh wow.....If this is really where the code is running, something
> very fundamental is broken in the hardware because there should have
> been lots more printed out on the console. You are still running in
> very generic kernel functions that work on all architectures.
>
But this is only a problem if I do "make zImage.initrd" and not "make zImage". The
latter actually passes this point without error, it fails when it can't get the root
image from the network, when is expected since I am not planning to boot using that
method.
Anyway, I will give your suggestions a try, but my feeling is that they won't make
much difference. BTW, the hardware is not "new" and it works fine with another OS and
applications. I ported the UPM setup from the existing code so I'm pretty sure they
are ok.
Daniel
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-06-12 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 22:38 Using zImage.initrd Daniel Wu
2000-06-09 2:40 ` Murray Jensen
2000-06-09 2:52 ` Dan Malek
2000-06-09 3:59 ` Murray Jensen
2000-06-09 3:15 ` Dan Malek
2000-06-09 8:51 ` Daniel Wu
2000-06-09 15:43 ` Dan Malek
2000-06-12 23:09 ` Daniel Wu [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=00Jun13.090942est.115229@border.alcanet.com.au \
--to=daniel.wu@alcatel.com.au \
--cc=dan@netx4.com \
--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 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.