From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josef Angermeier Date: Mon, 20 Feb 2006 14:02:59 +0100 Subject: [U-Boot-Users] hang after "Transferring Control to Linux": bd_info difference ? In-Reply-To: <20060220124123.DDBB9353C11@atlas.denx.de> References: <20060220121837.GC31756@false> <20060220124123.DDBB9353C11@atlas.denx.de> Message-ID: <20060220130259.GA7009@false> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.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