From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: schardt <g.schardt@fz-juelich.de>
Cc: Linux PPC Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: Re: Init hangs on Xilinx4
Date: Thu, 29 Nov 2007 07:41:17 -0500 [thread overview]
Message-ID: <474EB36D.1080408@dlasys.net> (raw)
In-Reply-To: <474D8839.6020609@fz-juelich.de>
I had a similar problem. In my instance it turned out that I was
inadvertently using the physical address of my uart as the output address.
This worked during boot becasue there was a 1:1 physical-logical entry
stuffed into the MMU. But since Linux did nto know about it, as soon as
the VM system decided to use that TLB entry IO died - right in the
middle of a string.
While it is unlikely you made exactly the same mistake. One area you can
check is memory.
What is your output device ?
schardt wrote:
> Hi all,
>
> i still have some problems booting linux from flash and don't know how
> to debug.
>
> i have a xilinx4-ppc with 64MB Ram and 4MB Flash, U-Boot works fine,
> kernel is booting, but my little hello world program runs as init, died
> after printing "He" (intead of "Hello World"). i tried initramfs with
> build in cpio-image and jffs2 rootfs
>
> Is there a log-buffer to look at ?
> Should i try another compiler version ? (btw. booting from systemace
> works with the version i use).
>
> ---------------------------
> famous last words :
>
> [ 50.476641] VFS: Mounted root (jffs2 filesystem).
> [ 50.533581] Freeing unused kernel memory: 68k init
> He
> ---------------------------
>
>
> regards
> Georg
>
>
>
> -------------------------------------------------------------------
> -------------------------------------------------------------------
> Forschungszentrum Jülich GmbH
> 52425 Jülich
>
> Sitz der Gesellschaft: Jülich
> Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498
> Vorsitzende des Aufsichtsrats: MinDirig'in Bärbel Brumme-Bothe
> Geschäftsführung: Prof. Dr. Achim Bachem (Vorsitzender),
> Dr. Ulrich Krafft (stellv. Vorsitzender), Dr. Sebastian M. Schmidt
> -------------------------------------------------------------------
> -------------------------------------------------------------------
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
"Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction."
Albert Einstein
next prev parent reply other threads:[~2007-11-29 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 15:24 Init hangs on Xilinx4 schardt
2007-11-29 12:41 ` David H. Lynch Jr. [this message]
2007-11-29 12:53 ` schardt
[not found] ` <474ECB50.90303@dlasys.net>
[not found] ` <474ED262.5010408@fz-juelich.de>
2007-11-30 9:27 ` David H. Lynch Jr.
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=474EB36D.1080408@dlasys.net \
--to=dhlii@dlasys.net \
--cc=g.schardt@fz-juelich.de \
--cc=linuxppc-embedded@ozlabs.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).