linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Xianghua Xiao <xiaoxianghua@gmail.com>
To: "Dunda, Matthias" <Matthias.Dunda@de.thalesgroup.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Kernel errors at very early stage
Date: Wed, 5 May 2010 13:36:38 -0500	[thread overview]
Message-ID: <q2ke6bf505b1005051136mceda63d6re9295bd7b1f812b3@mail.gmail.com> (raw)
In-Reply-To: <569685F045B85741820D0265E0D2999D019CFE8B@tddhh01.hh.thales-naval.de>

On Wed, May 5, 2010 at 3:27 AM, Dunda, Matthias
<Matthias.Dunda@de.thalesgroup.com> wrote:
> Hi all-
>
> we've built a custom board with a FSL MPC8568EMDS CPU.
>
> U-Boot works so far - at least it is able to load a Linux kernel and a
> flattened device tree via network and launch the kernel.
>
> I get no output on the serial console from the kernel, so my only chance is
> to read out the __log_buf while in memory with my Abatron BDI 3000 debugger.
>
> The thing is, I cannot break into the code really, because it never stops
> reliable at my break points... :-(
>
> Can anyone of you see a usual suspect in the attached log?
>
> Is there something wrong with the timing, maybe? Maybe a hardware issue?
>
> How can I check this?
>
> Cheers
> Matthias
>
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
from the log it seems your device tree has issue, also you may want to
turn on verbose debug, turn off preempt, turn off no_hz and see how
far it can go.

if only log_buf is available to get some output, you may want to
increase the buffer size to see more

xianghua

      reply	other threads:[~2010-05-05 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05  8:27 Kernel errors at very early stage Dunda, Matthias
2010-05-05 18:36 ` Xianghua Xiao [this message]

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=q2ke6bf505b1005051136mceda63d6re9295bd7b1f812b3@mail.gmail.com \
    --to=xiaoxianghua@gmail.com \
    --cc=Matthias.Dunda@de.thalesgroup.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).