All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Packham <judge.packham@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] relocation problem on powerpc
Date: Mon, 8 Sep 2014 16:32:26 +1200	[thread overview]
Message-ID: <CAFOYHZC-WxSJ2fy0EucYrdaT2YfDpUnZRSvEaALegQ3YXe2ubQ@mail.gmail.com> (raw)

Hi All,

I have come across what I think is a relocation problem for powerpc.

I've added the following to ArpTimeoutCheck

+       printf("NetArpWaitTimerStart = %ld\n", NetArpWaitTimerStart);
+       printf("&NetArpWaitTimerStart = %p\n", &NetArpWaitTimerStart);
+       printf("NetArpWaitTry = %d\n", NetArpWaitTry);
+       printf("&NetArpWaitTry = %p\n", &NetArpWaitTry);
+       printf("NetArpWaitTxPacketSize = %d\n", NetArpWaitTxPacketSize);
+       printf("&NetArpWaitTxPacketSize = %p\n", &NetArpWaitTxPacketSize);

Which yields the following output

  NetArpWaitTimerStart = 0
  &NetArpWaitTimerStart = f00000d0
  NetArpWaitTry = 1
  &NetArpWaitTry = 7ffb0058
  NetArpWaitTxPacketSize = 42
  &NetArpWaitTxPacketSize = 7ffb0078

That looks to me like NetArpWaitTimerStart hasn't been relocated for
some reason. Looking at my u-boot.map NetArpWaitTimerStart is the last
item in the .sbss section

Here's the relevant snippets for the variables I'm displaying

 0x00000000f0000058                NetArpWaitTry
 0x00000000f0000078                NetArpWaitTxPacketSize
 0x00000000f00000d0                NetArpWaitTimerStart

The actual problem for me is that ARPs timeout and various network
things fail. Has anyone got any clues as to why this one particular
variable isn't getting relocated.

Thanks,
Chris

More info:
  I'm building P2041RDB_config

  $ git describe
  v2014.10-rc2-15-g2ec8915

  => version
  U-Boot 2014.10-rc2-00015-g2ec8915-dirty (Sep 08 2014 - 16:18:42)
  powerpc-e500-linux-gnu-gcc (Gentoo 4.6.3-r1 p1.9, pie-0.5.2) 4.6.3
  GNU ld (GNU Binutils) 2.21

             reply	other threads:[~2014-09-08  4:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08  4:32 Chris Packham [this message]
2014-09-08  5:18 ` [U-Boot] relocation problem on powerpc Chris Packham
2014-09-08  5:51 ` Chris Packham
2014-09-08  9:04   ` Joakim Tjernlund
2014-09-08 12:22     ` Joakim Tjernlund
2014-09-08 23:07       ` Chris Packham
2014-09-09  9:05         ` Joakim Tjernlund
     [not found]         ` <OF3B16B156.FBE577FB-ONC1257D4E.002B79D7-C1257D4E.0031F02B@LocalDomain>
2014-09-09 12:30           ` Joakim Tjernlund
     [not found]           ` <OF76BFAD6D.627B6C04-ONC1257D4E.00438406-C1257D4E.0044AF3E@LocalDomain>
2014-09-09 13:20             ` Joakim Tjernlund
2014-09-10  3:48               ` Chris Packham
2014-09-10  4:03                 ` [U-Boot] [RFC PATCH v1] powerpc: add --bss-plt to LDFLAGS Chris Packham
2014-09-10 10:47                   ` Joakim Tjernlund
2014-09-24 22:14                   ` York Sun
2014-09-25  7:26                     ` Joakim Tjernlund
2014-09-25 16:49                   ` York Sun
2014-09-08 22:07     ` [U-Boot] relocation problem on powerpc Chris Packham
2014-09-09  0:22       ` [U-Boot] [RFC PATCH v1] powerpc: Fix off-by-one error in relocation Chris Packham
2014-09-10  3:54         ` Chris Packham
2014-09-08 20:21   ` [U-Boot] relocation problem on powerpc Wolfgang Denk
2014-09-08 22:10     ` Chris Packham
2014-09-09  6:37       ` 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=CAFOYHZC-WxSJ2fy0EucYrdaT2YfDpUnZRSvEaALegQ3YXe2ubQ@mail.gmail.com \
    --to=judge.packham@gmail.com \
    --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.