On Thu, Nov 20, 2014 at 11:10:55AM -0500, Dave Jones wrote: > On Wed, Nov 19, 2014 at 11:28:06AM -0500, Vivek Goyal wrote: > > > I am wondering may be in some cases we panic in second kernel and sit > > there. Probably we should append a kernel command line automatically > > say "panic=1" so that it reboots itself if second kernel panics. > > > > By any chance, have you enabled "CONFIG_RANDOMIZE_BASE"? If yes, please > > disable that as currently kexec/kdump stuff does not work with it. And > > it hangs very early in the boot process and I had to hook serial console > > to get following message on console. > > I did have that enabled. (Perhaps the kconfig should conflict?)
Hi Dave, Can you please also send me your kernel config file. I will try that on my machine and see if I can reproduce the problem on my machine. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
