[meta-freescale] P2041RDB, P3041DS CRASH_DUMP enabled kernel unable to boot

[Luo Zhenhua]

Hello Alex, 

The kexec/kdump is not officially supported for QorIQ targets currently. 

You can contact with FSL FAE to submit the request, SDK team will plan effort to add the support in subsequent SDK. 


Best Regards,

Zhenhua

> -----Original Message-----
> From: Alexandru Vaduva [mailto:Alexandru.Vaduva at enea.com]
> Sent: Tuesday, July 14, 2015 9:25 PM
> To: Luo Zhenhua-B19537; Siva Borra; meta-freescale at yoctoproject.org
> Cc: Adrian Dudau
> Subject: RE: [meta-freescale] P2041RDB, P3041DS CRASH_DUMP enabled
> kernel unable to boot
> 
> Hello,
> 
> I also require the full support for kdump and kexec.
> Do you have available the according patches necessary for enabling this
> support?
> The same applies for the NUMA support on PPC32.
> 
> If you guys able to help me with this, or direct me to the correct source I would
> be more then happy.
> 
> 
> Thanks for all the help,
> Alex V.
> 
> -----Original Message-----
> From: meta-freescale-bounces at yoctoproject.org [mailto:meta-freescale-
> bounces at yoctoproject.org] On Behalf Of Luo Zhenhua
> Sent: Tuesday, July 14, 2015 1:02 PM
> To: Siva Borra; meta-freescale at yoctoproject.org
> Subject: Re: [meta-freescale] P2041RDB, P3041DS CRASH_DUMP enabled
> kernel unable to boot
> 
> Hi,
> 
> The CONFIG_CRASH_DUMP feature is not officially supported for p2041ds and
> p3041ds.
> 
> 
> Best Regards,
> 
> Zhenhua
> 
> > -----Original Message-----
> > From: meta-freescale-bounces at yoctoproject.org [mailto:meta-freescale-
> > bounces at yoctoproject.org] On Behalf Of Siva Borra
> > Sent: Thursday, July 09, 2015 10:20 PM
> > To: meta-freescale at yoctoproject.org
> > Cc: Adrian Dudau
> > Subject: [meta-freescale] P2041RDB, P3041DS CRASH_DUMP enabled kernel
> > unable to boot
> >
> > Hi,
> > I have enabled the CONFIG_CRASH_DUMP=y Unable to boot the image on
> > machines, P2041rdb and p3041ds.
> > How could I enable and boot kernel with this option? I have provided
> > the commandline option "crashkernel=384M-:128M"
> > I have seen issues with both nfsboot and ramdisk boot.
> > The following is log before hang
> > "  Flattened Device Tree blob at 0c100000
> >     Booting using the fdt blob at 0xc100000
> >     Uncompressing Kernel Image ... OK
> >     Loading Ramdisk to 12e40000, end 2ffff00e ... OK
> >     Loading Device Tree to 03fe4000, end 03fff6f0 ... OK "
> >
> > Regards,
> > Siva Borra
> >
> > --
> > _______________________________________________
> > meta-freescale mailing list
> > meta-freescale at yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-freescale
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale