All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Angermeier <Josef.Angermeier@informatik.stud.uni-erlangen.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] hang after "Transferring Control to Linux": bd_info difference ?
Date: Mon, 20 Feb 2006 14:02:59 +0100	[thread overview]
Message-ID: <20060220130259.GA7009@false> (raw)
In-Reply-To: <20060220124123.DDBB9353C11@atlas.denx.de>

Hello Wolfgang

> > Just wanted to be sure, that its no bd_info-differ-bug. But you are
> > probably right. Please be so kind and tell me, if the
> > monitor-func-pointer difference in the two bd_info struct is of any
> > concern.

> No. If this is the only difference, then it's just  an  absolete  and
> unsued  field  at  the end of the structure. But why don't you simply
> remove it???

Ok, good to know!

> > Analyzing the kernel log revealed the following: Most of the time there
> > is nothing in the log, sometimes the kernel version etc. can be found
> > and a "Ooops: kern" and once i also found a "Machine ch" output. 

> > Any hint what could go wrong ?

> With a likelyhood of 99.93% your SDRAM initialization is broken.

> [I think I should program a function key to automatically insert this
> text. ;-) ]

Oooh no, i hoped i would never have to get familiar with SDRAM
initialization, of which i have no clue. But i feared that because "mtest"
failes with:

=> mtest
Pattern 00000000  Writing...

But how is this possible ? - u-boot gets successfully executed in SDRAM!

Thanks for your guess, at least i know in which direction to go for
bug hunting.

> Best regards,

> Wolfgang Denk

Schoene Gruesse,
Josef

  reply	other threads:[~2006-02-20 13:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20  9:58 [U-Boot-Users] hang after "Transferring Control to Linux": bd_info difference ? Josef Angermeier
2006-02-20 10:35 ` Wolfgang Denk
2006-02-20 12:18   ` Josef Angermeier
2006-02-20 12:41     ` Wolfgang Denk
2006-02-20 13:02       ` Josef Angermeier [this message]
2006-02-20 13:45         ` 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=20060220130259.GA7009@false \
    --to=josef.angermeier@informatik.stud.uni-erlangen.de \
    --cc=u-boot@lists.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.