From mboxrd@z Thu Jan 1 00:00:00 1970 From: festevam@gmail.com (Fabio Estevam) Date: Tue, 16 Jun 2015 17:13:37 -0300 Subject: Running kexec on mx6 In-Reply-To: <20150616195828.GT7557@n2100.arm.linux.org.uk> References: <20150616094242.GR7557@n2100.arm.linux.org.uk> <20150616161317.GS7557@n2100.arm.linux.org.uk> <20150616195828.GT7557@n2100.arm.linux.org.uk> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Jun 16, 2015 at 4:58 PM, Russell King - ARM Linux wrote: > If you don't have that commit, kexec should fail gracefully if it thinks > it can't cope with the existing system config - it shouldn't get to the > point where it takes the existing kernel down. That's correct. On 4.0.5: root at wandboard-solo:~# kexec -d -l /tmp/zImage --dtb /tmp/imx6dl-wandboard.dtb --command-line="console=ttymxc0,115200 earlyprintk root=/dev/mmcblk0p2 rootwait rw" my_load:667: do kernel: 0x75dd1008 kernel_size: 0x5664c8 kexec_load: entry = 0x10008000 flags = 0x280000 nr_segments = 2 segment[0].buf = 0x75dd1008 segment[0].bufsz = 0x5664c8 segment[0].mem = 0x10008000 segment[0].memsz = 0x567000 segment[1].buf = 0x10ab008 segment[1].bufsz = 0x6ba7 segment[1].mem = 0x1159b000 segment[1].memsz = 0x7000 kexec_load failed: Invalid argument entry = 0x10008000 flags = 0x280000 nr_segments = 2 segment[0].buf = 0x75dd1008 segment[0].bufsz = 0x5664c8 segment[0].mem = 0x10008000 segment[0].memsz = 0x567000 segment[1].buf = 0x10ab008 segment[1].bufsz = 0x6ba7 segment[1].mem = 0x1159b000 segment[1].memsz = 0x7000 Applying fee3fd4fd2ad136b into 4.0.5 then kexec works fine. Should we send fee3fd4fd2ad136b to stable? Thanks