From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Simon Glass <sjg@chromium.org>
Cc: "Ramirez Luna, Omar" <omar.ramirez@ti.com>,
Rabin Vincent <rabin@rab.in>, lk <linux-kernel@vger.kernel.org>,
lak <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: BUG() dies silently
Date: Mon, 19 Sep 2011 19:25:44 +0100 [thread overview]
Message-ID: <20110919182544.GY16381@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAPnjgZ1JDGt7Dzp9VrRKKApeZ9RT9oqry+UkQZwVCw1P+t9pew@mail.gmail.com>
On Mon, Sep 19, 2011 at 11:02:08AM -0700, Simon Glass wrote:
> Hi Russell,
>
> On Mon, Sep 19, 2011 at 9:59 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> > On Mon, Sep 19, 2011 at 03:43:13PM +0100, Russell King - ARM Linux wrote:
> >> On Mon, Sep 19, 2011 at 09:26:49AM -0500, Ramirez Luna, Omar wrote:
> >> > Hi
> >> >
> >> > On Sat, Sep 17, 2011 at 1:07 AM, Rabin Vincent <rabin@rab.in> wrote:
> >> > > If the "Use generic BUG() handler" patch is only scheduled for the next
> >> > > merge window and not for 3.1, can this patch be merged instead for 3.1
> >> > > and -stable? This problem is easily seen with GCC 4.6.
> >> >
> >> > I can send it for both and let the maintainers decide.
> >> >
> >> > Russell, do you give your ack?
> >>
> >> I think it's too large a change for -stable and 3.1 - let's get it into
> >> 3.2 first, and make sure no one sees any regressions there. Then we can
> >> think about submitting it to stable once its proven itself.
> >
> > And we're seeing link failures with the patch in the kernel, so it's
> > *definitely* not stable material as it stands, even if the current code
> > is a problem for GCC 4.6.
> >
> > Regressions trump bug fixes.
>
> Can you point me to the link failures please?
There's two emails during the last couple of months on lakml:
3.1-rc1 link failure
Link failures due to __bug_table in current -next
The former I looked into and came to the conclusion that the only way to
solve it is to stop using asm-generic/vmlinux.lds.S in its entirety and
go back to hand-coding ARMs vmlinux.lds file. No one's come forward
with any better suggestion to fix this, so I'm getting very close to
having to make a decision over this. I think I'm going to have to drop
the generic bug support for the time being.
next prev parent reply other threads:[~2011-09-19 18:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 20:15 Omar Ramirez Luna
2011-04-01 1:47 ` Simon Glass
2011-04-01 8:44 ` Stephen Boyd
2011-04-01 22:29 ` Simon Glass
2011-04-03 7:15 ` Stephen Boyd
2011-04-05 1:55 ` Simon Glass
2011-04-05 17:36 ` Stephen Boyd
2011-04-05 2:29 ` Ramirez Luna, Omar
2011-04-05 5:46 ` Simon Glass
2011-04-05 16:02 ` Ramirez Luna, Omar
2011-04-05 16:43 ` Simon Glass
2011-09-17 6:07 ` Rabin Vincent
2011-09-19 14:26 ` Ramirez Luna, Omar
2011-09-19 14:43 ` Russell King - ARM Linux
2011-09-19 16:59 ` Russell King - ARM Linux
2011-09-19 18:02 ` Simon Glass
2011-09-19 18:25 ` Russell King - ARM Linux [this message]
2011-09-19 18:32 ` Ramirez Luna, Omar
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=20110919182544.GY16381@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=omar.ramirez@ti.com \
--cc=rabin@rab.in \
--cc=sjg@chromium.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
all inboxes | Powered by JetHome®