* Could kernel support kexec on PPC64(e6500)?
@ 2014-12-18 0:46 liu.song11
2014-12-18 2:03 ` Baoquan He
0 siblings, 1 reply; 5+ messages in thread
From: liu.song11 @ 2014-12-18 0:46 UTC (permalink / raw)
Cc: kexec
Hi,
My board is PPC64(e6500 series).When I use kexec-tools, I do the following operations,
then the kernel panic.
1. ./kexec -l ./vmlinux --initrd=/ramdisk.bin (segments load right)
2. ./kexec -e
Then the kernel panic in kexec_sequence. I check NIP is point at mtmsrd r3,1
which in kexec_sequence（misc_64.S）. I have no idea on this fault, and need
some help.
Regards
--------------------------------------------------------------------------------------
Starting new kernel
Oops: Exception in kernel mode, sig: 4 [#1]
CoreNet Generic
Modules linked in:
CPU: 0 PID: 963 Comm: kexec Not tainted 3.10.55-EMBSYS-CGEL-5.01.20.P0 #2
task: c000000006408300 ti: c000000000af8000 task.ti: c0000000753dc000
NIP: c000000000015bf0 LR: c0000000000243f8 CTR: 0000000000000000
REGS: c000000000afbc60 TRAP: 0700 Not tainted (3.10.55-EMBSYS-CGEL-5.01.20.P0)
MSR: 0000000080021000 <CE,ME> CR: 24022480 XER: 00000000
SOFTE: 0
GPR00: 0000000000000000 c000000000afbee0 c000000000af8b88 8002100080021000
GPR04: 000000000178f600 c0000000753ccc00 c0000000753cd000 c000000000a6f240
GPR08: c00000000256c4d8 00000000000753cd c000000000000000 0000000000001b08
GPR12: 0000000022022444 c000000000b0f080 0000000000000001 ffffffffffffffff
GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR20: 0000000000000000 0000000000000002 0000000000000001 0000000000000001
GPR24: 0000000000000001 0000000000000000 c00000000256c4d8 c000000000a6f240
GPR28: c0000000753cd000 c0000000753ccc00 000000000178f600 c000000000afbf90
NIP [c000000000015bf0] .kexec_sequence+0x5c/0xac
LR [c0000000000243f8] .default_machine_kexec+0x128/0x190
Call Trace:
Instruction dump:
fb41ffd0 fb21ffc8 f821ff51 7c7f1b78 7c9e2378 7cbd2b78 7cdc3378 7cfb3b78
7d1a4378 a32d0030 7c6000a6 5463045e <7c610164> 7fa3eb78 4800e519 4bffff71
---[ end trace 70e6c52cd522dd05 ]---
Kernel panic - not syncing: Fatal exception in interrupt
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Could kernel support kexec on PPC64(e6500)?
2014-12-18 0:46 Could kernel support kexec on PPC64(e6500)? liu.song11
@ 2014-12-18 2:03 ` Baoquan He
2014-12-18 2:32 ` liu.song11
0 siblings, 1 reply; 5+ messages in thread
From: Baoquan He @ 2014-12-18 2:03 UTC (permalink / raw)
To: liu.song11; +Cc: kexec
On 12/18/14 at 08:46am, liu.song11@zte.com.cn wrote:
>
> Hi,
>
> My board is PPC64(e6500 series).When I use kexec-tools, I do the following operations,
> then the kernel panic.
>
> 1. ./kexec -l ./vmlinux --initrd=/ramdisk.bin (segments load right)
Please try with below command again, you had better get cmdline options from
1st kernel.
./kexec -l ./vmlinux --initrd=/ramdisk.bin --reuse-cmdline
Let me know if it helps or any new questions.
> 2. ./kexec -e
>
> Then the kernel panic in kexec_sequence. I check NIP is point at mtmsrd r3,1
> which in kexec_sequence（misc_64.S）. I have no idea on this fault, and need
> some help.
>
> Regards
> --------------------------------------------------------------------------------------
> Starting new kernel
> Oops: Exception in kernel mode, sig: 4 [#1]
> CoreNet Generic
> Modules linked in:
> CPU: 0 PID: 963 Comm: kexec Not tainted 3.10.55-EMBSYS-CGEL-5.01.20.P0 #2
> task: c000000006408300 ti: c000000000af8000 task.ti: c0000000753dc000
> NIP: c000000000015bf0 LR: c0000000000243f8 CTR: 0000000000000000
> REGS: c000000000afbc60 TRAP: 0700 Not tainted (3.10.55-EMBSYS-CGEL-5.01.20.P0)
> MSR: 0000000080021000 <CE,ME> CR: 24022480 XER: 00000000
> SOFTE: 0
>
> GPR00: 0000000000000000 c000000000afbee0 c000000000af8b88 8002100080021000
> GPR04: 000000000178f600 c0000000753ccc00 c0000000753cd000 c000000000a6f240
> GPR08: c00000000256c4d8 00000000000753cd c000000000000000 0000000000001b08
> GPR12: 0000000022022444 c000000000b0f080 0000000000000001 ffffffffffffffff
> GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> GPR20: 0000000000000000 0000000000000002 0000000000000001 0000000000000001
> GPR24: 0000000000000001 0000000000000000 c00000000256c4d8 c000000000a6f240
> GPR28: c0000000753cd000 c0000000753ccc00 000000000178f600 c000000000afbf90
> NIP [c000000000015bf0] .kexec_sequence+0x5c/0xac
> LR [c0000000000243f8] .default_machine_kexec+0x128/0x190
> Call Trace:
> Instruction dump:
> fb41ffd0 fb21ffc8 f821ff51 7c7f1b78 7c9e2378 7cbd2b78 7cdc3378 7cfb3b78
> 7d1a4378 a32d0030 7c6000a6 5463045e <7c610164> 7fa3eb78 4800e519 4bffff71
> ---[ end trace 70e6c52cd522dd05 ]---
>
> Kernel panic - not syncing: Fatal exception in interrupt
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Could kernel support kexec on PPC64(e6500)?
2014-12-18 2:03 ` Baoquan He
@ 2014-12-18 2:32 ` liu.song11
2014-12-19 2:03 ` Baoquan He
0 siblings, 1 reply; 5+ messages in thread
From: liu.song11 @ 2014-12-18 2:32 UTC (permalink / raw)
To: Baoquan He; +Cc: kexec
Hi, Baoquan
Follow your advice，I found --reuse-cmdline appear could not work well which will
print usage message.
My board is PPC64(e6500 PPC_BOOK3E), maybe kexec couldn't support this type?
Supported kernel file types and options:
elf-ppc64
--command-line=<Command line> command line to append.
--append=<Command line> same as --command-line.
--ramdisk=<filename> Initial RAM disk.
--initrd=<filename> same as --ramdisk.
--devicetreeblob=<filename> Specify device tree blob file.
--dtb=<filename> same as --devicetreeblob.
Regards
From: Baoquan He <bhe@redhat.com>
To: liu.song11@zte.com.cn,
Cc: kexec@lists.infradead.org
Date: 2014-12-18 10:03
Subject: Re: Could kernel support kexec on PPC64(e6500)?
On 12/18/14 at 08:46am, liu.song11@zte.com.cn wrote:
>
> Hi,
>
> My board is PPC64(e6500 series).When I use kexec-tools, I do the following operations,
> then the kernel panic.
>
> 1. ./kexec -l ./vmlinux --initrd=/ramdisk.bin (segments load right)
Please try with below command again, you had better get cmdline options from
1st kernel.
./kexec -l ./vmlinux --initrd=/ramdisk.bin --reuse-cmdline
Let me know if it helps or any new questions.
> 2. ./kexec -e
>
> Then the kernel panic in kexec_sequence. I check NIP is point at mtmsrd r3,1
> which in kexec_sequence（misc_64.S）. I have no idea on this fault, and need
> some help.
>
> Regards
> --------------------------------------------------------------------------------------
> Starting new kernel
> Oops: Exception in kernel mode, sig: 4 [#1]
> CoreNet Generic
> Modules linked in:
> CPU: 0 PID: 963 Comm: kexec Not tainted 3.10.55-EMBSYS-CGEL-5.01.20.P0 #2
> task: c000000006408300 ti: c000000000af8000 task.ti: c0000000753dc000
> NIP: c000000000015bf0 LR: c0000000000243f8 CTR: 0000000000000000
> REGS: c000000000afbc60 TRAP: 0700 Not tainted (3.10.55-EMBSYS-CGEL-5.01.20.P0)
> MSR: 0000000080021000 <CE,ME> CR: 24022480 XER: 00000000
> SOFTE: 0
>
> GPR00: 0000000000000000 c000000000afbee0 c000000000af8b88 8002100080021000
> GPR04: 000000000178f600 c0000000753ccc00 c0000000753cd000 c000000000a6f240
> GPR08: c00000000256c4d8 00000000000753cd c000000000000000 0000000000001b08
> GPR12: 0000000022022444 c000000000b0f080 0000000000000001 ffffffffffffffff
> GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> GPR20: 0000000000000000 0000000000000002 0000000000000001 0000000000000001
> GPR24: 0000000000000001 0000000000000000 c00000000256c4d8 c000000000a6f240
> GPR28: c0000000753cd000 c0000000753ccc00 000000000178f600 c000000000afbf90
> NIP [c000000000015bf0] .kexec_sequence+0x5c/0xac
> LR [c0000000000243f8] .default_machine_kexec+0x128/0x190
> Call Trace:
> Instruction dump:
> fb41ffd0 fb21ffc8 f821ff51 7c7f1b78 7c9e2378 7cbd2b78 7cdc3378 7cfb3b78
> 7d1a4378 a32d0030 7c6000a6 5463045e <7c610164> 7fa3eb78 4800e519 4bffff71
> ---[ end trace 70e6c52cd522dd05 ]---
>
> Kernel panic - not syncing: Fatal exception in interrupt
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Could kernel support kexec on PPC64(e6500)?
2014-12-18 2:32 ` liu.song11
@ 2014-12-19 2:03 ` Baoquan He
2014-12-19 2:12 ` liu.song11
0 siblings, 1 reply; 5+ messages in thread
From: Baoquan He @ 2014-12-19 2:03 UTC (permalink / raw)
To: liu.song11; +Cc: kexec
On 12/18/14 at 10:32am, liu.song11@zte.com.cn wrote:
> Hi, Baoquan
>
> Follow your advice，I found --reuse-cmdline appear could not work well which will
> print usage message.
>
> My board is PPC64(e6500 PPC_BOOK3E), maybe kexec couldn't support this type?
>
>
> Supported kernel file types and options:
> elf-ppc64
> --command-line=<Command line> command line to append.
> --append=<Command line> same as --command-line.
> --ramdisk=<filename> Initial RAM disk.
> --initrd=<filename> same as --ramdisk.
> --devicetreeblob=<filename> Specify device tree blob file.
> --dtb=<filename> same as --devicetreeblob.
Then just add a cmdline-line by --command-line="xxxx" which can be
copied from your /proc/cmdline. I am not sure if dtb is necessary.
Hope this can make it work.
>
> Regards
>
>
>
> From: Baoquan He <bhe@redhat.com>
> To: liu.song11@zte.com.cn,
> Cc: kexec@lists.infradead.org
> Date: 2014-12-18 10:03
> Subject: Re: Could kernel support kexec on PPC64(e6500)?
>
>
>
> On 12/18/14 at 08:46am, liu.song11@zte.com.cn wrote:
> >
> > Hi,
> >
> > My board is PPC64(e6500 series).When I use kexec-tools, I do the following operations,
> > then the kernel panic.
> >
> > 1. ./kexec -l ./vmlinux --initrd=/ramdisk.bin (segments load right)
>
> Please try with below command again, you had better get cmdline options from
> 1st kernel.
> ./kexec -l ./vmlinux --initrd=/ramdisk.bin --reuse-cmdline
>
> Let me know if it helps or any new questions.
>
>
> > 2. ./kexec -e
> >
> > Then the kernel panic in kexec_sequence. I check NIP is point at mtmsrd r3,1
> > which in kexec_sequence（misc_64.S）. I have no idea on this fault, and need
> > some help.
> >
> > Regards
> > --------------------------------------------------------------------------------------
> > Starting new kernel
> > Oops: Exception in kernel mode, sig: 4 [#1]
> > CoreNet Generic
> > Modules linked in:
> > CPU: 0 PID: 963 Comm: kexec Not tainted 3.10.55-EMBSYS-CGEL-5.01.20.P0 #2
> > task: c000000006408300 ti: c000000000af8000 task.ti: c0000000753dc000
> > NIP: c000000000015bf0 LR: c0000000000243f8 CTR: 0000000000000000
> > REGS: c000000000afbc60 TRAP: 0700 Not tainted (3.10.55-EMBSYS-CGEL-5.01.20.P0)
> > MSR: 0000000080021000 <CE,ME> CR: 24022480 XER: 00000000
> > SOFTE: 0
> >
> > GPR00: 0000000000000000 c000000000afbee0 c000000000af8b88 8002100080021000
> > GPR04: 000000000178f600 c0000000753ccc00 c0000000753cd000 c000000000a6f240
> > GPR08: c00000000256c4d8 00000000000753cd c000000000000000 0000000000001b08
> > GPR12: 0000000022022444 c000000000b0f080 0000000000000001 ffffffffffffffff
> > GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > GPR20: 0000000000000000 0000000000000002 0000000000000001 0000000000000001
> > GPR24: 0000000000000001 0000000000000000 c00000000256c4d8 c000000000a6f240
> > GPR28: c0000000753cd000 c0000000753ccc00 000000000178f600 c000000000afbf90
> > NIP [c000000000015bf0] .kexec_sequence+0x5c/0xac
> > LR [c0000000000243f8] .default_machine_kexec+0x128/0x190
> > Call Trace:
> > Instruction dump:
> > fb41ffd0 fb21ffc8 f821ff51 7c7f1b78 7c9e2378 7cbd2b78 7cdc3378 7cfb3b78
> > 7d1a4378 a32d0030 7c6000a6 5463045e <7c610164> 7fa3eb78 4800e519 4bffff71
> > ---[ end trace 70e6c52cd522dd05 ]---
> >
> > Kernel panic - not syncing: Fatal exception in interrupt
> > --------------------------------------------------------
> > ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
> > _______________________________________________
> > kexec mailing list
> > kexec@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/kexec
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Could kernel support kexec on PPC64(e6500)?
2014-12-19 2:03 ` Baoquan He
@ 2014-12-19 2:12 ` liu.song11
0 siblings, 0 replies; 5+ messages in thread
From: liu.song11 @ 2014-12-19 2:12 UTC (permalink / raw)
To: Baoquan He; +Cc: kexec
OK, maybe also need dtb. For now, the kernel couldn't support kexec of BOOK3E(PPC64) very well, I think
there also need some work about that, maybe a little difficult.
Thanks a lot.
Regards
From: Baoquan He <bhe@redhat.com>
To: liu.song11@zte.com.cn,
Cc: kexec@lists.infradead.org
Date: 2014-12-19 10:03
Subject: Re: Could kernel support kexec on PPC64(e6500)?
On 12/18/14 at 10:32am, liu.song11@zte.com.cn wrote:
> Hi, Baoquan
>
> Follow your advice，I found --reuse-cmdline appear could not work well which will
> print usage message.
>
> My board is PPC64(e6500 PPC_BOOK3E), maybe kexec couldn't support this type?
>
>
> Supported kernel file types and options:
> elf-ppc64
> --command-line=<Command line> command line to append.
> --append=<Command line> same as --command-line.
> --ramdisk=<filename> Initial RAM disk.
> --initrd=<filename> same as --ramdisk.
> --devicetreeblob=<filename> Specify device tree blob file.
> --dtb=<filename> same as --devicetreeblob.
Then just add a cmdline-line by --command-line="xxxx" which can be
copied from your /proc/cmdline. I am not sure if dtb is necessary.
Hope this can make it work.
>
> Regards
>
>
>
> From: Baoquan He <bhe@redhat.com>
> To: liu.song11@zte.com.cn,
> Cc: kexec@lists.infradead.org
> Date: 2014-12-18 10:03
> Subject: Re: Could kernel support kexec on PPC64(e6500)?
>
>
>
> On 12/18/14 at 08:46am, liu.song11@zte.com.cn wrote:
> >
> > Hi,
> >
> > My board is PPC64(e6500 series).When I use kexec-tools, I do the following operations,
> > then the kernel panic.
> >
> > 1. ./kexec -l ./vmlinux --initrd=/ramdisk.bin (segments load right)
>
> Please try with below command again, you had better get cmdline options from
> 1st kernel.
> ./kexec -l ./vmlinux --initrd=/ramdisk.bin --reuse-cmdline
>
> Let me know if it helps or any new questions.
>
>
> > 2. ./kexec -e
> >
> > Then the kernel panic in kexec_sequence. I check NIP is point at mtmsrd r3,1
> > which in kexec_sequence（misc_64.S）. I have no idea on this fault, and need
> > some help.
> >
> > Regards
> > --------------------------------------------------------------------------------------
> > Starting new kernel
> > Oops: Exception in kernel mode, sig: 4 [#1]
> > CoreNet Generic
> > Modules linked in:
> > CPU: 0 PID: 963 Comm: kexec Not tainted 3.10.55-EMBSYS-CGEL-5.01.20.P0 #2
> > task: c000000006408300 ti: c000000000af8000 task.ti: c0000000753dc000
> > NIP: c000000000015bf0 LR: c0000000000243f8 CTR: 0000000000000000
> > REGS: c000000000afbc60 TRAP: 0700 Not tainted (3.10.55-EMBSYS-CGEL-5.01.20.P0)
> > MSR: 0000000080021000 <CE,ME> CR: 24022480 XER: 00000000
> > SOFTE: 0
> >
> > GPR00: 0000000000000000 c000000000afbee0 c000000000af8b88 8002100080021000
> > GPR04: 000000000178f600 c0000000753ccc00 c0000000753cd000 c000000000a6f240
> > GPR08: c00000000256c4d8 00000000000753cd c000000000000000 0000000000001b08
> > GPR12: 0000000022022444 c000000000b0f080 0000000000000001 ffffffffffffffff
> > GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > GPR20: 0000000000000000 0000000000000002 0000000000000001 0000000000000001
> > GPR24: 0000000000000001 0000000000000000 c00000000256c4d8 c000000000a6f240
> > GPR28: c0000000753cd000 c0000000753ccc00 000000000178f600 c000000000afbf90
> > NIP [c000000000015bf0] .kexec_sequence+0x5c/0xac
> > LR [c0000000000243f8] .default_machine_kexec+0x128/0x190
> > Call Trace:
> > Instruction dump:
> > fb41ffd0 fb21ffc8 f821ff51 7c7f1b78 7c9e2378 7cbd2b78 7cdc3378 7cfb3b78
> > 7d1a4378 a32d0030 7c6000a6 5463045e <7c610164> 7fa3eb78 4800e519 4bffff71
> > ---[ end trace 70e6c52cd522dd05 ]---
> >
> > Kernel panic - not syncing: Fatal exception in interrupt
> > --------------------------------------------------------
> > ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
> > _______________________________________________
> > kexec mailing list
> > kexec@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/kexec
> --------------------------------------------------------
> ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-12-19 2:13 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-18 0:46 Could kernel support kexec on PPC64(e6500)? liu.song11
2014-12-18 2:03 ` Baoquan He
2014-12-18 2:32 ` liu.song11
2014-12-19 2:03 ` Baoquan He
2014-12-19 2:12 ` liu.song11
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.