public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista•com>
To: Sam Song <samlinuxppc@yahoo•com.cn>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: 824x Sandpoint with 2.6.x
Date: Wed, 20 Apr 2005 10:46:58 -0700	[thread overview]
Message-ID: <42669592.6080602@mvista.com> (raw)
In-Reply-To: <20050420135401.29160.qmail@web15808.mail.cnb.yahoo.com>

Sam Song wrote:

>"Mark A. Greer" <mgreer@mvista•com> wrote:
>  
>
>>>Kernel command line:
>>>console=uart,mmio,0xfdfce500,115200n8
>>>console=ttyS0,115200
>>>root=/dev/ram rw ramdisk_size=200000
>>>ip=192.168.0.3:192.168..2:::sandpoint:et
>>>h0:off panic=1
>>>
>>>      
>>>
>><snip>
>>
>>Get rid of the
>>"console=uart,mmio,0xfdfce500,115200n8" part of the
>>cmdline and see what happens (keep the
>>"console=ttyS0,115200" part).
>>    
>>
>
>If so, kernel will hang after loading the kernel......
>

Okay, obviously something is wrong. Adding another console line isn't
fixing anything, its just allowing you to flounder on a little further.
IMHO, adding another console line isn't going to help and will only add
confusion.

>I cannot see any active info.Is early console output 
>message not enough to find out something useful? 
>  
>

Sure it does. You have to enable it, then add some progress lines to
help narrow down where you're panic'ing/hanging. You can even use the
progress facility to dump the __log_buf.

I'm taking your unwillingness to use a jtag/cops debugger as indication
that you don't have such a tool!?!?

Mark

  reply	other threads:[~2005-04-20 17:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 13:54 824x Sandpoint with 2.6.x Sam Song
2005-04-20 17:46 ` Mark A. Greer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-22  2:21 Sam Song
2005-04-21  2:40 Sam Song
2005-04-21 19:57 ` Mark A. Greer
2005-04-20 13:59 Sam Song
2005-04-19 13:52 Sam Song
2005-04-19 18:27 ` Mark A. Greer
2005-04-15  2:24 Sam Song
2005-04-18 19:54 ` Mark A. Greer
2005-04-18 19:55   ` Mark A. Greer
2005-04-14  5:01 Sam Song
2005-04-12  4:10 Sam Song
2005-04-13 16:48 ` Mark A. Greer
2005-04-11  9:28 Sam Song
2005-04-11 18:46 ` Mark A. Greer

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=42669592.6080602@mvista.com \
    --to=mgreer@mvista$(echo .)com \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    --cc=samlinuxppc@yahoo$(echo .)com.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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