All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Qiu <qiudayu@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: Boot failure in Power7 pSeries
Date: Wed, 18 Jun 2014 11:27:08 +0800	[thread overview]
Message-ID: <53A1070C.50106@linux.vnet.ibm.com> (raw)
In-Reply-To: <53A00E2B.8030903@linux.vnet.ibm.com>

Anyone has a idea on this issue?

Thanks
Mike
On 06/17/2014 05:45 PM, Mike Qiu wrote:
> Hi all,
>
> I use newest linux-next( top commit: 
> 5f295cdf5c5dbbb0c40f10f2ddae02ff46bbf773) to boot up my Power7 
> machine, PowerVM mode(HypMode 01), use defualt config file in /boot/, 
> it show error log below:
>
> OF stdout device is: /vdevice/vty@30000000
> Preparing to boot Linux version 3.16.0-rc1-next-20140617+ (root@shui) 
> (gcc version 4.8.2 20131212 (Red Hat 4.8.2-7) (GCC) ) #5 SMP Tue Jun 
> 17 05:16:21 EDT 2014
> Detected machine type: 0000000000000101
> Max number of cores passed to firmware: 256 (NR_CPUS = 1024)
> Calling ibm,client-architecture-support... done
> command line: BOOT_IMAGE=/vmlinux-3.16.0-rc1-next-20140617+ 
> root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.md=0 rd.dm=0 
> vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvt
> memory layout at init:
>   memory_limit : 0000000000000000 (16 MB aligned)
>   alloc_bottom : 0000000005910000
>   alloc_top    : 0000000010000000
>   alloc_top_hi : 0000000010000000
>   rmo_top      : 0000000010000000
>   ram_top      : 0000000010000000
> instantiating rtas at 0x000000000ee80000... done
> Querying for OPAL presence... DEFAULT CATCH!, exception-handler=fff00700
> at   %SRR0: 00000000041a1c14   %SRR1: 0000000000081002
> Open Firmware exception handler entered from non-OF code
>
> Client's Fix Pt Regs:
>  00 00000000042c017c 00000000042c2ce8 0000000004ae8d58 00000000042c2f38
>  04 000000000369aafc 00000000042c2f38 0000000001adc100 00000000042c2f38
>  08 0000000000000000 0000000004328d58 0000000028002024 0000000000001002
>  0c a000000000000001 0000000000000000 0000000001a9fd20 00000000041a7df8
>  10 00000000041a2130 00000000041a1e70 f821ff913d220005 0000000001a9fd20
>  14 0000000000007962 000000000ee80000 0000000001180000 000000000ee80000
>  18 00000000041a2610 0000000003690000 00000000042c3070 00000000041a1ce8
>  1c 00000000041a1ce0 00000000041b89f0 0000000000000003 0000000000000001
> Special Regs:
>     %IV: 00000700     %CR: 48002024    %XER: 00000000  %DSISR: 40000000
>   %SRR0: 00000000041a1c14   %SRR1: 0000000000081002
>     %LR: 000000000369aafc    %CTR: 0000000000000000
>    %DAR: f821ff913d220035
> Virtual PID = 0
>  ok
> 0 >
>
> Thanks
> Mike
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2014-06-18  3:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17  9:45 Boot failure in Power7 pSeries Mike Qiu
2014-06-18  3:27 ` Mike Qiu [this message]
2014-06-18  7:54   ` Michael Ellerman
2014-06-18  9:02     ` Mike Qiu
2014-06-19  1:32       ` Michael Ellerman
2014-06-19  2:18         ` Mike Qiu
2014-06-19  3:55           ` Michael Ellerman
2014-06-19  5:33             ` Mike Qiu
2014-06-19  5:49             ` Mike Qiu
2014-06-19  7:21               ` Michael Ellerman
2014-06-19  2:20         ` Mike Qiu
2014-06-19  2:22         ` Mike Qiu

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=53A1070C.50106@linux.vnet.ibm.com \
    --to=qiudayu@linux.vnet.ibm.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.