kexec works well with "dash l" but not working with "dash p"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Add several experts known from Google.

-- begin resent body --

Hi experts,

I have a problem when using kexec-tools on freescale powerpc P1014E(ppc32).

I have 256MB memory and reserved 78MB for crashkernel.
The cmdline for production kernel is,

bver=0.0.10 root=/dev/ram rw console=ttyS0,115200 crashkernel=78M


I used below command to load crash kernel into memory.
/mnt/uspace/abc/kexec -d -l /mnt/uspace/abc/vmlinux.z.img \
--initrd=/mnt/uspace/abc/ramdisk.img.gz \
--append="root=/dev/ram1 rw console=ttyS0,115200 1 maxcpus=1
noirqdistrib reset_devices"

Then I used "kexec -e" to execute the crash kernel.
The crash kernel works *well* and I can enter busybox after the crash
kernel is up.


But when I used below command to load crash kernel into memory for
panic catching,
/mnt/uspace/abc/kexec -d -p /mnt/uspace/abc/vmlinux.z.img \
--initrd=/mnt/uspace/abc/ramdisk.img.gz \
--append="root=/dev/ram1 rw console=ttyS0,115200 1 maxcpus=1
noirqdistrib reset_devices"

and tried to trigger panic by "echo c > /proc/sysrq",

system hung after "Bye!" was printed to console.

I attached the debug output of "kexec -d -l" and "kexec -d -p".

Can someone please help here or point me a correct place to post the question?

Thanks.

BR

On Thu, Jun 11, 2015 at 9:22 PM, os user <gnusercn at gmail.com> wrote:
> Hi experts,
>
> I have a problem when using kexec-tools on freescale powerpc P1014E.
>
> I have 256MB memory and reserved 78MB for crashkernel.
> The cmdline for production kernel is,
>
> bver=0.0.10 root=/dev/ram rw console=ttyS0,115200 crashkernel=78M
>
>
> I used below command to load crash kernel into memory.
> /mnt/uspace/abc/kexec -d -l /mnt/uspace/abc/vmlinux.z.img \
> --initrd=/mnt/uspace/abc/ramdisk.img.gz \
> --append="root=/dev/ram1 rw console=ttyS0,115200 1 maxcpus=1
> noirqdistrib reset_devices"
>
> Then I used "kexec -e" to execute the crash kernel.
> The crash kernel works *well* and I can enter busybox after the crash
> kernel is up.
>
>
> But when I used below command to load crash kernel into memory for
> panic catching,
> /mnt/uspace/abc/kexec -d -p /mnt/uspace/abc/vmlinux.z.img \
> --initrd=/mnt/uspace/abc/ramdisk.img.gz \
> --append="root=/dev/ram1 rw console=ttyS0,115200 1 maxcpus=1
> noirqdistrib reset_devices"
>
> and tried to trigger panic by "echo c > /proc/sysrq",
>
> system hung after "Bye!" was printed to console.
>
> I attached the debug output of "kexec -d -l" and "kexec -d -p".
>
> Can someone please help here or point me a correct place to post the question?
>
> Thanks.
>
> BR



[Index of Archives]     [LM Sensors]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux