All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Reif <reif@earthlink.net>
To: sparclinux@vger.kernel.org
Subject: Re: sparc boot failure
Date: Thu, 06 Nov 2008 11:44:59 +0000	[thread overview]
Message-ID: <4912D8BB.3070904@earthlink.net> (raw)
In-Reply-To: <49125E98.8070905@earthlink.net>

Frédéric Weisbecker wrote:
> 2008/11/6 David Miller <davem@davemloft.net>:
>   
>> From: Robert Reif <reif@earthlink.net>
>> Date: Wed, 05 Nov 2008 22:03:52 -0500
>>
>>     
>>> sparc has failed to boot recently and I bisected it down to this patch:
>>>       
>>  ...
>>     
>>>  sparc: correct section of current_pc()
>>>       
>>  ...
>>     
>>> Reverting this patch gets current git booting again.
>>>       
>> Thanks for tracking this down.  I'll take a look and if I
>> can't figure it out I'll revert.
>>     
>
>
> Sorry, I will not have the time to look at it. But this bug is weird...
> --
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   
You can't change sections in the middle of a chunk of code.  The code 
above current_pc: falls through to that label which is now in a 
different section.  Thats why you get an illegal instruction trap at bootup.

  parent reply	other threads:[~2008-11-06 11:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  3:03 sparc boot failure Robert Reif
2008-11-06  4:10 ` David Miller
2008-11-06 10:40 ` Frédéric Weisbecker
2008-11-06 11:44 ` Robert Reif [this message]
2008-11-06 13:10 ` Frédéric Weisbecker
2008-11-06 21:10 ` Sam Ravnborg
2008-11-08  2:41 ` Robert Reif
2008-11-08  6:34 ` David Miller
2008-11-08  8:41 ` Sam Ravnborg

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=4912D8BB.3070904@earthlink.net \
    --to=reif@earthlink.net \
    --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.