All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Gardner <rob.gardner@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: Bisected: RED State Exception in 4.5 on E420R
Date: Wed, 27 Apr 2016 20:06:04 +0000	[thread overview]
Message-ID: <57211BAC.9070902@oracle.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1604061729350.16827@math.ut.ee>

On 04/27/2016 02:01 PM, David Miller wrote:
> From: Rob Gardner <rob.gardner@oracle.com>
> Date: Wed, 27 Apr 2016 13:46:46 -0600
>
>> On 04/27/2016 01:36 PM, David Miller wrote:
>>> From: David Miller <davem@davemloft.net>
>>> Date: Wed, 27 Apr 2016 15:33:55 -0400 (EDT)
>>>
>>>> Therefore some other aspect of the change is causing problems and I
>>>> think that aspect is the size of the new code.
>>> Actually, there is a way to prove that this is indeed the bug, Meelis
>>> what does the entry for "swapper_tsb" say in your System.map file for
>>> a failing kernel?
>>>
>>> If it is not "0000000000408000", then that shows the bug.
>>>
>>
>> I've run into this situation, and the assembler emits a warning that
>> looks like this:
>>
>> arch/sparc/kernel/head_64.S:869: Warning: .space or .fill with
>> negative value, ignored
>>
>> I've worked around it by moving some of the includes to after the
>> ttable include. I think this is ok as long as code doesn't get
>> situated too far away for the branch displacement to handle.
> Maybe older binutils don't catch this properly.
>
> On my config here I definitely can see that the size is getting
> really close to the limit, and that's without all of the mentioned
> features enabled.
>
> Meanwhile, I'll keep working on the patch I said I'd do which trims
> down the size of all of this code.

Also, perhaps think about a way to make the assembler emit something 
fatal instead of a warning when this situation occurs? People tend to 
ignore warnings. ;)

Rob


  parent reply	other threads:[~2016-04-27 20:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07  8:22 Bisected: RED State Exception in 4.5 on E420R Meelis Roos
2016-04-11  3:45 ` David Miller
2016-04-27 13:21 ` Meelis Roos
2016-04-27 19:33 ` David Miller
2016-04-27 19:36 ` David Miller
2016-04-27 19:46 ` Rob Gardner
2016-04-27 19:55 ` Meelis Roos
2016-04-27 20:01 ` David Miller
2016-04-27 20:02 ` David Miller
2016-04-27 20:06 ` Rob Gardner [this message]
2016-04-27 20:22 ` David Miller
2016-04-27 20:49 ` Sam Ravnborg
2016-04-27 20:52 ` David Miller
2016-04-27 20:53 ` David Miller
2016-04-28  4:58 ` Joerg Abraham
2016-04-28 17:26 ` mroos
2016-04-28 17:38 ` David Miller
2016-04-28 19:49 ` Sam Ravnborg
2016-04-28 20:10 ` David Miller
2016-04-28 20:57 ` Sam Ravnborg
2016-04-28 22:54 ` Rob Gardner
2016-04-29  0:16 ` Julian Calaby
2016-05-01 23:36 ` David Miller
2016-05-01 23:41 ` David Miller

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=57211BAC.9070902@oracle.com \
    --to=rob.gardner@oracle.com \
    --cc=sparclinux@vger.kernel.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 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.