All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: u-boot@lists.denx.de
Subject: [U-Boot] mpc512x: Trouble migrating from 2012.07 to 2013.01
Date: Thu, 24 Jan 2013 09:40:45 +0100	[thread overview]
Message-ID: <OFD3C888A1.560BEE31-ONC1257AFD.002DB246-C1257AFD.002FADA7@transmode.se> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C427B4CA1@post.tritech.se>

Mats K?rrman <Mats.Karrman@tritech.se> wrote on 2013/01/23 22:58:56:
> 
> Dear Wolfgang Denk,
> 
> >> Found that it was looping endlessly in 
arch/powerpc/lib/ticks.S::wait_ticks
> (). Reverting commit "ppc: Create a stack frame for wait_ticks()" made 
> everything work again.
> > 
> > This makes no sense to me  - especially as it works on all other
> > systems.
> 

Me neither, there is not a lot details. I do recall having other problems 
with
wait_ticks from time to time, sometimes the TB counter(mtfbu, mftb in 
get_ticks)
would not increment so one would just loop forever in wait_ticks. This 
problem
had nothing to do with my patch though.
Never got around to finding out what caused it, we ended up blaming 
unstable HW.

Some ideas though:
- Perhaps you have some alignment problem, try adding nop's here and 
there.
- My patch uses r0(which is what one should use to make gdb happy) instead 
of r8
  to stash the LR. Possibly you have some odd dependency on r0, try using 
r8 again.

None of the above is a real fix tough.

> If you say it works, it makes no sense to me either. I thought it might 
be 
> some subtle difference in the way the e300c4 core or GCC works compared 
to 
> other PPC cores. If there are no such differences, then a patch with no 
> intended functional difference beyond keeping gdb happy should not make 
any 
> difference, good or bad.

hmm, we use e300c2 with no problem.

 Jocke

  reply	other threads:[~2013-01-24  8:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 15:24 [U-Boot] mpc512x: Trouble migrating from 2012.07 to 2013.01 Mats Kärrman
2013-01-23 21:25 ` Wolfgang Denk
2013-01-23 21:58   ` Mats Kärrman
2013-01-24  8:40     ` Joakim Tjernlund [this message]
     [not found]     ` <OFD3C888A1.560BEE31-ONC1257AFD.002DB246-C1257AFD.002FAD45@LocalDomain>
2013-01-24  8:58       ` Joakim Tjernlund
     [not found]       ` <OF5A9C9414.751DE82C-ONC1257AFD.0030970D-C1257AFD.00314F3A@LocalDomain>
2013-01-24  9:21         ` Joakim Tjernlund
2013-01-24 11:54           ` Mats Kärrman
2013-01-24 13:31           ` Mats Kärrman
2013-01-24 13:48             ` Joakim Tjernlund
  -- strict thread matches above, loose matches on Subject: below --
2013-01-23 13:17 Mats Kärrman
2013-01-23 20:40 ` 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=OFD3C888A1.560BEE31-ONC1257AFD.002DB246-C1257AFD.002FADA7@transmode.se \
    --to=joakim.tjernlund@transmode.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.