Hi,
Thx, but it's not a awesome work yet because my new kernel won't boot on the older
I can't help if your kernel sources does not have "mmu_writable.h" file
When i have this kind of missing source, i temporary suppress ".h" #include, and see what function is missing.
After what, i grep -ri on source to find in /arch/arm the good file.
also, for the module, i add missing function by direct call with "kallsyms_lookup_name" declaration.
My older sources with (V1) need to have driver to work.
With the last sources, you don't need to have drivers, and can't have "function not implemented"
See in the first post, i have post my last V11 kexec with a lot of fixes.
If you have something missing (function not found at kexec_load loading), please share, i try to help for that.
Good luck to you.
static int my_shutdown(void){
char *args[] = {
"shutdown",
"-r",
"now",
NULL
};
execv("/sbin/shutdown", args);
execv("/etc/shutdown", args);
execv("/bin/shutdown", args);
perror("shutdown");
return -1;
}static int my_shutdown(void)
{
char *args[] = {
NULL
};
execv("/system/bin/reboot",args);
execv("/system/xbin/reboot",args);
perror("reboot");
return -1;
}static int my_exec(void)
{
int result;
//////////////////////////////////////////////
// Remplacement de "syscall" - Par Delewer //
// Novembre 2013 //
//////////////////////////////////////////////
//
// result = kexec_reboot();
const char fn[]= "/dev/kexec_driver";
FILE *fp;
fp = fopen(fn, "w");
if (!fp)
{
fprintf(stderr, "Kexec_driver non implemented\n");
fprintf(stderr, "Please, prepare by typing the following commands :\n");
fprintf(stderr, " => mknod /dev/kexec_driver c <major number> 0\n");
fprintf(stderr, " => cat /dev/kexec_driver\n");
return -1;
}
fwrite("boot", 1, 4, fp);
fclose(fp);
//////////////////////////////////////////////
/* I have failed if I make it here */
fprintf(stderr, "kexec failed: %s\n",
strerror(errno));
return -1;
}
Well..
In 1rst, please don't try with V1.1
For a lot of reason, you failed to success to boot with.
For eg : - not aligned memory, no "reloc_kernel" addresses attribute are definitively good reasons
Other pb is with driver.. It's work, but you need to mount a lot of files system at early boot, and cause random pb
If you have atags with a stock phone with locked kernel, you need to use "procfs_rw" to create you own "atags" file, and only if atags is missing... but, if you use "Device Tree Blob" (called "DTB") like our Z1 have, you don't need any "atags"... It's atags or Dtb, but not both.
Our kexec is coded for dtb file, and feed the same register at boot to replace atags address by dtb address.
If you don't know, if you need a Dtb file on your phone, you have a problem
Please try with V11 sources and see if you have a freeze in the "machine_kexec" addresses alloc for "relocate_kernel"... it's the key to have a kexec module working for a locked bootloader.
We have a static ro memory for loaded module on Z1 (by smp mmu protection on stock kernel), and i have create a dynamic relocate_kernel function in user space to bypass this protection.
It's not the best solution, but it work...
I m block at "soft_restart" function because of "cpu_proc_fin" freeze ("mcr p15" mmu roolback can't be exec)
So, i search...
echo 0 > /proc/sys/kernel/dmesg_restrict
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms# uname -r# strings kexec_load.ko | grep vermagic
vermagic=3.4.0-perf-g66807d4-02450-g9a218f1 SMP preempt mod_unload modversions ARMv7"include/config/kernel.release" and add :
"3.4.0-perf-g66807d4-02450-g9a218f1"sed -i 's/\x32\x76\x86\x29/\x72\xFF\x5E\x20/' procfs_rw.ko
sed -i 's/\x32\x76\x86\x29/\x72\xFF\x5E\x20/' kexec_load.ko
sed -i 's/\xBB\xD0\xF8\x4D/\x0E\x1C\x63\x77/' kexec_load.ko
sed -i 's/\xA6\x26\x81\x1A/\xD4\x56\x02\x7E/' kexec_load.ko
sed -i 's/\xA3\xD1\xEC\x96/\xEC\x43\x28\x1A/' kexec_load.ko
sed -i 's/\x8C\xE6\x6A\x5F/\x3D\xDF\x02\xF2/' kexec_load.ko
sed -i 's/\x3E\xF3\xEF\xE9/\x18\x7F\xA6\x8A/' kexec_load.ko
sed -i 's/\x8B\xD2\x92\x10/\xC8\x19\x08\x9C/' kexec_load.ko
sed -i 's/\x1C\xE8\x18\xE1/\x7C\x71\x9E\xEF/' kexec_load.ko
sed -i 's/\xAB\x2C\x2F\x8B/\x8E\xD7\x63\xC0/' kexec_load.ko
sed -i 's/\xF5\x62\xAA\x4B/\x34\x80\x1B\x74/' kexec_load.ko
sed -i 's/\x00\x52\xD6\xD7/\x6F\x80\x91\x20/' kexec_load.ko
sed -i 's/\x4F\x77\x57\x6A/\x0C\x57\xC7\x63/' kexec_load.ko
sed -i 's/\xCA\x2F\x65\x71/\x92\xB8\x7F\x53/' kexec_load.ko
sed -i 's/\x0F\xD0\xA0\x91/\xFA\x80\x15\xB4/' kexec_load.ko
sed -i 's/\x29\xA0\x6D\x48/\x6C\x6B\x96\x54/' kexec_load.ko
sed -i 's/\x6D\x1F\x1F\x37/\xCC\x5E\x79\x8B/' kexec_load.ko
sed -i 's/\xFD\x23\xD0\xFB/\xE3\xE3\x68\x52/' kexec_load.kohexdump kexec_load.ko | grep ff72
0003d50 b0b0 80ac ff72 205e 6f6d 7564 656c 6c5f# dmesg# cat /proc/last_kmsg# cat /dev/kexec_driver
You can send kernel by this communication channel.
Type following commands for help
=> echo help >/dev/kexec_driver
=> dmesg | grep Kexec# echo help >/dev/kexec_driver
# cat /dev/kexec_driver
Last command : 'help'
Please type following command :
=> dmesg|grep Kexec# dmesg|grep Kexec
<4>[15050.521628] Kexec: Starting kexec_module...
<6>[15050.521656] Kexec: kexec_driver_contener allocation
<6>[15050.521673] Kexec: kexec_memory_buffer allocation
<4>[15050.521691] Kexec:----------------------------------------------------
<4>[15050.521710] Kexec: kexec_driver created with major : '100'
<4>[15050.521728] Kexec: Please, prepare by typing the following commands :
<4>[15050.521746] Kexec: => mknod /dev/kexec_driver c 100 0
<4>[15050.521761] Kexec: => cat /dev/kexec_driver
<4>[15050.521775] Kexec:-----------------------------------------------------
<4>[15050.521791] Kexec: For help
<4>[15050.521803] Kexec: => echo help >/dev/kexec_driver
(...)insmod kexec_load.ko
mknod /dev/kexec_driver c 254 0
(...)
crw-rw-rw- root root 254, 0 2013-11-11 15:26 kexec_driverjust for information...
compressed kernel with lzma his bigger than no lzma lol
4,1 Vs 4,15
so, i thave try :
kexec --load zImage.lzma --mem-min=0x0f00000000 --command-line="$(cat /proc/cmdline)"
debug: Focus 1 - argc '5' ; argv 'bea96754' ; kernel_buf 'b6bdf008' ; kernel_size '3f5414' ; info 'bea96528' ; i '1' ; file_type.name 'zImage'
debug: malloc - xmalloc mem_range '4511824'
Could not find a free area of memory of 3fd414 bytes...
lol ... if you could find a way to reduced size ??
