public inbox for u-boot@lists.denx.de
 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 13:18:37 +0100	[thread overview]
Message-ID: <20060220121837.GC31756@false> (raw)
In-Reply-To: <20060220103522.B2EC7353C11@atlas.denx.de>

Rehi

Thanks for your quick reply.

> > What else could i tryout before analyzing kernel log buffer and debugging the
> > kernel ?

> Why do you want to do other things  first?  Why  not  just  take  the
> logical next step?

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.

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 ?

0009adb4: 00000000 00000000 00000000 00000000    ................
0009adc4: 00000000 00000000 00000000 00000000    ................
0009add4: 00000000 00000000 00000000 00000000    ................


0009adb4: 3c343e4c 696e7578 20766572 73696f6e    <4>Linux version
0009adc4: 20322e34 2e323520 28616e67 65726d65     2.4.25 (angerme
0009add4: 69657240 636f6465 7369676e 34332920    ier at codesign43) 
0009ade4: 28676363 2d566572 73696f6e 20332e33    (gcc-Version 3.3
0009adf4: 2e332028 44454e58 20454c44 4b20332e    .3 (DENX ELDK 3.
0009ae04: 312e3120 332e332e 332d3130 29292023    1.1 3.3.3-10)) #
0009ae14: 35204d6f 6e204665 62203230 2031313a    5 Mon Feb 20 11:
0009ae24: 30323a35 32204345 54203230 30360a3c    02:52 CET 2006.<
0009ae34: 343e4f6f 70733a20 6b65726e 00000000    4>Oops: kern....
0009ae44: 00000000 00000000 00000000 00000000    ................
0009ae54: 00000000 00000000 00000000 00000000    ................


0009adb4: 3c343e4c 696e7578 20766572 73696f6e    <4>Linux version
0009adc4: 20322e34 2e323520 28616e67 65726d65     2.4.25 (angerme
0009add4: 69657240 636f6465 7369676e 34332920    ier at codesign43) 
0009ade4: 28676363 2d566572 73696f6e 20332e33    (gcc-Version 3.3
0009adf4: 2e332028 44454e58 20454c44 4b20332e    .3 (DENX ELDK 3.
0009ae04: 312e3120 332e332e 332d3130 29292023    1.1 3.3.3-10)) #
0009ae14: 35204d6f 6e204665 62203230 2031313a    5 Mon Feb 20 11:
0009ae24: 30323a35 32204345 54203230 30360a3c    02:52 CET 2006.<
0009ae34: 343e4d61 6368696e 65206368 00000000    4>Machine ch....
0009ae44: 00000000 00000000 00000000 00000000    ................

  reply	other threads:[~2006-02-20 12:18 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 [this message]
2006-02-20 12:41     ` Wolfgang Denk
2006-02-20 13:02       ` Josef Angermeier
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=20060220121837.GC31756@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox