All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: u-boot@lists.denx.de
Subject: [U-Boot] Data Abort with gcc 7.1
Date: Sun, 23 Jul 2017 12:55:26 +0200	[thread overview]
Message-ID: <1500807326.2333.1.camel@embedded.rocks> (raw)
In-Reply-To: <yw1xfue1tbd2.fsf@mansr.com>

Hi,

On Thu, 2017-07-13 at 01:43 +0100, Måns Rullgård wrote:
> Maxime Ripard <maxime.ripard@free-electrons.com> writes:
> 
> > Hi,
> > 
> > I recently got a gcc 7.1 based toolchain, and it seems like it
> > generates unaligned code, specifically in the net_set_ip_header
> > function in my case.
> > 
> > Whenever some packet is sent, this data abort is triggered:
> > 
> > => setenv ipaddr 10.42.0.1; ping 10.42.0.254
> > using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
> > MAC de:ad:be:ef:00:01
> > HOST MAC de:ad:be:af:00:00
> > RNDIS ready
> > musb-hdrc: peripheral reset irq lost!
> > high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
> > USB RNDIS network up!
> > Using usb_ether device
> > data abort
> > pc : [<7ff9db10>]	   lr : [<7ff9f00c>]
> > reloc pc : [<4a043b10>]	   lr : [<4a04500c>]
> > sp : 7bf37cc8  ip : 00000000	 fp : 7ff6236c
> > r10: 7ffed2b8  r9 : 7bf39ee8	 r8 : 7ffed2b8
> > r7 : 00000001  r6 : 00000000	 r5 : 0000002a  r4 : 7ffed30e
> > r3 : 14000045  r2 : 01002a0a	 r1 : fe002a0a  r0 : 7ffed30e
> > Flags: nZCv  IRQs off  FIQs off  Mode SVC_32
> > Resetting CPU ...

I'm running into the same issue using a Buildroot GCC 7 toolchain.

[snip]

> What hardware did this happen on?  If it was on ARMv5, adding the packed
> attribute is probably the correct fix.  If it was ARMv6 or later,
> something else is broken as well.
> 

FWIW, the board I'm using is ARMv5 (an i.MX28).

Jörg Krause

      parent reply	other threads:[~2017-07-23 10:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 16:54 [U-Boot] Data Abort with gcc 7.1 Maxime Ripard
2017-07-11 16:59 ` Tom Rini
2017-07-11 17:59   ` Dr. Philipp Tomsich
2017-07-12 14:20     ` Maxime Ripard
2017-07-12 14:34       ` Tom Rini
2017-07-12 14:41         ` Dr. Philipp Tomsich
2017-07-12 15:30         ` Thomas Petazzoni
2017-07-12 17:37           ` Tom Rini
2017-07-12 15:48         ` Dr. Philipp Tomsich
2017-07-12 17:49           ` Tom Rini
2017-07-12 17:49             ` Dr. Philipp Tomsich
2017-07-12 18:07           ` Siarhei Siamashka
2017-07-12 18:26             ` Dr. Philipp Tomsich
2017-07-12 20:42               ` Mark Kettenis
2017-07-12 17:55 ` Siarhei Siamashka
2017-07-13  0:43 ` Måns Rullgård
2017-07-13  3:52   ` Siarhei Siamashka
2017-07-13 10:11     ` Måns Rullgård
2017-07-13 10:20       ` Peter Robinson
2017-07-13 12:32         ` Maxime Ripard
2017-07-13 12:34           ` Måns Rullgård
2017-07-23 10:55   ` Jörg Krause [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=1500807326.2333.1.camel@embedded.rocks \
    --to=joerg.krause@embedded.rocks \
    --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.