From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by ozlabs.org (Postfix) with ESMTP id CE5DEDDF2D for ; Wed, 17 Oct 2007 05:37:59 +1000 (EST) Received: by rv-out-0910.google.com with SMTP id c27so1388069rvf for ; Tue, 16 Oct 2007 12:37:59 -0700 (PDT) Message-ID: Date: Tue, 16 Oct 2007 13:37:58 -0600 From: "Grant Likely" Sender: glikely@secretlab.ca To: aauer1 Subject: Re: Linux booting problem on Xilinx ppc In-Reply-To: <13239003.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <12694083.post@talk.nabble.com> <12696686.post@talk.nabble.com> <13219154.post@talk.nabble.com> <000901c81006$7303b490$bb3ca688@LGE.NET> <13239003.post@talk.nabble.com> Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 10/16/07, aauer1 wrote: > > The on-chip memories are disabled. Only the BRAM is enabled. Now, we also use > the ELDK 4.1 from Denx and the included cross compiler. The result is the > same... the Kernel stops at "Now booting the kernel". Now, we also have an > USB JTAG cable. So, we can debug the memory. > Probably, anyone has another idea. There are two common reasons for this behaviour: 1. kernel crashes before the console is configured 2. the console is not configured correctly. In both cases; finding a way to look at __log_buf is the fastest way to figure out what is going on. Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. grant.likely@secretlab.ca (403) 399-0195