All of lore.kernel.org
 help / color / mirror / Atom feed
From: "tiejun.chen" <tiejun.chen@windriver.com>
To: kevin diggs <diggskevin38@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: elf section .text.unlikely
Date: Mon, 24 Jan 2011 11:29:25 +0800	[thread overview]
Message-ID: <4D3CF215.206@windriver.com> (raw)
In-Reply-To: <AANLkTinhu1fS5ESwivxSepnp-CXirm9dfV74_GEUi9qB@mail.gmail.com>

kevin diggs wrote:
> Hi,
> 
> One more thing:
> 
> The last message printed is:
> 
> Driver 'sd' needs updating - please us bus_type methods
> 
> The mesh SCSI controller seems to successfully scan the bus. The next
> message that a 3.4.6 compiled kernel prints are details about disk sda
> (from SCSI disk driver?).
> 
> 4.3.5 keyboard is dead.
> 
> Jog any thoughts?

Maybe the kernel already panic then serial cannot print the last messages
immediately. So after reset the target you can dump __log_buf from the u-boot
prompt to track this in detail.

Tiejun

> 
> Thanks!
> 
> kevin
> 
> On Fri, Jan 21, 2011 at 8:31 PM, kevin diggs <diggskevin38@gmail.com> wrote:
>> For what it is worth, this section contains dump_stack, panic, and printk
>>
>> Thanks!
>>
>> kevin
>>
>> On Fri, Jan 21, 2011 at 7:40 PM, kevin diggs <diggskevin38@gmail.com> wrote:
>>> Hi,
>>>
>>> I am trying to get a PowerMac 8600 to boot past 2.6.28.
>>>
>>> I can boot 2.6.28 compiled with either 3.3.3 or 3.4.6. I can't get
>>> 2.6.28 to boot using 4.3.5. The 4.3.5 vmlinux has a section
>>> '.text.unlikely' that the 3.4.6 version does not. Anyone know what
>>> this might be?
>>>
>>> kevin

      reply	other threads:[~2011-01-24  3:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22  1:40 elf section .text.unlikely kevin diggs
2011-01-22  2:31 ` kevin diggs
2011-01-22  3:17   ` kevin diggs
2011-01-24  3:29     ` tiejun.chen [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=4D3CF215.206@windriver.com \
    --to=tiejun.chen@windriver.com \
    --cc=diggskevin38@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.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.