From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Frysinger <vapier.adi@gmail.com>,
Bob Liu <lliubbo@gmail.com>
Subject: Re: Blackfin link issue (Was: linux-next: triage for March 27, 2012)
Date: Tue, 27 Mar 2012 20:23:59 -0400 [thread overview]
Message-ID: <20120328002359.GA12442@windriver.com> (raw)
In-Reply-To: <20120328110350.e2d44e1f66b6ac7f9fd82843@canb.auug.org.au>
[Blackfin link issue (Was: linux-next: triage for March 27, 2012)] On 28/03/2012 (Wed 11:03) Stephen Rothwell wrote:
> Hi Paul,
>
> On Tue, 27 Mar 2012 17:36:27 -0400 Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> >
> > The blackfin builds are no longer failing on vm_is_stack but instead
> > are all failing with "L1 data A overflow!" at final link, which smells
> > like some kind of binutils/toolchain issue.
> >
> >
> > bfin:***all-builds***
> > when: Mar 26
> > why: bfin-uclinux-ld: L1 data A overflow!
> > status: unknown, binutils issue?
> > fix:
> > ref: http://kisskb.ellerman.id.au/kisskb/buildresult/5981475/
>
> It actually looks like this comes from an ASSERT in the blackfin
> vmlinux.lds.S ... looks like some sections overflowed.
Thanks Stephen -- I see you've CC'd some blackfin folks -- lets hope
they can help shed some light on this. I'll admit my guess above
was only that --- just a guess.
Paul.
--
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
next prev parent reply other threads:[~2012-03-28 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 21:36 linux-next: triage for March 27, 2012 Paul Gortmaker
2012-03-28 0:03 ` Blackfin link issue (Was: linux-next: triage for March 27, 2012) Stephen Rothwell
2012-03-28 0:23 ` Paul Gortmaker [this message]
2012-03-28 3:34 ` Mike Frysinger
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=20120328002359.GA12442@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lliubbo@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=vapier.adi@gmail.com \
/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).